draft-ietf-bess-mvpn-extranet-01.txt   draft-ietf-bess-mvpn-extranet-02.txt 
BESS Working Group Y. Rekhter, Ed. BESS Working Group Y. Rekhter, Ed.
Internet-Draft E. Rosen, Ed. Internet-Draft E. Rosen, Ed.
Updates: 6513,6514,6625 (if approved) Juniper Networks, Inc. Updates: 6513,6514,6625 (if approved) Juniper Networks, Inc.
Intended status: Standards Track R. Aggarwal Intended status: Standards Track R. Aggarwal
Expires: October 22, 2015 Arktan Expires: November 8, 2015 Arktan
Y. Cai Y. Cai
Microsoft Microsoft
W. Henderickx
Alcatel-Lucent
T. Morin T. Morin
Orange Orange
P. Muley May 7, 2015
Alcatel-Lucent
R. Qiu
Juniper Networks, Inc.
IJ. Wijnands
Cisco Systems, Inc.
April 20, 2015
Extranet Multicast in BGP/IP MPLS VPNs Extranet Multicast in BGP/IP MPLS VPNs
draft-ietf-bess-mvpn-extranet-01 draft-ietf-bess-mvpn-extranet-02
Abstract Abstract
Previous RFCs specify the procedures necessary to allow IP multicast Previous RFCs specify the procedures necessary to allow IP multicast
traffic to travel from one site to another within a BGP/MPLS IP VPN traffic to travel from one site to another within a BGP/MPLS IP VPN
(Virtual Private Network). However, it is sometimes desirable to (Virtual Private Network). However, it is sometimes desirable to
allow multicast traffic whose source is in one VPN to be received by allow multicast traffic whose source is in one VPN to be received by
systems that are in another VPN. This is known as a "Multicast VPN systems that are in another VPN. This is known as a "Multicast VPN
(MVPN) extranet". This document updates RFCs 6513, 6514, and 6625 by (MVPN) extranet". This document updates RFCs 6513, 6514, and 6625 by
specifying the procedures that are necessary in order to provide MVPN specifying the procedures that are necessary in order to provide MVPN
skipping to change at page 2, line 4 skipping to change at page 1, line 42
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 22, 2015.
This Internet-Draft will expire on November 8, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1. Customer Multicast Control 1.2.1. Customer Multicast Control
Protocols . . . . . . . . . . . . . . . . . . . . . . 7 Protocols . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2. Provider Multicast Control 1.2.2. Provider Multicast Control
Protocols . . . . . . . . . . . . . . . . . . . . . . 7 Protocols . . . . . . . . . . . . . . . . . . . . . . 7
1.3. Clarification on Use of Route 1.3. Clarification on Use of Route
Distinguishers . . . . . . . . . . . . . . . . . . . . . 7 Distinguishers . . . . . . . . . . . . . . . . . . . . . 7
1.4. Overview . . . . . . . . . . . . . . . . . . . . . . . . 9 1.4. Overview . . . . . . . . . . . . . . . . . . . . . . . . 8
2. Extranets and Overlapping Address 2. Extranets and Overlapping Address
Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1. Ambiguity: P-tunnel with 2.1. Ambiguity: P-tunnel with
Extranet/Non-Extranet Flows . . . . . . . . . . . . . . . 12 Extranet/Non-Extranet Flows . . . . . . . . . . . . . . . 12
2.2. Ambiguity: P-tunnel with Multiple 2.2. Ambiguity: P-tunnel with Multiple
Extranet Flows . . . . . . . . . . . . . . . . . . . . . 14 Extranet Flows . . . . . . . . . . . . . . . . . . . . . 14
2.3. Preventing Misdelivery in These 2.3. Preventing Misdelivery in These
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 17 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.1. Do Not Deliver Packets from the 'Wrong' P-tunnel . . 17 2.3.1. Do Not Deliver Packets from the 'Wrong' P-tunnel . . 17
2.3.2. Policies to Prevent Ambiguity on a P-tunnel . . . . . 18 2.3.2. Policies to Prevent Ambiguity on a P-tunnel . . . . . 18
3. Extranet Transmission Models . . . . . . . . . . . . . . . . 20 3. Extranet Transmission Models . . . . . . . . . . . . . . . . 20
3.1. Transmitting an Extranet C-flow on a Single PMSI . . . . 20 3.1. Transmitting an Extranet C-flow on a Single PMSI . . . . 20
skipping to change at page 4, line 11 skipping to change at page 4, line 4
7.3.3. Source Active A-D Routes . . . . . . . . . . . . . . 48 7.3.3. Source Active A-D Routes . . . . . . . . . . . . . . 48
7.4. Determining the Expected P-tunnel for a C-flow . . . . . 48 7.4. Determining the Expected P-tunnel for a C-flow . . . . . 48
7.4.1. (C-S,C-G) S-PMSI A-D Routes . . . . . . . . . . . . . 50 7.4.1. (C-S,C-G) S-PMSI A-D Routes . . . . . . . . . . . . . 50
7.4.2. (C-S,C-*) S-PMSI A-D Routes . . . . . . . . . . . . . 51 7.4.2. (C-S,C-*) S-PMSI A-D Routes . . . . . . . . . . . . . 51
7.4.3. (C-*,C-G) S-PMSI A-D Routes . . . . . . . . . . . . . 51 7.4.3. (C-*,C-G) S-PMSI A-D Routes . . . . . . . . . . . . . 51
7.4.4. (C-*,C-*) S-PMSI A-D Routes . . . . . . . . . . . . . 52 7.4.4. (C-*,C-*) S-PMSI A-D Routes . . . . . . . . . . . . . 52
7.4.5. I-PMSI A-D Routes . . . . . . . . . . . . . . . . . . 52 7.4.5. I-PMSI A-D Routes . . . . . . . . . . . . . . . . . . 52
7.5. Packets Arriving from the Wrong P-tunnel . . . . . . . . 53 7.5. Packets Arriving from the Wrong P-tunnel . . . . . . . . 53
8. Multiple Extranet VRFs on the same 8. Multiple Extranet VRFs on the same
PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
10. Security Considerations . . . . . . . . . . . . . . . . . . . 55 10. Security Considerations . . . . . . . . . . . . . . . . . . . 55
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 56 12. Contributor Addresses . . . . . . . . . . . . . . . . . . . . 56
12.1. Normative References . . . . . . . . . . . . . . . . . . 56 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
12.2. Informative References . . . . . . . . . . . . . . . . . 57 13.1. Normative References . . . . . . . . . . . . . . . . . . 57
13.2. Informative References . . . . . . . . . . . . . . . . . 58
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
1. Introduction 1. Introduction
Previous RFCs ([RFC6513], [RFC6514]) specify the procedures necessary Previous RFCs ([RFC6513], [RFC6514]) specify the procedures necessary
to allow IP multicast traffic to travel from one site to another to allow IP multicast traffic to travel from one site to another
within a BGP/MPLS IP VPN (Virtual Private Network). However, it is within a BGP/MPLS IP VPN (Virtual Private Network). However, it is
sometimes desirable to allow multicast traffic whose source is in one sometimes desirable to allow multicast traffic whose source is in one
VPN to be received by systems that are in another VPN. This is known VPN to be received by systems that are in another VPN. This is known
as an "extranet MVPN". This document specifies the procedures that as an "extranet MVPN". This document specifies the procedures that
skipping to change at page 56, line 39 skipping to change at page 56, line 39
The authors wish to thank DP Ayyadevara, Robert Kebler, Padmini The authors wish to thank DP Ayyadevara, Robert Kebler, Padmini
Misra, Rayen Mohanty, Maria Napierala, Karthik Subramanian, and Kurt Misra, Rayen Mohanty, Maria Napierala, Karthik Subramanian, and Kurt
Windisch for their contributions to this work. Windisch for their contributions to this work.
We also wish to thank Lizhong Jin and Rishabh Parekh for their We also wish to thank Lizhong Jin and Rishabh Parekh for their
reviews and comments. reviews and comments.
Special thanks to Jeffrey (Zhaohui) Zhang for his careful review and Special thanks to Jeffrey (Zhaohui) Zhang for his careful review and
for providing the ascii art appearing in Section 2. for providing the ascii art appearing in Section 2.
12. References 12. Contributor Addresses
12.1. Normative References Below is a list of other contributing authors in alphabetical order:
Wim Henderickx
Alcatel-Lucent
Copernicuslaan 50
Antwerp 2018
Belgium
Email: wim.henderickx@alcatel-lucent.com
Praveen Muley
Alcatel-Lucent
Email: Praveen.Muley@alcatel-lucent.com
Ray Qiu
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
United States
Email: rqiu@juniper.net
IJsbrand Wijnands
Cisco Systems, Inc.
De Kleetlaan 6a
Diegem 1831
Belgium
Email: ice@cisco.com
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.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006. Networks (VPNs)", RFC 4364, February 2006.
[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.
skipping to change at page 57, line 16 skipping to change at page 58, line 13
VPNs", RFC 6513, February 2012. VPNs", RFC 6513, February 2012.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, February 2012. VPNs", RFC 6514, February 2012.
[RFC6625] Rosen, E., Rekhter, Y., Hendrickx, W., and R. Qiu, [RFC6625] Rosen, E., Rekhter, Y., Hendrickx, W., and R. Qiu,
"Wildcards in Multicast VPN Auto-Discovery Routes", RFC "Wildcards in Multicast VPN Auto-Discovery Routes", RFC
6625, May 2012. 6625, May 2012.
12.2. Informative References 13.2. Informative References
[MVPN-IR] Rosen, E., Subramanian, K., and Z. Zhang, "Ingress [MVPN-IR] Rosen, E., Subramanian, K., and Z. Zhang, "Ingress
Replication Tunnels in Multicast VPN", internet-draft Replication Tunnels in Multicast VPN", internet-draft
draft-ietf-bess-ir-00, July 2014. draft-ietf-bess-ir-01, May 2015.
[RFC3446] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast [RFC3446] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast
Rendevous Point (RP) mechanism using Protocol Independent Rendevous Point (RP) mechanism using Protocol Independent
Multicast (PIM) and Multicast Source Discovery Protocol Multicast (PIM) and Multicast Source Discovery Protocol
(MSDP)", RFC 3446, January 2003. (MSDP)", RFC 3446, January 2003.
[RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery
Protocol (MSDP)", RFC 3618, October 2003. Protocol (MSDP)", RFC 3618, October 2003.
[RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol [RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol
skipping to change at page 58, line 34 skipping to change at page 59, line 31
Email: raggarwa_1@yahoo.com Email: raggarwa_1@yahoo.com
Yiqun Cai Yiqun Cai
Microsoft Microsoft
1065 La Avenida 1065 La Avenida
Mountain View, CA 94043 Mountain View, CA 94043
United States United States
Email: yiqunc@microsoft.com Email: yiqunc@microsoft.com
Wim Henderickx
Alcatel-Lucent
Copernicuslaan 50
Antwerp 2018
Belgium
Email: wim.henderickx@alcatel-lucent.com
Thomas Morin Thomas Morin
Orange Orange
2 Avenue Pierre-Marzin 2 Avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
France France
Email: thomas.morin@orange.com Email: thomas.morin@orange.com
Praveen Muley
Alcatel-Lucent
Email: Praveen.Muley@alcatel-lucent.com
Ray Qiu
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
United States
Email: rqiu@juniper.net
IJsbrand Wijnands
Cisco Systems, Inc.
De Kleetlaan 6a
Diegem 1831
Belgium
Email: ice@cisco.com
 End of changes. 17 change blocks. 
30 lines changed or deleted 51 lines changed or added

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