draft-ietf-bess-ir-02.txt   draft-ietf-bess-ir-03.txt 
BESS Working Group E. Rosen, Ed. BESS Working Group E. Rosen, Ed.
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Updates: 6513,6514 (if approved) K. Subramanian Updates: 6513,6514 (if approved) K. Subramanian
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: April 17, 2016 Z. Zhang Expires: October 13, 2016 Z. Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
October 15, 2015 April 11, 2016
Ingress Replication Tunnels in Multicast VPN Ingress Replication Tunnels in Multicast VPN
draft-ietf-bess-ir-02 draft-ietf-bess-ir-03
Abstract Abstract
RFCs 6513, 6514, and other RFCs describe procedures by which a RFCs 6513, 6514, and other RFCs describe procedures by which a
Service Provider may offer Multicast VPN service to its customers. Service Provider may offer Multicast VPN service to its customers.
These procedures create point-to-multipoint (P2MP) or multipoint-to- These procedures create point-to-multipoint (P2MP) or multipoint-to-
multipoint trees across the Service Provider's backbone. One type of multipoint trees across the Service Provider's backbone. One type of
P2MP tree that may be used is known as an "Ingress Replication (IR) P2MP tree that may be used is known as an "Ingress Replication (IR)
tunnel". In an IR tunnel, a parent node need not be "directly tunnel". In an IR tunnel, a parent node need not be "directly
connected" to its child nodes. When a parent node has to send a connected" to its child nodes. When a parent node has to send a
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 April 17, 2016. This Internet-Draft will expire on October 13, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 5, line 12 skipping to change at page 5, line 12
procedures that are not clearly specified in [RFC6513] or [RFC6514]. procedures that are not clearly specified in [RFC6513] or [RFC6514].
As the material in this document must be understood in order to As the material in this document must be understood in order to
properly implement IR P-tunnels, this document is considered to properly implement IR P-tunnels, this document is considered to
update [RFC6513] and [RFC6514]. update [RFC6513] and [RFC6514].
This document also discusses the application of "seamless multicast" This document also discusses the application of "seamless multicast"
[RFC7524] and "extranet" [MVPN-XNET] procedures to IR P-tunnels. [RFC7524] and "extranet" [MVPN-XNET] procedures to IR P-tunnels.
This draft does not discuss the use of IR P-tunnels to support a VPN This draft does not discuss the use of IR P-tunnels to support a VPN
customer's use of Bidirectional Protocol Independent Multicast customer's use of Bidirectional Protocol Independent Multicast
(BIDIR-PIM). [C-BIDIR-IR] explains how to adapt the procedures of (BIDIR-PIM). [RFC7740] explains how to adapt the procedures of
[RFC6513], [RFC6514], and [RFC7582] so that a customer's use of [RFC6513], [RFC6514], and [RFC7582] so that a customer's use of
BIDIR-PIM can be supported by IR P-tunnels. BIDIR-PIM can be supported by IR P-tunnels.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when and only when appearing in all capital letters, are "OPTIONAL", when and only when appearing in all capital letters, are
to be interpreted as described in [RFC2119]. to be interpreted as described in [RFC2119].
2. What is an IR P-tunnel? 2. What is an IR P-tunnel?
An IR P-tunnel is a P2MP tree. Its nodes are BGP speakers that An IR P-tunnel is a P2MP tree. Its nodes are BGP speakers that
support the MVPN procedures of [RFC6514] and related RFCs. In support the MVPN procedures of [RFC6514] and related RFCs. In
general, the nodes of an IR P-tunnel are either Provider Edge (PE) general, the nodes of an IR P-tunnel are either Provider Edge (PE)
routers, Autonomous System Border Routers (ASBRs), or (if [RFC7524] routers, Autonomous System Border Routers (ASBRs), or (if [RFC7524]
is supported) Area Border Routers (ABRs). (MVPN procedures are is supported) Area Border Routers (ABRs). (MVPN procedures are
sometimes used to support non-MVPN, or "global table" multicast; one sometimes used to support non-MVPN, or "global table" multicast; one
way of doing this is defined in [RFC7524]. Another way is defined in way of doing this is defined in [RFC7524]. Another way is defined in
[GTM]. In such cases, IR P-tunnels can be used outside the context [RFC7716]. In such cases, IR P-tunnels can be used outside the
of MVPN.) context of MVPN.)
MVPN P-tunnels may be either "segmented" or "non-segmented" (as these MVPN P-tunnels may be either "segmented" or "non-segmented" (as these
terms are defined in [RFC6513] and [RFC6514]). terms are defined in [RFC6513] and [RFC6514]).
A "non-segmented" IR P-tunnel is a two-level P2MP tree, consisting A "non-segmented" IR P-tunnel is a two-level P2MP tree, consisting
only of a root node and a set of nodes that are children of the root only of a root node and a set of nodes that are children of the root
node. When used in an MVPN context, the root is an ingress PE, and node. When used in an MVPN context, the root is an ingress PE, and
the child nodes of the root are the egress PEs. the child nodes of the root are the egress PEs.
In a segmented P-tunnel, IR may be used for some or all of the In a segmented P-tunnel, IR may be used for some or all of the
skipping to change at page 21, line 17 skipping to change at page 21, line 17
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<http://www.rfc-editor.org/info/rfc6514>. <http://www.rfc-editor.org/info/rfc6514>.
[RFC6515] Aggarwal, R. and E. Rosen, "IPv4 and IPv6 Infrastructure [RFC6515] Aggarwal, R. and E. Rosen, "IPv4 and IPv6 Infrastructure
Addresses in BGP Updates for Multicast VPN", RFC 6515, Addresses in BGP Updates for Multicast VPN", RFC 6515,
DOI 10.17487/RFC6515, February 2012, DOI 10.17487/RFC6515, February 2012,
<http://www.rfc-editor.org/info/rfc6515>. <http://www.rfc-editor.org/info/rfc6515>.
14.2. Informative References 14.2. Informative References
[C-BIDIR-IR]
Zhang, Z., Rekhter, Y., and A. Dolganow, "Simulating
'Partial Mesh of MP2MP P-Tunnels' with Ingress
Replication", internet-draft draft-ietf-bess-mvpn-bidir-
ingress-replication-03, September 2015.
[GTM] Zhang, J., Giulano, L., Rosen, E., Subramanian, K., and D.
Pacella, "Global Table Multicast with BGP-MVPN
Procedures", internet-draft draft-ietf-bess-mvpn-global-
table-mcast-03, September 2015.
[MVPN-XNET] [MVPN-XNET]
Rekhter, Y., Rosen, E., Aggarwal, R., Cai, Y., and T. Rekhter, Y., Rosen, E., Aggarwal, R., Cai, Y., and T.
Morin, "Extranet Multicast in BGP/IP MPLS VPNs", internet- Morin, "Extranet Multicast in BGP/IP MPLS VPNs", internet-
draft draft-ietf-bess-mvpn-extranet-02, May 2015. draft draft-ietf-bess-mvpn-extranet-06, January 2016.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<http://www.rfc-editor.org/info/rfc3209>. <http://www.rfc-editor.org/info/rfc3209>.
[RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.,
"LDP Specification", RFC 5036, DOI 10.17487/RFC5036, "LDP Specification", RFC 5036, DOI 10.17487/RFC5036,
October 2007, <http://www.rfc-editor.org/info/rfc5036>. October 2007, <http://www.rfc-editor.org/info/rfc5036>.
skipping to change at page 22, line 16 skipping to change at page 22, line 5
Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area
Point-to-Multipoint (P2MP) Segmented Label Switched Paths Point-to-Multipoint (P2MP) Segmented Label Switched Paths
(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,
<http://www.rfc-editor.org/info/rfc7524>. <http://www.rfc-editor.org/info/rfc7524>.
[RFC7582] Rosen, E., Wijnands, IJ., Cai, Y., and A. Boers, [RFC7582] Rosen, E., Wijnands, IJ., Cai, Y., and A. Boers,
"Multicast Virtual Private Network (MVPN): Using "Multicast Virtual Private Network (MVPN): Using
Bidirectional P-Tunnels", RFC 7582, DOI 10.17487/RFC7582, Bidirectional P-Tunnels", RFC 7582, DOI 10.17487/RFC7582,
July 2015, <http://www.rfc-editor.org/info/rfc7582>. July 2015, <http://www.rfc-editor.org/info/rfc7582>.
[RFC7716] Zhang, J., Giuliano, L., Rosen, E., Ed., Subramanian, K.,
and D. Pacella, "Global Table Multicast with BGP Multicast
VPN (BGP-MVPN) Procedures", RFC 7716,
DOI 10.17487/RFC7716, December 2015,
<http://www.rfc-editor.org/info/rfc7716>.
[RFC7740] Zhang, Z., Rekhter, Y., and A. Dolganow, "Simulating
Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider
Tunnels with Ingress Replication", RFC 7740,
DOI 10.17487/RFC7740, January 2016,
<http://www.rfc-editor.org/info/rfc7740>.
Authors' Addresses Authors' Addresses
Eric C. Rosen (editor) Eric C. Rosen (editor)
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, Massachusetts 01886 Westford, Massachusetts 01886
United States United States
Email: erosen@juniper.net Email: erosen@juniper.net
 End of changes. 10 change blocks. 
20 lines changed or deleted 21 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/