draft-ietf-softwire-dslite-multicast-07.txt   draft-ietf-softwire-dslite-multicast-08.txt 
Softwire WG J. Qin Softwire WG J. Qin
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track M. Boucadair Intended status: Standards Track M. Boucadair
Expires: September 26, 2014 C. Jacquenet Expires: March 19, 2015 C. Jacquenet
France Telecom France Telecom
Y. Lee Y. Lee
Comcast Comcast
Q. Wang Q. Wang
China Telecom China Telecom
March 25, 2014 September 15, 2014
Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6
Multicast Network Multicast Network
draft-ietf-softwire-dslite-multicast-07 draft-ietf-softwire-dslite-multicast-08
Abstract Abstract
This document specifies a solution for the delivery of IPv4 multicast This document specifies a solution for the delivery of IPv4 multicast
services to IPv4 clients over an IPv6 multicast network. The services to IPv4 clients over an IPv6 multicast network. The
solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
and uses the IPv6 multicast distribution tree to deliver IPv4 and uses the IPv6 multicast distribution tree to deliver IPv4
multicast traffic. The solution is particularly useful for the multicast traffic. The solution is particularly useful for the
delivery of multicast service offerings to DS-Lite serviced delivery of multicast service offerings to DS-Lite serviced
customers. customers.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 26, 2014. This Internet-Draft will expire on March 19, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 52 skipping to change at page 2, line 52
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14 8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8.1. Firewall Configuration . . . . . . . . . . . . . . . . . 14 8.1. Firewall Configuration . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
11.1. Normative References . . . . . . . . . . . . . . . . . . 14 11.1. Normative References . . . . . . . . . . . . . . . . . . 14
11.2. Informative References . . . . . . . . . . . . . . . . . 15 11.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Use Case: IPTV . . . . . . . . . . . . . . . . . . . 16 Appendix A. Use Case: IPTV . . . . . . . . . . . . . . . . . . . 16
Appendix B. Deployment Considerations . . . . . . . . . . . . . 16 Appendix B. Deployment Considerations . . . . . . . . . . . . . 16
B.1. Other operational Modes . . . . . . . . . . . . . . . . . 16 B.1. Other operational Modes . . . . . . . . . . . . . . . . . 16
B.1.1. MLD Querier with mAFTR Embedded . . . . . . . . . . . 16 B.1.1. MLD Querier with mAFTR Embedded . . . . . . . . . . . 17
B.1.2. mAFTR embedded in DR . . . . . . . . . . . . . . . . 17 B.1.2. mAFTR embedded in DR . . . . . . . . . . . . . . . . 17
B.2. Older Version of Group Membership management Protocols . 17 B.2. Older Version of Group Membership management Protocols . 17
B.3. Load-Balancing . . . . . . . . . . . . . . . . . . . . . 17 B.3. Load-Balancing . . . . . . . . . . . . . . . . . . . . . 17
B.4. RP for IPv4-Embedded IPv6 Multicast Groups . . . . . . . 17 B.4. RP for IPv4-Embedded IPv6 Multicast Groups . . . . . . . 18
B.5. mAFTR Policy Configuration . . . . . . . . . . . . . . . 18 B.5. mAFTR Policy Configuration . . . . . . . . . . . . . . . 18
B.6. Static vs. Dynamic PIM Triggering . . . . . . . . . . . . 18 B.6. Static vs. Dynamic PIM Triggering . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
DS-Lite [RFC6333] is a technique that rationalizes the usage of the DS-Lite [RFC6333] is a technique that rationalizes the usage of the
remaining global IPv4 addresses during the transition period by remaining global IPv4 addresses during the transition period by
sharing a single IPv4 address with multiple users. A typical DS-Lite sharing a single IPv4 address with multiple users. A typical DS-Lite
scenario is the delivery of an IPv4 service to an IPv4 user over an scenario is the delivery of an IPv4 service to an IPv4 user over an
skipping to change at page 4, line 19 skipping to change at page 4, line 19
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Terminology 2. Terminology
This document makes use of the following terms: This document makes use of the following terms:
o IPv4-embedded IPv6 address: is an IPv6 address which embeds a 32 o IPv4-embedded IPv6 address: is an IPv6 address which embeds a 32-
-bit-encoded IPv4 address. An IPv4-embedded IPv6 address can be bit-encoded IPv4 address. An IPv4-embedded IPv6 address can be
unicast or multicast. unicast or multicast.
o mPrefix64: is a dedicated multicast IPv6 prefix for constructing o mPrefix64: is a dedicated multicast IPv6 prefix for constructing
IPv4-embedded IPv6 multicast addresses. mPrefix64 can be of two IPv4-embedded IPv6 multicast addresses. mPrefix64 can be of two
types: ASM_mPrefix64 used in Any Source Multicast (ASM) mode or types: ASM_mPrefix64 used in Any Source Multicast (ASM) mode or
SSM_mPrefix64 used in Source Specific Multicast (SSM) mode SSM_mPrefix64 used in Source Specific Multicast (SSM) mode
[RFC4607]. [RFC4607].
o uPrefix64: is a dedicated IPv6 unicast prefix for constructing o uPrefix64: is a dedicated IPv6 unicast prefix for constructing
IPv4-embedded IPv6 unicast addresses [RFC6052]. IPv4-embedded IPv6 unicast addresses [RFC6052].
skipping to change at page 10, line 5 skipping to change at page 10, line 5
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| uPrefix64 | IPv4 address | IPv4-Embedded IPv6 address | | uPrefix64 | IPv4 address | IPv4-Embedded IPv6 address |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
| 2001:db8::/96 | 192.0.2.33 | 2001:db8::192.0.2.33 | | 2001:db8::/96 | 192.0.2.33 | 2001:db8::192.0.2.33 |
+---------------------+--------------+----------------------------+ +---------------------+--------------+----------------------------+
IPv4 and IPv6 addresses used in this example are derived from the IPv4 and IPv6 addresses used in this example are derived from the
IPv4 and IPv6 blocks reserved for documentation, as per [RFC6676]. IPv4 and IPv6 blocks reserved for documentation, as per [RFC6676].
The unicast IPv4 address of the above example is derived from The unicast IPv4 address of the above example is derived from the
[RFC5735]. documentation address block defined in [RFC6890].
6. Multicast B4 (mB4) 6. Multicast B4 (mB4)
6.1. IGMP-MLD Interworking Function 6.1. IGMP-MLD Interworking Function
The IGMP-MLD Interworking Function combines the IGMP/MLD Proxying The IGMP-MLD Interworking Function combines the IGMP/MLD Proxying
function and the address synthesizing operations. The IGMP/MLD function and the address synthesizing operations. The IGMP/MLD
Proxying function is specified in [RFC4605]. The address translation Proxying function is specified in [RFC4605]. The address translation
is stateless and MUST follow the address mapping specified in is stateless and MUST follow the address mapping specified in
Section 5. Section 5.
skipping to change at page 14, line 34 skipping to change at page 14, line 34
The CPE that embeds the mB4 function SHOULD be configured to accept The CPE that embeds the mB4 function SHOULD be configured to accept
incoming MLD messages and traffic forwarded to multicast groups incoming MLD messages and traffic forwarded to multicast groups
subscribed by receivers located in the customer premises. subscribed by receivers located in the customer premises.
9. Acknowledgements 9. Acknowledgements
The authors would like to thank Dan Wing for his guidance in the The authors would like to thank Dan Wing for his guidance in the
early discussions which initiated this work. We also thank Peng Sun, early discussions which initiated this work. We also thank Peng Sun,
Jie Hu, Qiong Sun, Lizhong Jin, Alain Durand, Dean Cheng, Behcet Jie Hu, Qiong Sun, Lizhong Jin, Alain Durand, Dean Cheng, Behcet
Sarikaya, Tina Tsou, Rajiv Asati, Xiaohong Deng and S. Venaas for Sarikaya, Tina Tsou, Rajiv Asati, Xiaohong Deng and S. Venaas for
their valuable comments. their valuable comments.
10. IANA Considerations 10. IANA Considerations
This document includes no request to IANA. This document includes no request to IANA.
11. References 11. References
11.1. Normative References 11.1. Normative References
skipping to change at page 15, line 14 skipping to change at page 15, line 14
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick, [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick,
"Internet Group Management Protocol (IGMP) / Multicast "Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP Listener Discovery (MLD)-Based Multicast Forwarding
/MLD Proxying")", RFC 4605, August 2006. ("IGMP/MLD Proxying")", RFC 4605, August 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.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
skipping to change at page 15, line 45 skipping to change at page 15, line 45
[I-D.ietf-mboned-v4v6-mcast-ps] [I-D.ietf-mboned-v4v6-mcast-ps]
Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., Tsou, T., Jacquenet, C., Boucadair, M., Lee, Y., Qin, J., Tsou, T.,
and Q. Qiong, "IPv4-IPv6 Multicast: Problem Statement and and Q. Qiong, "IPv4-IPv6 Multicast: Problem Statement and
Use Cases", draft-ietf-mboned-v4v6-mcast-ps-04 (work in Use Cases", draft-ietf-mboned-v4v6-mcast-ps-04 (work in
progress), September 2013. progress), September 2013.
[I-D.ietf-softwire-multicast-prefix-option] [I-D.ietf-softwire-multicast-prefix-option]
Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6 Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", draft-ietf-softwire-multicast-prefix-option-05 Prefixes", draft-ietf-softwire-multicast-prefix-option-06
(work in progress), October 2013. (work in progress), March 2014.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
RFC 5735, January 2010.
[RFC6676] Venaas, S., Parekh, R., Van de Velde, G., Chown, T., and [RFC6676] Venaas, S., Parekh, R., Van de Velde, G., Chown, T., and
M. Eubanks, "Multicast Addresses for Documentation", RFC M. Eubanks, "Multicast Addresses for Documentation", RFC
6676, August 2012. 6676, August 2012.
[RFC6890] Cotton, M., Vegoda, L., Bonica, R., and B. Haberman,
"Special-Purpose IP Address Registries", BCP 153, RFC
6890, April 2013.
Appendix A. Use Case: IPTV Appendix A. Use Case: IPTV
IPTV generally includes two categories of service offerings: IPTV generally includes two categories of service offerings:
o Video on Demand (VoD) that unicast video content to receivers. o Video on Demand (VoD) that unicast video content to receivers.
o Multicast live TV broadcast services. o Multicast live TV broadcast services.
Two players intervene in the delivery of this service: Two players intervene in the delivery of this service:
 End of changes. 13 change blocks. 
18 lines changed or deleted 19 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/