Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8299
Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8299
This document defines a YANG data model that can be used forcommunication between customers and network operators and to delivera Layer 3 provider-provisioned VPN service. This document is limitedto BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. Thismodel is intended to be instantiated at the management system todeliver the overall service. It is not a configuration model to beused directly on network elements. This model provides an abstractedview of the Layer 3 IP VPN service configuration components. It willbe up to the management system to take this model as input and usespecific configuration models to configure the different networkelements to deliver the service. How the configuration of networkelements is done is out of scope for this document.
This document obsoletes RFC 8049; it replaces the unimplementablemodule in that RFC with a new module with the same name that is notbackward compatible. The changes are a series of small fixes to theYANG module and some clarifications to the text.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.