Network Working Group T. Eubanks
Internet-Draft Iformata Communications
Intended status: Informational R. Parekh
Expires: January 14, 2011 S. Venaas
cisco Systems
July 13, 2010
Multicast Addresses for Documentation
draft-venaas-mboned-mcaddrdoc-01.txt
Abstract
This document reserves IPv4 and IPv6 multicast addresses for use in
documentation, RFCs etc. Some multicast addresses are derived from
AS numbers or unicast addresses. This document also explains how
these can be used for documentation purposes by deriving them from AS
numbers and unicast addresses that are reserved for such purposes.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on January 14, 2011.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Eubanks, et al. Expires January 14, 2011 [Page 1]
Internet-Draft Multicast Addresses for Documentation July 2010
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Documentation IPv4 and IPv6 multicast addresses . . . . . . . 4
3. GLOP multicast addresses . . . . . . . . . . . . . . . . . . . 5
4. Unicast prefix based multicast addresses . . . . . . . . . . . 6
5. Other multicast addresses . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Informative References . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Eubanks, et al. Expires January 14, 2011 [Page 2]
Internet-Draft Multicast Addresses for Documentation July 2010
1. Introduction
It is often useful in documentation to give examples containing IP
multicast addresses. To prevent conflicts or confusion, one should
avoid using multicast addresses that may be in actual use. For
unicast there are both IPv4 and IPv6 addresses reserved for this
purpose, see [RFC5737] and [RFC3849] respectively. There are however
no multicast addresses available for such purposes. This document
reserves such addresses.
There are also some multicast addresses that are derived from AS
numbers or unicast addresses. For examples where such addresses are
desired, one should derive them from the AS numbers and unicast
addresses reserved for documentation purposes. This document also
discusses the use of these.
Eubanks, et al. Expires January 14, 2011 [Page 3]
Internet-Draft Multicast Addresses for Documentation July 2010
2. Documentation IPv4 and IPv6 multicast addresses
For documentation where examples of general purpose multicast
addresses are needed, one should use multicast addresses that never
will be assigned or in actual use. There is a risk that addresses
used in examples may accidentally be used. It is then important that
the same addresses are not used by other multicast applications or
services. It may also be beneficial to filter out such addresses
from multicast signalling and multicast data sent to such addresses.
The IPv4 multicast address allocated for documentation purposes is
TBD. The IPv6 multicast address allocated for documentation purposes
is TBD.
Eubanks, et al. Expires January 14, 2011 [Page 4]
Internet-Draft Multicast Addresses for Documentation July 2010
3. GLOP multicast addresses
GLOP [RFC3180] is a method for deriving IPv4 multicast group
addresses from 16 bit AS numbers. For examples where GLOP addresses
are desired, the addresses should be derived from the AS numbers
reserved for documentation use. See [RFC5398].
Eubanks, et al. Expires January 14, 2011 [Page 5]
Internet-Draft Multicast Addresses for Documentation July 2010
4. Unicast prefix based multicast addresses
IPv6 multicast addresses can be derived from IPv6 unicast prefixes.
The two ways currently defined are unicast-prefix based addresses
[RFC3306] and Embedded-RP addresses [RFC3956]. There is also a
proposal for doing this with IPv4
[I-D.ietf-mboned-ipv4-uni-based-mcast]. For examples where these
types of addresses are desired, the addresses should be derived from
the unicast addresses reserved for documentation purposes. For IPv4,
see [RFC5737]. For IPv6, see [RFC3849].
Eubanks, et al. Expires January 14, 2011 [Page 6]
Internet-Draft Multicast Addresses for Documentation July 2010
5. Other multicast addresses
For both IPv4 and IPv6, multicast address ranges have been defined
for link-local, SSM, admin scoped etc. It may be considered to
reserve a multicast address from these ranges for the purpose of
documentation. For IPv6 this can be done by assigning a Group ID,
see [RFC3307]. The question here is how common it is that examples
require a multicast address of a particular non-global scope.
Eubanks, et al. Expires January 14, 2011 [Page 7]
Internet-Draft Multicast Addresses for Documentation July 2010
6. Security Considerations
The use of specific multicast addresses for documentation purposes
has no impact on security.
Eubanks, et al. Expires January 14, 2011 [Page 8]
Internet-Draft Multicast Addresses for Documentation July 2010
7. IANA Considerations
IANA is requested to assign both an IPv4 multicast address and an
IPv6 multicast address for documentation purposes.
Eubanks, et al. Expires January 14, 2011 [Page 9]
Internet-Draft Multicast Addresses for Documentation July 2010
8. Informative References
[I-D.ietf-mboned-ipv4-uni-based-mcast]
Thaler, D., "Unicast-Prefix-based IPv4 Multicast
Addresses", draft-ietf-mboned-ipv4-uni-based-mcast-06
(work in progress), April 2010.
[RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8",
BCP 53, RFC 3180, September 2001.
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", RFC 3306, August 2002.
[RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast
Addresses", RFC 3307, August 2002.
[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
Reserved for Documentation", RFC 3849, July 2004.
[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address",
RFC 3956, November 2004.
[RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", RFC 5398, December 2008.
[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
Reserved for Documentation", RFC 5737, January 2010.
Eubanks, et al. Expires January 14, 2011 [Page 10]
Internet-Draft Multicast Addresses for Documentation July 2010
Authors' Addresses
T.M. Eubanks
Iformata Communications
130 W. Second Street
Dayton, Ohio 45402
US
Phone: +1 703 501 4376
Email: marshall.eubanks@iformata.com
URI: http://www.iformata.com/
Rishabh Parekh
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: riparekh@cisco.com
Stig Venaas
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: stig@cisco.com
Eubanks, et al. Expires January 14, 2011 [Page 11]