draft-ietf-ipv6-link-scoped-mcast-01.txt   draft-ietf-ipv6-link-scoped-mcast-02.txt 
INTERNET DRAFT Jung-Soo Park INTERNET DRAFT Jung-Soo Park
Expires: October 2002 Myung-Ki Shin Expires: April 2003 Myung-Ki Shin
Yong-Jin Kim
ETRI ETRI
April 2002 October 2002
Link Scoped IPv6 Multicast Addresses Link Scoped IPv6 Multicast Addresses
<draft-ietf-ipv6-link-scoped-mcast-01.txt> <draft-ietf-ipv6-link-scoped-mcast-02.txt>
Status of this Memo Status of this Memo
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 working groups. Note that other Task Force (IETF), its areas, and working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 50 skipping to change at page 1, line 49
their multicast addresses automatically at Layer 1 without running their multicast addresses automatically at Layer 1 without running
an intra- or inter-domain allocation protocol in serverless an intra- or inter-domain allocation protocol in serverless
environments. environments.
Table of Contents: Table of Contents:
1. Introduction 1. Introduction
2. Terminology 2. Terminology
3. Applicability 3. Applicability
4. Link scoped multicast address format 4. Link scoped multicast address format
5. Examples 5. Source-specific multicast addresses
6. Considerations 6. Examples
7. Security considerations 7. Considerations
8. References 8. Security considerations
9. Acknowledgements 9. References
10. Acknowledgements
1. Introduction 1. Introduction
This specification defines an extension to the multicast portion of This specification defines an extension to the multicast portion of
the IPv6 addressing architecture [ADDRARCH]. The current the IPv6 addressing architecture [ADDRARCH]. The current
architecture does not contain any built-in support for dynamic architecture does not contain any built-in support for dynamic
address allocation. The extension allows for use of interface-IDs to address allocation. The extension allows for use of interface-IDs to
allocate multicast addresses. When the link-local unicast address allocate multicast addresses. When the link-local unicast address
is configured at each interface of a host, an interface ID is uniquely is configured at each interface of a host, an interface ID is uniquely
determined. By delegating multicast addresses at the same time as determined. By delegating multicast addresses at the same time as
skipping to change at page 4, line 18 skipping to change at page 4, line 18
group ID is generated to indicate multicast application and is used group ID is generated to indicate multicast application and is used
to guarantee its uniqueness only in the host. It may also be set on to guarantee its uniqueness only in the host. It may also be set on
the basis of the guidelines outlined in [IPV6 GID]. the basis of the guidelines outlined in [IPV6 GID].
The lifetime of an Interface ID-based multicast address has no The lifetime of an Interface ID-based multicast address has no
dependency on the Valid Lifetime field in the Prefix Information dependency on the Valid Lifetime field in the Prefix Information
option, corresponding to the unicast address being used, contained option, corresponding to the unicast address being used, contained
in the Router Advertisement message [RFC 2461]. in the Router Advertisement message [RFC 2461].
5. Examples 5. Source-specific multicast addresses
The link scoped multicast address format supports source-specific
multicast addresses, as defined by [SSM ARCH]. To accomplish this,
a node MUST:
o Set P = 1.
o Set interface ID = 0.
These settings create an SSM range of FF32::/96. The source address
field in the IPv6 header identifies the owner of the multicast
address.
6. Examples
This is an example of an interface ID-based multicast address with This is an example of an interface ID-based multicast address with
link-local scope. For example in an ethernet environment, if the IEEE link-local scope. For example in an ethernet environment, if the
48-bit MAC's address is 12:34:56:78:90:AB, the mutlicast prefix of link-local unicast address is FE80::12:34:56:78:90:AB,
the host is FF32:0:1234:56FF:FE78:90AB::/96. the mutlicast prefix of the host is FF32:0:1234:56FF:FE78:90AB::/96.
For SSM, multicast adrress will be FF32::/96.
6. Considerations 7. Considerations
This draft considers only link-local multicast addresses. For This draft considers only link-local multicast addresses. For
this purpose, P flag is used in figure 2. The [UNIMULTI] draft also this purpose, P flag is used in figure 2. The [UNIMULTI] draft also
uses the P flag to indicate a multicast address that is assigned on uses the P flag to indicate a multicast address that is assigned on
the basis of the network prefix. For consistency, some modifications the basis of the network prefix. For consistency, some modifications
in the [UNIMULTI] draft are required. For example, by restrictng the in the [UNIMULTI] draft are required. For example, by restrictng the
syntax to scope > 2 in [UNIMULTI]. syntax to scope > 2 in [UNIMULTI].
7. Security considerations 8. Security considerations
[RFC3041] describes the privacy extension to IPv6 stateless [RFC3041] describes the privacy extension to IPv6 stateless
address autoconfiguration for an interface ID. So, [RFC3041] address autoconfiguration for an interface ID. So, [RFC3041]
satisfied our requirements. satisfied our requirements.
8. References Using source-specific multicast addresses can sometimes aid in the
prevention of denial-of-service attacks by arbitrary sources,
although no guarantee is provided. A more in-depth discussion of
the security considerations for SSM can be found in [SSM ARCH].
9. References
[RFC 2373] [RFC 2373]
R. Hinden and S. Deering, "IP Version 6 Addressing Architecture", R. Hinden and S. Deering, "IP Version 6 Addressing Architecture",
RFC 2373, July 1998. RFC 2373, October 1998.
[RFC 2460]
S. Deering and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998.
[RFC 2461] [RFC 2461]
Narten, T., Nordmark, E., Simpson, W., "Neighbor Discovery for IP Narten, T., Nordmark, E., Simpson, W., "Neighbor Discovery for IP
Version 6 (IPv6)", RFC 2461, December 1998. Version 6 (IPv6)", RFC 2461, December 1998.
[RFC 2464]
M. Crawford, "Transmission of IPv6 Packets over Ethernet Networks,"
RFC2464, December 1998
[RFC 2908] [RFC 2908]
D. Thaler, M. Handley and D. Estrin, "Th Internet Multicast Address D. Thaler, M. Handley and D. Estrin, "Th Internet Multicast Address
Allocation Architecture," RFC2908, September 2000. Allocation Architecture," RFC2908, September 2000.
[RFC 2909] [RFC 2909]
Radoslavov, P., Estrin, D., Govindan, R., Handley, M., Kumar, S. Radoslavov, P., Estrin, D., Govindan, R., Handley, M., Kumar, S.
and D. Thaler, "The Multicast Address-Set Claim (MASC) Protocol", and D. Thaler, "The Multicast Address-Set Claim (MASC) Protocol",
RFC 2909, September 2000. RFC 2909, September 2000.
[RFC 3041] [RFC 3041]
T. Narten and R. Draves, "Privacy Extensions for Stateless Address T. Narten and R. Draves, "Privacy Extensions for Stateless Address
Autoconfiguration in IPv6," RFC 3041, January 2001. Autoconfiguration in IPv6," RFC 3041, April 2001.
[RFC 3138]
Meyer, D., "Extended Assignments in 233/8", RFC 3138, June 2001.
[RFC 3180]
Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8", RFC 3180,
September 2001.
[AAP WORK] [AAP WORK]
Handley, M. and S. Hanna, "Multicast Address Allocation Protocol Handley, M. and S. Hanna, "Multicast Address Allocation Protocol
(AAP)", Work in Progress. (AAP)", Work in Progress.
[ADDRARCH] [ADDRARCH]
R. Hinden and S. Deering, "IP Version 6 Addressing Architecture", R. Hinden and S. Deering, "IP Version 6 Addressing Architecture",
Work In Progress, July 2001. Work In Progress, October 2001.
[UNIMULTI] [UNIMULTI]
B. Haberman and D. Thaler, "Unicast-Prefix-based IPv6 Multicast B. Haberman and D. Thaler, "Unicast-Prefix-based IPv6 Multicast
Addresses," Work In Progress, December 2001. Addresses," Work In Progress, December 2001.
[IPV6 GID] [IPV6 GID]
B. Haberman, "Dynamic Allocation Guidelines for IPv6 Multicast B. Haberman, "Dynamic Allocation Guidelines for IPv6 Multicast
Addresses," Work In Progress, October 2001. Addresses," Work In Progress, October 2001.
9. Acknowledgements [SSM ARCH]
H. Holbrook and B. Cain, "Source-Specific Multicast for IP",
Work In Progress, March 2001.
10. Acknowledgements
We would like to thank Dave Thaler for his comments related to the We would like to thank Dave Thaler for his comments related to the
consistency between the unicast prefix-based multicast draft and consistency between the unicast prefix-based multicast draft and
this one. this one.
Authors Addresses Authors Addresses
Jung-Soo Park Jung-Soo Park
ETRI PEC ETRI PEC
161 Kajong-Dong, Yusong-Gu, Taejon 305-600, Korea 161 Kajong-Dong, Yusong-Gu, Taejon 305-600, Korea
Tel : +82 42 860 6514 Tel : +82 42 860 6514
Fax : +82 42 861 5404 Fax : +82 42 861 5404
E-mail : jspark@pec.etri.re.kr E-mail : jspark@pec.etri.re.kr
Myung-Ki Shin Myung-Ki Shin
ETRI PEC ETRI PEC
161 Kajong-Dong, Yusong-Gu, Taejon 305-600, Korea 161 Kajong-Dong, Yusong-Gu, Taejon 305-600, Korea
Tel : +82 42 860 4847 Tel : +82 42 860 4847
Fax : +82 42 861 5404 Fax : +82 42 861 5404
E-mail : mkshin@pec.etri.re.kr E-mail : mkshin@pec.etri.re.kr
Yong-Jin Kim
ETRI PEC
161 Kajong-Dong, Yusong-Gu, Taejon 305-600, Korea
Tel : +82 42 860 6564
Fax : +82 42 861 5404
E-mail : yjkim@pec.etri.re.kr
 End of changes. 

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