A YANG Network Data Model for Layer 2 VPNs
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 139
- Abstract
- 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.
- Publication Date
- 2022-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9291- Link
- https://doi.org/10.17487/RFC9291
- Author(s)
- Mohamed BoucadairOscar Gonzalez de DiosSamier BarguilLuis Angel Munoz
- Keyword(s)
- Automation, Service Provider, Network Automation, Service Delivery
Latest version of IETF RFC 9291
Document Versions — IETF RFC 9291
-
▶ IETF RFC 9291 (2022-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- 10.1109-IEEESTD.2007.4431836 — IEEE802.1ag EXTERNAL
- 10.1109-IEEESTD.2018.8467507 — IEEE802.1Qcp EXTERNAL
- IANA, "MPLS Pseudowire Types Registry", <http://www.iana.org/assignments/pwe3-parameters/>. EXTERNAL
- IANA, "BGP Layer 2 Encapsulation Types", <https://www.iana.org/assignments/bgp-parameters>. EXTERNAL
- IETF RFC 3688 [Active*]
- IETF RFC 4026 [Active*]
- IETF RFC 4446 [Active*]
- IETF RFC 4667 [Active*]
- IETF RFC 4761 [Active*]
- IETF RFC 4762 [Active*]
- IETF RFC 6020 [Active*]
- IETF RFC 6074 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 6624 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 7432 [Active*]
- RFC7623 — RFC7623 EXTERNAL
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 8040 [Active*]
- IETF RFC 8077 [Active*]
- IETF RFC 8214 [Active*]
- IETF RFC 8294 [Active*]
- IETF RFC 8341 [Active*]
- IETF RFC 8342 [Active*]
- IETF RFC 8365 [Active*]
- IETF RFC 8446 [Superseded*]
- IETF RFC 8466 [Active*]
- IETF RFC 8584 [Active*]
- RFC9181 — RFC9181 EXTERNAL
- T-REC-G.8013.2015 — y1731 EXTERNAL
Bibliographic Reference(s)
- 10.1109-IEEESTD.2004.94617 — IEEE-802-3ah EXTERNAL
- 10.1109-IEEESTD.2018.8403927 — SPB EXTERNAL
- 10.1109-IEEESTD.2020.9105034 — IEEE802.1AX EXTERNAL
- GITHUB.mbj4668.pyang.201802 — Pyang EXTERNAL
- IEEE.STD801.3AH.2008 — IEEE-802-1ah EXTERNAL
- IETF.draft-ietf-bess-evpn-pref-df-10 — I-D.ietf-bess-evpn-pref-df EXTERNAL
- IETF.draft-ietf-bess-evpn-yang-07 — I-D.ietf-bess-evpn-yang EXTERNAL
- IETF.draft-ietf-idr-bgp-model-14 — I-D.ietf-idr-bgp-model EXTERNAL
- IETF.draft-ietf-opsawg-sap-09 — I-D.ietf-opsawg-sap EXTERNAL
- IETF.draft-ietf-teas-enhanced-vpn-11 — I-D.ietf-teas-enhanced-vpn EXTERNAL
- IETF.draft-ietf-teas-ietf-network-slices-14 — I-D.ietf-teas-ietf-network-slices EXTERNAL
- IETF.draft-ietf-teas-te-service-mapping-yang-11 — I-D.ietf-teas-te-service-mapping-yang EXTERNAL
- MFA Forum Technical Committee, "The Use of Virtual Trunks for ATM/MPLS Control Plane Interworking Specification", MFA Forum 9.0.0, February 2006. EXTERNAL
- IETF RFC 2507 [Active*]
- IETF RFC 2508 [Active*]
- IETF RFC 3032 [Active*]
- IETF RFC 3545 [Active*]
- IETF RFC 3644 [Active*]
- IETF RFC 4448 [Active*]
- IETF RFC 4553 [Active*]
- IETF RFC 4618 [Active*]
- IETF RFC 4619 [Active*]
- IETF RFC 4664 [Active*]
- IETF RFC 4717 [Active*]
- IETF RFC 4816 [Active*]
- IETF RFC 4842 [Active*]
- IETF RFC 4863 [Active*]
- RFC4901 — RFC4901 EXTERNAL
- IETF RFC 5086 [Active*]
- IETF RFC 5087 [Active*]
- IETF RFC 5143 [Superseded*]
- IETF RFC 5795 [Active*]
- IETF RFC 5880 [Active*]
- IETF RFC 6307 [Active*]
- IETF RFC 7209 [Active*]
- IETF RFC 7267 [Active*]
- IETF RFC 7297 [Active*]
- IETF RFC 7951 [Active*]
- IETF RFC 8309 [Active*]
- IETF RFC 8340 [Active*]
- IETF RFC 8343 [Active*]
- IETF RFC 8345 [Active*]
- IETF RFC 8453 [Active*]
- IETF RFC 8519 [Active*]
- IETF RFC 8792 [Active*]
- RFC8960 — RFC8960 EXTERNAL
- IETF RFC 8969 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9291.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9291, A YANG Network Data Model for Layer 2 VPNs. Available at https://doi.org/10.17487/RFC9291
Snippet:
IETF RFC 9291, A YANG Network Data Model for Layer 2 VPNs. Available at https://doi.org/10.17487/RFC9291
HTML (ISO 690 compliant)
Preview:
IETF RFC 9291, A YANG Network Data Model for Layer 2 VPNs. Available at https://doi.org/10.17487/RFC9291
Snippet:
<span class="citation"><cite>IETF RFC 9291</cite>, A YANG Network Data Model for Layer 2 VPNs. Available at <a href="https://doi.org/10.17487/RFC9291" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9291</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9291, A YANG Network Data Model for Layer 2 VPNs
doi: 10.17487/RFC9291
url: https://doi.org/10.17487/RFC9291
doi: 10.17487/RFC9291
url: https://doi.org/10.17487/RFC9291
Snippet:
<li> <cite id="bib-rfc9291">IETF RFC 9291</cite>, A YANG Network Data Model for Layer 2 VPNs <span class="doi">10.17487/RFC9291</span> </li>
Referenced By
- IETF RFC 9907 [Active*]