idnits 2.17.1 draft-ietf-manet-iana-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 247. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 258. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 265. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 271. 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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 18, 2007) is 5976 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-17) exists of draft-ietf-manet-packetbb-11 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mobile Ad hoc Networks I. Chakeres 3 Internet-Draft Motorola 4 Intended status: Standards Track November 18, 2007 5 Expires: May 21, 2008 7 IANA Allocations for MANET Protocols 8 draft-ietf-manet-iana-07.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on May 21, 2008. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document enumerates several common IANA allocations for use by 42 MANET protocols. The following well-known numbers are required: a 43 UDP port number, an IP protocol number, and a link-local multicast 44 group address. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Conventions Used in This Document . . . . . . . . . . . . . . . 3 50 3. UDP Port Number . . . . . . . . . . . . . . . . . . . . . . . . 3 51 4. IP Protocol Number . . . . . . . . . . . . . . . . . . . . . . 3 52 5. Link-local Multicast Group for MANET Routers . . . . . . . . . 3 53 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 54 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 55 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 56 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 58 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 Intellectual Property and Copyright Statements . . . . . . . . . . 7 62 1. Introduction 64 This document enumerates several common IANA allocations for use by 65 one or more protocols that conform to [I-D.ietf-manet-packetbb]. The 66 following well-known numbers are required: a UDP port number, an IP 67 protocol number, and a link-local multicast group address. All 68 interoperable protocols running on these well-known IANA allocations 69 MUST conform to [I-D.ietf-manet-packetbb]. [I-D.ietf-manet-packetbb] 70 provides a common format that enables one or more protocols to share 71 the IANA allocations defined in this document unambiguously. 73 2. Conventions Used in This Document 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in RFC 2119 [RFC2119]. 79 3. UDP Port Number 81 MANET routers require a well-known UDP port number [IANAPort] to send 82 and receive MANET routing protocol packets. The title of this UDP 83 port is "manet". The value of this UDP port is TBD1. 85 4. IP Protocol Number 87 MANET routers require a well-known IP protocol number [IANAProtocol] 88 to send and receive MANET routing protocol packets. The title of 89 this IP protocol number is "manet". The value of this IP protocol 90 number is TBD2. 92 5. Link-local Multicast Group for MANET Routers 94 MANET routers require a well-known link-local multicast address 95 [RFC4291] to send and receive MANET routing protocol packets. The 96 name of the multicast address to reach link-local (LL) MANET routers 97 is "LL-MANET-Routers". 99 For IPv4, a well-known, link-local scope multicast address is 100 required. The address for LL-MANET-Routers is 224.0.0.TBD3 to appear 101 in the [IANAv4Multicast] registry. 103 For IPv6, a well-known, link-local scope multicast address is 104 required. The address for LL-MANET-Routers is FF02:0:0:0:0:0:0:TBD4 105 to appear in the [IANAv6Multicast] registry. 107 6. IANA Considerations 109 This document enumerates several common IANA allocations for use by 110 one or more protocols that conform to [I-D.ietf-manet-packetbb]. 111 Specifically, the following well-known numbers have been assigned: a 112 UDP port (Section 3), an IP protocol number (Section 4), and a link- 113 local multicast group address (Section 5). 115 Action 1: 117 Upon approval of this document, the IANA will make the following 118 assignments in the "PORT NUMBERS" registry located at 119 http://www.iana.org/assignments/port-numbers 121 sub-registry "WELL KNOWN PORT NUMBERS" 123 Keyword Decimal Description References 125 ------- ------- ----------- ---------- 127 manet TBD1/udp MANET Protocols [ietf-manet-iana] 129 Action 2: 131 Upon approval of this document, the IANA will make the following 132 assignments in the "PROTOCOL NUMBERS" registry located at 133 http://www.iana.org/assignments/protocol-numbers 135 sub-registry "WELL KNOWN PORT NUMBERS" 137 Keyword Decimal Description References 139 ------- ------- ----------- ---------- 141 manet TBD2 MANET Protocols [ietf-manet-iana] 143 Action 3: 145 Upon approval of this document, the IANA will make the following 146 assignments in the "Internet Multicast Addresses" registry located at 148 http://www.iana.org/assignments/multicast-addresses 150 sub-registry 224.0.0.0 - 224.0.0.255 (224.0.0/24) 152 Local Network Control Block Date registered" 154 224.0.0.TBD3 LL-MANET-Routers [ietf-manet-iana] 155 Action 4: 157 Upon approval of this document, the IANA will make the following 158 assignments in the "INTERNET PROTOCOL VERSION 6 MULTICAST ADDRESSES" 159 registry located at 161 http://www.iana.org/assignments/ipv6-multicast-addresses 163 sub-registry "Fixed Scope Multicast Addresses" 165 sub-sub-registry "Link-Local Scope" 167 FF02:0:0:0:0:0:0:TBD4 LL-MANET-Routers [ietf-manet-iana] 169 7. Security Considerations 171 This document specifies only well-known number for protocols that 172 conform to [I-D.ietf-manet-packetbb], and it not does not specify the 173 protocols that carry the information across the network. Each 174 protocol using these well-known numbers may have its own set of 175 security issues, but those issues are not affected by using the IANA 176 allocations specified herein. 178 The security issues associated with possibly operating multiple 179 cooperating protocols using the same IANA assignments (e.g. UDP 180 port) MUST be addressed in each protocols' specification. 182 8. Acknowledgements 184 Fred Templin, Bill Fenner, Alexandru Petrescu, Sam Weiler, Ross 185 Callon, and Lars Eggert provided valuable input to this document. 187 9. References 189 9.1. Normative References 191 [I-D.ietf-manet-packetbb] 192 Clausen, T., "Generalized MANET Packet/Message Format", 193 draft-ietf-manet-packetbb-11 (work in progress), 194 November 2007. 196 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 197 Requirement Levels", BCP 14, RFC 2119, March 1997. 199 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 200 Architecture", RFC 4291, February 2006. 202 9.2. Informative References 204 [IANAPort] 205 "IANA Port Numbers", 206 . 208 [IANAProtocol] 209 "IANA Protocol Numbers", 210 . 212 [IANAv4Multicast] 213 "IPv4 Multicast Address Assignments", 214 . 216 [IANAv6Multicast] 217 "IPv6 Multicast Address Assignments", 218 . 221 Author's Address 223 Ian D Chakeres 224 Motorola 225 Bagmane Tech Park 226 66/1, Plot 5, CV Raman Nagar 227 Bangalore, Karnataka 560093 228 India 230 Email: ian.chakeres@gmail.com 231 URI: http://www.ianchak.com/ 233 Full Copyright Statement 235 Copyright (C) The IETF Trust (2007). 237 This document is subject to the rights, licenses and restrictions 238 contained in BCP 78, and except as set forth therein, the authors 239 retain all their rights. 241 This document and the information contained herein are provided on an 242 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 243 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 244 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 245 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 246 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 247 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 249 Intellectual Property 251 The IETF takes no position regarding the validity or scope of any 252 Intellectual Property Rights or other rights that might be claimed to 253 pertain to the implementation or use of the technology described in 254 this document or the extent to which any license under such rights 255 might or might not be available; nor does it represent that it has 256 made any independent effort to identify any such rights. Information 257 on the procedures with respect to rights in RFC documents can be 258 found in BCP 78 and BCP 79. 260 Copies of IPR disclosures made to the IETF Secretariat and any 261 assurances of licenses to be made available, or the result of an 262 attempt made to obtain a general license or permission for the use of 263 such proprietary rights by implementers or users of this 264 specification can be obtained from the IETF on-line IPR repository at 265 http://www.ietf.org/ipr. 267 The IETF invites any interested party to bring to its attention any 268 copyrights, patents or patent applications, or other proprietary 269 rights that may cover technology that may be required to implement 270 this standard. Please address the information to the IETF at 271 ietf-ipr@ietf.org. 273 Acknowledgment 275 Funding for the RFC Editor function is provided by the IETF 276 Administrative Support Activity (IASA).