draft-ietf-mboned-rfc3171bis-00.txt   draft-ietf-mboned-rfc3171bis-01.txt 
INTERNET-DRAFT Z. Albanna INTERNET-DRAFT Z. Albanna
draft-ietf-mboned-rfc3171bis-00.txt K. Almeroth draft-ietf-mboned-rfc3171bis-01.txt K. Almeroth
M. Cotton
D. Meyer D. Meyer
M. Schipper
Category Best Current Practice Category Best Current Practice
Expires: May 2004 November 2003 Expires: July 2004 January 2004
IANA Guidelines for IPv4 Multicast Address Assignments IANA Guidelines for IPv4 Multicast Address Assignments
<draft-ietf-mboned-rfc3171bis-00.txt> <draft-ietf-mboned-rfc3171bis-01.txt>
Status of this Document Status of this Document
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 43 skipping to change at page 1, line 43
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 RFC 2119 [RFC 2119]. document are to be interpreted as described in RFC 2119 [RFC 2119].
This document is a product of the ABC working group. Comments should This document is a product of the ABC working group. Comments should
be addressed to the authors, or the mailing list at be addressed to the authors, or the mailing list at
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
The Internet Assigned Numbers Authority is charged with allocating The Internet Assigned Numbers Authority is charged with allocating
parameter values for fields in protocols which have been designed, parameter values for fields in protocols which have been designed,
created or are maintained by the Internet Engineering Task Force. created or are maintained by the Internet Engineering Task Force.
This document provides guidelines for the assignment of the IPv4 IP This document provides guidelines for the assignment of the IPv4 IP
multicast address space. multicast address space.
Table of Contents Table of Contents
skipping to change at page 3, line 27 skipping to change at page 3, line 27
7. Source Specific Multicast Block (232/8). . . . . . . . . . . . 6 7. Source Specific Multicast Block (232/8). . . . . . . . . . . . 6
7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 6 7.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 6
8. GLOP Block (233/8) . . . . . . . . . . . . . . . . . . . . . . 7 8. GLOP Block (233/8) . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 7 8.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 7
9. Administratively Scoped Address Block (239/8). . . . . . . . . 7 9. Administratively Scoped Address Block (239/8). . . . . . . . . 7
9.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 7 9.1. Assignment Guidelines . . . . . . . . . . . . . . . . . . . 7
9.1.1. Relative Offsets . . . . . . . . . . . . . . . . . . . . 7 9.1.1. Relative Offsets . . . . . . . . . . . . . . . . . . . . 7
10. Annual Review . . . . . . . . . . . . . . . . . . . . . . . . 8 10. Annual Review . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Address Reclamation. . . . . . . . . . . . . . . . . . . . 8 10.1. Address Reclamation. . . . . . . . . . . . . . . . . . . . 8
11. Use of IANA Reserved Addresses. . . . . . . . . . . . . . . . 8 11. Use of IANA Reserved Addresses. . . . . . . . . . . . . . . . 8
12. Intellectual Property . . . . . . . . . . . . . . . . . . . . 8 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 13. Intellectual Property . . . . . . . . . . . . . . . . . . . . 9
14. Security Considerations . . . . . . . . . . . . . . . . . . . 10 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 15. Security Considerations . . . . . . . . . . . . . . . . . . . 10
16. Informative References. . . . . . . . . . . . . . . . . . . . 11 16. Informative References. . . . . . . . . . . . . . . . . . . . 11
17. Author's Addresses. . . . . . . . . . . . . . . . . . . . . . 12 17. Author's Addresses. . . . . . . . . . . . . . . . . . . . . . 12
18. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 12 18. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 12
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
skipping to change at page 8, line 30 skipping to change at page 8, line 30
The IANA should also review assignments reclaim those addresses that The IANA should also review assignments reclaim those addresses that
are not in use on the global Internet (i.e, those applications which are not in use on the global Internet (i.e, those applications which
can use SSM, GLOP, or Administratively Scoped addressing, or are not can use SSM, GLOP, or Administratively Scoped addressing, or are not
globally routed). globally routed).
11. Use of IANA Reserved Addresses 11. 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.
12. Intellectual Property 12. IANA Considerations
This document provides guidelines for the IANA to use in assiging
IPv4 multicast addresses but does not create any new namespaces for
the IANA to manage.
13. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028]. standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any Copies of claims of rights made available for publication and any
skipping to change at page 9, line 15 skipping to change at page 9, line 27
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
13. Acknowledgments 14. Acknowledgments
The authors would like to thank Randy Bush, John Meylor, Thomas The authors would like to thank Scott Bradner, Randy Bush, John
Narten, Joe St. Sauver, and Beau Williamson for their constructive Meylor, Thomas Narten, Joe St. Sauver, and Beau Williamson for their
feedback and comments. constructive feedback and comments.
14. 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.
15. IANA Considerations
This document creates no new requirements on IANA namespaces
[RFC2434].
16. Informative References 16. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", RFC 2119, March, Indicate Requirement Levels", RFC 2119, March,
1997. 1997.
[RFC2026] Bradner, S., "The Internet Standards Process -- [RFC2026] Bradner, S., "The Internet Standards Process --
Revision 3", RFC 2026/BCP 9, October, 1996. Revision 3", RFC 2026/BCP 9, October, 1996.
[RFC2028] Hovey, R. and S. Bradner, "The Organizations [RFC2028] Hovey, R. and S. Bradner, "The Organizations
skipping to change at page 12, line 16 skipping to change at page 12, line 16
Zaid Albanna Zaid Albanna
Email: zaid@juniper.net Email: zaid@juniper.net
Kevin Almeroth Kevin Almeroth
Email: almeroth@cs.ucsb.edu Email: almeroth@cs.ucsb.edu
David Meyer David Meyer
Email: dmm@1-4-5.net Email: dmm@1-4-5.net
Michelle S. Schipper Michelle S. Cotton
Email: iana@iana.org Email: iana@iana.org
18. Full Copyright Statement 18. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/