draft-ietf-mboned-rfc3171bis-07.txt   draft-ietf-mboned-rfc3171bis-08.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 April 15, 2009 Intended status: BCP November 17, 2009
Expires: October 17, 2009 Expires: May 21, 2010
IANA Guidelines for IPv4 Multicast Address Assignments IANA Guidelines for IPv4 Multicast Address Assignments
draft-ietf-mboned-rfc3171bis-07 draft-ietf-mboned-rfc3171bis-08
Abstract
This document provides guidance for the Internet Assigned Numbers
Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes
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 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 40
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 October 17, 2009. This Internet-Draft will expire on May 21, 2010.
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
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This document provides guidance for the Internet Assigned Numbers described in the BSD License.
Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes
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 . . . . . . . . . . 4
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 . . . . . . . . . . . . . . . . . . 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, 6. AD-HOC blocks (including 224.0.2.0 - 224.0.255.255,
224.3.0.0 - 224.4.255.255 and 233.252.0.0 - 224.3.0.0 - 224.4.255.255 and 233.252.0.0 -
233.255.255.255) . . . . . . . . . . . . . . . . . . . . . . . 5 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) . . . . . . . . . . . . . . . . . . . 6
7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . 6 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 III . . . . . . . . . . . . . . . . . . . . . 7 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
skipping to change at page 3, line 17 skipping to change at page 3, line 17
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
IPv4 multicast addresses. 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]. obsoletes. It also obsoletes RFC 3138 [RFC3138] and updates
[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 the dynamic should only assign addresses in those cases where:
selection (SDP/SAP), GLOP, SSM or Administratively Scoped address - the dynamic selection Session Description Protocol/Session
spaces cannot be used. The guidelines described below are reflected Announcement Protocol (SDP/SAP);
in <http://www.iana.org/numbers.html>. Network operators should also - GLOP (not an acronym);
be aware of the availability of IPv6 multicast addresses and consider - Source Specific Multicast (SSM); or
using them where feasible. - Administratively Scoped address spaces
cannot be used. 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
skipping to change at page 5, line 16 skipping to change at page 5, line 18
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 [RFC2030]) and 224.0.1.68 (mdhcpdiscover include 224.0.1.1 (NTP [RFC4330]) and 224.0.1.68 (mdhcpdiscover
[RFC2730]). [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 (including 224.0.2.0 - 224.0.255.255, 224.3.0.0 -
skipping to change at page 6, line 16 skipping to change at page 6, line 21
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)
The Source Specific Multicast (SSM) is an extension of IP Multicast SSM [RFC4607] is an extension of IP Multicast in which traffic is
in which traffic is forwarded to receivers from only those multicast forwarded to receivers from only those multicast sources for which
sources for which the receivers have explicitly expressed interest, the receivers have explicitly expressed interest, and is primarily
and is primarily targeted at one-to-many (broadcast) applications. targeted at one-to-many (broadcast) applications. Note that this
Note that this block was initially assigned to the VMTP transient block was initially assigned to the Versatile Message Transaction
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 SSM block are explicitly for use by SSM and MUST NOT
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 a 32
ASN should apply for space in AD-HOC Block III, or consider using 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 AS space (233.252.0.0 - 233.255.255.255) mapped by the private Auronomous
(64512-65534) and the IANA reserved ASN 65535 [RFC1930]. This space System (AS) space (64512-65534) and the IANA reserved ASN 65535
was known as eGLOP. RFC 3138 should not have asked the RIRs to [RFC1930]. This space was known as Extended GLOP (EGLOP). RFC 3138
develop policies for the EGLOP space because [RFC2860] reserves that should not have asked the RIRs to develop policies for the EGLOP
to the IETF. It is important to make this space available for use by space because [RFC2860] reserves that to the IETF. It is important
network operators and it is therefore appropriate to obsolete RFC to make this space available for use by network operators and it is
3138 and classify this address range as available for AD-HOC therefore appropriate to obsolete RFC 3138 and classify this address
assignment as per the guidelines in section 6. range as available for AD-HOC 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. 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 Address Block (239/8)
skipping to change at page 7, line 49 skipping to change at page 7, line 50
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]
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[IANA-registration]. It
is important to submit sufficient detail to allow the IESG designated
<http://www.iana.org/protocols/apply/> expert to review the application. If the details given in the
request are not clear, or further information is needed, the IESG
It is important to submit sufficient detail to allow the IESG
designated expert to review the application. If the details given in
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 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).
skipping to change at page 8, line 39 skipping to change at page 8, line 36
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 [RFC1190] 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 which 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
skipping to change at page 9, line 39 skipping to change at page 9, line 38
RFC3171), Kevin Almeroth (co-author of RFC3171) Pekka Savola and RFC3171), Kevin Almeroth (co-author of RFC3171) 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
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
17.2. Informative References 17.2. Informative References
[IANA] IANA, "IANA Matrix for Protocol Parameter Assignment/ [IANA] IANA, "IANA Protocol Registries", <http://www.iana.org/>.
Registration Procedures",
<http://www.iana.org/numbers.html>.
[RFC1190] Casner, S., Lynn, C., Park, P., Schroder, K., and C. [IANA-protocols]
Topolcic, "Experimental Internet Stream Protocol: Version IANA, "IANA Protocol Registries",
2 (ST-II)", RFC 1190, October 1990. <http://www.iana.org/protocols>.
[IANA-registration]
IANA, "IANA Protocol Registration Forms",
<http://www.iana.org/protocols>.
[RFC1819] Delgrossi, L., Berger, L., Duong, D., Jackowski, S., and
S. Schaller, "Internet Stream Protocol Version 2 (ST2)
Protocol Specification - Version ST2+", RFC 1819,
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.
[RFC2030] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", RFC 2030, October 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, 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,
skipping to change at page 10, line 46 skipping to change at page 11, line 5
[RFC3138] Meyer, D., "Extended Assignments in 233/8", RFC 3138, [RFC3138] Meyer, D., "Extended Assignments in 233/8", RFC 3138,
June 2001. June 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 53, RFC 3180, September 2001. BCP 53, RFC 3180, September 2001.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
IANA Considerations Section in RFCs", BCP 26, RFC 5226, for IPv4, IPv6 and OSI", RFC 4330, January 2006.
May 2008.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006.
[SDR] UCL/ISI, "Session Directory Tool",
<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 90292
United States 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 90292
United States 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. 21 change blocks. 
62 lines changed or deleted 82 lines changed or added

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