RFC 9408: A YANG Network Data Model for Service Attachment Points (SAPs)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9408
- Published
- June 2023
- Authors
- M. Boucadair; O. Gonzalez de Dios; S. Barguil; Q. Wu; V. Lopez
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9291A YANG Network Data Model for Layer 2 VPNsCurrent
September 2022
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
- RFC 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent
February 2022
- RFC 9833A Common YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9834YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)Current
September 2025
- RFC 9835A Network YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9836A YANG Data Model for Augmenting VPN Service and Network Models with Attachment CircuitsCurrent
September 2025
- RFC 8969A Framework for Automating Service and Network Management with YANGCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?