< draft-irtf-icnrg-ccnxmessages-04.txt   draft-irtf-icnrg-ccnxmessages-05.txt >
ICNRG M. Mosko ICNRG M. Mosko
Internet-Draft PARC, Inc. Internet-Draft PARC, Inc.
Intended status: Experimental I. Solis Intended status: Experimental I. Solis
Expires: September 14, 2017 LinkedIn Expires: March 15, 2018 LinkedIn
C. Wood C. Wood
University of California Irvine University of California Irvine
March 13, 2017 September 11, 2017
CCNx Messages in TLV Format CCNx Messages in TLV Format
draft-irtf-icnrg-ccnxmessages-04 draft-irtf-icnrg-ccnxmessages-05
Abstract Abstract
This document specifies version "1" of CCNx message TLV packet This document specifies version "1" of CCNx message TLV packet
format, including the TLV types used by each message element and the format, including the TLV types used by each message element and the
encoding of each value. The semantics of CCNx messages follow the encoding of each value. The semantics of CCNx messages follow the
CCNx Semantics specification. CCNx Semantics specification.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017. This Internet-Draft will expire on March 15, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 39, line 11 skipping to change at page 39, line 11
not store large fields there. Deployments may choose to use their not store large fields there. Deployments may choose to use their
own guidelines for name limitations. There is currently no own guidelines for name limitations. There is currently no
recommended practices for Interest deployments. recommended practices for Interest deployments.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2119>. editor.org/info/rfc2119>.
6.2. Informative References 6.2. Informative References
[CCN] PARC, Inc., "CCNx Open Source", 2007, [CCN] PARC, Inc., "CCNx Open Source", 2007,
<http://www.CCNx.org>. <http://www.CCNx.org>.
[CCNSemantics] [CCNSemantics]
Mosko, M., Solis, I., and C. Wood, "CCNx Semantics Mosko, M., Solis, I., and C. Wood, "CCNx Semantics
(Internet draft)", 2017, <http://tools.ietf.org/html/ (Internet draft)", 2017, <http://tools.ietf.org/html/
draft-mosko-icnrg-ccnxsemantics-04>. draft-mosko-icnrg-ccnxsemantics-04>.
skipping to change at page 39, line 39 skipping to change at page 39, line 39
Domain Parameters", 2010, Domain Parameters", 2010,
<http://www.secg.org/sec2-v2.pdf>. <http://www.secg.org/sec2-v2.pdf>.
[EpriseNumbers] [EpriseNumbers]
IANA, "IANA Private Enterprise Numbers", 2015, IANA, "IANA Private Enterprise Numbers", 2015,
<http://www.iana.org/assignments/enterprise-numbers/ <http://www.iana.org/assignments/enterprise-numbers/
enterprise-numbers>. enterprise-numbers>.
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, Text on Security Considerations", BCP 72, RFC 3552,
DOI 10.17487/RFC3552, July 2003, DOI 10.17487/RFC3552, July 2003, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3552>. editor.org/info/rfc3552>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5226>. editor.org/info/rfc5226>.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,
<http://www.rfc-editor.org/info/rfc5280>. <https://www.rfc-editor.org/info/rfc5280>.
[RFC6920] Farrell, S., Kutscher, D., Dannewitz, C., Ohlman, B., [RFC6920] Farrell, S., Kutscher, D., Dannewitz, C., Ohlman, B.,
Keranen, A., and P. Hallam-Baker, "Naming Things with Keranen, A., and P. Hallam-Baker, "Naming Things with
Hashes", RFC 6920, DOI 10.17487/RFC6920, April 2013, Hashes", RFC 6920, DOI 10.17487/RFC6920, April 2013,
<http://www.rfc-editor.org/info/rfc6920>. <https://www.rfc-editor.org/info/rfc6920>.
Authors' Addresses Authors' Addresses
Marc Mosko Marc Mosko
PARC, Inc. PARC, Inc.
Palo Alto, California 94304 Palo Alto, California 94304
USA USA
Phone: +01 650-812-4405 Phone: +01 650-812-4405
Email: marc.mosko@parc.com Email: marc.mosko@parc.com
 End of changes. 9 change blocks. 
13 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/