Multicast VPN with Segment Routing Point-to-Multipoint Segment
draft-parekh-bess-mvpn-sr-p2mp-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-11
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group R. Parekh
Internet-Draft C. Filsfils
Intended status: Standards Track A. Venkateswaran
Expires: September 12, 2019 Cisco Systems, Inc.
H. Bidgoli
Nokia
D. Voyer
C. Hassen
Bell Canada
March 11, 2019
Multicast VPN with Segment Routing Point-to-Multipoint Segment
draft-parekh-bess-mvpn-sr-p2mp-00.txt
Abstract
A Point-to-Multipoint (P2MP) Segment in a Segment Routing domain
efficiently carries traffic from a Root to a set of Leaves. This
document describes extensions to BGP encodings and procedures for
P2MP segments used in BGP/MPLS IP VPNs.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 12, 2019.
Parekh, et al. Expires September 12, 2019 [Page 1]
Internet-Draft BGP MVPN with SR P2MP Segment March 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. P2MP Segment P-Tunnels for MPVN . . . . . . . . . . . . . . . 3
3. PMSI Tunnel Attribute for P2MP Segment . . . . . . . . . . . 4
3.1. MPLS Label . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. SR MPLS . . . . . . . . . . . . . . . . . . . . . . . 5
4. Auto-Discovery and Binding Procedures . . . . . . . . . . . . 5
4.1. Intra-AS I-PMSI . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Originating Intra-AS I-PMSI routes . . . . . . . . . 5
4.1.2. Receiving Intra-AS I-PMSI A-D routes . . . . . . . . 6
4.2. Using S-PMSIs for binding customer flows to P2MP Segments 7
4.2.1. Originating S-PMSI A-D routes . . . . . . . . . . . . 7
4.2.2. Receiving S-PMSI A-D routes . . . . . . . . . . . . . 7
4.3. Inter-AS P-tunnels using P2MP Segments . . . . . . . . . 8
4.3.1. Advertising Inter-AS I-PMSI routes into iBGP . . . . 8
4.3.2. Receiving Inter-AS I-PMSI A-D routes in iBGP . . . . 8
4.4. Leaf A-D routes for P2MP Segment Leaf Discovery . . . . . 8
4.4.1. Originating Leaf A-D routes . . . . . . . . . . . . . 9
4.4.2. Receiving Leaf A-D routes . . . . . . . . . . . . . . 9
5. Damping of MVPN routes . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Parekh, et al. Expires September 12, 2019 [Page 2]
Show full document text