draft-ietf-mboned-mcaddrdoc-01.txt   draft-ietf-mboned-mcaddrdoc-02.txt 
Network Working Group T. Chown Network Working Group S. Venaas
Internet-Draft University of Southampton Internet-Draft R. Parekh
Intended status: Informational M. Eubanks Intended status: Informational G. Van de Velde
Expires: January 9, 2012 Iformata Communications Expires: April 27, 2012 cisco Systems
R. Parekh T. Chown
G. Van de Velde University of Southampton
S. Venaas M. Eubanks
cisco Systems Iformata Communications
July 8, 2011 October 25, 2011
Multicast Addresses for Documentation Multicast Addresses for Documentation
draft-ietf-mboned-mcaddrdoc-01.txt draft-ietf-mboned-mcaddrdoc-02.txt
Abstract Abstract
This document discusses which multicast addresses should be used for This document discusses which multicast addresses should be used for
documentation purposes and reserves multicast addresses for such use. documentation purposes and reserves multicast addresses for such use.
Some multicast addresses are derived from AS numbers or unicast Some multicast addresses are derived from AS numbers or unicast
addresses. This document also explains how these can be used for addresses. This document also explains how these can be used for
documentation purposes. documentation purposes.
Status of this Memo Status of this Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on January 9, 2012. This Internet-Draft will expire on April 27, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 17 skipping to change at page 2, line 17
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IPv4 multicast documentation addresses . . . . . . . . . . . . 4 2. IPv4 multicast documentation addresses . . . . . . . . . . . . 4
2.1. Administratively scoped IPv4 multicast addresses . . . . . 4 2.1. Administratively scoped IPv4 multicast addresses . . . . . 4
2.2. GLOP multicast addresses . . . . . . . . . . . . . . . . . 4 2.2. GLOP multicast addresses . . . . . . . . . . . . . . . . . 4
2.3. Unicast prefix based IPv4 multicast addresses . . . . . . 4 2.3. Unicast prefix based IPv4 multicast addresses . . . . . . 4
3. IPv6 multicast documentation addresses . . . . . . . . . . . . 5 3. IPv6 multicast documentation addresses . . . . . . . . . . . . 6
3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 5 3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 6
3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 5 3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
7. Informative References . . . . . . . . . . . . . . . . . . . . 9 7. Informative References . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 10
A.1. GLOP multicast addresses . . . . . . . . . . . . . . . . . 10
A.2. Unicast prefix based IPv4 multicast addresses . . . . . . 10
A.3. Unicast prefix based IPv6 multicast addresses . . . . . . 10
A.4. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
It is often useful in documentation, IETF documents, etc., to provide It is often useful in documentation, IETF documents, etc., to provide
examples containing IP multicast addresses. For documentation where examples containing IP multicast addresses. For documentation where
examples of general purpose multicast addresses are needed, one examples of general purpose multicast addresses are needed, one
should use multicast addresses that never will be assigned or in should use multicast addresses that never will be assigned or in
actual use. There is a risk that addresses used in examples may actual use. There is a risk that addresses used in examples may
accidentally be used. It is then important that the same addresses accidentally be used. It is then important that the same addresses
skipping to change at page 4, line 16 skipping to change at page 4, line 16
The type of multicast addresses most commonly used today, are The type of multicast addresses most commonly used today, are
addresses used for so-called ASM (Any-Source Multicast). For ASM, addresses used for so-called ASM (Any-Source Multicast). For ASM,
the IPv4 multicast addresses allocated for documentation purposes are the IPv4 multicast addresses allocated for documentation purposes are
233.252.0.0 - 233.252.0.255 (233.252.0.0/24). 233.252.0.0 - 233.252.0.255 (233.252.0.0/24).
Another type of multicast is SSM (Source-Specific Multicast). For Another type of multicast is SSM (Source-Specific Multicast). For
SSM it is less important which multicast addresses are used, since a SSM it is less important which multicast addresses are used, since a
host/application joins a channel identified by both source and group. host/application joins a channel identified by both source and group.
Any source addresses used in SSM examples should be unicast addresses Any source addresses used in SSM examples should be unicast addresses
reserved for documentation purposes, see [RFC5737]. reserved for documentation purposes. There are three unicast address
ranges provided for documentation use in [RFC5737]. The ranges are
192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24.
Sometimes one wants to give examples where a specific type of address Sometimes one wants to give examples where a specific type of address
is desired. E.g. for text about multicast scoping, one might want is desired. E.g. for text about multicast scoping, one might want
the examples to use addresses that are to be used for administrative the examples to use addresses that are to be used for administrative
scoping. See below for guidance on how to construct specific types scoping. See below for guidance on how to construct specific types
of example addresses. of example addresses.
2.1. Administratively scoped IPv4 multicast addresses 2.1. Administratively scoped IPv4 multicast addresses
Administratively scoped IPv4 multicast addresses [RFC2365] are Administratively scoped IPv4 multicast addresses [RFC2365] are
skipping to change at page 4, line 38 skipping to change at page 4, line 40
organization. Apart from a small set of scope relative addresses, organization. Apart from a small set of scope relative addresses,
these addresses are not assigned. There are no specific scoped these addresses are not assigned. There are no specific scoped
addresses available for documentation purposes. Except for examples addresses available for documentation purposes. Except for examples
detailing the use of scoped multicast, one should avoid using them. detailing the use of scoped multicast, one should avoid using them.
2.2. GLOP multicast addresses 2.2. GLOP multicast addresses
GLOP [RFC3180] is a method for deriving IPv4 multicast group GLOP [RFC3180] is a method for deriving IPv4 multicast group
addresses from 16 bit AS numbers. For examples where GLOP addresses addresses from 16 bit AS numbers. For examples where GLOP addresses
are desired, the addresses should be derived from the AS numbers are desired, the addresses should be derived from the AS numbers
reserved for documentation use. See [RFC5398]. reserved for documentation use.
The 16 bit AS numbers reserved for documentation use in [RFC5398] are
64496 - 64511. By use of [RFC3180], we then get 16 /24 multicast
prefixes for documentation use. The first one 233.251.240.0/24, and
the last 233.251.255.0/24.
2.3. Unicast prefix based IPv4 multicast addresses 2.3. Unicast prefix based IPv4 multicast addresses
IPv4 multicast addresses can be derived from IPv4 unicast prefixes, IPv4 multicast addresses can be derived from IPv4 unicast prefixes,
see [RFC6034]. For examples where this type of addresses are see [RFC6034]. For examples where this type of addresses are
desired, the addresses should be derived from the unicast addresses desired, the addresses should be derived from the unicast addresses
reserved for documentation purposes, see [RFC5737]. reserved for documentation purposes, see [RFC5737].
There are three unicast address ranges provided for documentation use
in [RFC5737]. The ranges are 192.0.2.0/24, 198.51.100.0/24 and
203.0.113.0/24. Using [RFC6034] this leaves us with the unicast
prefix based IPv4 multicast addresses 234.192.0.2, 234.198.51.100 and
234.203.0.113.
3. IPv6 multicast documentation addresses 3. IPv6 multicast documentation addresses
The type of multicast addresses most commonly used today, are The type of multicast addresses most commonly used today, are
addresses used for so-called ASM (Any-Source Multicast). For ASM, addresses used for so-called ASM (Any-Source Multicast). For ASM,
the IPv6 multicast addresses allocated for documentation purposes are the IPv6 multicast addresses allocated for documentation purposes are
TBD. TBD.
Another type of multicast is SSM (Source-Specific Multicast). For Another type of multicast is SSM (Source-Specific Multicast). For
SSM it is less important which multicast addresses are used, since a SSM it is less important which multicast addresses are used, since a
host/application joins a channel identified by both source and group. host/application joins a channel identified by both source and group.
Any source addresses used in SSM examples should be unicast addresses Any source addresses used in SSM examples should be unicast addresses
reserved for documentation purposes, see [RFC3849]. reserved for documentation purposes. The IPv6 unicast prefix
reserved for documentation purposes is 2001:DB8::/32, see [RFC3849].
Sometimes one wants to give examples where a specific type of address Sometimes one wants to give examples where a specific type of address
is desired. E.g. for text about multicast scoping, one might want is desired. E.g. for text about multicast scoping, one might want
the examples to use addresses that are to be used for administrative the examples to use addresses that are to be used for administrative
scoping. See below for guidance on how to construct specific types scoping. See below for guidance on how to construct specific types
of example addresses. of example addresses.
3.1. Unicast prefix based IPv6 multicast addresses 3.1. Unicast prefix based IPv6 multicast addresses
IPv6 multicast addresses can be derived from IPv6 unicast prefixes, IPv6 multicast addresses can be derived from IPv6 unicast prefixes,
see [RFC3306]. For examples where this type of addresses is desired, see [RFC3306]. For examples where this type of addresses is desired,
the addresses should be derived from the unicast addresses reserved the addresses should be derived from the unicast addresses reserved
for documentation purposes, see [RFC3849]. for documentation purposes.
The IPv6 unicast prefix reserved for documentation purposes is 2001:
DB8::/32, see [RFC3849]. This allows a wide range of different IPv6
multicast addresses. Using just the base /32 prefix, one get the
IPv6 multicast prefixes FF3X:20:2001:DB8::/64, one for each available
scope X. One can also produce longer prefixes from this. Just as an
example, one can pick say a /64 prefix 2001:DB8:DEAD:BEEF::/64 which
gives the multicast prefixes FF3X:40:2001:DB8:DEAD:BEEF::/96, one for
each available scope X.
3.2. Embedded-RP IPv6 multicast addresses 3.2. Embedded-RP IPv6 multicast addresses
There is a type of IPv6 multicast addresses called Embedded-RP There is a type of IPv6 multicast addresses called Embedded-RP
addresses where the IPv6 address of a Rendezvous-Point is embedded addresses where the IPv6 address of a Rendezvous-Point is embedded
inside the multicast address, see [RFC3956]. For examples where this inside the multicast address, see [RFC3956]. For examples where this
type of addresses is desired, the addresses should be derived from type of addresses is desired, the addresses should be derived from
the unicast addresses reserved for documentation purposes, see see the unicast addresses reserved for documentation purposes, see see
[RFC3849]. [RFC3849].
For documentation purposes, the RP address can be any address from
the range 2001:DB8::/32 that follows the constraints specified in
[RFC3956]. One example address could be 2001:DB8::1. The
embedded-RP multicast prefixes might then be FF7X:120:2001:DB8::/96.
Another example could be the RP address 2001:DB8:BEEF:FEED::7 which
gives the prefixes FF7X:740:2001:DB8:BEEF:FEED::/96. See also the
examples in [RFC3956].
4. Security Considerations 4. Security Considerations
The use of specific multicast addresses for documentation purposes The use of specific multicast addresses for documentation purposes
has no impact on security. has no impact on security.
5. IANA Considerations 5. IANA Considerations
IANA is requested to assign "variable scope" IPv6 multicast addresses IANA is requested to assign "variable scope" IPv6 multicast addresses
for documentation purposes. This should be a /96 prefix of the form for documentation purposes. This should be a /96 prefix of the form
FF0X:... FF0X:... The word TBD in this text should be replaced with the
assigned prefix, and this sentence should be deleted before
publishing.
6. Acknowledgments 6. Acknowledgments
The authors thank Roberta Maglione for providing comments on this The authors thank Roberta Maglione and Leonard Giuliano for providing
document. comments on this document.
7. Informative References 7. Informative References
[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.
[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.
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
skipping to change at page 10, line 5 skipping to change at page 12, line 5
[RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for [RFC5398] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", RFC 5398, December 2008. Documentation Use", RFC 5398, December 2008.
[RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks [RFC5737] Arkko, J., Cotton, M., and L. Vegoda, "IPv4 Address Blocks
Reserved for Documentation", RFC 5737, January 2010. Reserved for Documentation", RFC 5737, January 2010.
[RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast [RFC6034] Thaler, D., "Unicast-Prefix-Based IPv4 Multicast
Addresses", RFC 6034, October 2010. Addresses", RFC 6034, October 2010.
Appendix A. Examples Authors' Addresses
Usually addresses for documentation can simply be selected from the
addresses reserved for such. But as we discuss in this document,
there are cases where one wants to use multicast addresses derived
from AS numbers (GLOP) or from unicast addresses. In this appendix
we will just provide some examples for how such addresses can be
derived.
A.1. GLOP multicast addresses
GLOP [RFC3180] is a method for deriving IPv4 multicast group
addresses from 16 bit AS numbers. The 16 bit AS numbers reserved for
documentation use in [RFC5398] are 64496 - 64511. By use of
[RFC3180], we then get 16 /24 multicast prefixes for documentation
use. The first one 233.251.240.0/24, and the last 233.251.255.0/24.
A.2. Unicast prefix based IPv4 multicast addresses
IPv4 multicast addresses can be derived from IPv4 unicast prefixes,
see [RFC6034]. There are three unicast address ranges provided for
documentation use in [RFC5737]. The ranges are 192.0.2.0/24,
198.51.100.0/24 and 203.0.113.0/24. Using [RFC6034] this leaves us
with the unicast prefix based IPv4 multicast addresses 234.192.0.2,
234.198.51.100 and 234.203.0.113.
A.3. Unicast prefix based IPv6 multicast addresses Stig Venaas
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
IPv6 multicast addresses can be derived from IPv6 unicast prefixes, Email: stig@cisco.com
see [RFC3306]. The IPv6 unicast prefix reserved for documentation
purposes is 2001:DB8::/32, see [RFC3849]. This allows a wide range
of different IPv6 multicast addresses. Using just the base /32
prefix, one get the IPv6 multicast prefixes FF3X:20:2001:DB8::/64,
one for each available scope X. But also, from 2001:DB8::/32 one can
pick say a /64 prefix 2001:DB8:DEAD:BEEF::/64 which gives us the
multicast prefixes FF3X:40:2001:DB8:DEAD:BEEF::/96, one for each
available scope X.
A.4. Embedded-RP IPv6 multicast addresses Rishabh Parekh
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
For Embedded-RP IPv6 multicast addresses, the the IPv6 address of a Email: riparekh@cisco.com
Rendezvous-Point is embedded inside the multicast address, see
[RFC3956]. For documentation purposes, the RP address can be any
address from the range 2001:DB8::/32, see [RFC3849], that follows the
constraints specified in [RFC3956]. One example address could be
2001:DB8::1. The embedded-RP multicast prefixes might then be FF7X:
120:2001:DB8::/96. Another example could be the RP address 2001:DB8:
BEEF:FEED::7 which gives the prefixes FF7X:740:2001:DB8:BEEF:
FEED::/96. See also the examples in [RFC3956]. Gunter Van de Velde
cisco Systems
De Kleetlaan 6a
Diegem 1831
Belgium
Authors' Addresses Phone: +32 476 476 022
Email: gvandeve@cisco.com
Tim Chown Tim Chown
University of Southampton University of Southampton
Highfield Highfield
Southampton, Hampshire SO17 1BJ Southampton, Hampshire SO17 1BJ
United Kingdom United Kingdom
Email: tjc@ecs.soton.ac.uk Email: tjc@ecs.soton.ac.uk
Marshall Eubanks Marshall Eubanks
Iformata Communications Iformata Communications
130 W. Second Street 130 W. Second Street
Dayton, Ohio 45402 Dayton, Ohio 45402
US US
Phone: +1 703 501 4376 Phone: +1 703 501 4376
Email: marshall.eubanks@iformata.com Email: marshall.eubanks@iformata.com
URI: http://www.iformata.com/ URI: http://www.iformata.com/
Rishabh Parekh
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: riparekh@cisco.com
Gunter Van de Velde
cisco Systems
De Kleetlaan 6a
Diegem 1831
Belgium
Phone: +32 476 476 022
Email: gvandeve@cisco.com
Stig Venaas
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: stig@cisco.com
 End of changes. 21 change blocks. 
77 lines changed or deleted 78 lines changed or added

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