draft-ietf-mboned-64-multicast-address-format-01.txt   draft-ietf-mboned-64-multicast-address-format-02.txt 
MBONED Working Group M. Boucadair, Ed. MBONED Working Group M. Boucadair, Ed.
Internet-Draft France Telecom Internet-Draft France Telecom
Updates: 4291 (if approved) J. Qin Updates: 4291 (if approved) J. Qin
Intended status: Standards Track ZTE Intended status: Standards Track Cisco
Expires: September 1, 2012 Y. Lee Expires: November 24, 2012 Y. Lee
Comcast Comcast
S. Venaas S. Venaas
Cisco Systems Cisco Systems
X. Li X. Li
CERNET Center/Tsinghua CERNET Center/Tsinghua
University University
M. Xu M. Xu
Tsinghua University Tsinghua University
February 29, 2012 May 23, 2012
IPv4-Embedded IPv6 Multicast Address Format IPv6 Multicast Address Format With Embedded IPv4 Multicast Address
draft-ietf-mboned-64-multicast-address-format-01 draft-ietf-mboned-64-multicast-address-format-02
Abstract Abstract
This document specifies an extension to the IPv6 multicast addressing This document specifies an extension to the IPv6 multicast addressing
architecture to be used in the context of IPv4-IPv6 interconnection. architecture to be used in the context of IPv4-IPv6 interconnection.
In particular, this document defines an address format for IPv4- In particular, this document defines an address format for IPv4-
embedded IPv6 multicast addresses. This address format can be used embedded IPv6 multicast addresses. This address format can be used
for IPv4-IPv6 translation or encapsulation schemes. for IPv4-IPv6 translation or encapsulation schemes.
This document updates RFC4291. This document updates RFC4291.
skipping to change at page 2, line 6 skipping to change at page 2, line 6
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 September 1, 2012. This Internet-Draft will expire on November 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. IPv4-Embedded IPv6 Multicast Address Format: ASM Mode . . . . 4 3. IPv4-Embedded IPv6 Multicast Address Format: ASM Mode . . . . 5
4. IPv4-Embedded IPv6 Multicast Address Format: SSM Mode . . . . 5 4. IPv4-Embedded IPv6 Multicast Address Format: SSM Mode . . . . 6
5. Textual Representation . . . . . . . . . . . . . . . . . . . . 6 5. Textual Representation . . . . . . . . . . . . . . . . . . . . 7
6. Multicast PREFIX64 . . . . . . . . . . . . . . . . . . . . . . 6 6. Multicast PREFIX64 . . . . . . . . . . . . . . . . . . . . . . 7
7. Source IPv4 Address in the IPv6 Realm . . . . . . . . . . . . 7 7. Source IPv4 Address in the IPv6 Realm . . . . . . . . . . . . 8
8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Address Translation Algorithm . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10. Security Considerations . . . . . . . . . . . . . . . . . . . 8 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 11. Security Considerations . . . . . . . . . . . . . . . . . . . 9
12. Normative References . . . . . . . . . . . . . . . . . . . . . 8 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
Appendix A. Design Choices . . . . . . . . . . . . . . . . . . . 9 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
A.1. Location of the IPv4 Address . . . . . . . . . . . . . . . 9 13.1. Normative References . . . . . . . . . . . . . . . . . . 10
A.2. Location of the M-bit . . . . . . . . . . . . . . . . . . 9 13.2. Informative References . . . . . . . . . . . . . . . . . 10
A.3. Encapsulation vs. Translation . . . . . . . . . . . . . . 11 Appendix A. Design Choices . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 A.1. Why an Address Format is Needed for Multicast
IPv4-IPv6 Interconnection? . . . . . . . . . . . . . . . 11
A.2. Why Identifying an IPv4-Embedded IPv6 Multicast
Address is Required? . . . . . . . . . . . . . . . . . . 11
A.3. Location of the IPv4 Address . . . . . . . . . . . . . . 12
A.4. Location of the M-bit . . . . . . . . . . . . . . . . . . 12
A.5. Encapsulation vs. Translation . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Various solutions (e.g., [I-D.ietf-softwire-mesh-multicast],
[I-D.ietf-softwire-dslite-multicast]) have been proposed to allow
access to IPv4 multicast content from hosts attached to IPv6-enabled
domains. Even if these solutions have distinct applicability scopes
(translation vs. encapsulation) and target different use cases, they
all make use of specific IPv6 multicast addresses to embed an IPv4
multicast address. Particularly, the IPv4-embedded IPv6 multicast
address is used as a destination IPv6 address of multicast flows
received from an IPv4-enabled domain and injected by the IPv4-IPv6
Interconnection Function into an IPv6-enabled domain. It is also
used to build an IPv6 multicast state (*, G6) or (S6, G6)
corresponding to their (*, G4) or (S4, G4) IPv4 counter parts by the
IPv4-IPv6 Interconnection Function. [I-D.ietf-mboned-v4v6-mcast-ps]
provides more discussion about issues related to IPv4/IPv6 multicast.
This document specifies an extension to the IPv6 multicast addressing This document specifies an extension to the IPv6 multicast addressing
architecture to be used in the context of IPv4-IPv6 interconnection. architecture to be used in the context of IPv4-IPv6 interconnection.
In particular, this document defines an address format for IPv4- In particular, this document defines an address format for IPv4-
embedded IPv6 multicast addresses. This address format can be used embedded IPv6 multicast addresses. This address format can be used
for IPv4-IPv6 translation or encapsulation schemes. for IPv4-IPv6 translation or encapsulation schemes.
This document updates [RFC4291]. This document updates [RFC4291]. A new M-bit is defined; if set to
"1", it indicates an IPv4 multicast address is embedded in the low-
order 32 bits of the IPv6 multicast address. Appendix A.1 enumerates
the arguments in favor of defining an address format while
Appendix A.2 discusses why identifying an IPv4-embedded IPv6
multicast address is needed.
This specification can be used in conjunction with other extensions This specification can be used in conjunction with other extensions
such as building unicast prefix-based multicast IPv6 address such as building unicast prefix-based multicast IPv6 address
[RFC3306] or embedding the rendezvous point [RFC3956]. [RFC3306] or embedding the rendezvous point [RFC3956].
This document is a companion document to [RFC6052] which focuses This document is a companion document to [RFC6052] which focuses
exclusively on IPv4-embedded IPv6 unicast addresses. exclusively on IPv4-embedded IPv6 unicast addresses.
Details about design choices are documented in Appendix A. Details about design choices are documented in Appendix A.
2. Terminology 2. Terminology
This document makes use of the following terms: This document makes use of the following terms:
o IPv4-embedded IPv6 multicast address: denotes a multicast IPv6 o IPv4-embedded IPv6 multicast address: denotes a multicast IPv6
address which includes in 32 bits an IPv4 address. Two types of address which includes in 32 bits an IPv4 address. Two types of
IPv6 addresses are defined that carry an IPv4 address in the low- IPv6 addresses are defined that carry an IPv4 address in the low-
order 32 bits of the address. The format to build such addresses order 32 bits of the address. The format to build such addresses
is defined in Section 3 for ASM mode and Section 4 for SSM mode. is defined in Section 3 for Any Source Multicast (ASM) mode and
Section 4 for Source Specific Multicast (SSM) mode.
o Multicast Prefix64 (or MPREFIX64 for short) refers to an IPv6 o Multicast Prefix64 (or MPREFIX64 for short) refers to an IPv6
multicast prefix to be used to construct IPv4-embedded IPv6 multicast prefix to be used to construct IPv4-embedded IPv6
multicast addresses. multicast addresses. This prefix is used to build an IPv4-
embedded IPv6 multicast address as defined in Section 8.
Section 8 specifies also how to extract an IPv4 address from an
IPv4-embedded IPv6 multicast address.
o ASM_MPREFIX64: denotes a multicast Prefix64 used in ASM mode. It o ASM_MPREFIX64: denotes a multicast Prefix64 used in ASM mode. It
follows the format described in Section 3. follows the format described in Section 3.
o SSM_MPREFIX64: denotes a multicast Prefix64 used in SSM mode. It o SSM_MPREFIX64: denotes a multicast Prefix64 used in SSM mode. It
follows the format described in Section 4. follows the format described in Section 4.
o IPv4-IPv6 Interconnection Function: refers to a function which is
enabled in a node interconnecting an IPv4-enabled domain with an
IPv6-enabled one. It can be located in various places of the
multicast network. Particularly, in terms of multicast control
messages, it can be an IGMP/MLD Interworking Function or an IPv4-
IPv6 PIM Interworking Function. An IPv4-IPv6 Interconnection
Function is configured with one or two MPREFIX64s.
3. IPv4-Embedded IPv6 Multicast Address Format: ASM Mode 3. IPv4-Embedded IPv6 Multicast Address Format: ASM Mode
To meet the requirements listed in Appendix A.2, the following To meet the requirements listed in Appendix A.4, the IPv6 multicast
address format is defined to enclose an IPv4 multicast address when address format defined in [RFC4291] is modified to enclose an IPv4
ASM mode is used: multicast address. Figure 1 shows the modified address format when
ASM mode is used.
| 8 | 4 | 4 | 4 | 76 | 32 | | 8 | 4 | 4 | 4 | 76 | 32 |
+--------+----+----+----+------------------------------+----------+ +--------+----+----+----+------------------------------+----------+
|11111111|flgs|scop|64IX| sub-group-id |v4 address| |11111111|flgs|scop|64IX| sub-group-id |v4 address|
+--------+----+----+----+-----------------------------------------+ +--------+----+----+----+-----------------------------------------+
+-+-+-+-+ +-+-+-+-+
IPv4-IPv6 Interconnection bits (64IX): |M|r|r|r| IPv4-IPv6 Interconnection bits (64IX): |M|resvd|
+-+-+-+-+ +-+-+-+-+
"resvd" are reserved bits.
Figure 1: IPv4-Embedded IPv6 Multicast Address Format: ASM Mode Figure 1: IPv4-Embedded IPv6 Multicast Address Format: ASM Mode
The description of the fields is as follows: The description of the fields is as follows:
o "flgs" and "scop" fields are defined in [RFC4291]. o "flgs" and "scop" fields are defined in [RFC4291].
o 64IX field (IPv4-IPv6 interconnection bits): The first bit is the o 64IX field (IPv4-IPv6 interconnection bits): The first bit is the
M-bit. When "M-bit" is set to 1, it indicates that a multicast M-bit. When "M-bit" is set to 1, it indicates that a multicast
IPv4 address is embedded in the low-order 32 bits of the multicast IPv4 address is embedded in the low-order 32 bits of the multicast
IPv6 address. All the remaining bits are reserved and MUST be set IPv6 address. All the remaining bits are reserved and MUST be set
to 0. to 0.
o sub-group-id: This field is configurable according to local o sub-group-id: This field is configurable according to local
policies of the entity managing the IPv4-IPv6 Interconnection policies (e.g., enable embedded-RP) of the entity managing the
Function. This field must follow the recommendations specified in IPv4-IPv6 Interconnection Function. This field MUST follow the
[RFC3306] if unicast-based prefix is used or the recommendations recommendations specified in [RFC3306] if unicast-based prefix is
specified in [RFC3956] if embedded-RP is used. The default value used or the recommendations specified in [RFC3956] if embedded-RP
is all zeros. is used. The default value is all zeros.
o The low-order 32 bits MUST include an IPv4 multicast address when o The low-order 32 bits MUST include an IPv4 multicast address when
the M-bit is set to 1. The enclosed IPv4 multicast address SHOULD the M-bit is set to 1. The enclosed IPv4 multicast address SHOULD
NOT be in 232/8 range. NOT be in 232/8 range.
4. IPv4-Embedded IPv6 Multicast Address Format: SSM Mode 4. IPv4-Embedded IPv6 Multicast Address Format: SSM Mode
As mentioned above, any IPv4-embedded IPv6 address used in SSM mode As mentioned in Appendix A.4, any IPv4-embedded IPv6 address used in
MUST be part of ff3x::/32 [RFC4607]. Figure 2 describes the format SSM mode MUST be part of ff3x::/32 [RFC4607]. Figure 2 describes the
of the IPv6 multicast address to be used to enclose an IPv4 multicast format of the IPv6 multicast address to be used to enclose an IPv4
address. multicast address.
| 8 | 4 | 4 | 16 | 4 | 60 | 32 | | 8 | 4 | 4 | 16 | 4 | 60 | 32 |
+--------+----+----+-----------+----+------------------+----------+ +--------+----+----+-----------+----+------------------+----------+
|11111111|0011|scop|00.......00|64IX| sub-group-id |v4 address| |11111111|0011|scop|00.......00|64IX| sub-group-id |v4 address|
+--------+----+----+-----------+----+------------------+----------+ +--------+----+----+-----------+----+------------------+----------+
+-+-+-+-+ +-+-+-+-+
IPv4-IPv6 Interconnection bits (64IX): |M|r|r|r| IPv4-IPv6 Interconnection bits (64IX): |M|resvd|
+-+-+-+-+ +-+-+-+-+
"resvd" are reserved bits.
Figure 2: IPv4-Embedded IPv6 Multicast Address Format: SSM Mode Figure 2: IPv4-Embedded IPv6 Multicast Address Format: SSM Mode
The description of the fields is as follows: The description of the fields is as follows:
o Flags must be set to 0011. o Flags MUST be set to 0011.
o "scop" is defined in [RFC4291]. o "scop" is defined in [RFC4291].
o 64IX field (IPv4-IPv6 interconnection bits): Same meaning as o 64IX field (IPv4-IPv6 interconnection bits): Same meaning as
Section 3. Section 3.
o sub-group-id: The default value is all zeros. o sub-group-id: The default value is all zeros.
o The low-order 32 bits MUST include an IPv4 multicast address when o The low-order 32 bits MUST include an IPv4 multicast address when
the M-bit is set to 1. The embedded IPv4 address SHOULD be in the the M-bit is set to 1. The embedded IPv4 address SHOULD be in the
232/8 range [RFC4607]. 232.0.0.1-232.0.0.255 range is being 232/8 range [RFC4607].
reserved to IANA.
5. Textual Representation 5. Textual Representation
The embedded IPv4 address in an IPv6 multicast address is included in The embedded IPv4 address in an IPv6 multicast address is included in
the last 32 bits; therefore dotted decimal notation can be used. the last 32 bits; therefore dotted decimal notation can be used.
6. Multicast PREFIX64 6. Multicast PREFIX64
For the delivery of the IPv4-IPv6 multicast interconnection services, For the delivery of the IPv4-IPv6 multicast interconnection services,
a dedicated multicast prefix denoted as MPREFIX64 should be a dedicated multicast prefix denoted as MPREFIX64 should be
provisioned to any function requiring to build an IPv4-embedded IPv6 provisioned (e.g., using NETCONF or
multicast address based on an IPv4 multicast address. MPREFIX64 can [I-D.ietf-softwire-multicast-prefix-option]) to any function
be of ASM or SSM type. When both modes are used, two prefixes are requiring to build an IPv4-embedded IPv6 multicast address based on
required to be provisioned. an IPv4 multicast address. MPREFIX64 can be of ASM or SSM type.
When both modes are used, two prefixes are required to be
provisioned.
The structure of the MPREFIX64 follows the guidelines specified in The structure of the MPREFIX64 follows the guidelines specified in
Section 3 for the ASM mode and Section 4 when SSM mode is used. Section 3 for the ASM mode and Section 4 when SSM mode is used.
The RECOMMENDED MPREFIX64 length is /96 (as shown in Figure 3). The length of MPREFIX64 MUST be /96 (as shown in Figure 3).
The format of the MPREFIX64 should follow what is specified in The format of the MPREFIX64 should follow what is specified in
[RFC3306] and [RFC3956] if corresponding mechanisms are used. [RFC3306] and [RFC3956] if corresponding mechanisms are used.
The format specified in Section 3 uses some reserved bits defined The format specified in Section 3 uses some reserved bits defined
in [RFC3306] and [RFC3956]: the first of the reserved bits now has in [RFC3306] and [RFC3956]: the first of the reserved bits now has
a meaning, while the remaining bits MUST be set to 0. a meaning, while the remaining bits MUST be set to 0.
ASM Mode: ASM Mode:
skipping to change at page 7, line 40 skipping to change at page 8, line 36
| SSM_MPREFIX64 |v4 address| | SSM_MPREFIX64 |v4 address|
+------------------------------------------------------+----------+ +------------------------------------------------------+----------+
Figure 3: MPREFIX64 Figure 3: MPREFIX64
7. Source IPv4 Address in the IPv6 Realm 7. Source IPv4 Address in the IPv6 Realm
An IPv4 source is represented in the IPv6 realm with its IPv4- An IPv4 source is represented in the IPv6 realm with its IPv4-
converted IPv6 address [RFC6052]. converted IPv6 address [RFC6052].
8. Examples 8. Address Translation Algorithm
IPv4-embedded IPv6 multicast addresses are composed according to the
following algorithm:
o Concatenate the MPREFIX64 and the 32 bits of the IPv4 address to
obtain a 128-bit address.
The IPv4 multicast addresses are extracted from the IPv4-embedded
IPv6 multicast addresses according to the following algorithm:
o If the multicast address belongs to ff3x:0:8000/33 or ffxx:
8000/17, extract the last 32 bits of the IPv6 multicast address.
9. Examples
Figure 4 provides an example of ASM IPv4-Embedded IPv6 Address while Figure 4 provides an example of ASM IPv4-Embedded IPv6 Address while
Figure 5 provides an example of SSM IPv4-Embedded IPv6 Address. Figure 5 provides an example of SSM IPv4-Embedded IPv6 Address.
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| MPREFIX64 | IPv4 address | IPv4-embedded IPv6 address | | MPREFIX64 | IPv4 address | IPv4-embedded IPv6 address |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| ffxx:8000:abc::/96 | 224.1.2.3 | ffxx:8000:abc::224.1.2.3 | | ffxx:8000:abc::/96 | 224.1.2.3 | ffxx:8000:abc::224.1.2.3 |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
Figure 4: Example of ASM IPv4-embedded IPv6 address Figure 4: Example of ASM IPv4-embedded IPv6 address
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| MPREFIX64 | IPv4 address | IPv4-embedded IPv6 address | | MPREFIX64 | IPv4 address | IPv4-embedded IPv6 address |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| ff3x:0:8000::/96 | 232.1.2.3 | ff3x:0:8000::232.1.2.3 | | ff3x:0:8000::/96 | 232.1.2.3 | ff3x:0:8000::232.1.2.3 |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
Figure 5: Example of SSM IPv4-embedded IPv6 address Figure 5: Example of SSM IPv4-embedded IPv6 address
9. IANA Considerations 10. IANA Considerations
Authors of this document request to reserve: Authors of this document request to reserve:
o ff3x:0:8000/33 SSM block to embed an IPv4 multicast address in the o ff3x:0:8000/33 SSM block to embed an IPv4 multicast address in the
last 32 bits. last 32 bits.
o ffxx:8000/17 ASM block to embed an IPv4 multicast address in the o ffxx:8000/17 ASM block to embed an IPv4 multicast address in the
last 32 bits. last 32 bits.
10. Security Considerations 11. Security Considerations
This document defined an address format to embed an IPv4 multicast This document defines an address format to embed an IPv4 multicast
address in an IPv6 multicast address. The same security address in an IPv6 multicast address. The same security
considerations as those discussed in [RFC6052] are to be taken into considerations as those discussed in [RFC6052] are to be taken into
consideration. consideration.
11. Acknowledgements 12. Acknowledgements
Many thanks to R. Bonica, B. Sarikaya, P. Savola and T. Tsou for Many thanks to R. Bonica, B. Sarikaya, P. Savola, T. Tsou and C.
their comments and review. Bormann for their comments and review.
12. Normative References 13. References
13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", RFC 3306, August 2002. Multicast Addresses", RFC 3306, August 2002.
[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address", Point (RP) Address in an IPv6 Multicast Address",
RFC 3956, November 2004. RFC 3956, November 2004.
skipping to change at page 9, line 19 skipping to change at page 10, line 26
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006. IP", RFC 4607, August 2006.
[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
October 2010. October 2010.
13.2. Informative References
[I-D.ietf-behave-nat64-learn-analysis]
Korhonen, J. and T. Savolainen, "Analysis of solution
proposals for hosts to learn NAT64 prefix",
draft-ietf-behave-nat64-learn-analysis-03 (work in
progress), March 2012.
[I-D.ietf-mboned-v4v6-mcast-ps]
Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., Tsou, T.,
and Q. Sun, "IPv4-IPv6 Multicast: Problem Statement and
Use Cases", draft-ietf-mboned-v4v6-mcast-ps-00 (work in
progress), May 2012.
[I-D.ietf-softwire-dslite-multicast]
Qin, J., Boucadair, M., Jacquenet, C., Lee, Y., and Q.
Wang, "Multicast Extensions to DS-Lite Technique in
Broadband Deployments",
draft-ietf-softwire-dslite-multicast-02 (work in
progress), May 2012.
[I-D.ietf-softwire-mesh-multicast]
Xu, M., Cui, Y., Yang, S., Wu, J., Metz, C., and G.
Shepherd, "Softwire Mesh Multicast",
draft-ietf-softwire-mesh-multicast-02 (work in progress),
April 2012.
[I-D.ietf-softwire-multicast-prefix-option]
Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", draft-ietf-softwire-multicast-prefix-option-00
(work in progress), March 2012.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006.
Appendix A. Design Choices Appendix A. Design Choices
A.1. Location of the IPv4 Address A.1. Why an Address Format is Needed for Multicast IPv4-IPv6
Interconnection?
Arguments why an IPv6 address format is needed to embed multicast
IPv4 address are quite similar to those of [RFC6052]. Concretely,
the definition of a multicast address format embedding a multicast
IPv4 address allows:
o Stateless IPv4-IPv6 header translation of multicast flows;
o Stateless IPv4-IPv6 PIM interworking function;
o Stateless IGMP-MLD interworking function (e.g., required for an
IPv4 receiver to access to IPv4 multicast content via an IPv6
network);
o Stateless (local) synthesis of IPv6 address when IPv4 multicast
address are embedded in application payload (e.g., SDP [RFC4566]);
o Except the provisioning of the same MPREFIX64, no coordination is
required between IPv4-IPv6 PIM interworking function, IGMP-MLD
interworking function, IPv4-IPv6 Interconnection Function and any
ALG (Application Level Gateway) in the path;
o Minimal operational constraints on the multicast address
management: IPv6 multicast addresses can be constructed using what
has been deployed for IPv4 delivery mode.
A.2. Why Identifying an IPv4-Embedded IPv6 Multicast Address is
Required?
Reserving an M-bit in the IPv6 multicast address (which is equivalent
to reserving a dedicated multicast block for IPv4-IPv6
interconnection purposes) is a means to guide the address selection
process at the receiver side; in particular it assists the receiver
to select the appropriate IP multicast address while avoiding to
involve an IPv4-IPv6 interconnection function in the path.
Two use cases to illustrate this behavior are provided below:
1. An ALG is required to help an IPv6 receiver to select the
appropriate IP address when only the IPv4 address is advertised
(e.g., using SDP); otherwise the access to the IPv4 multicast
content can not be offered to the IPv6 receiver. The ALG may be
located downstream the receiver. As such, the ALG does not know
in advance whether the receiver is dual-stack or IPv6-only. The
ALG may be tuned to insert both the original IPv4 address and
corresponding IPv6 multicast address. If the M-bit is not used,
a dual-stack receiver may prefer to use the IPv6 address to
receive the multicast content. This address selection would
require multicast flows to cross an IPv4-IPv6 interconnection
function.
2. In order to avoid involving an ALG in the path, an IPv4-only
source can advertise both its IPv4 address and IPv4-embedded IPv6
multicast address. If the M-bit is not used, a dual-stack
receiver may prefer to use the IPv6 address to receive the
multicast content. This address selection would require
multicast flows to cross an IPv4-IPv6 interconnection function.
Reserving an M-bit in the IPv6 multicast address for IPv4-IPv6
interconnection purposes mitigates the issues discussed in
[I-D.ietf-behave-nat64-learn-analysis] in a multicast context.
A.3. Location of the IPv4 Address
There is no strong argument to allow for flexible options to encode There is no strong argument to allow for flexible options to encode
the IPv4 address inside the multicast IPv6 address. The option the IPv4 address inside the multicast IPv6 address. The option
retained by the authors is to encode the multicast IPv4 address in retained by the authors is to encode the multicast IPv4 address in
the low-order 32 bits of the IPv6 address. the low-order 32 bits of the IPv6 address.
This choice is also motivated by the need to be compliant with This choice is also motivated by the need to be compliant with
[RFC3306] and [RFC3956]. [RFC3306] and [RFC3956].
A.2. Location of the M-bit A.4. Location of the M-bit
Figure 6 is a reminder of the IPv6 multicast address format as Figure 6 is a reminder of the IPv6 multicast address format as
defined in [RFC4291]: defined in [RFC4291]:
| 8 | 4 | 4 | 112 bits | | 8 | 4 | 4 | 112 bits |
+------ -+----+----+---------------------------------------------+ +------ -+----+----+---------------------------------------------+
|11111111|flgs|scop| group ID | |11111111|flgs|scop| group ID |
+--------+----+----+---------------------------------------------+ +--------+----+----+---------------------------------------------+
+-+-+-+-+ +-+-+-+-+
flgs is a set of 4 flags: |0|R|P|T| flgs is a set of 4 flags: |0|R|P|T|
skipping to change at page 11, line 7 skipping to change at page 14, line 7
(3) Avoid ff3x::4000:0001-ff3x::7fff:ffff which is reserved for (3) Avoid ff3x::4000:0001-ff3x::7fff:ffff which is reserved for
IANA. IANA.
Meeting (1) and (2) with the same location of the M-bit is not Meeting (1) and (2) with the same location of the M-bit is not
feasible without modifying embedded-RP and unicast-based prefix feasible without modifying embedded-RP and unicast-based prefix
specifications; this option is avoided. specifications; this option is avoided.
As a consequence, two multicast blocks are proposed to be used when As a consequence, two multicast blocks are proposed to be used when
embedding IPv4 address: one block for ASM (Section 3 ) and another embedding IPv4 address: one block for ASM (Section 3 ) and another
one for the SSM (Section 4). one for the SSM (Section 4).
A.3. Encapsulation vs. Translation A.5. Encapsulation vs. Translation
IPv4-IPv6 encapsulator and translator may be embedded in the same IPv4-IPv6 encapsulator and translator may be embedded in the same
device or even implemented with the same software module. In order device or even implemented with the same software module. In order
to help the function whether an encapsulated IPv6 multicast packets to help the function whether an encapsulated IPv6 multicast packets
or translated IPv6 ones are to be transferred. It was tempting to or translated IPv6 ones are to be transferred. It was tempting to
define an S-bit for that purpose but this choice has been abandoned define an S-bit for that purpose but this choice has been abandoned
in favor of the recommendation to use distinct MPREFIX64 for each in favor of the recommendation to use distinct MPREFIX64 for each
scheme. scheme.
As such, there is no need to reserve a bit in the IPv6 multicast As such, there is no need to reserve a bit in the IPv6 multicast
skipping to change at page 11, line 31 skipping to change at page 14, line 31
Authors' Addresses Authors' Addresses
Mohamed Boucadair (editor) Mohamed Boucadair (editor)
France Telecom France Telecom
Rennes, 35000 Rennes, 35000
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Jacni Qin Jacni Qin
ZTE Cisco
Shanghai
China China
Email: jacniq@gmail.com Email: jacni@jacni.com
Yiu L. Lee Yiu L. Lee
Comcast Comcast
U.S.A U.S.A
Email: yiu_lee@cable.comcast.com Email: yiu_lee@cable.comcast.com
Stig Venaas Stig Venaas
Cisco Systems Cisco Systems
Tasman Drive Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
 End of changes. 35 change blocks. 
60 lines changed or deleted 209 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/