CCNx 1.0 — selected stack
IPv4 / UDP / CCNx 1.0 semantics RFC 8569 and TLV encoding RFC 8609. Independent deployment uses private IPv4, numeric adjacent forwarders, locally configured name-prefix FIB entries and known content names. Producer Content Objects use ECDSA-SHA256 signatures with locally generated keys explicitly trusted by consumers; no externally mandated name registry or certificate authority selected. Interests use CRC32C integrity checks, not authenticated consumer identities. In-network matching, pending Interests and caching follow CCNx semantics. No TLS, encrypted-session extension, application authentication wrapper or NDN/NLSR extension is added. Dynamic routing and automatic global name discovery are not silently supplied by static FIB configuration. Documentary composition; executable integration remains unqualified. G01 global deployment: conventional BGP-routed IPv4 Internet underlay, matching IP, PRP-over-IP and Multipath QUIC. Independent private deployment remains the separate S03/S04 capability; adjacent-only private IP meshes are not this global case. F37/F38: optional native RFC 8569 Interest Return behavior explicitly selected: locally congested forwarders discard Interests and report Congestion; preceding forwarders handle returns under section 10.3, including alternative next-hop selection when available. Per-forwarder name/interface ACLs and Prohibited handling selected under 10.3.6. Documentary capability, not measured congestion performance or executable integration. F39 bounded request/reply witness: one producer process owns the chosen globally scoped name prefix; use previously unrequested names with no matching cached response and configure the prefix toward that producer. The same name-based exchange reaches a local producer attachment or a remote producer through the selected network. No RPC framework, process migration, exactly-once execution, arbitrary duplex stream or new authentication layer is added.
Official project website · Logo credits · Methodology and limits