RFC 9291: A YANG Network Data Model for Layer 2 VPNs
In plain English — editorial summary, not part of the RFC
This document defines an L2VPN Network Model (L2NM) that can be used to manage the provisioning of Layer 2 Virtual Private Network (L2VPN) services within a network (e.g., a service provider network). The L2NM complements the L2VPN Service Model (L2SM) by providing a network-centric view of the service that is internal to a service provider. The L2NM is particularly meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices. Also, this document defines a YANG module to manage Ethernet segments and the initial versions of two IANA-maintained modules that include a set of identities of BGP Layer 2 encapsulation types and pseudowire types.
Document record
- Document ID
- RFC9291
- Published
- September 2022
- Authors
- M. Boucadair; O. Gonzalez de Dios; S. Barguil; L. Munoz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 139
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
- RFC 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent
February 2022
- RFC 9833A Common YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9834YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)Current
September 2025
- RFC 9835A Network YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9836A YANG Data Model for Augmenting VPN Service and Network Models with Attachment CircuitsCurrent
September 2025
- RFC 9408A YANG Network Data Model for Service Attachment Points (SAPs)Current
June 2023
- RFC 8969A Framework for Automating Service and Network Management with YANGCurrent
January 2021
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?