rfc9833v1.txt		rfc9833.txt
	skipping to change at line 156 ¶		skipping to change at line 156 ¶
	from service to network models as per [RFC8969]).		from service to network models as per [RFC8969]).
	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].
	2. Conventions and Definitions		2. Conventions and Definitions
	The meanings of the symbols in the YANG tree diagrams are defined in		The meanings of the symbols in the YANG tree diagrams are defined in
	[RFC8340].		[RFC8340].
	LxSM refers to both the Layer 2 Service Model (L2SM) [RFC8466] and		LxSM refers to both the L2VPN Service Model (L2SM) [RFC8466] and the
	the Layer 3 Service Model (L3SM) [RFC8299].		L3VPN Service Model (L3SM) [RFC8299].
	LxNM refers to both the Layer 2 Network Model (L2NM) [RFC9291] and		LxNM refers to both the L2VPN Network Model (L2NM) [RFC9291] and the
	the Layer 3 Network Model (L3NM) [RFC9182].		L3VPN Network Model (L3NM) [RFC9182].
	This document uses the following term:		This document uses the following term:
	Bearer: A physical or logical link that connects a CE (or site) to a		Bearer: A physical or logical link that connects a CE (or site) to a
	provider network.		provider network.
	A bearer can be a wireless or wired link. One or multiple		A bearer can be a wireless or wired link. One or multiple
	technologies can be used to build a bearer. The bearer type can		technologies can be used to build a bearer. The bearer type can
	be specified by a customer.		be specified by a customer.
	skipping to change at line 2438 ¶		skipping to change at line 2438 ¶
	uses bandwidth-parameters;		uses bandwidth-parameters;
	}		}
	}		}
	}		}
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	6. Security Considerations		6. Security Considerations
	This section is modeled after the template described in Section 3.7
	of [YANG-GUIDELINES].
	The "ietf-ac-common" YANG module defines a data model that is		The "ietf-ac-common" YANG module defines a data model that is
	designed to be accessed via YANG-based management protocols, such as		designed to be accessed via YANG-based management protocols, such as
	NETCONF [RFC6241] and RESTCONF [RFC8040]. These protocols have to		NETCONF [RFC6241] and RESTCONF [RFC8040]. These protocols have to
	use a secure transport layer (e.g., SSH [RFC4252], TLS [RFC8446], and		use a secure transport layer (e.g., SSH [RFC4252], TLS [RFC8446], and
	QUIC [RFC9000]) and have to use mutual authentication.		QUIC [RFC9000]) and have to use mutual authentication.
	The Network Configuration Access Control Model (NACM) [RFC8341]		The Network Configuration Access Control Model (NACM) [RFC8341]
	provides the means to restrict access for particular NETCONF or		provides the means to restrict access for particular NETCONF or
	RESTCONF users to a preconfigured subset of all available NETCONF or		RESTCONF users to a preconfigured subset of all available NETCONF or
	RESTCONF protocol operations and content.		RESTCONF protocol operations and content.
	skipping to change at line 2743 ¶		skipping to change at line 2740 ¶
	Giraldo, S., and B. Wu, "A Network YANG Data Model for		Giraldo, S., and B. Wu, "A Network YANG Data Model for
	Attachment Circuits", RFC 9835, August 2025,		Attachment Circuits", RFC 9835, August 2025,
	<https://www.rfc-editor.org/info/rfc9835>.		<https://www.rfc-editor.org/info/rfc9835>.
	[RFC9836] Boucadair, M., Ed., Roberts, R., Barguil Giraldo, S., and		[RFC9836] Boucadair, M., Ed., Roberts, R., Barguil Giraldo, S., and
	O. Gonzalez de Dios, "A YANG Data Model for Augmenting VPN		O. Gonzalez de Dios, "A YANG Data Model for Augmenting VPN
	Service and Network Models with Attachment Circuits",		Service and Network Models with Attachment Circuits",
	RFC 9836, August 2025,		RFC 9836, August 2025,
	<https://www.rfc-editor.org/info/rfc9836>.		<https://www.rfc-editor.org/info/rfc9836>.
	[YANG-GUIDELINES]
	Bierman, A., Boucadair, M., Ed., and Q. Wu, "Guidelines
	for Authors and Reviewers of Documents Containing YANG
	Data Models", Work in Progress, Internet-Draft, draft-
	ietf-netmod-rfc8407bis-22, 14 January 2025,
	<https://datatracker.ietf.org/doc/html/draft-ietf-netmod-
	rfc8407bis-22>.
	[YANG-NSS] Wu, B., Dhody, D., Rokui, R., Saad, T., and J. Mullooly,		[YANG-NSS] Wu, B., Dhody, D., Rokui, R., Saad, T., and J. Mullooly,
	"A YANG Data Model for the RFC 9543 Network Slice		"A YANG Data Model for the RFC 9543 Network Slice
	Service", Work in Progress, Internet-Draft, draft-ietf-		Service", Work in Progress, Internet-Draft, draft-ietf-
	teas-ietf-network-slice-nbi-yang-25, 9 May 2025,		teas-ietf-network-slice-nbi-yang-25, 9 May 2025,
	<https://datatracker.ietf.org/doc/html/draft-ietf-teas-		<https://datatracker.ietf.org/doc/html/draft-ietf-teas-
	ietf-network-slice-nbi-yang-25>.		ietf-network-slice-nbi-yang-25>.
	[YANG-SCHEDULE]		[YANG-SCHEDULE]
	Ma, Q., Ed., Wu, Q., Boucadair, M., Ed., and D. King, "A		Ma, Q., Ed., Wu, Q., Boucadair, M., Ed., and D. King, "A
	Common YANG Data Model for Scheduling", Work in Progress,		Common YANG Data Model for Scheduling", Work in Progress,
End of changes. 4 change blocks.
	15 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.