YANG Data Model for L3VPN Service Delivery
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 188
- Abstract
- 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. This document obsoletes RFC 8049; it replaces the unimplementable module in that RFC with a new module with the same name that is not backward compatible. The changes are a series of small fixes to the YANG module and some clarifications to the text.
- Publication Date
- 2018-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8299- Link
- https://doi.org/10.17487/RFC8299
- Author(s)
- Qin WuStephane LitkowskiLuis TomotakiKenichi Ogaki
Latest version of IETF RFC 8299
Document Versions — IETF RFC 8299
-
▶ IETF RFC 8299 (2018-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3022 [Active*]
- IETF RFC 3688 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4577 [Active*]
- IETF RFC 4862 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 6020 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6242 [Active*]
- IETF RFC 6513 [Active*]
- IETF RFC 6536 [Superseded*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 8040 [Active*]
- IETF RFC 8049 [Superseded*]
- IETF RFC 8174 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-netmod-acl-model-14 — ACL-YANG EXTERNAL
- IETF RFC 4026 [Active*]
- IETF RFC 4110 [Active*]
- IETF RFC 4760 [Active*]
- IETF RFC 8277 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8299.json
Supersedes:
IETF RFC 8049 [Superseded*]
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 8299, YANG Data Model for L3VPN Service Delivery. Available at https://doi.org/10.17487/RFC8299
Snippet:
IETF RFC 8299, YANG Data Model for L3VPN Service Delivery. Available at https://doi.org/10.17487/RFC8299
HTML (ISO 690 compliant)
Preview:
IETF RFC 8299, YANG Data Model for L3VPN Service Delivery. Available at https://doi.org/10.17487/RFC8299
Snippet:
<span class="citation"><cite>IETF RFC 8299</cite>, YANG Data Model for L3VPN Service Delivery. Available at <a href="https://doi.org/10.17487/RFC8299" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8299</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8299, YANG Data Model for L3VPN Service Delivery
doi: 10.17487/RFC8299
url: https://doi.org/10.17487/RFC8299
doi: 10.17487/RFC8299
url: https://doi.org/10.17487/RFC8299
Snippet:
<li> <cite id="bib-rfc8299">IETF RFC 8299</cite>, YANG Data Model for L3VPN Service Delivery <span class="doi">10.17487/RFC8299</span> </li>
Referenced By
- IETF RFC 8466 [Active*]
- IETF RFC 8969 [Active*]
- IETF RFC 9182 [Active*]
- IETF RFC 9315 [Active*]
- IETF RFC 9907 [Active*]