A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 158
- Abstract
- This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is done is out of scope for this document. The YANG data model defined in this document includes support for point-to-point Virtual Private Wire Services (VPWSs) and multipoint Virtual Private LAN Services (VPLSs) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFCs 4761 and 6624. The YANG data model defined in this document conforms to the Network Management Datastore Architecture defined in RFC 8342.
- Publication Date
- 2018-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8466- Link
- https://doi.org/10.17487/RFC8466
- Author(s)
- Bin WenGiuseppe FioccolaChongfeng XieLuay Jalil
- Keyword(s)
- L2SM
Latest version of IETF RFC 8466
Document Versions — IETF RFC 8466
-
▶ IETF RFC 8466 (2018-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3688 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4761 [Active*]
- IETF RFC 6020 [Active*]
- IETF RFC 6073 [Active*]
- IETF RFC 6074 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 7432 [Active*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 8040 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8214 [Active*]
- IETF RFC 8341 [Active*]
- IETF RFC 8342 [Active*]
- IETF RFC 8446 [Superseded*]
- W3C XML 1 [Active]
Bibliographic Reference(s)
- 10.1109-IEEESTD.2004.94569 — IEEE8021D-2004 EXTERNAL
- 10.1109-IEEESTD.2004.94617 — IEEE-802-3ah EXTERNAL
- 10.1109-IEEESTD.2007.4431836 — IEEE802.1ag EXTERNAL
- 10.1109-IEEESTD.2014.6991462 — 802.1Q-2014 EXTERNAL
- IETF.draft-ietf-bess-evpn-yang-05 — EVPN-YANG EXTERNAL
- IETF.draft-ietf-bess-l2vpn-yang-08 — I-D.ietf-bess-l2vpn-yang EXTERNAL
- Metro Ethernet Forum, "Ethernet Services Definitions - Phase 2", April 2008, < https://mef.net/PDF_Documents/ technical-specifications/MEF6-1.pdf >. EXTERNAL
- IETF RFC 4119 [Active*]
- IETF RFC 6624 [Active*]
- IETF RFC 7130 [Active*]
- IETF RFC 7209 [Active*]
- IETF RFC 7348 [Active*]
- IETF RFC 7436 [Active*]
- IETF RFC 8199 [Active*]
- IETF RFC 8299 [Active*]
- IETF RFC 8309 [Active*]
- IETF RFC 8340 [Active*]
- T-REC-Y.1731.2015 — ITU-T-Y-1731 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8466.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 8466, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery. Available at https://doi.org/10.17487/RFC8466
Snippet:
IETF RFC 8466, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery. Available at https://doi.org/10.17487/RFC8466
HTML (ISO 690 compliant)
Preview:
IETF RFC 8466, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery. Available at https://doi.org/10.17487/RFC8466
Snippet:
<span class="citation"><cite>IETF RFC 8466</cite>, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery. Available at <a href="https://doi.org/10.17487/RFC8466" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8466</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8466, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
doi: 10.17487/RFC8466
url: https://doi.org/10.17487/RFC8466
doi: 10.17487/RFC8466
url: https://doi.org/10.17487/RFC8466
Snippet:
<li> <cite id="bib-rfc8466">IETF RFC 8466</cite>, A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery <span class="doi">10.17487/RFC8466</span> </li>
Referenced By
- IETF RFC 8969 [Active*]
- IETF RFC 9182 [Active*]
- IETF RFC 9291 [Active*]
- IETF RFC 9907 [Active*]