INTERNET-DRAFT M. Yevstifeyev Intended Status: Informational December 28, 2010 Updates: 998 (if approved) Expires: July 1, 2011 Network Block Transfer Protocol (NETBLT) IANA Considerations Abstract This document defined IANA considerations for Network Block Transfer Protocol (NETBLT). 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 998. 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. 'NETBLT 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. 'CONTROL Messages Types' Sub-Registry . . . . . . . . . . n 2.5.1. The Name of the Sub-Registry . . . . . . . . . . . . . 5 2.5.2. The Format of the Sub-Registry . . . . . . . . . . . . 5 2.5.3. Registration Procedures . . . . . . . . . . . . . . . 5 2.5.4. The Initial Contents of the Sub-Registry . . . . . . . 5 3. 'NETBLT Port Numbers' Registry . . . . . . . . . . . . . . . . . 6 3.1. The Name of the Registry . . . . . . . . . . . . . . . . . 6 3.2. The Format of the Registry . . . . . . . . . . . . . . . . 6 3.3. Registration Procedures . . . . . . . . . . . . . . . . . . 6 3.4. The Initial Contents of the Registry . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 6. Normative References . . . . . . . . . . . . . . . . . . . . . 7 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Yevstifeyev Expires July 1, 2011 [Page 2] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 1. Introduction Network Block Transfer Protocol (NETBLT) was originally defined in RFC 998 [RFC998]. 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. 'NETBLT Packet Types' Registry 2.1. The Name of the Registry The name of created registry is 'NETBLT Packet Types'. 2.2. The Format of the Registry The 'NETBLT 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 NETBLT 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 'NETBLT 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 'NETBLT Packet Types' registry. +--------+-------------------------------------+-----------+ | Number | Description | Reference | +--------+-------------------------------------+-----------+ |0 | OPEN | RFC 998 | |1 | RESPONSE | RFC 998 | |2 | KEEPALIVE | RFC 998 | |3 | QUIT | RFC 998 | |4 | QUITACK | RFC 998 | |5 | ABORT | RFC 998 | |6 | DATA | RFC 998 | |7 | LDATA | RFC 998 | |8 | NULL-ACK | RFC 998 | |9 | CONTROL | RFC 998 | |10 | REFUSED | RFC 998 | |11 | DONE | RFC 998 | |12-253 | Unassigned | RFC xxxx | |254 | Used for Experimentation | RFC xxxx | |255 | Reserved | RFC xxxx | +--------+-------------------------------------+-----------+ [RFC Editor: Replace xxxx with assigned RFC number] Yevstifeyev Expires July 1, 2011 [Page 4] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 2.5. 'CONTROL Messages Types' Sub-Registry One sub-registry is currently created in 'NETBLT Packet Types' registry - 'CONTROL Messages Types'. It is described below. 2.5.1. The Name of the Sub-Registry The name of created sub-registry is 'CONTROL Messages Types'. 2.5.2. The Format of the Sub-Registry The 'CONTROL Messages Types' sub-registry consists of 3 values: CONTROL Message Type Number, Description and Reference. They are described below: CONTROL Message Type Number - an integer; refers to the value used in NETBLT CONTROL message. Values form 0 to 255 are assigned. Description - a brief decryption of packet type. Reference - the reference document, that defines the packet type. 2.5.3. Registration Procedures New assignments to 'CONTROL Messages Types' sub-registry are to be made following the 'IETF Consensus' policies [RFC5226]. 2.5.4. The Initial Contents of the Sub-Registry This section contains the initial contents of the 'CONTROL Messages Types' sub-registry. +--------+-------------------------------------+-----------+ | Number | Description | Reference | +--------+-------------------------------------+-----------+ |0 | GO | RFC 998 | |1 | OK | RFC 998 | |2 | RESEND | RFC 998 | |3-253 | Unassigned | RFC xxxx | |254 | Used for Experimentation | RFC xxxx | |255 | Reserved | RFC xxxx | +--------+-------------------------------------+-----------+ [RFC Editor: Replace xxxx with assigned RFC number] Yevstifeyev Expires July 1, 2011 [Page 5] INTERNET DRAFT IRTP IANA Considerations December 28, 2010 3. 'NETBLT Port Numbers' Registry 3.1. The Name of the Registry The name of created registry is 'NETBLT Port Numbers'. 3.2. The Format of the Registry The 'NETBLT 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 NETBLT header. Values form 0 to 65535 are assigned. Ports from 0 to 1023 are well-known. Ports from 1024 to 65535 are user-registered. 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 'NETBLT Port Numbers' registry for well-known ports are to be made following the 'IESG Approval' policies; for user-registered ones - via Expert Review. [RFC5226] 3.4. The Initial Contents of the Registry This section contains the initial contents of the 'NETBLT Port Numbers' registry. +--------+-------------------------------------+-----------------+ | Number | Description | Reference or | | | | Registrant Info | +--------+-------------------------------------+-----------------+ |0-1020 | Unassigned | RFC xxxx | |1021 | Used for Experimentation | RFC xxxx | |1022 | Used for Experimentation | RFC xxxx | |1023 | Reserved | RFC xxxx | |1024- | Unassigned | RFC xxxx | |65534 | | | |65535 | Reserved | RFC xxxx | +--------+-------------------------------------+-----------------+ [RFC Editor: Replace xxxx with assigned RFC number] Yevstifeyev Expires July 1, 2011 [Page 6] 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 NETBLT not discussed in RFC 998 [RFC998]. 5. IANA Considerations IANA has assigned the IP Protocol Number 30 to NETBLT. IANA has created the 'NETBLT Packet Types' and 'NETBLT Port Numbers' registries following Section 2 and Section 3 of this document. 6. Normative References [RFC998] Clark, D., Lambert, M., and L. Zhang, "NETBLT: A bulk data transfer protocol", RFC 998, March 1987. [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 7]