A YANG Network Data Model for Layer 3 VPNs
RFC 9182
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['l3vpn', 'Automation', 'Service Provisioning', 'Network Automation', 'Service Orchestration', 'Service Delivery', 'NETCONF', 'RESTCONF', 'Slices', 'network slicing']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "A. Aguado": changed name from "Alejandro Aguado" to "A. Aguado", cleared country (was "Spain") |
|
2026-05-20
|
(System) | Changed author "L. Munoz": changed name from "Luis Munoz" to "L. Munoz", cleared country (was "Spain") |
|
2026-05-20
|
(System) | Changed author "M. Boucadair": changed name from "Mohamed Boucadair" to "M. Boucadair", changed is_editor from "False" to "True", cleared country (was "France") |
|
2026-05-20
|
(System) | Changed author "O. Gonzalez de Dios": changed name from "Oscar de Dios" to "O. Gonzalez de Dios", changed is_editor from "False" to "True", cleared country … Changed author "O. Gonzalez de Dios": changed name from "Oscar de Dios" to "O. Gonzalez de Dios", changed is_editor from "False" to "True", cleared country (was "Spain") |
|
2026-05-20
|
(System) | Changed author "S. Barguil": changed name from "Samir Barguil" to "S. Barguil", cleared country (was "Spain") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2022-02-15
|
(System) | Received changes through RFC Editor sync (created alias RFC 9182, changed title to 'A YANG Network Data Model for Layer 3 VPNs', changed abstract … Received changes through RFC Editor sync (created alias RFC 9182, changed title to 'A YANG Network Data Model for Layer 3 VPNs', changed abstract to '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.', changed pages to 129, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2022-02-15, changed IESG state to RFC Published) |
|
2022-02-15
|
(System) | RFC published |