Context Label for MPLS EVPN
draft-wang-bess-evpn-context-label-04

Document Type Expired Internet-Draft (individual)
Authors Yubao Wang  , Bing Song 
Last updated 2021-02-21 (latest revision 2020-08-20)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wang-bess-evpn-context-label-04.txt

Abstract

EVPN is designed to provide a better VPLS service than [RFC4761] and [RFC4762], and EVPN indeed introduced many new features which couldn't be achieved in those old VPLS implementions. But EVPN didn't inherit all features of old VPLS, and a few issues arises for EVPN only. Some of these issues can be imputed to the MP2P nature of EVPN labels. The PW label in old VPLS is a label for P2P VC, so it contains more context than a identifier in dataplane for it's VSI instance.But the EVPN label just identifies it's VSI instnace and it can't stand for the ingress PE in dataplane. So the following issues arises with MPLS EVPN service: * MPLS EVPN statistics can't be done per ingress PE. * MPLS EVPN can't support hub/spoke use case which the spoke PE can

Authors

Yubao Wang (wang.yubao2@zte.com.cn)
Bing Song (song.bing@zte.com.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)