Content-Centric Networking (CCNx) Semantics
RFC 8569

Document Type RFC - Experimental (July 2019; No errata)
Last updated 2019-07-09
Stream IRTF
Formats plain text pdf htmlized bibtex
IETF conflict review conflict-review-irtf-icnrg-ccnxsemantics
Stream IRTF state Published RFC
Consensus Boilerplate Yes
Document shepherd David Oran
Shepherd write-up Show (last changed 2019-06-25)
IESG IESG state RFC 8569 (Experimental)
Telechat date
Responsible AD (None)
Send notices to David Oran <daveoran@orandom.net>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
Internet Research Task Force (IRTF)                             M. Mosko
Request for Comments: 8569                                    PARC, Inc.
Category: Experimental                                          I. Solis
ISSN: 2070-1721                                                 LinkedIn
                                                                 C. Wood
                                         University of California Irvine
                                                               July 2019

              Content-Centric Networking (CCNx) Semantics

Abstract

   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.

Mosko, et al.                 Experimental                      [Page 1]
RFC 8569                     CCNx Semantics                    July 2019

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Research Task
   Force (IRTF).  The IRTF publishes the results of Internet-related
   research and development activities.  These results might not be
   suitable for deployment.  This RFC represents the consensus of the
   Information-Centric Networking Research Group of the Internet
   Research Task Force (IRTF).  Documents approved for publication by
   the IRSG are not candidates for any level of Internet Standard; see
   Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8569.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Mosko, et al.                 Experimental                      [Page 2]
RFC 8569                     CCNx Semantics                    July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     1.2.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Protocol Overview . . . . . . . . . . . . . . . . . . . .   6
   2.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     2.1.  Message Grammar . . . . . . . . . . . . . . . . . . . . .  10
     2.2.  Consumer Behavior . . . . . . . . . . . . . . . . . . . .  14
     2.3.  Publisher Behavior  . . . . . . . . . . . . . . . . . . .  15
     2.4.  Forwarder Behavior  . . . . . . . . . . . . . . . . . . .  16
       2.4.1.  Interest HopLimit . . . . . . . . . . . . . . . . . .  16
       2.4.2.  Interest Aggregation  . . . . . . . . . . . . . . . .  17
       2.4.3.  Content Store Behavior  . . . . . . . . . . . . . . .  19
       2.4.4.  Interest Pipeline . . . . . . . . . . . . . . . . . .  19
       2.4.5.  Content Object Pipeline . . . . . . . . . . . . . . .  20
   3.  Names . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21
     3.1.  Name Examples . . . . . . . . . . . . . . . . . . . . . .  23
     3.2.  Interest Payload ID . . . . . . . . . . . . . . . . . . .  23
   4.  Cache Control . . . . . . . . . . . . . . . . . . . . . . . .  23
   5.  Content Object Hash . . . . . . . . . . . . . . . . . . . . .  24
   6.  Link  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24
   7.  Hashes  . . . . . . . . . . . . . . . . . . . . . . . . . . .  25
   8.  Validation  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     8.1.  Validation Algorithm  . . . . . . . . . . . . . . . . . .  25
     8.2.  Message Integrity Codes . . . . . . . . . . . . . . . . .  26
Show full document text