Network Working Group Z. Albanna Request for Comments: 3171 Juniper Networks BCP: 51 K. Almeroth Category: Best Current Practice UCSB D. Meyer Sprint M. Schipper IANA August 2001 IANA Guidelines for IPv4 Multicast Address Assignments Status of this Memo This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved.
AbstractThis memo provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. RFC2780] provides the IANA guidance in the assignment of parameters for fields in newly developed protocols. This memo expands on section 4.4.2 of RFC 2780 and attempts to codify existing IANA practice used in the assignment IPv4 multicast addresses. The terms "Specification Required", "Expert Review", "IESG Approval", "IETF Consensus", and "Standards Action", are used in this memo to refer to the processes described in [RFC2434]. The keywords MUST, MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT, SHOULD, SHOULD NOT are to be interpreted as defined in RFC 2119 [RFC2119].
In general, due to the relatively small size of the IPv4 multicast addresses space, further assignment of IPv4 multicast address space is recommended only in limited circumstances. Specifically, the IANA should only assign addresses in those cases where the dynamic selection (SDP/SAP), GLOP, SSM or Administratively Scoped address spaces cannot be used. The guidelines described below are reflected in http://www.iana.org/numbers.html. IANA]: 184.108.40.206 - 220.127.116.11 (224.0.0/24) Local Network Control Block 18.104.22.168 - 22.214.171.124 (224.0.1/24) Internetwork Control Block 126.96.36.199 - 188.8.131.52 AD-HOC Block 184.108.40.206 - 220.127.116.11 (224.1/16) ST Multicast Groups 18.104.22.168 - 22.214.171.124 (224.2/16) SDP/SAP Block 126.96.36.199 - 188.8.131.52 DIS Transient Block 184.108.40.206 - 220.127.116.11 RESERVED 18.104.22.168 - 22.214.171.124 (232/8) Source Specific Multicast Block 126.96.36.199 - 188.8.131.52 (233/8) GLOP Block 184.108.40.206 - 220.127.116.11 RESERVED 18.104.22.168 - 22.214.171.124 (239/8) Administratively Scoped Block The IANA generally assigns addresses from the Local Network Control, Internetwork Control, and AD-HOC blocks. Assignment guidelines for each of these blocks, as well as for the Source Specific Multicast, GLOP and Administratively Scoped Blocks, are described below. RFC2328]. section 4.4.2 of RFC 2780 [RFC2780], assignments from the Local Network Control block follow an Expert Review, IESG Approval or Standards Action process. See [IANA] for the current set of assignments.
RFC2030]) and 126.96.36.199 (mdhcpdiscover [RFC2730]). section 4.4.2 of RFC 2780 [RFC2780], assignments from the Internetwork Control block follow an Expert Review, IESG Approval or Standards Action process. See [IANA] for the current set of assignments. section 4.4.2 of RFC 2780 [RFC2780], assignments from the AD-HOC block follow an Expert Review, IESG Approval or Standards Action process. See [IANA] for the current set of assignments. RFC2974] for use via applications like the session directory tool (such as SDR [SDR]). RFC2974], no IANA assignment policy is required. Note that while no additional IANA assignment is required, addresses in the SDP/SAP block are explicitly for use by SDP/SAP and MUST NOT be used for other purposes.
IANA]. RFC2770]. RFC3138] delegates assignment of the GLOP sub-block mapped by the RFC 1930 [RFC1930] private AS space (188.8.131.52 - 184.108.40.206) to the Internet Routing Registries. Note that while no additional IANA assignment is required, addresses in the GLOP block are assigned for use as defined in RFC 2770 and MUST NOT be used for other purposes. RFC2365].
RFC2365] are used to ensure that a service can be located independent of the extent of the enclosing scope (see RFC 2770 for details). Since there are only 256 such offsets, the IANA should only assign a relative offset to a protocol that provides an infrastructure supporting service. Examples of such services include the Session Announcement Protocol [RFC2974]. Pursuant to section 4.4.2 of RFC 2780 [RFC2780], assignments of Relative Offsets follow an Expert Review, IESG Approval or Standards Action process. See [IANA] for the current set of assignments.
[IANA] http://www.iana.org/numbers.html [RFC1190] Topolcic, C., "Experimental Internet Stream Protocol, Version 2 (ST-II)", RFC 1190, October 1990. [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, selection, and registration of an Autonomous System (AS)", RFC 1930, March 1996. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC2030] Mills, D., "Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI", RFC 2030, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, RFC 2365, July 1998. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2730] Hanna, S., Patel, B. and M. Shah, "Multicast Address Dynamic Client Allocation Protocol (MADCAP), RFC 2730, December 1999. [RFC2770] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", RFC 2770, February 2000. [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers", BCP 37, RFC 2780, March 2000. [RFC2908] Thaler, D., Handley, M. and D.Estrin, "The Internet Multicast Address Allocation Architecture", RFC 2908, September 2000. [RFC2909] Thaler, D., Handley, M. and D. Estrin, "The Multicast Address-Set Claim (MASC) Protocol", RFC 2909, September 2000. [RFC2974] Handley, M., Perkins, C. and E. Whelan, "Session Announcement Protocol", RFC 2974, October 2000. [RFC3138] Meyer, D., "Extended Assignments in 233/8", RFC 3138, June 2001. [SDR] http://www-mice.cs.ucl.ac.uk/multimedia/software/
Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.