Mobile Ad hoc Networks I. Chakeres Internet-Draft Motorola Intended status: Standards Track November 18, 2007 Expires: May 21, 2008 IANA Allocations for MANET Protocols draft-ietf-manet-iana-07.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on May 21, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document enumerates several common IANA allocations for use by MANET protocols. The following well-known numbers are required: a UDP port number, an IP protocol number, and a link-local multicast group address. Chakeres Expires May 21, 2008 [Page 1] Internet-Draft MANET-IANA November 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . . 3 3. UDP Port Number . . . . . . . . . . . . . . . . . . . . . . . . 3 4. IP Protocol Number . . . . . . . . . . . . . . . . . . . . . . 3 5. Link-local Multicast Group for MANET Routers . . . . . . . . . 3 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Chakeres Expires May 21, 2008 [Page 2] Internet-Draft MANET-IANA November 2007 1. Introduction This document enumerates several common IANA allocations for use by one or more protocols that conform to [I-D.ietf-manet-packetbb]. The following well-known numbers are required: a UDP port number, an IP protocol number, and a link-local multicast group address. All interoperable protocols running on these well-known IANA allocations MUST conform to [I-D.ietf-manet-packetbb]. [I-D.ietf-manet-packetbb] provides a common format that enables one or more protocols to share the IANA allocations defined in this document unambiguously. 2. Conventions Used in This Document 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]. 3. UDP Port Number MANET routers require a well-known UDP port number [IANAPort] to send and receive MANET routing protocol packets. The title of this UDP port is "manet". The value of this UDP port is TBD1. 4. IP Protocol Number MANET routers require a well-known IP protocol number [IANAProtocol] to send and receive MANET routing protocol packets. The title of this IP protocol number is "manet". The value of this IP protocol number is TBD2. 5. Link-local Multicast Group for MANET Routers MANET routers require a well-known link-local multicast address [RFC4291] to send and receive MANET routing protocol packets. The name of the multicast address to reach link-local (LL) MANET routers is "LL-MANET-Routers". For IPv4, a well-known, link-local scope multicast address is required. The address for LL-MANET-Routers is 224.0.0.TBD3 to appear in the [IANAv4Multicast] registry. For IPv6, a well-known, link-local scope multicast address is required. The address for LL-MANET-Routers is FF02:0:0:0:0:0:0:TBD4 to appear in the [IANAv6Multicast] registry. Chakeres Expires May 21, 2008 [Page 3] Internet-Draft MANET-IANA November 2007 6. IANA Considerations This document enumerates several common IANA allocations for use by one or more protocols that conform to [I-D.ietf-manet-packetbb]. Specifically, the following well-known numbers have been assigned: a UDP port (Section 3), an IP protocol number (Section 4), and a link- local multicast group address (Section 5). Action 1: Upon approval of this document, the IANA will make the following assignments in the "PORT NUMBERS" registry located at http://www.iana.org/assignments/port-numbers sub-registry "WELL KNOWN PORT NUMBERS" Keyword Decimal Description References ------- ------- ----------- ---------- manet TBD1/udp MANET Protocols [ietf-manet-iana] Action 2: Upon approval of this document, the IANA will make the following assignments in the "PROTOCOL NUMBERS" registry located at http://www.iana.org/assignments/protocol-numbers sub-registry "WELL KNOWN PORT NUMBERS" Keyword Decimal Description References ------- ------- ----------- ---------- manet TBD2 MANET Protocols [ietf-manet-iana] Action 3: Upon approval of this document, the IANA will make the following assignments in the "Internet Multicast Addresses" registry located at http://www.iana.org/assignments/multicast-addresses sub-registry 224.0.0.0 - 224.0.0.255 (224.0.0/24) Local Network Control Block Date registered" 224.0.0.TBD3 LL-MANET-Routers [ietf-manet-iana] Chakeres Expires May 21, 2008 [Page 4] Internet-Draft MANET-IANA November 2007 Action 4: Upon approval of this document, the IANA will make the following assignments in the "INTERNET PROTOCOL VERSION 6 MULTICAST ADDRESSES" registry located at http://www.iana.org/assignments/ipv6-multicast-addresses sub-registry "Fixed Scope Multicast Addresses" sub-sub-registry "Link-Local Scope" FF02:0:0:0:0:0:0:TBD4 LL-MANET-Routers [ietf-manet-iana] 7. Security Considerations This document specifies only well-known number for protocols that conform to [I-D.ietf-manet-packetbb], and it not does not specify the protocols that carry the information across the network. Each protocol using these well-known numbers may have its own set of security issues, but those issues are not affected by using the IANA allocations specified herein. The security issues associated with possibly operating multiple cooperating protocols using the same IANA assignments (e.g. UDP port) MUST be addressed in each protocols' specification. 8. Acknowledgements Fred Templin, Bill Fenner, Alexandru Petrescu, Sam Weiler, Ross Callon, and Lars Eggert provided valuable input to this document. 9. References 9.1. Normative References [I-D.ietf-manet-packetbb] Clausen, T., "Generalized MANET Packet/Message Format", draft-ietf-manet-packetbb-11 (work in progress), November 2007. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Chakeres Expires May 21, 2008 [Page 5] Internet-Draft MANET-IANA November 2007 Architecture", RFC 4291, February 2006. 9.2. Informative References [IANAPort] "IANA Port Numbers", . [IANAProtocol] "IANA Protocol Numbers", . [IANAv4Multicast] "IPv4 Multicast Address Assignments", . [IANAv6Multicast] "IPv6 Multicast Address Assignments", . Author's Address Ian D Chakeres Motorola Bagmane Tech Park 66/1, Plot 5, CV Raman Nagar Bangalore, Karnataka 560093 India Email: ian.chakeres@gmail.com URI: http://www.ianchak.com/ Chakeres Expires May 21, 2008 [Page 6] Internet-Draft MANET-IANA November 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Chakeres Expires May 21, 2008 [Page 7]