RFC 8466: A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8466
- Published
- October 2018
- Authors
- B. Wen; G. Fioccola; C. Xie; L. Jalil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 158
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8049YANG Data Model for L3VPN Service DeliveryObsoleted
February 2017
- RFC 8468IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) FrameworkCurrent
November 2018
- RFC 8475Using Conditional Router Advertisements for Enterprise MultihomingCurrent
October 2018
- RFC 8456Benchmarking Methodology for Software-Defined Networking (SDN) Controller PerformanceCurrent
October 2018
- RFC 8455Terminology for Benchmarking Software-Defined Networking (SDN) Controller PerformanceCurrent
October 2018
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
- RFC 8482Providing Minimal-Sized Responses to DNS Queries That Have QTYPE=ANYCurrent
January 2019
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?