idnits 2.17.1 draft-ietf-manet-iana-00.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 232. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 243. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 250. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 256. 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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 74: '... sent to this port MUST conform to the...' 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 (February 23, 2007) is 6270 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-17) exists of draft-ietf-manet-packetbb-02 Summary: 2 errors (**), 0 flaws (~~), 2 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 Boeing 4 Intended status: Informational February 23, 2007 5 Expires: August 27, 2007 7 MANET IANA Needs 8 draft-ietf-manet-iana-00.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 August 27, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document enumerates IANA assignments for immediate use in MANET. 42 Specifically, a UDP port, two link-local multicast group addresses 43 (IPv4 & IPv6), and two site-local multicast group addresses (IPv4 & 44 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. Site-local Scoped Multicast Groups for MANET Routers . . . . . 4 52 4.1. Site-Local Multicast Group for IPv4 . . . . . . . . . . . . 4 53 4.2. Site-local Scoped Multicast Group for IPv6 . . . . . . . . 5 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 55 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 56 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 57 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 59 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 Intellectual Property and Copyright Statements . . . . . . . . . . 7 63 1. Introduction 65 This document enumerates a port and several scoped multicast address 66 assignments for MANET protocols. 68 2. UDP Port for MANET Protocols 70 To aggregate MANET routing protocol traffic it must be sent to the 71 same IP destination address and the same port. Therefore, all 72 interoperable MANET routing protocol traffic should be sent to the 73 same UDP port. The title of this UDP port is "MANET". In order to 74 be interoperable all packets sent to this port MUST conform to the 75 packetbb specification [I-D.ietf-manet-packetbb]. 77 UDP Port Assignment 79 +-------+-------+ 80 | Name | Value | 81 +-------+-------+ 82 | MANET | TBD1 | 83 +-------+-------+ 85 Table 1 87 3. Link-local Multicast Group for MANET Routers 89 MANET protocols need a link-local multicast address [RFC4291] to 90 disseminate information. 92 The name of the multicast address to reach link-local (LL) MANET 93 routers is "LL MANET Routers". MANET routers subscribe to this LL 94 scoped multicast address and use it for LL transmissions of routing 95 protocol packets. 97 For IPv4, a statically assigned, link-local scope multicast address 98 is used. The address for LL MANET Routers is 224.0.0.TBD2 to appear 99 in the [IANAv4Multicast] registry. 101 For IPv6, a statically assigned, link-local scope multicast address 102 is used. The address for LL MANET Routers is FF02:0:0:0:0:0:0:TBD3 103 to appear in the [IANAv6Multicast] registry. 105 Link-local multicast address assignment 107 +------------------+--------------+-----------------------+ 108 | Name | IPv4 | IPv6 | 109 +------------------+--------------+-----------------------+ 110 | LL MANET Routers | 224.0.0.TBD2 | FF02:0:0:0:0:0:0:TBD3 | 111 +------------------+--------------+-----------------------+ 113 Table 2 115 4. Site-local Scoped Multicast Groups for MANET Routers 117 MANET protocols need a scoped multicast address [RFC4291] to 118 disseminate information more widely, greater than LL. This section 119 names the multicast address, defines the scope, and clarifies router 120 behavior. 122 The name of the multicast address to reach the MANET routers is 123 "MANET Routers". MANET routers subscribe to these site-local scoped 124 multicast addresses. 126 Site-local multicast address assignment 128 +---------------+------------------------+-----------------------+ 129 | Name | IPv4 | IPv6 | 130 +---------------+------------------------+-----------------------+ 131 | MANET Routers | 239.255.255.(255-TBD4) | FF05:0:0:0:0:0:0:TBD5 | 132 +---------------+------------------------+-----------------------+ 134 Table 3 136 MANET routers that forward these scoped multicast addresses must use 137 additional criteria as specified in [RFC2365] and [RFC4007]. 139 4.1. Site-Local Multicast Group for IPv4 141 For IPv4, statically assigned, scope-relative multicast address (as 142 defined by [RFC2365], Section 9) are used. The offset for the scope 143 relative address for scoped MANET Routers is TBD4 to appear in 144 [IANAv4Multicast] registry. 146 Different scopes are defined by [RFC2365]. The IPv4 Local Scope 147 (239.255.0.0/16) is the minimal enclosing scope for administratively 148 scoped multicast and not further divisible -- its exact extent is 149 site dependent. 151 For the IPv4 Local Scope, applying the rules of [RFC2365] and using 152 the assigned offset of TDB4, the multicast address is therefore 153 239.255.255.(255-TBD4). 155 4.2. Site-local Scoped Multicast Group for IPv6 157 IPv6 has different address ranges for different multicast scopes that 158 are implemented as a set of address prefixes for the different 159 address ranges ([RFC4291]). A permanently assigned multicast address 160 is used for site-local scoped MANET Routers multicast communication. 161 See [RFC4291] and the [IANAv6Multicast] registry for IPv6 multicast 162 assignments. 164 The permanent IPv6 multicast address for MANET Routers/IPv6 is 165 FF05:0:0:0:0:0:0:TBD5. 167 5. IANA Considerations 169 A summary of the decided IANA assignments will appear here. 171 6. Security Considerations 173 There are no security considerations associated with this document. 175 7. Acknowledgements 177 Fred Templin provided valuable input to this document. 179 8. References 181 8.1. Normative References 183 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 184 RFC 2365, July 1998. 186 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 187 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 188 March 2005. 190 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 191 Architecture", RFC 4291, February 2006. 193 8.2. Informative References 195 [I-D.ietf-manet-packetbb] 196 Clausen, T., "Generalized MANET Packet/Message Format", 197 draft-ietf-manet-packetbb-02 (work in progress), 198 July 2006. 200 [IANAv4Multicast] 201 "IPv4 Multicast Address Assignments", . 204 [IANAv6Multicast] 205 "IPv6 Multicast Address Assignments", . 208 Author's Address 210 Ian D Chakeres 211 Boeing 212 P.O. Box 3707 MC 7L-49 213 Seattle, WA 98124 214 USA 216 Email: ian.chakeres@gmail.com 218 Full Copyright Statement 220 Copyright (C) The IETF Trust (2007). 222 This document is subject to the rights, licenses and restrictions 223 contained in BCP 78, and except as set forth therein, the authors 224 retain all their rights. 226 This document and the information contained herein are provided on an 227 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 228 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 229 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 230 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 231 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 232 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 234 Intellectual Property 236 The IETF takes no position regarding the validity or scope of any 237 Intellectual Property Rights or other rights that might be claimed to 238 pertain to the implementation or use of the technology described in 239 this document or the extent to which any license under such rights 240 might or might not be available; nor does it represent that it has 241 made any independent effort to identify any such rights. Information 242 on the procedures with respect to rights in RFC documents can be 243 found in BCP 78 and BCP 79. 245 Copies of IPR disclosures made to the IETF Secretariat and any 246 assurances of licenses to be made available, or the result of an 247 attempt made to obtain a general license or permission for the use of 248 such proprietary rights by implementers or users of this 249 specification can be obtained from the IETF on-line IPR repository at 250 http://www.ietf.org/ipr. 252 The IETF invites any interested party to bring to its attention any 253 copyrights, patents or patent applications, or other proprietary 254 rights that may cover technology that may be required to implement 255 this standard. Please address the information to the IETF at 256 ietf-ipr@ietf.org. 258 Acknowledgment 260 Funding for the RFC Editor function is provided by the IETF 261 Administrative Support Activity (IASA).