idnits 2.17.1 draft-chakeres-manet-iana-02.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 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 249. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 226. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 233. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 239. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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 73: '... sent to this port MUST conform to the...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 (October 14, 2006) is 6403 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-02 Summary: 4 errors (**), 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 Boeing 4 Expires: April 17, 2007 October 14, 2006 6 MANET IANA Needs 7 draft-chakeres-manet-iana-02.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on April 17, 2007. 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This document enumerates IANA assignments for immediate use in MANET. 41 Specifically, a UDP port, two link-local multicast group addresses 42 (IPv4 & IPv6), and two site-local multicast group addresses (IPv4 & 43 IPv6). 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. UDP Port for MANET Protocols . . . . . . . . . . . . . . . . . 3 49 3. Link-local Multicast Group for MANET Routers . . . . . . . . . 3 50 4. Site-local Scoped Multicast Groups for MANET Routers . . . . . 4 51 4.1. Site-Local Multicast Group for IPv4 . . . . . . . . . . . . 4 52 4.2. Site-local Scoped Multicast Group for IPv6 . . . . . . . . 5 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 54 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 55 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 56 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 58 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 60 Intellectual Property and Copyright Statements . . . . . . . . . . 8 62 1. Introduction 64 This document enumerates a port and several scoped multicast address 65 assignments for MANET protocols. 67 2. UDP Port for MANET Protocols 69 To aggregate MANET routing protocol traffic it must be sent to the 70 same IP destination address and the same port. Therefore, all 71 interoperable MANET routing protocol traffic should be sent to the 72 same UDP port. The title of this UDP port is "MANET". In order to 73 be interoperable all packets sent to this port MUST conform to the 74 packetbb specification [I-D.ietf-manet-packetbb]. 76 UDP Port Assignment 78 +-------+-------+ 79 | Name | Value | 80 +-------+-------+ 81 | MANET | TBD1 | 82 +-------+-------+ 84 Table 1 86 3. Link-local Multicast Group for MANET Routers 88 MANET protocols need a link-local multicast address [RFC4291] to 89 disseminate information. 91 The name of the multicast address to reach link-local (LL) MANET 92 routers is "LL MANET Routers". MANET routers subscribe to this LL 93 scoped multicast address and use it for LL transmissions of routing 94 protocol packets. 96 For IPv4, a statically assigned, link-local scope multicast address 97 is used. The address for LL MANET Routers is 224.0.0.TBD2 to appear 98 in the [IANAv4Multicast] registry. 100 For IPv6, a statically assigned, link-local scope multicast address 101 is used. The address for LL MANET Routers is FF02:0:0:0:0:0:0:TBD3 102 to appear in the [IANAv6Multicast] registry. 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 4. Site-local Scoped Multicast Groups for MANET Routers 116 MANET protocols need a scoped multicast address [RFC4291] to 117 disseminate information more widely, greater than LL. This section 118 names the multicast address, defines the scope, and clarifies router 119 behavior. 121 The name of the multicast address to reach the MANET routers is 122 "MANET Routers". MANET routers subscribe to these site-local scoped 123 multicast addresses. 125 Site-local multicast address assignment 127 +---------------+------------------------+-----------------------+ 128 | Name | IPv4 | IPv6 | 129 +---------------+------------------------+-----------------------+ 130 | MANET Routers | 239.255.255.(255-TBD4) | FF05:0:0:0:0:0:0:TBD5 | 131 +---------------+------------------------+-----------------------+ 133 Table 3 135 MANET routers that forward these scoped multicast addresses must use 136 additional criteria as specified in [RFC2365] and [RFC4007]. 138 4.1. Site-Local Multicast Group for IPv4 140 For IPv4, statically assigned, scope-relative multicast address (as 141 defined by [RFC2365], Section 9) are used. The offset for the scope 142 relative address for scoped MANET Routers is TBD4 to appear in 143 [IANAv4Multicast] registry. 145 Different scopes are defined by [RFC2365]. The IPv4 Local Scope 146 (239.255.0.0/16) is the minimal enclosing scope for administratively 147 scoped multicast and not further divisible -- its exact extent is 148 site dependent. 150 For the IPv4 Local Scope, applying the rules of [RFC2365] and using 151 the assigned offset of TDB4, the multicast address is therefore 152 239.255.255.(255-TBD4). 154 4.2. Site-local Scoped Multicast Group for IPv6 156 IPv6 has different address ranges for different multicast scopes that 157 are implemented as a set of address prefixes for the different 158 address ranges ([RFC4291]). A permanently assigned multicast address 159 is used for site-local scoped MANET Routers multicast communication. 160 See [RFC4291] and the [IANAv6Multicast] registry for IPv6 multicast 161 assignments. 163 The permanent IPv6 multicast address for MANET Routers/IPv6 is 164 FF05:0:0:0:0:0:0:TBD5. 166 5. IANA Considerations 168 A summary of the decided IANA assignments will appear here. 170 6. Security Considerations 172 There are no security considerations associated with this document. 174 7. Acknowledgements 176 Fred Templin provided valuable input to this document. 178 8. References 180 8.1. Normative References 182 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 183 RFC 2365, July 1998. 185 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 186 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 187 March 2005. 189 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 190 Architecture", RFC 4291, February 2006. 192 8.2. Informative References 194 [I-D.ietf-manet-packetbb] 195 Clausen, T., "Generalized MANET Packet/Message Format", 196 draft-ietf-manet-packetbb-02 (work in progress), 197 July 2006. 199 [IANAv4Multicast] 200 "IPv4 Multicast Address Assignments", . 203 [IANAv6Multicast] 204 "IPv6 Multicast Address Assignments", . 207 Author's Address 209 Ian D Chakeres 210 Boeing 211 P.O. Box 3707 MC 7L-49 212 Seattle, WA 98124 213 USA 215 Email: ian.chakeres@gmail.com 217 Intellectual Property Statement 219 The IETF takes no position regarding the validity or scope of any 220 Intellectual Property Rights or other rights that might be claimed to 221 pertain to the implementation or use of the technology described in 222 this document or the extent to which any license under such rights 223 might or might not be available; nor does it represent that it has 224 made any independent effort to identify any such rights. Information 225 on the procedures with respect to rights in RFC documents can be 226 found in BCP 78 and BCP 79. 228 Copies of IPR disclosures made to the IETF Secretariat and any 229 assurances of licenses to be made available, or the result of an 230 attempt made to obtain a general license or permission for the use of 231 such proprietary rights by implementers or users of this 232 specification can be obtained from the IETF on-line IPR repository at 233 http://www.ietf.org/ipr. 235 The IETF invites any interested party to bring to its attention any 236 copyrights, patents or patent applications, or other proprietary 237 rights that may cover technology that may be required to implement 238 this standard. Please address the information to the IETF at 239 ietf-ipr@ietf.org. 241 Disclaimer of Validity 243 This document and the information contained herein are provided on an 244 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 245 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 246 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 247 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 248 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 249 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 251 Copyright Statement 253 Copyright (C) The Internet Society (2006). This document is subject 254 to the rights, licenses and restrictions contained in BCP 78, and 255 except as set forth therein, the authors retain all their rights. 257 Acknowledgment 259 Funding for the RFC Editor function is currently provided by the 260 Internet Society.