Content-Centric Networking (CCNx) Semantics
RFC 8569

Revision differences

Document history

Date By Action
2026-05-20
 (System) Changed metadata: changed keywords to '['Content Centric Networking']' from '[]'
2026-05-20
 (System) Metadata update from RFC Editor
2026-05-20
 (System) Changed author "C. Wood": changed name from "Christopher Wood" to "C. Wood", cleared country (was "USA"), changed order from "2" to "3"
2026-05-20
 (System) Changed author "I. Solis": changed name from "Ignacio Solis" to "I. Solis", cleared country (was "USA"), changed order from "1" to "2"
2026-05-20
 (System) Changed author "M. Mosko": changed name from "Marc Mosko" to "M. Mosko", cleared country (was "USA"), changed order from "0" to "1"
2026-05-20
 (System) Metadata update from RFC Editor
2019-07-11
 Jenny Bui Posted related IPR disclosure: Cisco's Statement about IPR related to RFC 8569 and RFC 8609
2019-07-09
 (System)
Received changes through RFC Editor sync (created alias RFC 8569, changed title to 'Content-Centric Networking (CCNx) Semantics', changed abstract to 'This document describes the …
Received changes through RFC Editor sync (created alias RFC 8569, changed title to 'Content-Centric Networking (CCNx) Semantics', changed abstract to 'This document describes the core concepts of the Content-Centric Networking (CCNx) architecture and presents a network protocol based on two messages: Interests and Content Objects. It specifies the set of mandatory and optional fields within those messages and describes their behavior and interpretation. This architecture and protocol specification is independent of a specific wire encoding.

The protocol also uses a control message called an Interest Return, whereby one system can return an Interest message to the previous hop due to an error condition. This indicates to the previous hop that the current system will not respond to the Interest.

This document is a product of the Information-Centric Networking Research Group (ICNRG). The document received wide review among ICNRG participants. Two full implementations are in active use and have informed the technical maturity of the protocol specification.', changed pages to 40, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2019-07-09, changed IRTF state to Published RFC)
2019-07-09
 (System) RFC published