YANG Data Model for L3VPN service delivery
draft-l3vpn-service-yang-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Stephane Litkowski , Rob Shakir , Luis Tomotaki , Kevin D'Souza | ||
Last updated | 2015-02-26 | ||
Replaced by | draft-ltsd-l3sm-l3vpn-service-model | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ltsd-l3sm-l3vpn-service-model | |
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
This document defines a YANG data model that can be used to deliver a Layer 3 Provider Provisioned VPN service. The document is limited to the BGP PE-based VPNs as described in [RFC4110] and [RFC4364]. This model is intended to be instantiated at management system to deliver the overall service. This model is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IPVPN service configuration components. It will be up to a management system to take this as an input and use specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document.
Authors
Stephane Litkowski
Rob Shakir
Luis Tomotaki
Kevin D'Souza
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)