draft-ietf-mboned-rfc3171bis-05.txt   draft-ietf-mboned-rfc3171bis-06.txt 
Network Working Group M. Cotton Network Working Group M. Cotton
Internet-Draft ICANN Internet-Draft L. Vegoda
Obsoletes: 3171, 3138 D. Meyer Obsoletes: 3171, 3138 ICANN
(if approved) February 3, 2009 (if approved) D. Meyer
Intended status: BCP Intended status: BCP March 23, 2009
Expires: August 7, 2009 Expires: September 24, 2009
IANA Guidelines for IPv4 Multicast Address Assignments IANA Guidelines for IPv4 Multicast Address Assignments
draft-ietf-mboned-rfc3171bis-05 draft-ietf-mboned-rfc3171bis-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 7, 2009. This Internet-Draft will expire on September 24, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
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. RFC 3171 and RFC 3138.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Current Assignment Practice . . . . . . . . . . 3 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 . . . . . . . . . . . . . . . . . . 4 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) . . . . . 5 6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255 and
233.252.0.0 - 233.255.255.255) . . . . . . . . . . . . . . . . 5
6.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5 6.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5
7. SDP/SAP Block (224.2/16) . . . . . . . . . . . . . . . . . . . 5 7. SDP/SAP Block (224.2/16) . . . . . . . . . . . . . . . . . . . 5
7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5 7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 5
8. Source Specific Multicast Block (232/8) . . . . . . . . . . . 6 8. Source Specific Multicast Block (232/8) . . . . . . . . . . . 6
8.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 8.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6
9. GLOP Block (233/8) . . . . . . . . . . . . . . . . . . . . . . 6 9. GLOP Block (233/8) . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 9.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6
9.2. Extended AD-HOC . . . . . . . . . . . . . . . . . . . . . 6 9.2. AD-HOC Block II . . . . . . . . . . . . . . . . . . . . . 6
10. Administratively Scoped Address Block (239/8) . . . . . . . . 7 10. Administratively Scoped Address Block (239/8) . . . . . . . . 7
10.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 7 10.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 7
11. Application Form . . . . . . . . . . . . . . . . . . . . . . . 7 11. Application Form . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Size of assignments of IPv4 Multicast Addresses . . . . . 8 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 . . . . . . . . . . . . . . . . 9 13. Use of IANA Reserved Addresses . . . . . . . . . . . . . . . . 9
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
15. Security Considerations . . . . . . . . . . . . . . . . . . . 9 15. Security Considerations . . . . . . . . . . . . . . . . . . . 9
skipping to change at page 4, line 13 skipping to change at page 4, line 13
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
------------- ---- ----------- ------------- ---- -----------
224.0.0.0 - 224.0.0.255 (/24) Local Network Control Block 224.0.0.0 - 224.0.0.255 (/24) Local Network Control Block
224.0.1.0 - 224.0.1.255 (/24) Internetwork Control Block 224.0.1.0 - 224.0.1.255 (/24) Internetwork Control Block
224.0.2.0 - 224.0.255.255 (65024) AD-HOC Block (1) 224.0.2.0 - 224.0.255.255 (65024) AD-HOC Block I
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.252.0.0 - 224.255.255.255 (/14) RESERVED 224.252.0.0 - 224.255.255.255 (/14) 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 (2) 233.252.0.0 - 233.255.255.255 (/14) AD-HOC Block II
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.
skipping to change at page 5, line 19 skipping to change at page 5, line 19
control that MAY be forwarded through the Internet. Examples include control that MAY be forwarded through the Internet. Examples include
224.0.1.1 (NTP [RFC2030]) and 224.0.1.68 (mdhcpdiscover [RFC2730]). 224.0.1.1 (NTP [RFC2030]) and 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) 6. AD-HOC blocks (including 224.0.2.0 - 224.0.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 were traditionally used for
assignments for those applications that don't fit in either the Local assignments for those applications that don't fit in either the Local
or Internetwork Control blocks. These addresses are globally routed or Internetwork Control blocks. These addresses MAY be globally
and are typically used by applications that require small blocks of routed and are typically used by applications that require small
addressing (e.g., less than a /24 ). Future assignments of blocks of blocks of addressing (e.g., less than a /24 ). Future assignments of
addresses that do not fit in the Local or Internetwork block will be blocks of addresses that do not fit in the Local or Internetwork
made in the Extended block. block will be made in the Extended block.
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 addressing 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 [IANA] for the Approval or Standards Action process. See [IANA] for the current set
current set of assignments. 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 [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
skipping to change at page 6, line 32 skipping to change at page 6, line 33
be used for other purposes. 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 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 32 bit mapping and assignment is defined in [RFC3180]. Domains with 32 bit
ASN should apply for space in the Extended AD-HOC block, or consider ASN should apply for space in AD-HOC Block II, or consider using IPv6
using IPv6 multicast addresses. 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. Extended AD-HOC 9.2. AD-HOC Block II
[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 AS space (233.252.0.0 - 233.255.255.255) mapped by the private AS space
(64512-65534) and the IANA reserved ASN 65535 [RFC1930]. This space (64512-65534) and the IANA reserved ASN 65535 [RFC1930]. This space
was known as eGLOP. RFC 3138 should not have asked the RIRs to was known as eGLOP. RFC 3138 should not have asked the RIRs to
develop policies for the EGLOP space because [RFC2860] reserves that develop policies for the EGLOP space because [RFC2860] reserves that
to the IETF. It is important to make this space available for use by to the IETF. It is important to make this space available for use by
network operators and it is therefore appropriate to obsolete RFC network operators and it is therefore appropriate to obsolete RFC
3138 and classify this address range as available for AD-HOC 3138 and classify this address range as available for AD-HOC
assignment as per the guidelines in section 6. assignment as per the guidelines in section 6.
skipping to change at page 7, line 31 skipping to change at page 7, line 32
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 [IANA]
[IANA] for the current set of assignments. 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: the application form on the IANA web site at:
<http://www.iana.org/cgi-bin/multicast.pl> <http://www.iana.org/cgi-bin/multicast.pl>
It is important to submit sufficient detail to allow the IESG It is important to submit sufficient detail to allow the IESG
designated expert to review the application. If the details given in designated expert to review the application. If the details given in
the request are not clear, or further information is needed, the IESG the 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 the Extended AD-HOC block. cases multiple addresses are available in AD-HOC Block II. Where
Where a very large number of addresses is required, the assignment there is a requirement for a very large number of addresses, the
will be staged, with additional stages only being made after the assignment will be staged. The additional stages will only be made
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 and Extended AD-HOC blocks will be developed addresses in the AD-HOC blocks I and II will be developed and
and published. The format, location and content has not yet been published. The format, location and content has not yet been decided
decided and so these will be documented in a future version of this and so these will be documented in a future version of this document.
document.
12. Annual Review 12. Annual Review
Given the dynamic nature of IPv4 multicast and its associated infra- Given the dynamic nature of IPv4 multicast and its associated infra-
structure, and the previously undocumented IPv4 multicast address structure, and the previously undocumented IPv4 multicast address
assignment guidelines, the IANA should conduct an annual review of assignment guidelines, the IANA should conduct an annual review of
currently assigned addresses. currently assigned addresses.
12.1. Address Reclamation 12.1. Address Reclamation
skipping to change at page 9, line 11 skipping to change at page 9, line 11
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 for at least one calendar year. NOT be assigned for at least 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
This document is all about IANA Considerations. IANA is requested to update its IPv4 multicast request and assignment
procedures 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
RFC3171), Kevin Almeroth (co-author of RFC3171) and Leo Vegoda for RFC3171), Kevin Almeroth (co-author of RFC3171) Pekka Savola and
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.
17.2. Informative References 17.2. Informative References
[I-D.ietf-mboned-addrarch]
Savola, P., "Overview of the Internet Multicast Addressing
Architecture", draft-ietf-mboned-addrarch-05 (work in
progress), October 2006.
[IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/ [IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/
Registration Procedures", Registration Procedures",
<http://www.iana.org/numbers.html>. <http://www.iana.org/numbers.html>.
[RFC1190] Casner, S., Lynn, C., Park, P., Schroder, K., and C. [RFC1190] Casner, S., Lynn, C., Park, P., Schroder, K., and C.
Topolcic, "Experimental Internet Stream Protocol: Version Topolcic, "Experimental Internet Stream Protocol: Version
2 (ST-II)", RFC 1190, October 1990. 2 (ST-II)", RFC 1190, October 1990.
[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)",
skipping to change at page 11, line 17 skipping to change at page 11, line 17
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 90292
United States United States
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
Internet Corporation for Assigned Names and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey 90292
United States
Phone: +310-823-9358
Email: leo.vegoda@icann.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. 20 change blocks. 
41 lines changed or deleted 57 lines changed or added

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