MVPN/EVPN Composite Tunnel
draft-zzhang-bess-mvpn-evpn-composite-tunnel-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)
|
BESS Z. Zhang
Internet-Draft Juniper Networks
Intended status: Standards Track J. Rabadan, Ed.
Expires: September 12, 2019 Nokia
A. Sajassi
Cisco Systems
March 11, 2019
MVPN/EVPN Composite Tunnel
draft-zzhang-bess-mvpn-evpn-composite-tunnel-00
Abstract
EVPN E-Tree defines a composite tunnel to be used for a Root PE to
simultaneously indicate a non-Ingress-Replication tunnel (e.g., P2MP
tunnel) in the transmit direction and an Ingress Replication tunnel
in the receive direction for BUM traffic. This document extends it
to more generic use in both MVPN and general EVPN.
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 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.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Zhang, et al. Expires September 12, 2019 [Page 1]
Internet-Draft composite-tunnel March 2019
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. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. P2MP Tunnels . . . . . . . . . . . . . . . . . . . . . . 3
2.2. MP2MP Tunnels . . . . . . . . . . . . . . . . . . . . . . 4
3. Specifications . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. General MVPN/EVPN Use of Composite Tunnels . . . . . . . 4
3.2. EVPN-IP Assisted Replication with BIER-IR Composite
Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. BIER-IR Composite Tunnels in EVPN Networks . . . . . . . 7
4.2. Assisted Replication and BIER Composite Tunnels . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Terminologies
Familiarity with BIER/MVPN/EVPN protocols and procedures is assumed.
Some terminologies are listed below for convenience.
[To be added].
2. Introduction
The composite tunnel defined in [RFC8317] is specifically designed
for the particular use case of EVPN E-Tree in that the Root PE only
needs to receive on the Ingress Replication (IR) tunnel and transmit
on the non-IR tunnel encoded in the PMSI Tunnel Attribute (PTA) that
specifies a Composite Tunnel, hence the following language quoted
from [RFC8317]:
Zhang, et al. Expires September 12, 2019 [Page 2]
Internet-Draft composite-tunnel March 2019
Composite tunnel type is advertised by the Root PE to
simultaneously indicate a non-Ingress-Replication tunnel (e.g., P2MP
tunnel) in the transmit direction and an Ingress Replication tunnel
Show full document text