idnits 2.17.1 draft-ietf-manet-iana-05.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 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 166. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 177. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 184. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 190. 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 : ---------------------------------------------------------------------------- No issues found here. 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 (June 9, 2007) is 6165 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) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 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 June 9, 2007 5 Expires: December 11, 2007 7 Internet Assigned Numbers Authority (IANA) Allocations for the Mobile 8 Ad hoc Networks (MANET) Working Group 9 draft-ietf-manet-iana-05.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on December 11, 2007. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This document enumerates IANA allocations for use by MANET WG 43 protocols. Specifically, a UDP port and two link-local multicast 44 group addresses (IPv4 & IPv6). 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. UDP Port for MANET Protocols . . . . . . . . . . . . . . . . . 3 50 3. Link-local Multicast Group for MANET Routers . . . . . . . . . 3 51 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 52 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 53 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 54 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 56 7.2. Informative References . . . . . . . . . . . . . . . . . . 4 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 Intellectual Property and Copyright Statements . . . . . . . . . . 6 60 1. Introduction 62 This document enumerates IANA allocations for MANET WG protocols. A 63 well-known UDP port for MANET WG protocols. Well-known link-local 64 multicast addresses (IPv4 & IPv6) for link-local communication 65 between neighboring MANET routers. 67 2. UDP Port for MANET Protocols 69 MANET routing protocols require a well-known UDP port to send and 70 receive MANET routing protocol packets. The title of this UDP port 71 is "manet". The value of this UPD port is TBD1. 73 3. Link-local Multicast Group for MANET Routers 75 MANET protocols require a well-known link-local multicast address 76 [RFC4291] to send and receive MANET routing protocol packets. The 77 name of the multicast address to reach link-local (LL) MANET routers 78 is "LL MANET Routers". 80 MANET routers will use this well-known LL scoped multicast address to 81 receive routing protocol packets and use it for LL transmissions of 82 routing protocol packets. 84 For IPv4, a well-known, link-local scope multicast address is used. 85 The address for LL MANET Routers is 224.0.0.TBD2 to appear in the 86 [IANAv4Multicast] registry. 88 For IPv6, a well-known, link-local scope multicast address is used. 89 The address for LL MANET Routers is FF02:0:0:0:0:0:0:TBD3 to appear 90 in the [IANAv6Multicast] registry. 92 4. IANA Considerations 94 UDP Port Assignment 96 +-------+-------+ 97 | Name | Value | 98 +-------+-------+ 99 | manet | TBD1 | 100 +-------+-------+ 102 Table 1 104 Link-local multicast address assignment 106 +------------------+--------------+-----------------------+ 107 | Name | IPv4 | IPv6 | 108 +------------------+--------------+-----------------------+ 109 | LL MANET Routers | 224.0.0.TBD2 | FF02:0:0:0:0:0:0:TBD3 | 110 +------------------+--------------+-----------------------+ 112 Table 2 114 5. Security Considerations 116 There are no security considerations associated with this document. 118 6. Acknowledgements 120 Fred Templin, Bill Fenner, and Alexandru Petrescu provided valuable 121 input to this document. 123 7. References 125 7.1. Normative References 127 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 128 Architecture", RFC 4291, February 2006. 130 7.2. Informative References 132 [IANAv4Multicast] 133 "IPv4 Multicast Address Assignments", May 2007, 134 . 136 [IANAv6Multicast] 137 "IPv6 Multicast Address Assignments", May 2007, 138 . 141 Author's Address 143 Ian D Chakeres 144 Motorola 145 Bagmane Tech Park 146 66/1, Plot 5, CV Raman Nagar 147 Bangalore, Karnataka 560093 148 India 150 Email: ian.chakeres@gmail.com 152 Full Copyright Statement 154 Copyright (C) The IETF Trust (2007). 156 This document is subject to the rights, licenses and restrictions 157 contained in BCP 78, and except as set forth therein, the authors 158 retain all their rights. 160 This document and the information contained herein are provided on an 161 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 162 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 163 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 164 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 165 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 166 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 168 Intellectual Property 170 The IETF takes no position regarding the validity or scope of any 171 Intellectual Property Rights or other rights that might be claimed to 172 pertain to the implementation or use of the technology described in 173 this document or the extent to which any license under such rights 174 might or might not be available; nor does it represent that it has 175 made any independent effort to identify any such rights. Information 176 on the procedures with respect to rights in RFC documents can be 177 found in BCP 78 and BCP 79. 179 Copies of IPR disclosures made to the IETF Secretariat and any 180 assurances of licenses to be made available, or the result of an 181 attempt made to obtain a general license or permission for the use of 182 such proprietary rights by implementers or users of this 183 specification can be obtained from the IETF on-line IPR repository at 184 http://www.ietf.org/ipr. 186 The IETF invites any interested party to bring to its attention any 187 copyrights, patents or patent applications, or other proprietary 188 rights that may cover technology that may be required to implement 189 this standard. Please address the information to the IETF at 190 ietf-ipr@ietf.org. 192 Acknowledgment 194 Funding for the RFC Editor function is provided by the IETF 195 Administrative Support Activity (IASA).