rfc9836v1.txt		rfc9836.txt
	Internet Engineering Task Force (IETF) M. Boucadair, Ed.		Internet Engineering Task Force (IETF) M. Boucadair, Ed.
	Request for Comments: 9836 Orange		Request for Comments: 9836 Orange
	Category: Standards Track R. Roberts		Category: Standards Track R. Roberts
	ISSN: 2070-1721 Juniper		ISSN: 2070-1721 Juniper
	S. Barguil Giraldo		S. Barguil
	Nokia		Nokia
	O. Gonzalez de Dios		O. Gonzalez de Dios
	Telefonica		Telefonica
	August 2025		August 2025
	A YANG Data Model for Augmenting VPN Service and Network Models with		A YANG Data Model for Augmenting VPN Service and Network Models with
	Attachment Circuits		Attachment Circuits
	Abstract		Abstract
	This document defines a YANG data model, referred to as the "AC Glue"		This document defines a YANG data model, referred to as the "AC Glue"
	model, to augment the Layer 2/3 Service Model (LxSM) and Layer 2/3		model, to augment the LxVPN Service Model (LxSM) and LxVPN Network
	Network Model (LxNM) with references to attachment circuits (ACs).		Model (LxNM) with references to attachment circuits (ACs). The AC
	The AC Glue model enables a provider to associate Layer 2/3 VPN		Glue model enables a provider to associate Layer 2/3 VPN (LxVPN)
	(LxVPN) services with the underlying AC infrastructure, thereby		services with the underlying AC infrastructure, thereby facilitating
	facilitating consistent provisioning and management of new or		consistent provisioning and management of new or existing ACs in
	existing ACs in conjunction with LxVPN services. Specifically, by		conjunction with LxVPN services. Specifically, by introducing an
	introducing an integrated approach to AC and LxVPN management, this		integrated approach to AC and LxVPN management, this model supports
	model supports Attachment Circuit-as-a-Service (ACaaS) and provides a		Attachment Circuit-as-a-Service (ACaaS) and provides a standardized
	standardized mechanism for aligning AC/VPN requests with the network		mechanism for aligning AC/VPN requests with the network
	configurations required to deliver them.		configurations required to deliver them.
	Status of This Memo		Status of This Memo
	This is an Internet Standards Track document.		This is an Internet Standards Track document.
	This document is a product of the Internet Engineering Task Force		This document is a product of the Internet Engineering Task Force
	(IETF). It represents the consensus of the IETF community. It has		(IETF). It represents the consensus of the IETF community. It has
	received public review and has been approved for publication by the		received public review and has been approved for publication by the
	Internet Engineering Steering Group (IESG). Further information on		Internet Engineering Steering Group (IESG). Further information on
	skipping to change at line 96 ¶		skipping to change at line 96 ¶
	over these links. The required setup is referred to in this document		over these links. The required setup is referred to in this document
	as an attachment circuit (AC), while the underlying link is referred		as an attachment circuit (AC), while the underlying link is referred
	to as "bearer".		to as "bearer".
	The document specifies a YANG module ("ietf-ac-glue", Section 6) that		The document specifies a YANG module ("ietf-ac-glue", Section 6) that
	updates existing service and network Virtual Private Network (VPN)		updates existing service and network Virtual Private Network (VPN)
	modules with the required information to bind specific services to		modules with the required information to bind specific services to
	ACs that are created using the AC service model [RFC9834].		ACs that are created using the AC service model [RFC9834].
	Specifically, the following modules are augmented:		Specifically, the following modules are augmented:
	* The Layer 2 Service Model (L2SM) [RFC8466]		* The L2VPN Service Model (L2SM) [RFC8466]
	* The Layer 3 Service Model (L3SM) [RFC8299]		* The L3VPN Service Model (L3SM) [RFC8299]
	* The Layer 2 Network Model (L2NM) [RFC9291]		* The L2VPN Network Model (L2NM) [RFC9291]
	* The Layer 3 Network Model (L3NM) [RFC9182]		* The L3VPN Network Model (L3NM) [RFC9182]
	Likewise, the document augments the L2NM and L3NM with references to		Likewise, the document augments the L2NM and L3NM with references to
	the ACs that are managed using the AC network model [RFC9835].		the ACs that are managed using the AC network model [RFC9835].
	This approach allows operators to separate AC provisioning from		This approach allows operators to separate AC provisioning from
	actual VPN service provisioning. Refer to Section 4.2 for more		actual VPN service provisioning. Refer to Section 4.2 for more
	discussion.		discussion.
	The YANG data model in this document conforms to the Network		The YANG data model in this document conforms to the Network
	Management Datastore Architecture (NMDA) defined in [RFC8342].		Management Datastore Architecture (NMDA) defined in [RFC8342].
	skipping to change at line 1443 ¶		skipping to change at line 1443 ¶
	Authors' Addresses		Authors' Addresses
	Mohamed Boucadair (editor)		Mohamed Boucadair (editor)
	Orange		Orange
	Email: mohamed.boucadair@orange.com		Email: mohamed.boucadair@orange.com
	Richard Roberts		Richard Roberts
	Juniper		Juniper
	Email: rroberts@juniper.net		Email: rroberts@juniper.net
	Samier Barguil Giraldo		Samier Barguil
	Nokia		Nokia
	Email: samier.barguil_giraldo@nokia.com		Email: samier.barguil_giraldo@nokia.com
	Oscar Gonzalez de Dios		Oscar Gonzalez de Dios
	Telefonica		Telefonica
	Email: oscar.gonzalezdedios@telefonica.com		Email: oscar.gonzalezdedios@telefonica.com
End of changes. 7 change blocks.
	15 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.48.