EVPN VPWS as VRF Attachment Circuit
draft-wz-bess-evpn-vpws-as-vrf-ac-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yubao Wang , Zheng Zhang | ||
| Last updated | 2022-03-01 (Latest revision 2021-08-28) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When a VRF Attachment Cirucit (VRF-AC) is far away from its IP-VRF instance, we can deploy an EVPN VPWS ([RFC8214]) between that VRF-AC and its IP-VRF instance. From the viewpoint of the IP-VRF instance, a local virtual interface takes the place of that remote "VRF-AC". The IP address for that VRF-AC is now configured to the virtual interface, in other words, the virtual interface is the actual VRF-AC of the IP-VRF instance. The virtual interface is also the AC of that VPWS instance, in other words, the virtual interface is cross- connected to that remote "VRF-AC" by the VPWS instance. This document proposes an extension to [I-D.ietf-bess-evpn-inter-subnet-forwarding] to support this scenario.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)