EVPN auto provisioning using a controller
draft-boutros-bess-evpn-auto-provisoning-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sami Boutros , Rex Fernando , Ali Sajassi , Junying Pang, tsingh@juniper.net | ||
| Last updated | 2017-04-24 (Latest revision 2016-10-21) | ||
| 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
In some datacenter use cases, priori knowledge of what PE/NVE to be configured for a given L2 or L3 service may not be available. This document describes how EVPN can be extended to discover what L2 or L3 services to be enabled on a given PE/NVE, based on first sign of life FSOL packets received on the PE/NVE ports. An EVPN route based on the FSOL packets will be sent to a controller to trigger a push of the related L2/L3 or subscriber service configuration to be provisioned on the PE/NVE and on the switch ports.
Authors
Sami Boutros
Rex Fernando
Ali Sajassi
Junying Pang
tsingh@juniper.net
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)