Subject: [icnrg] Updated CCNx specifications

From: <[email-masked]>
Date: Mon, 11 Jan 2016 17:27:24 +0000

All,

We have run behind the clock and not updated the two specification documents before they expired on the IETF tracker.  Therefore, we are updating the tracker with these two new versions with the understanding that we will review each update with the research group and make a new update to the tracker with that input.

We here summarize all the updates except for spelling, grammatical, and references fixes.  Overall, the three main changes are (1) codify Nameless Objects, (2) hash agility, and (3) carrying ContentObjectHash in a header fields (e.g. only calculated at AS border systems).

=============================
draft-irtf-icnrg-ccnxsemantics-01

Full diff available at: https://datatracker.ietf.org/doc/draft-irtf-icnrg-ccnxsemantics/history/

1) Added Sec 3.1 on examples of names and to clarify the difference between lci:/ and lci:/NAME=,
where the first is an empty name and the second is a name with an empty first segment.

2) End of Sec 4, added note that we do not prevent loops, only eventually terminate them.

3) Modified Sec 5 to make the name optional and if not present require matching on hash.

4) Added Sec 7 on hash agility.

5) Added Sec 9 on "Interest to Content Object matching” which unambiguously spells out the exact rules of matching a ContentObject to an Interest.

6) Add two new InterestReturn types: Unsupported Content Object Hash Algorithm (due to hash agility) and Malformed Interest (a parsing error).

=============================
draft-irtf-icnrg-ccnxmessages-01

Full diff available at: https://datatracker.ietf.org/doc/draft-irtf-icnrg-ccnxmessages/history/

7) In Sec 3, made more obvious the reserved values and also included the T_ORG reserved value here.

8) Added the two new Interest return values

9) Sec 3.3 moved to “global formats” to the top of the TLV section before the per-hop headers.

10) Added the Hash Format as a “global format” for hash agility.

11) Added the Message Hash per-hop header for carrying the ContentObjectHash as an explicit field.  Does not specify what a trust domain is or how to make one or how to trust this.  (another possible header is something to sign headers)

12) Interest Payload ID (IPID) no longer uses RFC 6920, but uses the new Hash Formats.

13) Updated description of KeyIdRestriction and KeyId to use Hash Formats.  Updated description of ContentObjectHashRestriction to use Hash Formats (in both an Interest and a Link).

Marc Mosko