draft-ietf-mboned-rfc3171bis-06.txt   draft-ietf-mboned-rfc3171bis-07.txt 
Network Working Group M. Cotton Network Working Group M. Cotton
Internet-Draft L. Vegoda Internet-Draft L. Vegoda
Obsoletes: 3171, 3138 ICANN Obsoletes: 3171, 3138 ICANN
(if approved) D. Meyer (if approved) D. Meyer
Intended status: BCP March 23, 2009 Intended status: BCP April 15, 2009
Expires: September 24, 2009 Expires: October 17, 2009
IANA Guidelines for IPv4 Multicast Address Assignments IANA Guidelines for IPv4 Multicast Address Assignments
draft-ietf-mboned-rfc3171bis-06 draft-ietf-mboned-rfc3171bis-07
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 September 24, 2009. This Internet-Draft will expire on October 17, 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 13 skipping to change at page 2, line 13
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 . . . . . . . . . . . . . . . . . . 5
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 and 6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255,
233.252.0.0 - 233.255.255.255) . . . . . . . . . . . . . . . . 5 224.3.0.0 - 224.4.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 . . . . . . . . . . . . . . . . . . 6
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. AD-HOC Block II . . . . . . . . . . . . . . . . . . . . . 6 9.2. AD-HOC Block III . . . . . . . . . . . . . . . . . . . . . 7
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
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 . . . . . . . . . . . . . . . . . . . . . . . . 10 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
which have been designed, created or are maintained by the Internet which 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
skipping to change at page 4, line 19 skipping to change at page 4, line 19
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 I 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.3.0.0 - 224.4.255.255 (2 /16s) AD-HOC Block II
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 II 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.
skipping to change at page 5, line 9 skipping to change at page 5, line 15
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 that MAY be forwarded through the Internet. Examples include control traffic that MAY be forwarded through the Internet. Examples
224.0.1.1 (NTP [RFC2030]) and 224.0.1.68 (mdhcpdiscover [RFC2730]). include 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 and 233.252.0.0 - 6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255, 224.3.0.0 -
233.255.255.255) 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 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 MAY be globally or Internetwork Control blocks. These addresses MAY be globally
routed and are typically used by applications that require small routed and are typically used by applications that require small
blocks of addressing (e.g., less than a /24 ). Future assignments of blocks of addressing (e.g., less than a /24 ). Future assignments of
blocks of addresses that do not fit in the Local or Internetwork blocks of addresses that do not fit in the Local or Internetwork
block will be made in the Extended block. block will be made in the 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 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] for the current set Approval or Standards Action process. See [IANA] for the current set
of assignments. of assignments.
skipping to change at page 6, line 33 skipping to change at page 6, line 39
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 AD-HOC Block II, or consider using IPv6 ASN should apply for space in AD-HOC Block III, or consider using
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 II 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 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.
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. It SHOULD be TEST-NET" for use in documentation and example code. 233.252.0.0/24
used in conjunction with the [RFC2606] domain names example.com or SHOULD be used in conjunction with the [RFC2606] domain names
example.net in vendor and protocol documentation. Addresses within example.com or example.net in vendor and protocol documentation.
this block MUST NOT appear on the public Internet. Addresses within 233.252.0.0/24 MUST NOT appear on the public
Internet.
10. Administratively Scoped Address Block (239/8) 10. Administratively Scoped Address Block (239/8)
Addresses in the Administratively Scoped Address block are for local Addresses in the Administratively Scoped Address block are for local
use within a domain and are described in [RFC2365]. use 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.
skipping to change at page 7, line 40 skipping to change at page 8, line 5
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]
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/protocols/apply/>
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 AD-HOC Block II. 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 and II 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 decided
and so these will be documented in a future version of this document. 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 infra- Given the dynamic nature of IPv4 multicast and its associated
structure, and the previously undocumented IPv4 multicast address infrastructure, and the previously undocumented IPv4 multicast
assignment guidelines, the IANA should conduct an annual review of address assignment guidelines, the IANA should conduct an annual
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 [RFC1190] blocks and reclaim those Groups", and ST Multicast Groups [RFC1190] 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 which can use SSM, GLOP, or Administratively Scoped
skipping to change at page 8, line 47 skipping to change at page 9, line 7
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 for at least one calendar year. NOT be assigned to anyone other than the last registrant 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
IANA is requested to update its IPv4 multicast request and assignment IANA is requested to update its IPv4 multicast request and assignment
procedures to reflect this document. procedures to reflect this document.
skipping to change at page 9, line 36 skipping to change at page 9, line 41
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)",
 End of changes. 22 change blocks. 
37 lines changed or deleted 38 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/