RFC 9836: A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
In plain English — editorial summary, not part of the RFC
This document defines a YANG data model, referred to as the "AC Glue" model, to augment the LxVPN Service Model (LxSM) and LxVPN Network Model (LxNM) with references to attachment circuits (ACs). The AC Glue model enables a provider to associate Layer 2/3 VPN (LxVPN) services with the underlying AC infrastructure, thereby facilitating consistent provisioning and management of new or existing ACs in conjunction with LxVPN services. Specifically, by introducing an integrated approach to AC and LxVPN management, this model supports Attachment Circuit as a Service (ACaaS) and provides a standardized mechanism for aligning AC/VPN requests with the network configurations required to deliver them.
Document record
- Document ID
- RFC9836
- Published
- September 2025
- Authors
- M. Boucadair; R. Roberts; S. Barguil; O. Gonzalez de Dios
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 30
- 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 9834YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)Current
September 2025
- RFC 9833A Common YANG Data Model for 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?