Optimized Ingress Replication solution for EVPN
draft-ietf-bess-evpn-optimized-ir-07
| Document | Type | Active Internet-Draft (bess WG) | |
|---|---|---|---|
| Authors | Jorge Rabadan , Senthil Sathappan , Wen Lin , Mukul Katiyar , Ali Sajassi | ||
| Last updated | 2020-07-13 | ||
| Replaces | draft-rabadan-bess-evpn-optimized-ir | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | plain text pdf htmlized (tools) htmlized bibtex | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Matthew Bocci | ||
| Shepherd write-up | Show (last changed 2018-10-22) | ||
| IESG | IESG state | AD Evaluation::AD Followup | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Martin Vigoureux | ||
| Send notices to | Matthew Bocci <matthew.bocci@nokia.com> | ||
BESS Workgroup J. Rabadan, Ed.
Internet-Draft S. Sathappan
Intended status: Standards Track Nokia
Expires: January 14, 2021 W. Lin
Juniper Networks
M. Katiyar
Versa Networks
A. Sajassi
Cisco Systems
July 13, 2020
Optimized Ingress Replication solution for EVPN
draft-ietf-bess-evpn-optimized-ir-07
Abstract
Network Virtualization Overlay (NVO) networks using EVPN as control
plane may use Ingress Replication (IR) or PIM (Protocol Independent
Multicast) based trees to convey the overlay BUM traffic. PIM
provides an efficient solution to avoid sending multiple copies of
the same packet over the same physical link, however it may not
always be deployed in the NVO core network. IR avoids the dependency
on PIM in the NVO network core. While IR provides a simple multicast
transport, some NVO networks with demanding multicast applications
require a more efficient solution without PIM in the core. This
document describes a solution to optimize the efficiency of IR in NVO
networks.
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 January 14, 2021.
Rabadan, et al. Expires January 14, 2021 [Page 1]
Internet-Draft EVPN Optimized IR July 2020
Copyright Notice
Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4
3. Solution requirements . . . . . . . . . . . . . . . . . . . . 6
4. EVPN BGP Attributes for optimized-IR . . . . . . . . . . . . 6
5. Non-selective Assisted-Replication (AR) Solution Description 10
5.1. Non-selective AR-REPLICATOR procedures . . . . . . . . . 11
5.2. Non-selective AR-LEAF procedures . . . . . . . . . . . . 12
5.3. RNVE procedures . . . . . . . . . . . . . . . . . . . . . 15
6. Selective Assisted-Replication (AR) Solution Description . . 15
6.1. Selective AR-REPLICATOR procedures . . . . . . . . . . . 15
6.2. Selective AR-LEAF procedures . . . . . . . . . . . . . . 18
7. Pruned-Flood-Lists (PFL) . . . . . . . . . . . . . . . . . . 19
7.1. A PFL example . . . . . . . . . . . . . . . . . . . . . . 20
8. AR Procedures for single-IP AR-REPLICATORS . . . . . . . . . 21
9. AR Procedures and EVPN All-Active Multi-homing Split-Horizon 21
9.1. Ethernet Segments on AR-LEAF nodes . . . . . . . . . . . 22
9.2. Ethernet Segments on AR-REPLICATOR nodes . . . . . . . . 22
10. Security Considerations . . . . . . . . . . . . . . . . . . . 23
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
14.1. Normative References . . . . . . . . . . . . . . . . . . 24
14.2. Informative References . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction
Show full document text