draft-ietf-mboned-mcaddrdoc-00.txt   draft-ietf-mboned-mcaddrdoc-01.txt 
Network Working Group T. Chown Network Working Group T. Chown
Internet-Draft University of Southampton Internet-Draft University of Southampton
Intended status: Informational M. Eubanks Intended status: Informational M. Eubanks
Expires: November 6, 2011 Iformata Communications Expires: January 9, 2012 Iformata Communications
R. Parekh R. Parekh
G. Van de Velde G. Van de Velde
S. Venaas S. Venaas
cisco Systems cisco Systems
May 5, 2011 July 8, 2011
Multicast Addresses for Documentation Multicast Addresses for Documentation
draft-ietf-mboned-mcaddrdoc-00.txt draft-ietf-mboned-mcaddrdoc-01.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 November 6, 2011. This Internet-Draft will expire on January 9, 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 24 skipping to change at page 2, line 24
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 . . . . . . . . . . . . 5
3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 5 3.1. Unicast prefix based IPv6 multicast addresses . . . . . . 5
3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 5 3.2. Embedded-RP IPv6 multicast addresses . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
7. Informative References . . . . . . . . . . . . . . . . . . . . 9 7. Informative References . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 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
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
are not used by other multicast applications or services. It may are not used by other multicast applications or services. It may
skipping to change at page 10, line 5 skipping to change at page 10, 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
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
IPv6 multicast addresses can be derived from IPv6 unicast prefixes,
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
For Embedded-RP IPv6 multicast addresses, the the IPv6 address of a
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].
Authors' Addresses Authors' Addresses
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
 End of changes. 6 change blocks. 
5 lines changed or deleted 61 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/