File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

M. Boucadair, Ed.
O. Gonzalez de Dios
S. Barguil
Q. Wu
V. Lopez

Stream:

IETF

Source:

opsawg (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9408

Discuss this RFC: Send questions or comments to the mailing list opsawg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9408

Abstract

This document defines a YANG data model for representing an abstract view of the provider network topology that contains the points from which its services can be attached (e.g., basic connectivity, VPN, network slices). Also, the model can be used to retrieve the points where the services are actually being delivered to customers (including peer networks).

This document augments the 'ietf-network' data model defined in RFC 8345 by adding the concept of Service Attachment Points (SAPs). The SAPs are the network reference points to which network services, such as Layer 3 Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network (L2VPN), can be attached. One or multiple services can be bound to the same SAP. Both User-to-Network Interface (UNI) and Network-to-Network Interface (NNI) are supported in the SAP data model.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.