idnits 2.17.1 draft-ietf-mboned-iana-ipv4-mcast-guidelines-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 8 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 9 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 10 instances of too long lines in the document, the longest one being 6 characters in excess of 72. 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 the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1190' is defined on line 283, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA' ** Obsolete normative reference: RFC 1190 (Obsoleted by RFC 1819) ** Obsolete normative reference: RFC 2030 (Obsoleted by RFC 4330) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2770 (Obsoleted by RFC 3180) ** Obsolete normative reference: RFC 2908 (Obsoleted by RFC 6308) ** Downref: Normative reference to an Experimental RFC: RFC 2974 -- Possible downref: Non-RFC (?) normative reference: ref. 'SDR' Summary: 14 errors (**), 0 flaws (~~), 6 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Zaid Albanna 2 INTERNET DRAFT Juniper Networks 3 Kevin Almeroth 4 UCSB 5 David Meyer 6 Cisco Systems 7 Michelle Schipper 8 IANA 9 Category Best Current Practices 10 April, 2001 12 IANA Guidelines for IPv4 Multicast Address Assignments 13 15 1. Status of this Memo 17 This document specifies an Internet Best Current Practices for the 18 Internet Community, and requests discussion and suggestions for 19 improvements. Distribution of this memo is unlimited. 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC 2026. 24 Internet Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that other 26 groups may also distribute working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 2. Copyright Notice 41 Copyright (C) The Internet Society (2001). All Rights Reserved. 43 3. Abstract 45 This memo provides guidance for the IANA in assigning IPv4 multicast 46 addresses. 48 4. Introduction 50 The Internet Assigned Numbers Authority (IANA) (www.iana.org) is 51 charged with allocating parameter values for fields in protocols 52 which have been designed, created or are maintained by the Internet 53 Engineering Task Force (IETF). RFC 2780 [RFC2780] provides the IANA 54 guidance in the assignment of parameters for fields in newly 55 developed protocols. This memo expands on section 4.4.2 of RFC 2780 56 and attempts to codify existing IANA practice used in the assignment 57 IPv4 multicast addresses. 59 The terms "Specification Required", "Expert Review", "IESG Approval", 60 "IETF Consensus", and "Standards Action", are used in this memo to 61 refer to the processes described in [RFC2434]. The keywords MUST, 62 MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT, 63 SHOULD, SHOULD NOT are to be interpreted as defined in RFC 2119 64 [RFC2119]. 66 In general, due to the relatively small size of the IPv4 multicast 67 addresses space, further assignment of IPv4 multicast address space 68 is recommended only in limited circumstances. Specifically, the IANA 69 should only assign addresses in those cases where the dynamic 70 selection (SDP/SAP), GLOP, SSM or Administratively Scoped address 71 spaces cannot be used. The guidelines described below are reflected 72 in http://www.iana.org/assignments/multicast-addresses. 74 5. Definition of Current Assignment Practice 76 Unlike IPv4 unicast address assignment, where blocks of addresses are 77 delegated to regional registries, IPv4 multicast addresses are 78 assigned directly by the IANA. Current assignments appear as follows 79 [IANA]: 81 224.0.0.0 - 224.0.0.255 (224.0.0/24) Local Network Control Block 82 224.0.1.0 - 224.0.1.255 (224.0.1/24) Internetwork Control Block 83 224.0.2.0 - 224.0.255.0 AD-HOC Block 84 224.1.0.0 - 224.1.255.255 (224.1/16) ST Multicast Groups 85 224.2.0.0 - 224.2.255.255 (224.2/16) SDP/SAP Block 86 224.252.0.0 - 224.255.255.255 DIS Transient Block 87 225.0.0.0 - 225.255.255.255 (225/8) MALLOC Block 88 226.0.0.0 - 231.255.255.255 RESERVED 89 232.0.0.0 - 232.255.255.255 (232/8) Source Specific Multicast Block 90 233.0.0.0 - 233.255.255.255 (233/8) GLOP Block 91 234.0.0.0 - 238.255.255.255 RESERVED 92 239.0.0.0 - 239.255.255.255 (239/8) Administratively Scoped Block 94 The IANA generally assigns addresses from the Local Network Control, 95 Internetwork Control, and AD-HOC blocks. Assignment guidelines for 96 each of these blocks, as well as for the MALLOC, Source Specific 97 Multicast, GLOP and Administratively Scoped Blocks, are described 98 below. 100 6. Local Network Control Block (224.0.0/24) 102 Addresses in the Local Network Control block are used for protocol 103 control traffic that is not forwarded off link. Examples of this type 104 of use include OSPFIGP All Routers (224.0.0.5) [RFC2328]. 106 6.1. Assignment Guidelines 108 Assignment of addresses in the Local Network Configuration Block 109 SHOULD BE be accompanied by a specification ("Specification 110 Required"). This specification will typically take the form of an 111 internet draft or RFC. 113 7. Internetwork Control Block (224.0.1/24) 115 Addresses in the Internetwork Control block are used for protocol 116 control that must be forwarded through the Internet. Examples include 117 224.0.1.1 (NTP [RFC2030]) and 224.0.1.68 (mdhcpdisover [RFC2730]). 119 7.1. Assignment Guidelines 121 Assignment of addresses in the Internetwork Control block SHOULD BE 122 accompanied by a specification ("Specification Required"). This 123 specification will typically take the form of an internet draft or 124 RFC. 126 8. AD-HOC Block (224.0.2.0/24 - 224.0.255.0/24) 128 Addresses in the AD-HOC block have traditionally been assigned for 129 those applications that don't fit in either the Local or Internetwork 130 Control blocks. These addresses are globally routed and are typically 131 used by applications that require small blocks of addressing (e.g., 132 less than a /24). 134 8.1. Assignment Guidelines 136 IANA SHOULD NOT assign addressing in the AD-HOC Block unless it is a 137 special circumstance accompanied by a specification ("Specification 138 Required"). This specification will typically take the form of an 139 Internet-Draft or RFC. 141 9. SDP/SAP Block (224.2/16) 143 Addresses in the SDP/SAP block are used by applications that receive 144 addresses through the Session Announcement Protocol [RFC2974] for use 145 via applications like the session directory tool (such as SDR [SDR]). 147 9.1. Assignment Guidelines 149 Since addresses in the SDP/SAP block are chosen randomly from the 150 range of addresses not already in use [RFC2974], no IANA assignment 151 policy is required. Note that while no additional IANA assignment is 152 required, addresses in the SDP/SAP block are explicitly for use by 153 SDP/SAP and MUST NOT be used for other purposes. 155 10. MALLOC Block (225/8) 157 Addresses in the MALLOC block are dynamically assigned by the MALLOC 158 suite of protocols [RFC2908]. This assignment is temporary and MUST 159 BE reviewed annually. 161 10.1. Assignment Guidelines 163 Since addresses in the MALLOC block are chosen by elements of the 164 MALLOC architecture, no IANA assignment policy is required. Note that 165 while no additional IANA assignment is required, addresses in the 166 MALLOC block are explicitly for assignment by MALLOC servers and MUST 167 NOT be used for other purposes. 169 11. Source Specific Multicast Block (232/8) 171 The Source Specific Multicast (SSM) is an extension of IP Multicast 172 in which traffic is forwarded to receivers from only those multicast 173 sources for which the receivers have explicitly expressed interest, 174 and is primarily targeted at one-to-many (broadcast) applications. 176 11.1. Assignment Guidelines 178 Because the SSM model essentially makes the entire multicast address 179 space local to the host, no IANA assignment policy is required. Note, 180 however, that while no additional IANA assignment is required, 181 addresses in the SSM block are explicitly for use by SSM and MUST NOT 182 be used for other purposes. 184 12. GLOP Block (233/8) 186 Addresses in the GLOP block are globally scoped statically assigned 187 addresses. The assignment is made by mapping a domain's autonomous 188 system number into the middle two octets of 233.X.Y.0/24. The mapping 189 and assignment is defined in [RFC2770]. 191 12.1. Assignment Guidelines 193 Because addresses in the GLOP block are algorithmically preassigned, 194 no IANA assignment policy is required. Note that while no additional 195 IANA assignment is required, addresses in the GLOP block are assigned 196 for use as defined in RFC 2770 and MUST NOT be used for other 197 purposes. 199 13. Administratively Scoped Address Block (239/8) 201 Addresses in the Administratively Scoped Address block are for local 202 use within a domain and are described in [RFC2365]. 204 13.1. Assignment Guidelines 206 Since addresses in this block are local to a domain, no IANA 207 assignment policy is required. 209 13.1.1. Relative Offsets 211 The relative offsets [RFC2365] are used to ensure that a service can 212 be located independent of the extent of the enclosing scope (see RFC 213 2770 for details). Since there are only 256 such offsets, the IANA 214 should only assign a relative offset to a protocol that provides an 215 infra-structure supporting service. Examples of such services include 216 the Session Announcement Protocol [RFC2974]. See [IANA] for the 217 current set of assignments. 219 14. Annual Review 221 Given the dynamic nature of IPv4 multicast and its associated infra- 222 structure, and the previously undocumented IPv4 multicast address 223 assignment guidelines, the IANA should conduct an annual review of 224 currently assigned addresses. 226 14.1. Address Reclamation 228 During the review described above, addresses that were mis-assigned 229 should, where possible, be reclaimed or reassigned. 231 The IANA should also review assignments in the AD-HOC, DIS Transient 232 Groups, and ST Multicast Groups blocks and reclaim those addresses 233 that are not in use on the global Internet (i.e, those applications 234 which can use SSM, GLOP, or Administratively Scoped addressing, or 235 are not globally routed). 237 15. Use of IANA Reserved Addresses 239 Applications MUST NOT use addressing in the IANA reserved blocks. 241 16. Appeals Process 243 Appleals of this process are to be handled in accordance with Section 244 6.5 of RFC 2026 [RFC2026]. 246 17. Security Considerations 248 The assignment guidelines described in this document do not alter the 249 security properties of either the Any Source or Source Specific 250 multicast service models. 252 18. Acknowledgments 254 The authors would like to thank Joe St. Sauver, John Meylor, and 255 Randy Bush for their constructive feedback and comments. 257 19. Author's Address: 259 Zaid Albanna 260 1149 N. Mathilda Ave 261 Sunnyvale, CA. 94089 262 zaid@juniper.net 264 Kevin Almeroth 265 UC Santa Barbara 266 Sata Barbara, CA. 267 Email: almeroth@cs.ucsb.edu 269 David Meyer 270 Cisco Systems, Inc. 271 170 Tasman Drive 272 San Jose, CA, 95134 273 Email: dmm@cisco.com 275 Michelle Schipper 276 IANA Administrator 277 iana@iana.org 279 20. References 281 [IANA] http://www.iana.org/assignments/multicast-addresses 283 [RFC1190] C. Topolcic, "Experimental Internet Stream 284 Protocol, Version 2 (ST-II)", RFC 1190, October, 285 1990. 287 [RFC2026] S. Bradner, "The Internet Standards Process -- 288 Revision 3", RFC2026, October 1996. 290 [RFC2030] Mills, D., Simple Network Time Protocol (SNTP) Version 4 291 for IPv4, IPv6 and OSI", D. Mills, October 1996. 293 [RFC2119] S. Bradner, "Key words for use in RFCs to 294 Indicate Requirement Levels", RFC 2119, March, 295 1997. 297 [RFC2328] J. Moy,"OSPF Version 2", RFC 2328, April, 1998. 299 [RFC2365] D. Meyer,"Administratively Scoped IP Multicast", RFC 300 2365, July, 1998. 302 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 303 Writing an IANA Considerations Section in RFCs", 304 BCP 26, RFC 2434, October 1998. 306 [RFC2730] Hanna, S., Patel, B. and M. Shah, "Multicast Address 307 Dynamic Client Allocation Protocol (MADCAP), December 308 1999. 310 [RFC2770] D. Meyer, and P. Lothberg, "GLOP Addressing in 233/8", 311 RFC 2770, February, 2000 313 [RFC2780] S. Bradner and V. Paxson, "IANA Allocation Guidelines 314 For Values In the Internet Protocol and Related 315 Headers", RFC2780, March, 2000 317 [RFC2908] D. Thaler, M. Handley, D.Estrin, "Theh Internet Multicast 318 Address Allocation Architecture", RFC 2908, September 2000. 320 [RFC2974] M. Handley, C. Perkins, E. Whelan, "Session 321 Announcement Protocol", RFC 2974, October 2000. 323 [SDR] http://www.aciri.org/sdr/ 325 21. Full Copyright Statement 327 Copyright (C) The Internet Society (2001). All Rights Reserved. 329 This document and translations of it may be copied and furnished to 330 others, and derivative works that comment on or otherwise explain it 331 or assist in its implementation may be prepared, copied, published 332 and distributed, in whole or in part, without restriction of any 333 kind, provided that the above copyright notice and this paragraph are 334 included on all such copies and derivative works. However, this 335 document itself may not be modified in any way, such as by removing 336 the copyright notice or references to the Internet Society or other 337 Internet organizations, except as needed for the purpose of 338 developing Internet standards in which case the procedures for 339 copyrights defined in the Internet Standards process must be 340 followed, or as required to translate it into languages other than 341 English. 343 The limited permissions granted above are perpetual and will not be 344 revoked by the Internet Society or its successors or assigns. 346 This document and the information contained herein is provided on an 347 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 348 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 349 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 350 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 351 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.