RFC 8049: YANG Data Model for L3VPN Service Delivery
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8299.
Current version: RFC 8299 — YANG Data Model for L3VPN Service Delivery
In plain English — editorial summary, not part of the RFC
This document defines a YANG data model that can be used for communication between customers and network operators and to deliver a Layer 3 provider-provisioned VPN service. This document is limited to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. This model is intended to be instantiated at the management system to deliver the overall service. It is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IP VPN service configuration components. It will be up to the management system to take this model as input and use specific configuration models to configure the different network elements to deliver the service. How the configuration of network elements is done is out of scope for this document.
Document record
- Document ID
- RFC8049
- Published
- February 2017
- Authors
- S. Litkowski; L. Tomotaki; K. Ogaki
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 157
- Also known as
- —
- Obsoleted by:
- RFC 8299
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8040RESTCONF ProtocolUpdated
January 2017
- RFC 8194A YANG Data Model for LMAP Measurement AgentsCurrent
August 2017
- RFC 8309Service Models ExplainedCurrent
January 2018
- RFC 8341Network Configuration Access Control ModelCurrent
March 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 8466A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service DeliveryCurrent
October 2018
- RFC 8819YANG Module TagsCurrent
January 2021
- RFC 7224IANA Interface Type YANG ModuleCurrent
May 2014
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?