Internet DRAFT - draft-mosko-icnrg-ccnxserialversion

draft-mosko-icnrg-ccnxserialversion






ICNRG                                                           M. Mosko
Internet-Draft                                                      PARC
Intended status: Experimental                            January 9, 2015
Expires: July 13, 2015


                    CCNx Publisher Serial Versioning
                 draft-mosko-icnrg-ccnxserialversion-00

Abstract

   This document specifies using a serial number to indicate versions in
   name name segments.  A serial number is an increasing unsigned
   integer with an increment of 1.  Therefore, given one name with a
   serial version number, one may compute the next version number.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 13, 2015.

Copyright Notice

   Copyright (c) 2015 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
   (http://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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.




Mosko                     Expires July 13, 2015                 [Page 1]

Internet-Draft                  CCNx TLV                    January 2015


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 3
   2.  Protocol Description  . . . . . . . . . . . . . . . . . . . . . 4
   3.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 9







































Mosko                     Expires July 13, 2015                 [Page 2]

Internet-Draft                  CCNx TLV                    January 2015


1.  Introduction

   This document specifies using a serial number in a CCNx name as a
   version identifier.  It specifies a new name segment label and a TLV
   encoding.  The use of a serial number in a name to denote a version
   is limited to coordination among publishers if an attempt is made to
   use a serial number as a distributed ordering.

   Packets are represented as 32-bit wide words using ASCII art.
   Because of the TLV encoding and optional fields or sizes, there is no
   concise way to represent all possibilities.  We use the convention
   that ASCII art fields enclosed by vertical bars "|" represent exact
   bit widths.  Fields with a forward slash "/" are variable bitwidths,
   which we typically pad out to word alignment for picture readability.

   TODO -- we have not adopted the Requirements Language yet.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].





























Mosko                     Expires July 13, 2015                 [Page 3]

Internet-Draft                  CCNx TLV                    January 2015


2.  Protocol Description

   A serial number in a CCNx name name segment indicates an ordering on
   names based on the unsigned integer.  The serial number is encoded in
   network byte order using the minimum number of bytes.  The value of
   "0" is represented as the single byte %x00.

   The serial number must be incremented by 1 for consecutive versions
   of the prior name name segments.  There is no maximum serial number,
   it is limited only by the number of bytes put in to the name
   component.

   A "GONE" PayloadType means that this version is a terminal version.
   All prior versions should be interpreted as deleted.  A user,
   however, may publish more "DATA" after the terminal version, if he
   decides to un-delete it.

          +----------+-----------------------------------------+
          |   Type   |                   Name                  |
          +----------+-----------------------------------------+
          | 'Serial' | Serial number, displayed as an Integer. |
          +----------+-----------------------------------------+

                Table 1: Labeled Content Information Types

   +--------+----------+--------------+--------------------------------+
   |  Type  |  Symbol  |     Name     | Description                    |
   +--------+----------+--------------+--------------------------------+
   | %x0013 | T_SERIAL |    Serial    | Serial Number, incrementing by |
   |        |          |    Number    | +1.                            |
   +--------+----------+--------------+--------------------------------+

                         Table 2: CCNx Name Types


















Mosko                     Expires July 13, 2015                 [Page 4]

Internet-Draft                  CCNx TLV                    January 2015


3.  Acknowledgements


















































Mosko                     Expires July 13, 2015                 [Page 5]

Internet-Draft                  CCNx TLV                    January 2015


4.  IANA Considerations

   This memo includes no request to IANA.

   All drafts are required to have an IANA considerations section (see
   Guidelines for Writing an IANA Considerations Section in RFCs
   [RFC5226] for a guide).  If the draft does not require IANA to do
   anything, the section contains an explicit statement that this is the
   case (as above).  If there are no requirements for IANA, the section
   will be removed during conversion into an RFC by the RFC Editor.









































Mosko                     Expires July 13, 2015                 [Page 6]

Internet-Draft                  CCNx TLV                    January 2015


5.  Security Considerations

   All drafts are required to have a security considerations section.
   See RFC 3552 [RFC3552] for a guide.















































Mosko                     Expires July 13, 2015                 [Page 7]

Internet-Draft                  CCNx TLV                    January 2015


6.  References

6.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

6.2.  Informative References

   [CCNx]     PARC, Inc., "CCNx Open Source", 2007,
              <http://www.ccnx.org>.

   [RFC3552]  Rescorla, E. and B. Korver, "Guidelines for Writing RFC
              Text on Security Considerations", BCP 72, RFC 3552,
              July 2003.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.
































Mosko                     Expires July 13, 2015                 [Page 8]

Internet-Draft                  CCNx TLV                    January 2015


Author's Address

   Marc Mosko
   PARC
   Palo Alto, California  94304
   USA

   Phone: +01 650-812-4405
   Email: marc.mosko@parc.com










































Mosko                     Expires July 13, 2015                 [Page 9]