YANG Data Model for L2VPN service
draft-xie-l3sm-l2vpn-service-model-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Chongfeng Xie , Aijun Wang , Roland Schott , Dacheng Zhang | ||
| Last updated | 2016-05-04 (Latest revision 2015-11-01) | ||
| 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
This document provides an example of service yang data model for layer 2 provider provisioned VPN service. Unlike L3VPN, L2VPN doesn't provide L3 interface to customer using IP infrastructure or doesn't provide IP connectivity between pairs of customer sites. Therefore straight augment the l3vpn model with l2vpn parameters may not be appropriate. However [draft-ietf-l3sm-l3vpn-service-model] has defined a lot of reusable groupings such as operational- requirements, customer-location-info, site-diversity ,site- availability,etc. In this document, we reuse these common groupings and add some l2vpn parameters to develop the l2vpn service model. Similar to the l3vpn service model, this model provides an abstracted view of the Layer 2 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.
Authors
Chongfeng Xie
Aijun Wang
Roland Schott
Dacheng Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)