RFC 9182: A YANG Network Data Model for Layer 3 VPNs
In plain English — editorial summary, not part of the RFC
As a complement to the Layer 3 Virtual Private Network Service Model (L3SM), which is used for communication between customers and service providers, this document defines an L3VPN Network Model (L3NM) that can be used for the provisioning of Layer 3 Virtual Private Network (L3VPN) services within a service provider network. The model provides a network-centric view of L3VPN services. The L3NM is meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices. The model can also facilitate communication between a service orchestrator and a network controller/orchestrator.
Document record
- Document ID
- RFC9182
- Published
- February 2022
- Authors
- S. Barguil; O. Gonzalez de Dios; M. Boucadair; L. Munoz; A. Aguado
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 129
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent
February 2022
- RFC 9291A YANG Network Data Model for Layer 2 VPNsCurrent
September 2022
- RFC 9890An Update to YANG Module Names RegistrationCurrent
October 2025
- RFC 9907Guidelines for Authors and Reviewers of Documents Containing YANG Data ModelsCurrent
March 2026
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?