rfc9408v2.txt		rfc9408.txt
	skipping to change at line 12 ¶		skipping to change at line 12 ¶
	Internet Engineering Task Force (IETF) M. Boucadair, Ed.		Internet Engineering Task Force (IETF) M. Boucadair, Ed.
	Request for Comments: 9408 Orange		Request for Comments: 9408 Orange
	Category: Standards Track O. Gonzalez de Dios		Category: Standards Track O. Gonzalez de Dios
	ISSN: 2070-1721 Telefonica		ISSN: 2070-1721 Telefonica
	S. Barguil		S. Barguil
	Nokia		Nokia
	Q. Wu		Q. Wu
	Huawei		Huawei
	V. Lopez		V. Lopez
	Nokia		Nokia
	May 2023		June 2023
	A YANG Network Data Model for Service Attachment Points (SAPs)		A YANG Network Data Model for Service Attachment Points (SAPs)
	Abstract		Abstract
	This document defines a YANG data model for representing an abstract		This document defines a YANG data model for representing an abstract
	view of the provider network topology that contains the points from		view of the provider network topology that contains the points from
	which its services can be attached (e.g., basic connectivity, VPN,		which its services can be attached (e.g., basic connectivity, VPN,
	network slices). Also, the model can be used to retrieve the points		network slices). Also, the model can be used to retrieve the points
	where the services are actually being delivered to customers		where the services are actually being delivered to customers
	skipping to change at line 690 ¶		skipping to change at line 690 ¶
	Relating to IETF Documents		Relating to IETF Documents
	(https://trustee.ietf.org/license-info).		(https://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC 9408; see the		This version of this YANG module is part of RFC 9408; see the
	RFC itself for full legal notices.";		RFC itself for full legal notices.";
	revision 2023-05-22 {		revision 2023-05-22 {
	description		description
	"Initial version.";		"Initial version.";
	reference		reference
	"RFC 9408: A YANG Network Model for Service Attachment		"RFC 9408: A YANG Network Data Model for Service Attachment
	Points (SAPs)";		Points (SAPs)";
	}		}
	identity virtual-network {		identity virtual-network {
	base vpn-common:service-type;		base vpn-common:service-type;
	description		description
	"Virtual network. Refers to a logical network instance		"Virtual network. Refers to a logical network instance
	that is built over a physical network.";		that is built over a physical network.";
	reference		reference
	"RFC 8453: Framework for Abstraction and Control of TE		"RFC 8453: Framework for Abstraction and Control of TE
	skipping to change at line 1922 ¶		skipping to change at line 1922 ¶
	An example of a SAP topology is presented in Figure 7. This example		An example of a SAP topology is presented in Figure 7. This example
	includes four PEs with their SAPs, as well as the customer		includes four PEs with their SAPs, as well as the customer
	information.		information.
	Let us assume that an operator wants to create an L3VPN service		Let us assume that an operator wants to create an L3VPN service
	between two PEs (PE3 and PE4) that are servicing two CEs (CE6 and		between two PEs (PE3 and PE4) that are servicing two CEs (CE6 and
	CE7). To that aim, the operator would query the SAP topology and		CE7). To that aim, the operator would query the SAP topology and
	would obtain a response similar to what is depicted in Figure 7.		would obtain a response similar to what is depicted in Figure 7.
	That response indicates that the SAPs having "sap#31" and "sap#43" as		That response indicates that the SAPs having "sap#31" and "sap#43" as
	attachment identifiers do not have any installed services. This is		attachment identifiers do not have any installed services. This is
	particularly inferred from (1) the administrative 'service-status',		particularly inferred from (1) the administrative 'service-status'
	which is set to 'ietf-vpn-common:admin-down' for all the services		that is set to 'ietf-vpn-common:admin-down' for all the services that
	that are supported by these two SAPs and (2) the absence of the		are supported by these two SAPs and (2) the absence of the anomalies
	anomalies discussed in Section 5. Note that none of the anomalies		discussed in Section 5. Note that none of the anomalies discussed in
	discussed in Section 5 are detected. Once the "free" SAPs are		Section 5 are detected. Once the "free" SAPs are identified, the
	identified, the 'interface-type' and 'encapsulation-type' are checked		'interface-type' and 'encapsulation-type' are checked to see if the
	to see if the requested L3VPN service is compatible with the SAP		requested L3VPN service is compatible with the SAP characteristics.
	characteristics. If they are compatible, the 'attachment-id' value		If they are compatible, the 'attachment-id' value can be used as the
	can be used as the VPN network access identifier in an L3NM "create"		VPN network access identifier in an L3NM "create" query.
	query.
	A similar process can be followed for creating the so-called "Inter-		A similar process can be followed for creating the so-called "Inter-
	AS VPN Option A" services. Unlike the previous example, let us		AS VPN Option A" services. Unlike the previous example, let us
	assume that an operator wants to create an L3VPN service between two		assume that an operator wants to create an L3VPN service between two
	PEs (PE3 and PE4) but these PEs are not in the same AS: PE3 belongs		PEs (PE3 and PE4) but these PEs are not in the same AS: PE3 belongs
	to AS A while PE4 belongs to AS B. The NNIs between these ASes are		to AS A while PE4 belongs to AS B. The NNIs between these ASes are
	represented in Figure 11. The operator of AS A would query, via the		represented in Figure 11. The operator of AS A would query, via the
	controller of its AS, the SAP topology and would obtain not only the		controller of its AS, the SAP topology and would obtain not only the
	information that is depicted in Figure 7 but also the information		information that is depicted in Figure 7 but also the information
	shown in Figure 12 representing the NNIs. The operator would create		shown in Figure 12 representing the NNIs. The operator would create
End of changes. 3 change blocks.
	12 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.48.