INTERNET-DRAFT M. Yevstifeyev Intended Status: Informational December 28, 2010 Updates: 938 (if approved) Expires: July 1, 2011 Internet Reliable Transaction Protocol (IRTP) IANA Considerations Abstract This document defined IANA considerations for Internet Reliable Transaction Protocol (IRTP). This protocol uses several values that are to be assigned by IANA, but no appropriate registries have been created so far. This document serves as a foundation for such registries. It updates RFC 938. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2010 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 Yevstifeyev Expires July 1, 2011 [Page 1] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. 'IRTP Packet Types' Registry . . . . . . . . . . . . . . . . . 4 2.1. The Name of the Registry . . . . . . . . . . . . . . . . . 4 2.2. The Format of the Registry . . . . . . . . . . . . . . . . 4 2.3. Registration Procedures . . . . . . . . . . . . . . . . . . 4 2.4. The Initial Contents of the Registry . . . . . . . . . . . 4 2.5. Sub-Registries . . . . . . . . . . . . . . . . . . . . . . 4 3. 'IRTP Port Numbers' Registry . . . . . . . . . . . . . . . . . . 5 3.1. The Name of the Registry . . . . . . . . . . . . . . . . . 5 3.2. The Format of the Registry . . . . . . . . . . . . . . . . 5 3.3. Registration Procedures . . . . . . . . . . . . . . . . . . 5 3.4. The Initial Contents of the Registry . . . . . . . . . . . 5 3.5. Sub-Registries . . . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Yevstifeyev Expires July 1, 2011 [Page 2] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 1. Introduction Internet Reliable Transaction Protocol (IRTP) was originally defined in RFC 938 [RFC938]. This protocol uses several values that are to be assigned by IANA (such as port numbers or packet types), but no appropriate registries have been created so far. This document serves as a foundation for such registries. Yevstifeyev Expires July 1, 2011 [Page 3] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 2. 'IRTP Packet Types' Registry 2.1. The Name of the Registry The name of created registry is 'IRTP Packet Types'. 2.2. The Format of the Registry The 'IRTP Packet Types' registry consists of 3 values: Packet Type Number, Description and Reference. They are described below: Packet Type Number - an integer; refers to the value used in IRTP header. Values form 0 to 255 are assigned. Description - a brief decryption of packet type. Reference - the reference document, that defines the packet type. 2.3. Registration Procedures New assignments to 'IRTP Packet Types' registry are to be made following the 'IETF Consensus' policies [RFC5226]. 2.4. The Initial Contents of the Registry This section contains the initial contents of the 'IRTP Packet Types' registry. +--------+-------------------------------------+-----------+ | Number | Description | Reference | +--------+-------------------------------------+-----------+ |0 | SYNCH | RFC 938 | |1 | SYNCH ACK | RFC 938 | |2 | DATA | RFC 938 | |3 | DATA ACK | RFC 938 | |4 | PORT NAK | RFC 938 | |5-253 | Unassigned | RFC xxxx | |254 | Used for Experimentation | RFC xxxx | |255 | Reserved | RFC xxxx | +--------+-------------------------------------+-----------+ [RFC Editor: Replace xxxx with assigned RFC number] 2.5. Sub-Registries No sub-registries are currently defined in 'IRTP Packet Types' registry. Yevstifeyev Expires July 1, 2011 [Page 4] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 3. 'IRTP Port Numbers' Registry 3.1. The Name of the Registry The name of created registry is 'IRTP Port Numbers'. 3.2. The Format of the Registry The 'IRTP Port Numbers' registry consists of 3 values: Port Number, Description and Reference. They are described below: Port Number - an integer; refers to the value used in IRTP header. Values form 0 to 255 are assigned. Description - a brief decryption of port usage. Reference or Registrant Information - the reference document, that defines the port usage or information about the registrant of the port number. 3.3. Registration Procedures New assignments to 'IRTP Port Numbers' registry are to be made following the 'IESG Approval' policies [RFC5226]. 3.4. The Initial Contents of the Registry This section contains the initial contents of the 'IRTP Port Numbers' registry. +--------+-------------------------------------+-----------------+ | Number | Description | Reference or | | | | Registrant Info | +--------+-------------------------------------+-----------------+ |0-253 | Unassigned | RFC xxxx | |254 | Used for Experimentation | RFC xxxx | |255 | Reserved | RFC xxxx | +--------+-------------------------------------+-----------------+ [RFC Editor: Replace xxxx with assigned RFC number] 3.5. Sub-Registries No sub-registries are currently defined in 'IRTP Port Numbers' registry. Yevstifeyev Expires July 1, 2011 [Page 5] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 4. Security Considerations The creation of these registries is not believed to introduce any new security issues to IRTP not discussed in RFC 938 [RFC938]. 5. IANA Considerations IANA has assigned the IP Protocol Number 23 to IRTP. IANA has created the 'IRTP Packet Types' and 'IRTP Port Numbers' registries following Section 2 and Section 3 of this document. 6. Normative References [RFC938] Miller, T., "Internet Reliable Transaction Protocol functional and interface specification", RFC 938, February 1985. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Author's Addresses Mykyta Yevstifeyev Kotovsk, Ukraine EMail: evnikita2@gmail.com Yevstifeyev Expires July 1, 2011 [Page 6]