Skip to main content

Layer 3 VPN Network Model

Document Type Replaced Internet-Draft (candidate for opsawg WG)
Expired & archived
Authors Alejandro Aguado , Oscar Gonzalez de Dios , Victor Lopez , Daniel Voyer , Luis Angel Munoz
Last updated 2019-09-29 (Latest revision 2019-09-24)
Replaced by RFC 9182
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Yang Validation 0 errors, 0 warnings
Additional resources Yang catalog entry for ietf-l3vpn-ntw@2019-09-24.yang
Yang impact analysis for draft-aguado-opsawg-l3sm-l3nm
Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-opsawg-l3sm-l3nm
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be used for communication between customers and network operators. Such model is adequate for the customer to network operator conversation and plays the role of a Customer Service Model, according to the terminology defined in RFC8309. There is a need for a YANG model to be used in the communication between the entity that interacts directly with the customer, the service orchestrator, (either fully automated or a human operator) and the entity in charge of network orchestration and control (aka network controller / orchestrator). This document proposes a L3VPN Network Yang Model (L3NM) to facilitate communication between a service orchestrator and a network controller / orchestrator. The resulting model is called the L3VPN Network Model (L3NM) and provides a network-centric view of the L3VPN services.


Alejandro Aguado
Oscar Gonzalez de Dios
Victor Lopez
Daniel Voyer
Luis Angel Munoz

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)