EVPN BUM Using BIER
draft-ietf-bier-evpn-03
|
| Document |
Type |
|
Active Internet-Draft (bier WG)
|
|
Last updated |
|
2020-04-16
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
BIER Z. Zhang
Internet-Draft A. Przygienda
Intended status: Standards Track Juniper Networks
Expires: October 18, 2020 A. Sajassi
Cisco Systems
J. Rabadan
Nokia
April 16, 2020
EVPN BUM Using BIER
draft-ietf-bier-evpn-03
Abstract
This document specifies protocols and procedures for forwarding
broadcast, unknown unicast and multicast (BUM) traffic of Ethernet
VPNs (EVPN) using Bit Index Explicit Replication (BIER).
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 October 18, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Zhang, et al. Expires October 18, 2020 [Page 1]
Internet-Draft bier-evpn April 2020
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminologies . . . . . . . . . . . . . . . . . . . . . . 3
2. Use of the PMSI Tunnel Attribute . . . . . . . . . . . . . . 4
2.1. IP Based Tunnel and BIER PHP . . . . . . . . . . . . . . 5
2.2. Explicit Tracking . . . . . . . . . . . . . . . . . . . . 6
2.2.1. Using IMET/SMET routes . . . . . . . . . . . . . . . 6
2.2.2. Using S-PMSI/Leaf A-D Routes . . . . . . . . . . . . 6
2.3. MPLS Label in PTA . . . . . . . . . . . . . . . . . . . . 7
3. Multihoming Split Horizon . . . . . . . . . . . . . . . . . . 8
4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Encapsulation and Transmission . . . . . . . . . . . . . 8
4.1.1. At a BFIR that is an Ingress PE . . . . . . . . . . . 8
4.1.2. At a BFIR that is a P-tunnel Segmentation Point . . . 10
4.2. Disposition . . . . . . . . . . . . . . . . . . . . . . . 11
4.2.1. At a BFER that is an Egress PE . . . . . . . . . . . 11
4.2.2. At a BFER that is a P-tunnel Segmentation Point . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
[RFC7432] and [RFC8365] specify the protocols and procedures for
Ethernet VPNs (EVPNs). For broadcast, unknown unicast and multicast
(BUM) traffic, provider/underlay tunnels (referred to as P-tunnels)
are used to carry the BUM traffic. Several kinds of tunnel
technologies can be used, as specified in [RFC7432].
Bit Index Explicit Replication (BIER) ([RFC8279]) is an architecture
that provides optimal multicast forwarding through a "multicast
domain", without requiring intermediate routers to maintain any per-
Show full document text