draft-ietf-mboned-rfc3171bis-08.txt   rfc5771.txt 
Network Working Group M. Cotton Internet Engineering Task Force (IETF) M. Cotton
Internet-Draft L. Vegoda Request for Comments: 5771 L. Vegoda
Obsoletes: 3171, 3138 ICANN BCP: 51 ICANN
(if approved) D. Meyer Updates: 2780 D. Meyer
Intended status: BCP November 17, 2009 Obsoletes: 3138, 3171 March 2010
Expires: May 21, 2010 Category: Best Current Practice
ISSN: 2070-1721
IANA Guidelines for IPv4 Multicast Address Assignments IANA Guidelines for IPv4 Multicast Address Assignments
draft-ietf-mboned-rfc3171bis-08
Abstract Abstract
This document provides guidance for the Internet Assigned Numbers This document provides guidance for the Internet Assigned Numbers
Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes
RFC 3171 and RFC 3138 and updates RFC 2780. RFC 3171 and RFC 3138 and updates RFC 2780.
Status of this Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This memo documents an Internet Best Current Practice.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 5741.
This Internet-Draft will expire on May 21, 2010. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5771.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology .....................................................3
3. Definition of Current Assignment Practice . . . . . . . . . . 4 3. Definition of Current Assignment Practice .......................3
4. Local Network Control Block (224.0.0/24) . . . . . . . . . . . 4 4. Local Network Control Block (224.0.0/24) ........................4
4.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5 4.1. Assignment Guidelines ......................................4
5. Internetwork Control Block (224.0.1/24) . . . . . . . . . . . 5 5. Internetwork Control Block (224.0.1/24) .........................5
5.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5 5.1. Assignment Guidelines ......................................5
6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255, 6. AD-HOC Blocks (I, II, and III) ..................................5
224.3.0.0 - 224.4.255.255 and 233.252.0.0 - 6.1. Assignment Guidelines ......................................5
233.255.255.255) . . . . . . . . . . . . . . . . . . . . . . . 5 7. SDP/SAP Block (224.2/16) ........................................5
6.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5 7.1. Assignment Guidelines ......................................5
7. SDP/SAP Block (224.2/16) . . . . . . . . . . . . . . . . . . . 6 8. Source-Specific Multicast Block (232/8) .........................6
7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 8.1. Assignment Guidelines ......................................6
8. Source Specific Multicast Block (232/8) . . . . . . . . . . . 6 9. GLOP Block (233/8) ..............................................6
8.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 9.1. Assignment Guidelines ......................................6
9. GLOP Block (233/8) . . . . . . . . . . . . . . . . . . . . . . 6 9.2. AD-HOC Block III ...........................................6
9.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 10. Administratively Scoped Block (239/8) ..........................7
9.2. AD-HOC Block III . . . . . . . . . . . . . . . . . . . . . 7 10.1. Assignment Guidelines .....................................7
10. Administratively Scoped Address Block (239/8) . . . . . . . . 7 10.1.1. Relative Offsets ...................................7
10.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 7 11. Application Form ...............................................7
11. Application Form . . . . . . . . . . . . . . . . . . . . . . . 7 11.1. Size of Assignments of IPv4 Multicast Addresses ...........7
11.1. Size of assignments of IPv4 Multicast Addresses . . . . . 8 12. Annual Review ..................................................8
12. Annual Review . . . . . . . . . . . . . . . . . . . . . . . . 8 12.1. Address Reclamation .......................................8
12.1. Address Reclamation . . . . . . . . . . . . . . . . . . . 8 12.2. Positive Renewal ..........................................8
12.2. Positive renewal . . . . . . . . . . . . . . . . . . . . . 8 13. Use of IANA Reserved Addresses .................................8
13. Use of IANA Reserved Addresses . . . . . . . . . . . . . . . . 9 14. IANA Considerations ............................................8
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 15. Security Considerations ........................................9
15. Security Considerations . . . . . . . . . . . . . . . . . . . 9 16. Acknowledgments ................................................9
16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 17. References .....................................................9
17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 17.1. Normative References ......................................9
17.1. Normative References . . . . . . . . . . . . . . . . . . . 9 17.2. Informative References ....................................9
17.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
The Internet Assigned Numbers Authority (IANA) (www.iana.org) is The Internet Assigned Numbers Authority (IANA) (www.iana.org) is
charged with allocating parameter values for fields in protocols charged with allocating parameter values for fields in protocols that
which have been designed, created or are maintained by the Internet have been designed, created, or are maintained by the Internet
Engineering Task Force (IETF). RFC 2780 [RFC2780] provides the IANA Engineering Task Force (IETF). RFC 2780 [RFC2780] provides the IANA
guidance in the assignment of parameters for fields in newly guidance in the assignment of parameters for fields in newly
developed protocols. This memo expands on section 4.4.2 of RFC 2780 developed protocols. This memo expands on section 4.4.2 of RFC 2780
and attempts to codify existing IANA practice used in the assignment and attempts to codify existing IANA practice used in the assignment
IPv4 multicast addresses. of IPv4 multicast addresses.
This document is a revision of RFC 3171 [RFC3171], which it This document is a revision of RFC 3171 [RFC3171], which it
obsoletes. It also obsoletes RFC 3138 [RFC3138] and updates obsoletes. It also obsoletes RFC 3138 [RFC3138] and updates
[RFC2780]. [RFC2780].
The terms "Specification Required", "Expert Review", "IESG Approval", The terms "Specification Required", "Expert Review", "IESG Approval",
"IETF Review", and "Standards Action", are used in this memo to refer "IETF Review", and "Standards Action", are used in this memo to refer
to the processes described in [RFC5226]. to the processes described in [RFC5226].
In general, due to the relatively small size of the IPv4 multicast In general, due to the relatively small size of the IPv4 multicast
skipping to change at page 3, line 28 skipping to change at page 3, line 17
[RFC2780]. [RFC2780].
The terms "Specification Required", "Expert Review", "IESG Approval", The terms "Specification Required", "Expert Review", "IESG Approval",
"IETF Review", and "Standards Action", are used in this memo to refer "IETF Review", and "Standards Action", are used in this memo to refer
to the processes described in [RFC5226]. to the processes described in [RFC5226].
In general, due to the relatively small size of the IPv4 multicast In general, due to the relatively small size of the IPv4 multicast
address space, further assignment of IPv4 multicast address space is address space, further assignment of IPv4 multicast address space is
recommended only in limited circumstances. Specifically, the IANA recommended only in limited circumstances. Specifically, the IANA
should only assign addresses in those cases where: should only assign addresses in those cases where:
- the dynamic selection Session Description Protocol/Session - the dynamic selection Session Description Protocol/Session
Announcement Protocol (SDP/SAP); Announcement Protocol (SDP/SAP);
- GLOP (not an acronym); - GLOP (not an acronym);
- Source Specific Multicast (SSM); or
- Administratively Scoped address spaces - Source-Specific Multicast (SSM); or
cannot be used. The guidelines described below are reflected in
[IANA-protocols]. Network operators should also be aware of the - Administratively Scoped address spaces cannot be used.
availability of IPv6 multicast addresses and consider using them
where feasible. The guidelines described below are reflected in [IANA-protocols].
Network operators should also be aware of the availability of IPv6
multicast addresses and consider using them where feasible.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
The word "allocation" designates a block of addresses managed by a The word "allocation" designates a block of addresses managed by a
registry for the purpose of making assignments and allocations. The registry for the purpose of making assignments and allocations. The
word "assignment" designates a block of addresses, or a single word "assignment" designates a block of addresses, or a single
address, registered to an end-user for use on a specific network, or address, registered to an end-user for use on a specific network or
set of networks. set of networks.
3. Definition of Current Assignment Practice 3. Definition of Current Assignment Practice
Unlike IPv4 unicast address assignment, where blocks of addresses are Unlike IPv4 unicast address assignment, where blocks of addresses are
delegated to Regional Internet Registries (RIRs), IPv4 multicast delegated to Regional Internet Registries (RIRs), IPv4 multicast
addresses are assigned directly by the IANA. Current registration addresses are assigned directly by the IANA. Current registration
groups appear as follows [IANA]: groups appear as follows [IANA]:
Address Range Size Designation Address Range Size Designation
skipping to change at page 4, line 31 skipping to change at page 4, line 23
224.1.0.0 - 224.1.255.255 (/16) RESERVED 224.1.0.0 - 224.1.255.255 (/16) RESERVED
224.2.0.0 - 224.2.255.255 (/16) SDP/SAP Block 224.2.0.0 - 224.2.255.255 (/16) SDP/SAP Block
224.3.0.0 - 224.4.255.255 (2 /16s) AD-HOC Block II 224.3.0.0 - 224.4.255.255 (2 /16s) AD-HOC Block II
224.5.0.0 - 224.255.255.255 (251 /16s) RESERVED 224.5.0.0 - 224.255.255.255 (251 /16s) RESERVED
225.0.0.0 - 231.255.255.255 (7 /8s) RESERVED 225.0.0.0 - 231.255.255.255 (7 /8s) RESERVED
232.0.0.0 - 232.255.255.255 (/8) Source Specific Multicast Block 232.0.0.0 - 232.255.255.255 (/8) Source-Specific Multicast Block
233.0.0.0 - 233.251.255.255 (16515072) GLOP Block 233.0.0.0 - 233.251.255.255 (16515072) GLOP Block
233.252.0.0 - 233.255.255.255 (/14) AD-HOC Block III 233.252.0.0 - 233.255.255.255 (/14) AD-HOC Block III
234.0.0.0 - 238.255.255.255 (5 /8s) RESERVED 234.0.0.0 - 238.255.255.255 (5 /8s) RESERVED
239.0.0.0 - 239.255.255.255 (/8) Administratively Scoped Block 239.0.0.0 - 239.255.255.255 (/8) Administratively Scoped Block
The IANA generally assigns addresses from the Local Network Control, The IANA generally assigns addresses from the Local Network Control,
Internetwork Control and AD-HOC blocks. Assignment guidelines for Internetwork Control and AD-HOC blocks. Assignment guidelines for
each of these blocks, as well as for the Source Specific Multicast, each of these blocks, as well as for the Source-Specific Multicast,
GLOP and Administratively Scoped Blocks, are described below. GLOP, and Administratively Scoped blocks, are described below.
4. Local Network Control Block (224.0.0/24) 4. Local Network Control Block (224.0.0/24)
Addresses in the Local Network Control block are used for protocol Addresses in the Local Network Control Block are used for protocol
control traffic that is not forwarded off link. Examples of this control traffic that is not forwarded off link. Examples of this
type of use include OSPFIGP All Routers (224.0.0.5) [RFC2328]. type of use include OSPFIGP All Routers (224.0.0.5) [RFC2328].
4.1. Assignment Guidelines 4.1. Assignment Guidelines
Pursuant to section 4.4.2 of [RFC2780], assignments from the Local Pursuant to section 4.4.2 of [RFC2780], assignments from the Local
Network Control block follow an Expert Review, IESG Approval or Network Control Block follow an Expert Review, IESG Approval, or
Standards Action process. See IANA [IANA] for the current set of Standards Action process. See IANA [IANA] for the current set of
assignments. assignments.
5. Internetwork Control Block (224.0.1/24) 5. Internetwork Control Block (224.0.1/24)
Addresses in the Internetwork Control block are used for protocol Addresses in the Internetwork Control Block are used for protocol
control traffic that MAY be forwarded through the Internet. Examples control traffic that MAY be forwarded through the Internet. Examples
include 224.0.1.1 (NTP [RFC4330]) and 224.0.1.68 (mdhcpdiscover include 224.0.1.1 (Network Time Protocol (NTP) [RFC4330]) and
[RFC2730]). 224.0.1.68 (mdhcpdiscover [RFC2730]).
5.1. Assignment Guidelines 5.1. Assignment Guidelines
Pursuant to section 4.4.2 of [RFC2780], assignments from the Pursuant to section 4.4.2 of [RFC2780], assignments from the
Internetwork Control block follow an Expert Review, IESG Approval or Internetwork Control Block follow an Expert Review, IESG Approval, or
Standards Action process. See IANA [IANA] for the current set of Standards Action process. See IANA [IANA] for the current set of
assignments. assignments.
6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255, 224.3.0.0 - 6. AD-HOC Blocks (I, II, and III)
224.4.255.255 and 233.252.0.0 - 233.255.255.255)
Addresses in the AD-HOC blocks were traditionally used for Addresses in the AD-HOC blocks (including 224.0.2.0 - 224.0.255.255,
assignments for those applications that don't fit in either the Local 224.3.0.0 - 224.4.255.255, and 233.252.0.0 - 233.255.255.255) were
or Internetwork Control blocks. These addresses MAY be globally traditionally used for assignments for those applications that don't
routed and are typically used by applications that require small fit in either the Local or Internetwork Control blocks. These
blocks of addressing (e.g., less than a /24 ). Future assignments of addresses MAY be globally routed and are typically used by
blocks of addresses that do not fit in the Local or Internetwork applications that require small blocks of addressing (e.g., less than
block will be made in the Ad-Hoc Block III. a /24 ). Future assignments of blocks of addresses that do not fit
in the Local Network or Internetwork Control blocks will be made in
AD-HOC Block III.
6.1. Assignment Guidelines 6.1. Assignment Guidelines
In general, the IANA SHOULD NOT assign addressing in the AD-HOC In general, the IANA SHOULD NOT assign addresses in the AD-HOC
Blocks. However, the IANA MAY under special circumstances, assign blocks. However, the IANA MAY, under special circumstances, assign
addresses from these blocks. Pursuant to section 4.4.2 of [RFC2780], addresses from these blocks. Pursuant to section 4.4.2 of [RFC2780],
assignments from the AD-HOC blocks follow an Expert Review, IESG assignments from the AD-HOC blocks follow an Expert Review, IESG
Approval or Standards Action process. See [IANA] for the current set Approval, or Standards Action process. See [IANA] for the current
of assignments. set of assignments.
7. SDP/SAP Block (224.2/16) 7. SDP/SAP Block (224.2/16)
Addresses in the SDP/SAP block are used by applications that receive Addresses in the SDP/SAP Block are used by applications that receive
addresses through the Session Announcement Protocol [RFC2974] for use addresses through the Session Announcement Protocol [RFC2974] for use
via applications like the session directory tool (such as SDR [SDR]). via applications like the session directory tool (such as [SDR]).
7.1. Assignment Guidelines 7.1. Assignment Guidelines
Since addresses in the SDP/SAP block are chosen randomly from the Since addresses in the SDP/SAP Block are chosen randomly from the
range of addresses not already in use [RFC2974], no IANA assignment range of addresses not already in use [RFC2974], no IANA assignment
policy is required. Note that while no additional IANA assignment is policy is required. Note that while no additional IANA assignment is
required, addresses in the SDP/SAP block are explicitly for use by required, addresses in the SDP/SAP Block are explicitly for use by
SDP/SAP and MUST NOT be used for other purposes. SDP/SAP and MUST NOT be used for other purposes.
8. Source Specific Multicast Block (232/8) 8. Source-Specific Multicast Block (232/8)
SSM [RFC4607] is an extension of IP Multicast in which traffic is SSM [RFC4607] is an extension of IP Multicast in which traffic is
forwarded to receivers from only those multicast sources for which forwarded to receivers from only those multicast sources for which
the receivers have explicitly expressed interest, and is primarily the receivers have explicitly expressed interest and is primarily
targeted at one-to-many (broadcast) applications. Note that this targeted at one-to-many (broadcast) applications. Note that this
block was initially assigned to the Versatile Message Transaction block was initially assigned to the Versatile Message Transaction
Protocol (VMTP) transient groups [IANA]. Protocol (VMTP) transient groups [IANA].
8.1. Assignment Guidelines 8.1. Assignment Guidelines
Because the SSM model essentially makes the entire multicast address Because the SSM model essentially makes the entire multicast address
space local to the host, no IANA assignment policy is required. space local to the host, no IANA assignment policy is required.
Note, however, that while no additional IANA assignment is required, Note, however, that while no additional IANA assignment is required,
addresses in the SSM block are explicitly for use by SSM and MUST NOT addresses in the Source-Specific Multicast Block are explicitly for
be used for other purposes. use by SSM and MUST NOT be used for other purposes.
9. GLOP Block (233/8) 9. GLOP Block (233/8)
Addresses in the GLOP block are globally scoped statically assigned Addresses in the GLOP Block are globally-scoped, statically-assigned
addresses. The assignment is made, for a domain with 16 bit addresses. The assignment is made, for a domain with a 16-bit
Autonomous System Number (ASN), by mapping a domain's autonomous Autonomous System Number (ASN), by mapping a domain's autonomous
system number, expressed in octets as X.Y, into the middle two octets system number, expressed in octets as X.Y, into the middle two octets
of the GLOP block, yielding an assignment of 233.X.Y.0/24. The of the GLOP Block, yielding an assignment of 233.X.Y.0/24. The
mapping and assignment is defined in [RFC3180]. Domains with a 32 mapping and assignment is defined in [RFC3180]. Domains with a
bit ASN MAY apply for space in AD-HOC Block III, or consider using 32-bit ASN MAY apply for space in AD-HOC Block III, or consider using
IPv6 multicast addresses. IPv6 multicast addresses.
9.1. Assignment Guidelines 9.1. Assignment Guidelines
Because addresses in the GLOP block are algorithmically pre-assigned, Because addresses in the GLOP Block are algorithmically pre-assigned,
no IANA assignment policy is required. no IANA assignment policy is required.
9.2. AD-HOC Block III 9.2. AD-HOC Block III
[RFC3138] delegated to the RIRs the assignment of the GLOP sub-block [RFC3138] delegated to the RIRs the assignment of the GLOP sub-block
(233.252.0.0 - 233.255.255.255) mapped by the private Auronomous (233.252.0.0 - 233.255.255.255) mapped by the private Autonomous
System (AS) space (64512-65534) and the IANA reserved ASN 65535 System (AS) space (64512-65534) and the IANA reserved ASN 65535
[RFC1930]. This space was known as Extended GLOP (EGLOP). RFC 3138 [RFC1930]. This space was known as Extended GLOP (EGLOP). RFC 3138
should not have asked the RIRs to develop policies for the EGLOP should not have asked the RIRs to develop policies for the EGLOP
space because [RFC2860] reserves that to the IETF. It is important space because [RFC2860] reserves that to the IETF. It is important
to make this space available for use by network operators and it is to make this space available for use by network operators, and it is
therefore appropriate to obsolete RFC 3138 and classify this address therefore appropriate to obsolete RFC 3138 and classify this address
range as available for AD-HOC assignment as per the guidelines in range as available for AD-HOC assignment as per the guidelines in
section 6. section 6.
The first /24 in this range, 233.252.0.0/24, is assigned as "MCAST- The first /24 in this range, 233.252.0.0/24, is assigned as "MCAST-
TEST-NET" for use in documentation and example code. 233.252.0.0/24 TEST-NET" for use in documentation and example code. 233.252.0.0/24
SHOULD be used in conjunction with the [RFC2606] domain names SHOULD be used in conjunction with the [RFC2606] domain names
example.com or example.net in vendor and protocol documentation. example.com or example.net in vendor and protocol documentation.
Addresses within 233.252.0.0/24 MUST NOT appear on the public Addresses within 233.252.0.0/24 MUST NOT appear on the public
Internet. Internet.
10. Administratively Scoped Address Block (239/8) 10. Administratively Scoped Block (239/8)
Addresses in the Administratively Scoped Address block are for local Addresses in the Administratively Scoped Block are for local use
use within a domain and are described in [RFC2365]. within a domain and are described in [RFC2365].
10.1. Assignment Guidelines 10.1. Assignment Guidelines
Since addresses in this block are local to a domain, no IANA Since addresses in this block are local to a domain, no IANA
assignment policy is required. assignment policy is required.
10.1.1. Relative Offsets 10.1.1. Relative Offsets
The relative offsets [RFC2365] are used to ensure that a service can The relative offsets [RFC2365] are used to ensure that a service can
be located independent of the extent of the enclosing scope (see be located independent of the extent of the enclosing scope (see
[RFC3180] for details). Since there are only 256 such offsets, the [RFC3180] for details). Since there are only 256 such offsets, the
IANA should only assign a relative offset to a protocol that provides IANA should only assign a relative offset to a protocol that provides
an infrastructure supporting service. Examples of such services an infrastructure supporting service. Examples of such services
include the Session Announcement Protocol [RFC2974]. Pursuant to include the Session Announcement Protocol [RFC2974]. Pursuant to
section 4.4.2 of [RFC2780], assignments of Relative Offsets follow an section 4.4.2 of [RFC2780], assignments of relative offsets follow an
Expert Review, IESG Approval or Standards Action process. See [IANA] Expert Review, IESG Approval, or Standards Action process. See
for the current set of assignments. [IANA] for the current set of assignments.
11. Application Form 11. Application Form
Requests for multicast address assignments can be submitted through Requests for multicast address assignments can be submitted through
the application form on the IANA web site at[IANA-registration]. It the application form on the IANA web site at [IANA-registration]. It
is important to submit sufficient detail to allow the IESG designated is important to submit sufficient detail to allow the IESG designated
expert to review the application. If the details given in the expert to review the application. If the details given in the
request are not clear, or further information is needed, the IESG request are not clear, or further information is needed, the IESG
designated expert may request additional information before assigning designated expert may request additional information before assigning
an address. an address.
11.1. Size of assignments of IPv4 Multicast Addresses 11.1. Size of Assignments of IPv4 Multicast Addresses
Occasionally more than one multicast address is required. In these Occasionally, more than one multicast address is required. In these
cases multiple addresses are available in AD-HOC Block III. Where cases, multiple addresses are available in AD-HOC Block III. Where
there is a requirement for a very large number of addresses, the there is a requirement for a very large number of addresses, the
assignment will be staged. The additional stages will only be made assignment will be staged. The additional stages will only be made
after the complete use of the initial assignment(s). after the complete use of the initial assignment(s).
A separate document describing the policy governing assignment of A separate document describing the policy governing assignment of
addresses in the AD-HOC blocks I, II and III will be developed and addresses in the AD-HOC blocks I, II, and III will be developed and
published. The format, location and content has not yet been decided published. The format, location, and content has not yet been
and so these will be documented in a future version of this document. decided and so these will be documented in a future version of this
document.
12. Annual Review 12. Annual Review
Given the dynamic nature of IPv4 multicast and its associated Given the dynamic nature of IPv4 multicast and its associated
infrastructure, and the previously undocumented IPv4 multicast infrastructure, and the previously undocumented IPv4 multicast
address assignment guidelines, the IANA should conduct an annual address assignment guidelines, the IANA should conduct an annual
review of currently assigned addresses. review of currently assigned addresses.
12.1. Address Reclamation 12.1. Address Reclamation
During the review described above, addresses that were mis-assigned During the review described above, addresses that were mis-assigned
should, where possible, be reclaimed or reassigned. should, where possible, be reclaimed or reassigned.
The IANA should also review assignments in the AD-HOC, "DIS Transient The IANA should also review assignments in the AD-HOC, "DIS Transient
Groups", and ST Multicast Groups [RFC1819] blocks and reclaim those Groups", and ST Multicast Groups [RFC1819] blocks and reclaim those
addresses that are not in use on the global Internet (i.e, those addresses that are not in use on the global Internet (i.e., those
applications which can use SSM, GLOP, or Administratively Scoped applications that can use SSM, GLOP, or Administratively Scoped
addressing, or are not globally routed). addressing, or are not globally routed).
12.2. Positive renewal 12.2. Positive Renewal
It is occasionally appropriate to make temporary assignments that can It is occasionally appropriate to make temporary assignments that can
be renewed as necessary. In cases where this happens the registrant be renewed as necessary. In cases where this happens the registrant
needs to positively request an extension to the temporary assignment needs to positively request an extension to the temporary assignment
or the addresses assigned. When the IANA has not received a request or the addresses assigned. When the IANA has not received a request
to renew the registration of a temporary assignment within 30 days of to renew the registration of a temporary assignment within 30 days of
the expiry of the assignment it MUST be removed from the multicast the expiry of the assignment, it MUST be removed from the multicast
registry. registry.
Addresses returned to the IANA when a temporary assignment ends MUST Addresses returned to the IANA when a temporary assignment ends MUST
NOT be assigned to anyone other than the last registrant for at least NOT be assigned to anyone other than the last registrant for at least
one calendar year. one calendar year.
13. Use of IANA Reserved Addresses 13. Use of IANA Reserved Addresses
Applications MUST NOT use addressing in the IANA reserved blocks. Applications MUST NOT use addressing in the IANA reserved blocks.
14. IANA Considerations 14. IANA Considerations
IANA is requested to update its IPv4 multicast request and assignment IANA has updated its IPv4 multicast request and assignment procedures
procedures to reflect this document. to reflect this document.
15. Security Considerations 15. Security Considerations
The assignment guidelines described in this document do not alter the The assignment guidelines described in this document do not alter the
security properties of either the Any Source or Source Specific security properties of either the Any Source or Source-Specific
multicast service models. Multicast service models.
16. Acknowledgments 16. Acknowledgments
The authors would like to thank Joe St. Sauver, John Meylor, Randy The authors would like to thank Joe St. Sauver, John Meylor, Randy
Bush, Thomas Narten, Marshall Eubanks, Zaid Albanna (co-author of Bush, Thomas Narten, Marshall Eubanks, Zaid Albanna (co-author of RFC
RFC3171), Kevin Almeroth (co-author of RFC3171) Pekka Savola and 3171), Kevin Almeroth (co-author of RFC 3171), Pekka Savola, and
Alfred Hoenes for their constructive feedback and comments. Alfred Hoenes for their constructive feedback and comments.
17. References 17. References
17.1. Normative References 17.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
May 2008. 2008.
17.2. Informative References 17.2. Informative References
[IANA] IANA, "IANA Protocol Registries", <http://www.iana.org/>. [IANA] IANA, "IANA Protocol Registries", <http://www.iana.org/>.
[IANA-protocols] [IANA-protocols]
IANA, "IANA Protocol Registries", IANA, "IANA Protocol Registries",
<http://www.iana.org/protocols>. <http://www.iana.org/protocols>.
[IANA-registration] [IANA-registration]
IANA, "IANA Protocol Registration Forms", IANA, "IANA Protocol Registration Forms",
<http://www.iana.org/protocols>. <http://www.iana.org/protocols/apply>.
[RFC1819] Delgrossi, L., Berger, L., Duong, D., Jackowski, S., and [RFC1819] Delgrossi, L., Ed., and L. Berger, Ed., "Internet Stream
S. Schaller, "Internet Stream Protocol Version 2 (ST2) Protocol Version 2 (ST2) Protocol Specification - Version
Protocol Specification - Version ST2+", RFC 1819, ST2+", RFC 1819, August 1995.
August 1995.
[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,
selection, and registration of an Autonomous System (AS)", selection, and registration of an Autonomous System (AS)",
BCP 6, RFC 1930, March 1996. BCP 6, RFC 1930, March 1996.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23,
RFC 2365, July 1998. RFC 2365, July 1998.
[RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS [RFC2606] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999. Names", BCP 32, RFC 2606, June 1999.
[RFC2730] Hanna, S., Patel, B., and M. Shah, "Multicast Address [RFC2730] Hanna, S., Patel, B., and M. Shah, "Multicast Address
Dynamic Client Allocation Protocol (MADCAP)", RFC 2730, Dynamic Client Allocation Protocol (MADCAP)", RFC 2730,
December 1999. December 1999.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers", Values In the Internet Protocol and Related Headers", BCP
BCP 37, RFC 2780, March 2000. 37, RFC 2780, March 2000.
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Understanding Concerning the Technical Work of the Internet
Internet Assigned Numbers Authority", RFC 2860, June 2000. Assigned Numbers Authority", RFC 2860, June 2000.
[RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session [RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session
Announcement Protocol", RFC 2974, October 2000. Announcement Protocol", RFC 2974, October 2000.
[RFC3138] Meyer, D., "Extended Assignments in 233/8", RFC 3138, [RFC3138] Meyer, D., "Extended Assignments in 233/8", RFC 3138, June
June 2001. 2001.
[RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper, [RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,
"IANA Guidelines for IPv4 Multicast Address Assignments", "IANA Guidelines for IPv4 Multicast Address Assignments",
BCP 51, RFC 3171, August 2001. BCP 51, RFC 3171, August 2001.
[RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", [RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", BCP
BCP 53, RFC 3180, September 2001. 53, RFC 3180, September 2001.
[RFC4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4 [RFC4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", RFC 4330, January 2006. for IPv4, IPv6 and OSI", RFC 4330, January 2006.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006. IP", RFC 4607, August 2006.
[SDR] UCL/ISI, "Session Directory Tool", [SDR] University College London / ISI, "Session Directory Tool",
<http://www-mice.cs.ucl.ac.uk/multimedia/software/sdr/>. <http://www-mice.cs.ucl.ac.uk/multimedia/software/sdr/>.
Authors' Addresses Authors' Addresses
Michelle Cotton Michelle Cotton
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey 90292 Marina del Rey, CA 90292
United States of America United States of America
Phone: +310-823-9358 Phone: +310-823-9358
Email: michelle.cotton@icann.org EMail: michelle.cotton@icann.org
URI: http://www.iana.org/ URI: http://www.iana.org/
Leo Vegoda Leo Vegoda
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey 90292 Marina del Rey, CA 90292
United States of America United States of America
Phone: +310-823-9358 Phone: +310-823-9358
Email: leo.vegoda@icann.org EMail: leo.vegoda@icann.org
URI: http://www.iana.org/ URI: http://www.iana.org/
David Meyer David Meyer
Email: dmm@1-4-5.net EMail: dmm@1-4-5.net
 End of changes. 76 change blocks. 
183 lines changed or deleted 177 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/