draft-ietf-softwire-dslite-multicast-05.txt   draft-ietf-softwire-dslite-multicast-06.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: October 17, 2013 C. Jacquenet Expires: April 10, 2014 C. Jacquenet
France Telecom France Telecom
Y. Lee Y. Lee
Comcast Comcast
Q. Wang Q. Wang
China Telecom China Telecom
April 15, 2013 October 07, 2013
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-05 draft-ietf-softwire-dslite-multicast-06
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 October 17, 2013. This Internet-Draft will expire on April 10, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 4, line 27 skipping to change at page 4, line 27
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].
o Multicast AFTR (mAFTR): is a functional entity which supports o Multicast AFTR (mAFTR): is a functional entity which supports
IPv4-IPv6 multicast interworking function (refer to Figure 3). It IPv4-IPv6 multicast interworking function (refer to Figure 3). It
receives and encapsulates the IPv4 multicast packets into IPv4-in- receives and encapsulates the IPv4 multicast packets into IPv4-in-
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 39 skipping to change at page 15, line 39
[I-D.ietf-mboned-multiaaa-framework] [I-D.ietf-mboned-multiaaa-framework]
Satou, H., Ohta, H., Hayashi, T., Jacquenet, C., and H. Satou, H., Ohta, H., Hayashi, T., Jacquenet, C., and H.
He, "AAA and Admission Control Framework for He, "AAA and Admission Control Framework for
Multicasting", draft-ietf-mboned-multiaaa-framework-12 Multicasting", draft-ietf-mboned-multiaaa-framework-12
(work in progress), August 2010. (work in progress), August 2010.
[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. Sun, "IPv4-IPv6 Multicast: Problem Statement and and Q. Sun, "IPv4-IPv6 Multicast: Problem Statement and
Use Cases", draft-ietf-mboned-v4v6-mcast-ps-02 (work in Use Cases", draft-ietf-mboned-v4v6-mcast-ps-04 (work in
progress), March 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-03 Prefixes", draft-ietf-softwire-multicast-prefix-option-04
(work in progress), October 2012. (work in progress), April 2013.
[RFC2236] Fenner, W.C., "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", [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
BCP 153, RFC 5735, January 2010. 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.
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.
skipping to change at page 18, line 12 skipping to change at page 18, line 12
the RP for the IPv4-embedded IPv6 multicast groups it manages. No the RP for the IPv4-embedded IPv6 multicast groups it manages. No
registration procedure is required under this configuration. registration procedure is required under this configuration.
B.5. mAFTR Policy Configuration B.5. mAFTR Policy Configuration
mAFTR may be configured with a list of IPv4 multicast groups and mAFTR may be configured with a list of IPv4 multicast groups and
sources. Only multicast flows bound to the configured addresses sources. Only multicast flows bound to the configured addresses
should be handled by the mAFTR. Otherwise, packets are silently should be handled by the mAFTR. Otherwise, packets are silently
drooped. drooped.
B.6. Static vs. Dynamic PIM Triggering B.6. Static vs. Dynamic PIM Triggering
To optimize the usage of network resources in current deployments, To optimize the usage of network resources in current deployments,
all multicast streams are conveyed in the core network while only all multicast streams are conveyed in the core network while only
popular ones are continuously conveyed in the aggregation/access popular ones are continuously conveyed in the aggregation/access
network (static mode). Non-popular streams are conveyed in the network (static mode). Non-popular streams are conveyed in the
access network upon request (dynamic mode). Depending on the access network upon request (dynamic mode). Depending on the
location of the mAFTR in the network, two modes can be envisaged: location of the mAFTR in the network, two modes can be envisaged:
static and dynamic. static and dynamic.
o Static Mode: the mAFTR is configured to instantiate permanent (S6, o Static Mode: the mAFTR is configured to instantiate permanent (S6,
 End of changes. 11 change blocks. 
13 lines changed or deleted 13 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/