RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
In plain English — editorial summary, not part of the RFC
Delivery of network services assumes that appropriate setup is provisioned over the links that connect customer termination points and a provider network. The required setup to allow successful data exchange over these links is referred to as an attachment circuit (AC), while the underlying link is referred to as a "bearer". This document specifies a YANG service data model for ACs. This model can be used for the provisioning of ACs before or during service provisioning (e.g., RFC 9543 Network Slice Service). The document also specifies a YANG service data model for managing bearers over which ACs are established.
Document record
- Document ID
- RFC9834
- Published
- September 2025
- Authors
- M. Boucadair; R. Roberts; O. Gonzalez de Dios; S. Barguil; B. Wu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 150
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9835A Network YANG Data Model for Attachment CircuitsCurrent
September 2025
- RFC 9833A Common 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 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 9291A YANG Network Data Model for Layer 2 VPNsCurrent
September 2022
- RFC 9889A Realization of Network Slices for 5G Networks Using Current IP/MPLS TechnologiesCurrent
November 2025
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
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?