Skip to main content

A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
RFC 8466

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2019-01-29
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-19
(System)
Received changes through RFC Editor sync (changed abstract to 'This document defines a YANG data model that can be used to configure a Layer 2 …
Received changes through RFC Editor sync (changed abstract to 'This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is done is out of scope for this document.

The YANG data model defined in this document includes support for point-to-point Virtual Private Wire Services (VPWSs) and multipoint Virtual Private LAN Services (VPLSs) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFCs 4761 and 6624.

The YANG data model defined in this document conforms to the Network Management Datastore Architecture defined in RFC 8342.')
2018-10-12
(System)
Received changes through RFC Editor sync (created alias RFC 8466, changed title to 'A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) …
Received changes through RFC Editor sync (created alias RFC 8466, changed title to 'A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery', changed abstract to 'This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is done is out of scope for this document.', changed pages to 158, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-10-12, changed IESG state to RFC Published)
2018-10-12
(System) RFC published