draft-ietf-softwire-mesh-multicast-15.txt   draft-ietf-softwire-mesh-multicast-16.txt 
Softwire WG M. Xu Softwire WG M. Xu
Internet-Draft Y. Cui Internet-Draft Y. Cui
Intended status: Standards Track J. Wu Intended status: Standards Track J. Wu
Expires: July 14, 2017 S. Yang Expires: October 2, 2017 S. Yang
Tsinghua University Tsinghua University
C. Metz C. Metz
G. Shepherd G. Shepherd
Cisco Systems Cisco Systems
January 10, 2017 March 31, 2017
Softwire Mesh Multicast Softwire Mesh Multicast
draft-ietf-softwire-mesh-multicast-15 draft-ietf-softwire-mesh-multicast-16
Abstract Abstract
The Internet needs to support IPv4 and IPv6 packets. Both address The Internet needs to support IPv4 and IPv6 packets. Both address
families and their related protocol suites support multicast of the families and their related protocol suites support multicast of the
single-source and any-source varieties. During IPv6 transition, single-source and any-source varieties. During IPv6 transition,
there will be scenarios where a backbone network running one IP there will be scenarios where a backbone network running one IP
address family internally (referred to as internal IP or I-IP) will address family internally (referred to as internal IP or I-IP) will
provide transit services to attached client networks running another provide transit services to attached client networks running another
IP address family (referred to as external IP or E-IP). It is IP address family (referred to as external IP or E-IP). It is
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 July 14, 2017. This Internet-Draft will expire on October 2, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 8, line 45 skipping to change at page 8, line 45
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| mPrefix46 |group address | | mPrefix46 |group address |
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
Figure 4: IPv4-Embedded IPv6 Multicast Address Format Figure 4: IPv4-Embedded IPv6 Multicast Address Format
An IPv6 multicast prefix (mPrefix46) is assigned to each AFBR. AFBRs An IPv6 multicast prefix (mPrefix46) is assigned to each AFBR. AFBRs
will prepend the prefix to an IPv4 multicast group address when will prepend the prefix to an IPv4 multicast group address when
translating it to an IPv6 multicast group address. translating it to an IPv6 multicast group address.
The mPrefix46 for SSM mode is also defined in Section 4.1 of The mPrefix46 for SSM mode is also defined in Section 2 of [RFC8114].
[RFC7371]
With this scheme, each IPv4 multicast address can be mapped into an With this scheme, each IPv4 multicast address can be mapped into an
IPv6 multicast address (with the assigned prefix), and each IPv6 IPv6 multicast address (with the assigned prefix), and each IPv6
multicast address with the assigned prefix can be mapped into an IPv4 multicast address with the assigned prefix can be mapped into an IPv4
multicast address. multicast address. The group address translation algorithm can be
reffered in Section 5.2 of [RFC8114].
4.3. Source Address Mapping 4.3. Source Address Mapping
There are two kinds of multicast: ASM and SSM. Considering that I-IP There are two kinds of multicast: ASM and SSM. Considering that I-IP
network and E-IP network may support different kinds of multicast, network and E-IP network may support different kinds of multicast,
the source address translation rules needed to support all possible the source address translation rules needed to support all possible
scenarios may become very complex. But since SSM can be implemented scenarios may become very complex. But since SSM can be implemented
with a strict subset of the PIM-SM protocol mechanisms [RFC7761], we with a strict subset of the PIM-SM protocol mechanisms [RFC7761], we
can treat the I-IP core as SSM-only to make it as simple as possible. can treat the I-IP core as SSM-only to make it as simple as possible.
There then remain only two scenarios to be discussed in detail: There then remain only two scenarios to be discussed in detail:
skipping to change at page 9, line 47 skipping to change at page 9, line 47
which is defined in [RFC6052]; which is defined in [RFC6052];
* The "v4" field is the IP address of one of upstream AFBR's * The "v4" field is the IP address of one of upstream AFBR's
E-IPv4 interfaces; E-IPv4 interfaces;
* The "u" field is defined in [RFC4291], and MUST be set to zero; * The "u" field is defined in [RFC4291], and MUST be set to zero;
* The "suffix" field is reserved for future extensions and SHOULD * The "suffix" field is reserved for future extensions and SHOULD
be set to zero; be set to zero;
* The "source address" field stores the original S. * The "source address" field stores the original source address.
We call the overall /96 prefix ("prefix" field and "v4" field and We call the overall /96 prefix ("prefix" field and "v4" field and
"u" field and "suffix" field altogether) "uPrefix46". "u" field and "suffix" field altogether) "uPrefix46".
o E-IP network supports ASM o E-IP network supports ASM
The (S,G) source list entry and the (*,G) source list entry only The (S,G) source list entry and the (*,G) source list entry only
differ in that the latter has both the WC and RPT bits of the differ in that the latter has both the WC and RPT bits of the
Encoded-Source-Address set, while the former is all cleared (See Encoded-Source-Address set, while the former is all cleared (See
Section 4.9.5.1 of [RFC7761]). So we can translate source list Section 4.9.5.1 of [RFC7761]). So we can translate source list
skipping to change at page 18, line 11 skipping to change at page 18, line 11
[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <http://www.rfc-editor.org/info/rfc6513>. 2012, <http://www.rfc-editor.org/info/rfc6513>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <http://www.rfc-editor.org/info/rfc7761>. 2016, <http://www.rfc-editor.org/info/rfc7761>.
[RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q.
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017,
<http://www.rfc-editor.org/info/rfc8114>.
11.2. Informative References 11.2. Informative References
[RFC7371] Boucadair, M. and S. Venaas, "Updates to the IPv6 [RFC7371] Boucadair, M. and S. Venaas, "Updates to the IPv6
Multicast Addressing Architecture", RFC 7371, Multicast Addressing Architecture", RFC 7371,
DOI 10.17487/RFC7371, September 2014, DOI 10.17487/RFC7371, September 2014,
<http://www.rfc-editor.org/info/rfc7371>. <http://www.rfc-editor.org/info/rfc7371>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Wenlong Chen, Xuan Chen, Alain Durand, Yiu Lee, Jacni Qin and Stig Wenlong Chen, Xuan Chen, Alain Durand, Yiu Lee, Jacni Qin and Stig
skipping to change at page 18, line 32 skipping to change at page 18, line 38
Authors' Addresses Authors' Addresses
Mingwei Xu Mingwei Xu
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R. China P.R. China
Phone: +86-10-6278-5822 Phone: +86-10-6278-5822
Email: xmw@cernet.edu.cn Email: xumwcs@gmail.com
Yong Cui Yong Cui
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R. China P.R. China
Phone: +86-10-6278-5822 Phone: +86-10-6278-5822
Email: cuiyong@tsinghua.edu.cn Email: cuiyong@tsinghua.edu.cn
Jianping Wu Jianping Wu
Tsinghua University Tsinghua University
Department of Computer Science, Tsinghua University Department of Computer Science, Tsinghua University
Beijing 100084 Beijing 100084
P.R. China P.R. China
Phone: +86-10-6278-5983 Phone: +86-10-6278-5983
Email: jianping@cernet.edu.cn Email: jianping@cernet.edu.cn
Shu Yang Shu Yang
Tsinghua University Tsinghua University
Graduate School at Shenzhen Graduate School at Shenzhen
Shenzhen 518055 Shenzhen 518055
P.R. China P.R. China
Phone: +86-10-6278-5822 Phone: +86-10-6278-5822
Email: yangshu@csnet1.cs.tsinghua.edu.cn Email: yangshu@csnet1.cs.tsinghua.edu.cn
Chris Metz Chris Metz
 End of changes. 11 change blocks. 
10 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/