idnits 2.17.1 draft-dtnrg-ltp-cbhe-registries-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC6260], [RFC5050], [RFC5326]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 8, 2013) is 3815 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Scott 3 Internet-Draft The MITRE Corporation 4 Intended status: Informational M. Blanchet 5 Expires: April 11, 2014 Viagenie 6 October 8, 2013 8 Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding 9 (CBHE), and Bundle Protocol IANA Registries 10 draft-dtnrg-ltp-cbhe-registries-07 12 Abstract 14 The DTNRG research group has defined the experimental Licklider 15 Transmission Protocol (LTP) [RFC5326] and the Compressed Bundle 16 Header Encoding (CBHE) [RFC6260] mechanism for the InterPlanetary 17 Network (ipn URI scheme). Moreover, RFC5050 [RFC5050] defines values 18 for the Bundle Administrative Record Type. All of these fields are 19 subject to a registry. For the purpose of its research work, the 20 group has created ad-hoc registries. As the specifications are 21 stable and have multiple interoperable implementations, the group 22 would like to hand off the registries to IANA for official 23 management. This document describes the actions needed to be 24 executed by IANA. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on April 11, 2014. 43 Copyright Notice 45 Copyright (c) 2013 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 62 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 63 3.1. Licklider Transmission Protocol . . . . . . . . . . . . . . 3 64 3.1.1. LTP Cancel Segment Reason Codes . . . . . . . . . . . . 4 65 3.1.2. LTP Engine ID . . . . . . . . . . . . . . . . . . . . . 4 66 3.1.3. LTP Client Service ID . . . . . . . . . . . . . . . . . 5 67 3.2. Compressed Bundle Header Encoding . . . . . . . . . . . . . 6 68 3.2.1. CBHE Node Numbers . . . . . . . . . . . . . . . . . . . 6 69 3.2.2. CBHE Service Numbers . . . . . . . . . . . . . . . . . 7 70 3.3. Bundle Administrative Record Types . . . . . . . . . . . . 8 71 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 72 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 73 5.1. Normative References . . . . . . . . . . . . . . . . . . . 9 74 5.2. Informative References . . . . . . . . . . . . . . . . . . 9 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 77 1. Introduction 79 The DTNRG research group has defined the Licklider Transmission 80 Protocol (LTP)[RFC5326]. LTP contains certain fields that are 81 subject to a registry. For the purpose of its research work, the 82 group has created ad-hoc registries. As the specifications are 83 stable and have multiple interoperable implementations, the group 84 would like to hand off the registries to IANA for official 85 management. This document describes the actions needed to be 86 executed by IANA using the Well-Known IANA Policy Definitions defined 87 in Section 4.1 of [RFC5226]. 89 The Compressed Bundle Header Encoding (CBHE) [RFC6260] specification 90 defines the concepts of Node Number and Service Number in the 'ipn' 91 URI scheme. In this document we request formation of an IANA 92 registry for the Node Number field in the 'ipn' scheme. 94 Because of its association with space communication and the 95 Consultative Committee on Space Data Systems [CCSDS], a portion of 96 the CBHE Node Number space and a corresponding portion of the LTP 97 Engine ID space is delegated by this document to the CCSDS Space 98 Assigned Numbers Authority [SANA]. SANA functions similarly to IANA 99 in that it maintains registries of managed values, with a focus on 100 values used by protocols used by CCSDS member agencies. 102 2. Security Considerations 104 This document requests the creation of registries managed by IANA. 105 There are no security issues involved. Refer to the Security 106 Considerations section of [RFC5326] for security issues with the LTP 107 protocol. 109 3. IANA Considerations 111 IANA is requested to create registries as described in this section. 113 3.1. Licklider Transmission Protocol 115 The Licklider Transmission Protocol has fields requiring registries 116 managed by IANA. This document requests the creation of the three 117 registries in this section and that they be associated with the other 118 registries for the Licklider Transmission protocol. 120 3.1.1. LTP Cancel Segment Reason Codes 122 Section 3.2.4 of [RFC5326] defines the reason codes that may be 123 present in Cancel Segments in the LTP protocol. 125 The registration policy for this registry is: Specification Required 127 The initial values (as defined by RFC5326) for the LTP Cancel Segment 128 Reason Codes registry shall be: 130 LTP Cancel Segment Reason Codes Registry 132 +-----------+---------------------------------+---------------+ 133 | Value | Description | Reference | 134 +-----------+---------------------------------+---------------+ 135 | 0 | Client service canceled session | [RFC5326] | 136 | 1 | Unreachable client service | [RFC5326] | 137 | 2 | Retransmission limit exceeded | [RFC5326] | 138 | 3 | Miscolored data received | [RFC5326] | 139 | 4 | System error caused termination | [RFC5326] | 140 | 5 | Retransmission limit exceeded | [RFC5326] | 141 | 0x06-0xFF | Unassigned | This document | 142 +-----------+---------------------------------+---------------+ 144 3.1.2. LTP Engine ID 146 The Licklider Transmission Protocol has an LTP Engine ID field 147 (section 2 of [RFC5326]). An IANA registry shall be set up as 148 follows. 150 The registration policy for this registry is: 152 1 -- (2**14)-1 Expert review required. 154 (2**14) -- (2**21)-1 Allocated to the Space Assigned Numbers 155 Authority ([SANA]) for use by Consultative Committee for Space 156 Data Systems (CCSDS) missions. 158 (2**21) -- (2**28)-1 Private or experimental use. 160 (2**28) -- (2**42)-1 First-come, First-Served basis for requests for 161 less than or equal to 2**14 values to a single entity or 162 organization. Expert review for requests of more than 2**14 163 values to a single entity or organization. 165 The LTP Engine ID is expressed as a Self-Delimiting Numeric Value 166 (SDNV) in the LTP protocol and no maximum is specified in the 167 protocol definition. SDNVs are described in Section 4.1 of the 168 Bundle Protocol in [RFC5050] and are also described in the stand- 169 alone document [RFC6256]. The initial values for the LTP Engine 170 Numbers registry shall be: 172 LTP Engine Numbers Registry 174 +--------------------+---------------------------+---------------+ 175 | Value | Description | Reference | 176 +--------------------+---------------------------+---------------+ 177 | 0 | Reserved | This document | 178 | 1--(2**14)-1 | Unassigned | This document | 179 | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document | 180 | (2**21)--(2**28)-1 | Private/Experimental Use | This document | 181 | (2**28)--(2**42)-1 | Unassigned | This document | 182 | >=(2**42) | Reserved | This document | 183 +--------------------+---------------------------+---------------+ 185 3.1.3. LTP Client Service ID 187 The Licklider Transmission Protocol has a client service ID number 188 field (section 3.2.1 of [RFC5326]). An IANA registry shall be set up 189 as follows. 191 The registration policy for this registry is: 193 4 -- (2**14)-1 Allocated to the Space Assigned Numbers Authority 194 ([SANA]) for use by Consultative Committee for Space Data Systems 195 (CCSDS) missions. 197 2**14 -- 32,767 Private or experimental use. 199 >= 32,768 Specification required. 201 The LTP Client Service ID is expressed as a Self-Delimiting Numeric 202 Value (SDNV) in the LTP protocol and no maximum value is specified in 203 the protocol definition. The initial values for the LTP Client 204 Service Identifiers registry shall be: 206 LTP Client Service Identifiers Registry 208 +-----------------+------------------------------+---------------+ 209 | Value | Description | Reference | 210 +-----------------+------------------------------+---------------+ 211 | 0 | Reserved | [RFC5326] | 212 | 1 | Bundle Protocol | This document | 213 | 2 | LTP Service Data Aggregation | This document | 214 | 3 | CCSDS File Delivery Service | This document | 215 | 4--(2**14)-1 | Allocated to CCSDS (SANA) | This document | 216 | (2**14)--32,767 | Private / Experimental Use | This document | 217 | >=32,768 | Unassigned | This document | 218 +-----------------+------------------------------+---------------+ 220 3.2. Compressed Bundle Header Encoding 222 The CBHE specification [RFC6260] defines concepts of 'Node Number' 223 and 'Service Number' that require registries managed by IANA. 225 3.2.1. CBHE Node Numbers 227 The CBHE specification defines a Node Number (node-nbr) field 228 (section 2.1 of [RFC6260]). An IANA registry shall be set up as 229 follows. 231 The registration policy for this registry is: 233 1 -- (2**14)-1 Expert review required. 235 (2**14) -- (2**21)-1 Allocated to the Space Assigned Numbers 236 Authority ([SANA]) for use by Consultative Committee for Space 237 Data Systems (CCSDS) missions. 239 (2**21) -- (2**28)-1 Private or experimental use. 241 (2**28) -- (2**42)-1 First-come, First-Served basis for requests for 242 less than or equal to 2**14 values to a single entity or 243 organization. Expert review required for requests of more than 244 2**14 values to a single entity or organization. 246 >= (2**42) Reserved 248 The CBHE Node Number is expressed as a Self-Delimiting Numeric Value 249 (SDNV) in the CBHE specification. Allowable values for the Node 250 Number range from 1 -- (2**64)-1. The initial values for the CBHE 251 Node Number registry shall be: 253 CBHE Node Number Registry 255 +--------------------+---------------------------+---------------+ 256 | Value | Description | Reference | 257 +--------------------+---------------------------+---------------+ 258 | 0 | Reserved | This document | 259 | 1--(2**14)-1 | Unassigned | This document | 260 | (2**14)--(2**21)-1 | Allocated to CCSDS (SANA) | This document | 261 | (2**21)--(2**28)-1 | Private/Experimental Use | This document | 262 | (2**28)--(2**42)-1 | Unassigned | This document | 263 | >=(2**42) | Reserved | This document | 264 +--------------------+---------------------------+---------------+ 266 3.2.2. CBHE Service Numbers 268 The Compressed Bundle Header Encoding specification defines a Service 269 Number (service-nbr) field (section 2.1 of [RFC6260]). An IANA 270 registry shall be set up as follows. 272 The registration policy for this registry is: 274 0-63 RFC Required 276 64-1023 Allocated to the Space Assigned Numbers Authority ([SANA]) 277 for use by Consultative Committee for Space Data Systems (CCSDS) 278 missions. 280 1024 - 2**16-1 Specification Required 282 >= 2**16 Private / Experimental Use 284 The CBHE Service Number is expressed as a Self-Delimiting Numeric 285 Value (SDNV) in the CBHE specification. Allowable values for the 286 Service Number range from 1 -- (2**64)-1. The initial values for the 287 CBHE Service Number registry shall be: 289 CBHE Service Number Registry 291 +--------------------+--------------------------------+-------------+ 292 | Value | Description | Reference | 293 +--------------------+--------------------------------+-------------+ 294 | 0 | Bundle Protocol Administrative | [RFC6260] | 295 | | Record | | 296 | 1 | CCSDS File Delivery Service | [CFDP] | 297 | 2 | Reserved | This | 298 | | | document | 299 | 3-63 | Unassigned | This | 300 | | | document | 301 | 64-1023 | Allocated to CCSDS (SANA) | This | 302 | | | document | 303 | 1024 - 2**16-1 | Unassigned | This | 304 | | | document | 305 | >=2**16 | Private/Experimental Use | This | 306 | | | document | 307 +--------------------+--------------------------------+-------------+ 309 3.3. Bundle Administrative Record Types 311 Section 6.1 of the Bundle Protocol specification [RFC5050] specifies 312 a 4-bit Administrative Record type code. An IANA registry shall be 313 set up as follows to manage these record types. This registry, 314 titled 'Bundle Administrative Record Type,' shall be added to the 315 list of registries associated with the Bundle Protcol. 317 The registration policy for this registry is: Specification required 319 The initial values for the Bundle Administrative Record Type registry 320 shall be: 322 Bundle Protocol Administrative Record Type Registry 324 +-------+----------------------+---------------+ 325 | Value | Description | Reference | 326 +-------+----------------------+---------------+ 327 | 0 | Reserved | This document | 328 | 1 | Bundle status report | [RFC5050] | 329 | 2 | Custody signal | [RFC5050] | 330 | 3-15 | Unassigned | This document | 331 +-------+----------------------+---------------+ 333 4. Acknowledgements 335 The editors would like to thank the following people, in no specific 336 order: Scott Burleigh, Stephen Farrell, John Buford. 338 5. References 340 5.1. Normative References 342 [CFDP] Consultative Committee for Space Data Systems 343 (http://www.ccsds.org), "CCSDS File Delivery Protocol 344 Version 4 (CCSDS 727.0-B-4)", January 2007. 346 [RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol 347 Specification", RFC 5050, November 2007. 349 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 350 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 351 May 2008. 353 [RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider 354 Transmission Protocol - Specification", RFC 5326, 355 September 2008. 357 [RFC6256] Eddy, W. and E. Davies, "Using Self-Delimiting Numeric 358 Values in Protocols", RFC 6256, May 2011. 360 [RFC6260] Burleigh, S., "Compressed Bundle Header Encoding (CBHE)", 361 RFC 6260, May 2011. 363 5.2. Informative References 365 [CCSDS] "The Consultative Committee for Space Data Systems at 366 http://www.ccsds.org". 368 [SANA] "The CCSDS SANA Registry page at http://sanaregistry.org". 370 Authors' Addresses 372 Keith Scott 373 The MITRE Corporation 374 7515 Colshire Drive 375 McLean, VA, California 22102 376 USA 378 Phone: +1-703-983-6547 379 Fax: +1-703-983-7142 380 Email: kscott@mitre.org 382 Marc Blanchet 383 Viagenie 384 246 Aberdeen 385 Quebec, Quebec G1R 2E1 386 Canada 388 Phone: +1-418-656-9254 389 Email: marc.blanchet@viagenie.ca