rfc9182v5.txt		rfc9182.txt
	Internet Engineering Task Force (IETF) S. Barguil		Internet Engineering Task Force (IETF) S. Barguil
	Request for Comments: 9182 O. Gonzalez de Dios, Ed.		Request for Comments: 9182 O. Gonzalez de Dios, Ed.
	Category: Standards Track Telefonica		Category: Standards Track Telefonica
	ISSN: 2070-1721 M. Boucadair, Ed.		ISSN: 2070-1721 M. Boucadair, Ed.
	Orange		Orange
	L. Munoz		L. Munoz
	Vodafone		Vodafone
	A. Aguado		A. Aguado
	Nokia		Nokia
	January 2022		February 2022
	A YANG Network Data Model for Layer 3 VPNs		A YANG Network Data Model for Layer 3 VPNs
	Abstract		Abstract
	As a complement to the Layer 3 Virtual Private Network Service Model		As a complement to the Layer 3 Virtual Private Network Service Model
	(L3SM), which is used for communication between customers and service		(L3SM), which is used for communication between customers and service
	providers, this document defines an L3VPN Network Model (L3NM) that		providers, this document defines an L3VPN Network Model (L3NM) that
	can be used for the provisioning of Layer 3 Virtual Private Network		can be used for the provisioning of Layer 3 Virtual Private Network
	(L3VPN) services within a service provider network. The model		(L3VPN) services within a service provider network. The model
	skipping to change at line 470 ¶		skipping to change at line 470 ¶
	actual activation and provisioning of the VPN service will involve		actual activation and provisioning of the VPN service will involve
	a variety of device modules to tweak the required functions for		a variety of device modules to tweak the required functions for
	the delivery of the service. These functions are supported by the		the delivery of the service. These functions are supported by the
	VPN nodes and can be managed using device YANG modules. A non-		VPN nodes and can be managed using device YANG modules. A non-
	comprehensive list of such device YANG modules is provided below:		comprehensive list of such device YANG modules is provided below:
	* Routing management [RFC8349].		* Routing management [RFC8349].
	* BGP [BGP-YANG].		* BGP [BGP-YANG].
	* PIM [RFC9128].		* PIM [PIM-YANG].
	* NAT management [RFC8512].		* NAT management [RFC8512].
	* QoS management [QoS-YANG].		* QoS management [QoS-YANG].
	* ACLs [RFC8519].		* ACLs [RFC8519].
	How the L3NM is used to derive device-specific actions is		How the L3NM is used to derive device-specific actions is
	implementation specific.		implementation specific.
	skipping to change at line 675 ¶		skipping to change at line 675 ¶
	+--rw vpn-name? string		+--rw vpn-name? string
	+--rw vpn-description? string		+--rw vpn-description? string
	+--rw customer-name? string		+--rw customer-name? string
	+--rw parent-service-id? vpn-common:vpn-id		+--rw parent-service-id? vpn-common:vpn-id
	+--rw vpn-type? identityref		+--rw vpn-type? identityref
	+--rw vpn-service-topology? identityref		+--rw vpn-service-topology? identityref
	+--rw status		+--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw vpn-instance-profiles		+--rw vpn-instance-profiles
	| ...		| ...
	+--rw underlay-transport		+--rw underlay-transport
	| +-- (type)?		| +-- (type)?
	| +--:(abstract)		| +--:(abstract)
	| | +--rw transport-instance-id? string		| | +--rw transport-instance-id? string
	| | +--rw instance-type? identityref		| | +--rw instance-type? identityref
	| +--:(protocol)		| +--:(protocol)
	skipping to change at line 971 ¶		skipping to change at line 971 ¶
	| | ...		| | ...
	| +--rw multicast {vpn-common:multicast}?		| +--rw multicast {vpn-common:multicast}?
	| ...		| ...
	+--rw msdp {msdp}?		+--rw msdp {msdp}?
	| +--rw peer? inet:ipv4-address		| +--rw peer? inet:ipv4-address
	| +--rw local-address? inet:ipv4-address		| +--rw local-address? inet:ipv4-address
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw groups		+--rw groups
	| +--rw group* [group-id]		| +--rw group* [group-id]
	| +--rw group-id string		| +--rw group-id string
	+--rw status		+--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw vpn-network-accesses		+--rw vpn-network-accesses
	...		...
	Figure 7: VPN Node Subtree Structure		Figure 7: VPN Node Subtree Structure
	The descriptions of the 'vpn-node' data nodes (Figure 7) are as		The descriptions of the 'vpn-node' data nodes (Figure 7) are as
	follows:		follows:
	skipping to change at line 1076 ¶		skipping to change at line 1076 ¶
	+--rw vpn-network-access* [id]		+--rw vpn-network-access* [id]
	+--rw id vpn-common:vpn-id		+--rw id vpn-common:vpn-id
	+--rw interface-id? string		+--rw interface-id? string
	+--rw description? string		+--rw description? string
	+--rw vpn-network-access-type? identityref		+--rw vpn-network-access-type? identityref
	+--rw vpn-instance-profile? leafref		+--rw vpn-instance-profile? leafref
	+--rw status		+--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw connection		+--rw connection
	| ...		| ...
	+--rw ip-connection		+--rw ip-connection
	| ...		| ...
	+--rw routing-protocols		+--rw routing-protocols
	| ...		| ...
	+--rw oam		+--rw oam
	| ...		| ...
	skipping to change at line 1515 ¶		skipping to change at line 1515 ¶
	| | | +--rw lan inet:ipv4-prefix		| | | +--rw lan inet:ipv4-prefix
	| | | +--rw lan-tag? string		| | | +--rw lan-tag? string
	| | | +--rw next-hop union		| | | +--rw next-hop union
	| | | +--rw bfd-enable? boolean		| | | +--rw bfd-enable? boolean
	| | | +--rw metric? uint32		| | | +--rw metric? uint32
	| | | +--rw preference? uint32		| | | +--rw preference? uint32
	| | | +--rw status		| | | +--rw status
	| | | +--rw admin-status		| | | +--rw admin-status
	| | | | +--rw status? identityref		| | | | +--rw status? identityref
	| | | | +--rw last-change? yang:date-and-time		| | | | +--rw last-change? yang:date-and-time
	| | | +--rw oper-status		| | | +--ro oper-status
	| | | +--ro status? identityref		| | | +--ro status? identityref
	| | | +--ro last-change? yang:date-and-time		| | | +--ro last-change? yang:date-and-time
	| | +--rw ipv6-lan-prefixes*		| | +--rw ipv6-lan-prefixes*
	| | [lan next-hop]		| | [lan next-hop]
	| | {vpn-common:ipv6}?		| | {vpn-common:ipv6}?
	| | +--rw lan inet:ipv6-prefix		| | +--rw lan inet:ipv6-prefix
	| | +--rw lan-tag? string		| | +--rw lan-tag? string
	| | +--rw next-hop union		| | +--rw next-hop union
	| | +--rw bfd-enable? boolean		| | +--rw bfd-enable? boolean
	| | +--rw metric? uint32		| | +--rw metric? uint32
	| | +--rw preference? uint32		| | +--rw preference? uint32
	| | +--rw status		| | +--rw status
	| | +--rw admin-status		| | +--rw admin-status
	| | | +--rw status? identityref		| | | +--rw status? identityref
	| | | +--rw last-change? yang:date-and-time		| | | +--rw last-change? yang:date-and-time
	| | +--rw oper-status		| | +--ro oper-status
	| | +--ro status? identityref		| | +--ro status? identityref
	| | +--ro last-change? yang:date-and-time		| | +--ro last-change? yang:date-and-time
	...		...
	Figure 15: Static Routing Subtree Structure		Figure 15: Static Routing Subtree Structure
	As depicted in Figure 15, the following data nodes can be defined for		As depicted in Figure 15, the following data nodes can be defined for
	a given IP prefix:		a given IP prefix:
	'lan-tag': Indicates a local tag (e.g., "myfavorite-lan") that is		'lan-tag': Indicates a local tag (e.g., "myfavorite-lan") that is
	skipping to change at line 1621 ¶		skipping to change at line 1621 ¶
	| | | +--:(explicit)		| | | +--:(explicit)
	| | | | +--rw key-id? uint32		| | | | +--rw key-id? uint32
	| | | | +--rw key? string		| | | | +--rw key? string
	| | | | +--rw crypto-algorithm? identityref		| | | | +--rw crypto-algorithm? identityref
	| | | +--:(ipsec)		| | | +--:(ipsec)
	| | | +--rw sa? string		| | | +--rw sa? string
	| | +--rw status		| | +--rw status
	| | +--rw admin-status		| | +--rw admin-status
	| | | +--rw status? identityref		| | | +--rw status? identityref
	| | | +--rw last-change? yang:date-and-time		| | | +--rw last-change? yang:date-and-time
	| | +--rw oper-status		| | +--ro oper-status
	| | +--ro status? identityref		| | +--ro status? identityref
	| | +--ro last-change? yang:date-and-time		| | +--ro last-change? yang:date-and-time
	...		...
	Figure 16: BGP Routing Subtree Structure		Figure 16: BGP Routing Subtree Structure
	The following data nodes are captured in Figure 16. It is up to the		The following data nodes are captured in Figure 16. It is up to the
	implementation (e.g., network orchestrator) to derive the		implementation (e.g., network orchestrator) to derive the
	corresponding BGP device configuration:		corresponding BGP device configuration:
	skipping to change at line 1769 ¶		skipping to change at line 1769 ¶
	| | | | +--rw key-id? uint32		| | | | +--rw key-id? uint32
	| | | | +--rw key? string		| | | | +--rw key? string
	| | | | +--rw crypto-algorithm?		| | | | +--rw crypto-algorithm?
	| | | | identityref		| | | | identityref
	| | | +--:(ipsec)		| | | +--:(ipsec)
	| | | +--rw sa? string		| | | +--rw sa? string
	| | +--rw status		| | +--rw status
	| | +--rw admin-status		| | +--rw admin-status
	| | | +--rw status? identityref		| | | +--rw status? identityref
	| | | +--rw last-change? yang:date-and-time		| | | +--rw last-change? yang:date-and-time
	| | +--rw oper-status		| | +--ro oper-status
	| | +--ro status? identityref		| | +--ro status? identityref
	| | +--ro last-change? yang:date-and-time		| | +--ro last-change? yang:date-and-time
	...		...
	Figure 17: OSPF Routing Subtree Structure		Figure 17: OSPF Routing Subtree Structure
	The following data nodes are captured in Figure 17:		The following data nodes are captured in Figure 17:
	'address-family': Indicates whether IPv4, IPv6, or both address		'address-family': Indicates whether IPv4, IPv6, or both address
	families are to be activated.		families are to be activated.
	skipping to change at line 1836 ¶		skipping to change at line 1836 ¶
	| | | | +--rw key-chain?		| | | | +--rw key-chain?
	| | | | key-chain:key-chain-ref		| | | | key-chain:key-chain-ref
	| | | +--:(auth-key-explicit)		| | | +--:(auth-key-explicit)
	| | | +--rw key-id? uint32		| | | +--rw key-id? uint32
	| | | +--rw key? string		| | | +--rw key? string
	| | | +--rw crypto-algorithm? identityref		| | | +--rw crypto-algorithm? identityref
	| | +--rw status		| | +--rw status
	| | +--rw admin-status		| | +--rw admin-status
	| | | +--rw status? identityref		| | | +--rw status? identityref
	| | | +--rw last-change? yang:date-and-time		| | | +--rw last-change? yang:date-and-time
	| | +--rw oper-status		| | +--ro oper-status
	| | +--ro status? identityref		| | +--ro status? identityref
	| | +--ro last-change? yang:date-and-time		| | +--ro last-change? yang:date-and-time
	...		...
	Figure 18: IS-IS Routing Subtree Structure		Figure 18: IS-IS Routing Subtree Structure
	The following IS-IS data nodes are supported:		The following IS-IS data nodes are supported:
	'address-family': Indicates whether IPv4, IPv6, or both address		'address-family': Indicates whether IPv4, IPv6, or both address
	families are to be activated.		families are to be activated.
	skipping to change at line 1897 ¶		skipping to change at line 1897 ¶
	| | | +--:(auth-key-chain)		| | | +--:(auth-key-chain)
	| | | | +--rw key-chain?		| | | | +--rw key-chain?
	| | | | key-chain:key-chain-ref		| | | | key-chain:key-chain-ref
	| | | +--:(auth-key-explicit)		| | | +--:(auth-key-explicit)
	| | | +--rw key? string		| | | +--rw key? string
	| | | +--rw crypto-algorithm? identityref		| | | +--rw crypto-algorithm? identityref
	| | +--rw status		| | +--rw status
	| | +--rw admin-status		| | +--rw admin-status
	| | | +--rw status? identityref		| | | +--rw status? identityref
	| | | +--rw last-change? yang:date-and-time		| | | +--rw last-change? yang:date-and-time
	| | +--rw oper-status		| | +--ro oper-status
	| | +--ro status? identityref		| | +--ro status? identityref
	| | +--ro last-change? yang:date-and-time		| | +--ro last-change? yang:date-and-time
	...		...
	Figure 19: RIP Subtree Structure		Figure 19: RIP Subtree Structure
	As shown in Figure 19, the following RIP data nodes are supported:		As shown in Figure 19, the following RIP data nodes are supported:
	'address-family': Indicates whether IPv4, IPv6, or both address		'address-family': Indicates whether IPv4, IPv6, or both address
	families are to be activated. This parameter is used to determine		families are to be activated. This parameter is used to determine
	skipping to change at line 1953 ¶		skipping to change at line 1953 ¶
	| +--rw address-family* identityref		| +--rw address-family* identityref
	| +--rw vrrp-group? uint8		| +--rw vrrp-group? uint8
	| +--rw backup-peer? inet:ip-address		| +--rw backup-peer? inet:ip-address
	| +--rw virtual-ip-address* inet:ip-address		| +--rw virtual-ip-address* inet:ip-address
	| +--rw priority? uint8		| +--rw priority? uint8
	| +--rw ping-reply? boolean		| +--rw ping-reply? boolean
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	...		...
	Figure 20: VRRP Subtree Structure		Figure 20: VRRP Subtree Structure
	The following data nodes are supported:		The following data nodes are supported:
	'address-family': Indicates whether IPv4, IPv6, or both address		'address-family': Indicates whether IPv4, IPv6, or both address
	families are to be activated. Note that VRRP version 3 [RFC5798]		families are to be activated. Note that VRRP version 3 [RFC5798]
	skipping to change at line 2007 ¶		skipping to change at line 2007 ¶
	| +--rw local-multiplier? uint8		| +--rw local-multiplier? uint8
	| +--rw holdtime? uint32		| +--rw holdtime? uint32
	| +--rw profile? leafref		| +--rw profile? leafref
	| +--rw authentication!		| +--rw authentication!
	| | +--rw key-chain? key-chain:key-chain-ref		| | +--rw key-chain? key-chain:key-chain-ref
	| | +--rw meticulous? boolean		| | +--rw meticulous? boolean
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	...		...
	Figure 21: IP Connection Subtree Structure (OAM)		Figure 21: IP Connection Subtree Structure (OAM)
	The following OAM data nodes can be specified:		The following OAM data nodes can be specified:
	'session-type': Indicates which BFD flavor is used to set up the		'session-type': Indicates which BFD flavor is used to set up the
	session (e.g., classic BFD [RFC5880], Seamless BFD [RFC7880]). By		session (e.g., classic BFD [RFC5880], Seamless BFD [RFC7880]). By
	skipping to change at line 2109 ¶		skipping to change at line 2109 ¶
	| {vpn-common:carriers-carrier}?		| {vpn-common:carriers-carrier}?
	| +--rw signaling-type? enumeration		| +--rw signaling-type? enumeration
	+--rw ntp		+--rw ntp
	| +--rw broadcast? enumeration		| +--rw broadcast? enumeration
	| +--rw auth-profile		| +--rw auth-profile
	| | +--rw profile-id? string		| | +--rw profile-id? string
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw multicast {vpn-common:multicast}?		+--rw multicast {vpn-common:multicast}?
	...		...
	Figure 23: Services Subtree Structure		Figure 23: Services Subtree Structure
	The following data nodes are defined:		The following data nodes are defined:
	'pe-to-ce-bandwidth': Indicates, in bits per second (bps), the		'pe-to-ce-bandwidth': Indicates, in bits per second (bps), the
	skipping to change at line 2524 ¶		skipping to change at line 2524 ¶
	| | +--rw source-addr?		| | +--rw source-addr?
	| | rt-types:ipv4-multicast-source-address		| | rt-types:ipv4-multicast-source-address
	| +--rw max-groups? uint32		| +--rw max-groups? uint32
	| +--rw max-entries? uint32		| +--rw max-entries? uint32
	| +--rw max-group-sources? uint32		| +--rw max-group-sources? uint32
	| +--rw version? identityref		| +--rw version? identityref
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw mld {vpn-common:mld}?		+--rw mld {vpn-common:mld}?
	| +--rw static-group* [group-addr]		| +--rw static-group* [group-addr]
	| | +--rw group-addr		| | +--rw group-addr
	| | rt-types:ipv6-multicast-group-address		| | rt-types:ipv6-multicast-group-address
	| | +--rw source-addr?		| | +--rw source-addr?
	| | rt-types:ipv6-multicast-source-address		| | rt-types:ipv6-multicast-source-address
	| +--rw max-groups? uint32		| +--rw max-groups? uint32
	| +--rw max-entries? uint32		| +--rw max-entries? uint32
	| +--rw max-group-sources? uint32		| +--rw max-group-sources? uint32
	| +--rw version? identityref		| +--rw version? identityref
	| +--rw status		| +--rw status
	| +--rw admin-status		| +--rw admin-status
	| | +--rw status? identityref		| | +--rw status? identityref
	| | +--rw last-change? yang:date-and-time		| | +--rw last-change? yang:date-and-time
	| +--rw oper-status		| +--ro oper-status
	| +--ro status? identityref		| +--ro status? identityref
	| +--ro last-change? yang:date-and-time		| +--ro last-change? yang:date-and-time
	+--rw pim {vpn-common:pim}?		+--rw pim {vpn-common:pim}?
	+--rw hello-interval? rt-types:timer-value-seconds16		+--rw hello-interval? rt-types:timer-value-seconds16
	+--rw dr-priority? uint32		+--rw dr-priority? uint32
	+--rw status		+--rw status
	+--rw admin-status		+--rw admin-status
	| +--rw status? identityref		| +--rw status? identityref
	| +--rw last-change? yang:date-and-time		| +--rw last-change? yang:date-and-time
	+--rw oper-status		+--ro oper-status
	+--ro status? identityref		+--ro status? identityref
	+--ro last-change? yang:date-and-time		+--ro last-change? yang:date-and-time
	Figure 30: Multicast Subtree Structure (VPN Network Access Level)		Figure 30: Multicast Subtree Structure (VPN Network Access Level)
	8. L3NM YANG Module		8. L3NM YANG Module
	This module uses types defined in [RFC6991], [RFC8343], and		This module uses types defined in [RFC6991], [RFC8343], and
	[RFC9181]. It also uses groupings defined in [RFC8519], [RFC8177],		[RFC9181]. It also uses groupings defined in [RFC8519], [RFC8177],
	and [RFC8294].		and [RFC8294].
	skipping to change at line 5933 ¶		skipping to change at line 5933 ¶
	Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October		Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October
	2018, <https://www.rfc-editor.org/info/rfc8466>.		2018, <https://www.rfc-editor.org/info/rfc8466>.
	[RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair,		[RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair,
	"YANG Data Model for Network Access Control Lists (ACLs)",		"YANG Data Model for Network Access Control Lists (ACLs)",
	RFC 8519, DOI 10.17487/RFC8519, March 2019,		RFC 8519, DOI 10.17487/RFC8519, March 2019,
	<https://www.rfc-editor.org/info/rfc8519>.		<https://www.rfc-editor.org/info/rfc8519>.
	[RFC9181] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M.,		[RFC9181] Barguil, S., Gonzalez de Dios, O., Ed., Boucadair, M.,
	Ed., and Q. Wu, "A Common YANG Data Model for Layer 2 and		Ed., and Q. Wu, "A Common YANG Data Model for Layer 2 and
	Layer 3 VPNs", RFC 9181, DOI 10.17487/RFC9181, January		Layer 3 VPNs", RFC 9181, DOI 10.17487/RFC9181, February
	2022, <https://www.rfc-editor.org/info/rfc9181>.		2022, <https://www.rfc-editor.org/info/rfc9181>.
	11.2. Informative References		11.2. Informative References
	[BGP-YANG] Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP		[BGP-YANG] Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP
	YANG Model for Service Provider Networks", Work in		YANG Model for Service Provider Networks", Work in
	Progress, Internet-Draft, draft-ietf-idr-bgp-model-12, 25		Progress, Internet-Draft, draft-ietf-idr-bgp-model-12, 25
	October 2021, <https://datatracker.ietf.org/doc/html/		October 2021, <https://datatracker.ietf.org/doc/html/
	draft-ietf-idr-bgp-model-12>.		draft-ietf-idr-bgp-model-12>.
	skipping to change at line 5966 ¶		skipping to change at line 5966 ¶
	<https://ieeexplore.ieee.org/document/9105034>.		<https://ieeexplore.ieee.org/document/9105034>.
	[Network-Slices-Framework]		[Network-Slices-Framework]
	Farrel, A., Ed., Gray, E., Drake, J., Rokui, R., Homma,		Farrel, A., Ed., Gray, E., Drake, J., Rokui, R., Homma,
	S., Makhijani, K., Contreras, LM., and J. Tantsura,		S., Makhijani, K., Contreras, LM., and J. Tantsura,
	"Framework for IETF Network Slices", Work in Progress,		"Framework for IETF Network Slices", Work in Progress,
	Internet-Draft, draft-ietf-teas-ietf-network-slices-05, 25		Internet-Draft, draft-ietf-teas-ietf-network-slices-05, 25
	October 2021, <https://datatracker.ietf.org/doc/html/		October 2021, <https://datatracker.ietf.org/doc/html/
	draft-ietf-teas-ietf-network-slices-05>.		draft-ietf-teas-ietf-network-slices-05>.
	[PYANG] "pyang", commit 5e2829d, November 2021,		[PIM-YANG] Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
			Y., and F. Hu, "A YANG Data Model for Protocol Independent
			Multicast (PIM)", Work in Progress, Internet-Draft, draft-
			ietf-pim-yang-17, 19 May 2018,
			<https://datatracker.ietf.org/doc/html/draft-ietf-pim-
			yang-17>.
			[PYANG] "pyang", commit 524cf61, December 2021,
	<https://github.com/mbj4668/pyang>.		<https://github.com/mbj4668/pyang>.
	[QoS-YANG] Choudhary, A., Jethanandani, M., Aries, E., and I. Chen,		[QoS-YANG] Choudhary, A., Jethanandani, M., Aries, E., and I. Chen,
	"A YANG Data Model for Quality of Service (QoS)", Work in		"A YANG Data Model for Quality of Service (QoS)", Work in
	Progress, Internet-Draft, draft-ietf-rtgwg-qos-model-06, 8		Progress, Internet-Draft, draft-ietf-rtgwg-qos-model-06, 8
	November 2021, <https://datatracker.ietf.org/doc/html/		November 2021, <https://datatracker.ietf.org/doc/html/
	draft-ietf-rtgwg-qos-model-06>.		draft-ietf-rtgwg-qos-model-06>.
	[RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source		[RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source
	Discovery Protocol (MSDP)", RFC 3618,		Discovery Protocol (MSDP)", RFC 3618,
	skipping to change at line 6116 ¶		skipping to change at line 6123 ¶
	[RFC8915] Franke, D., Sibold, D., Teichel, K., Dansarie, M., and R.		[RFC8915] Franke, D., Sibold, D., Teichel, K., Dansarie, M., and R.
	Sundblad, "Network Time Security for the Network Time		Sundblad, "Network Time Security for the Network Time
	Protocol", RFC 8915, DOI 10.17487/RFC8915, September 2020,		Protocol", RFC 8915, DOI 10.17487/RFC8915, September 2020,
	<https://www.rfc-editor.org/info/rfc8915>.		<https://www.rfc-editor.org/info/rfc8915>.
	[RFC8969] Wu, Q., Ed., Boucadair, M., Ed., Lopez, D., Xie, C., and		[RFC8969] Wu, Q., Ed., Boucadair, M., Ed., Lopez, D., Xie, C., and
	L. Geng, "A Framework for Automating Service and Network		L. Geng, "A Framework for Automating Service and Network
	Management with YANG", RFC 8969, DOI 10.17487/RFC8969,		Management with YANG", RFC 8969, DOI 10.17487/RFC8969,
	January 2021, <https://www.rfc-editor.org/info/rfc8969>.		January 2021, <https://www.rfc-editor.org/info/rfc8969>.
	[RFC9128] Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
	Y., and F. Hu, "YANG Data Model for Protocol Independent
	Multicast (PIM)", RFC 9128, DOI 10.17487/RFC9128, November
	2021, <https://www.rfc-editor.org/info/rfc9128>.
	[RFC9136] Rabadan, J., Ed., Henderickx, W., Drake, J., Lin, W., and		[RFC9136] Rabadan, J., Ed., Henderickx, W., Drake, J., Lin, W., and
	A. Sajassi, "IP Prefix Advertisement in Ethernet VPN		A. Sajassi, "IP Prefix Advertisement in Ethernet VPN
	(EVPN)", RFC 9136, DOI 10.17487/RFC9136, October 2021,		(EVPN)", RFC 9136, DOI 10.17487/RFC9136, October 2021,
	<https://www.rfc-editor.org/info/rfc9136>.		<https://www.rfc-editor.org/info/rfc9136>.
	[YANG-Composed-VPN]		[YANG-Composed-VPN]
	Even, R., Wu, B., Wu, Q., and Y. Cheng, "YANG Data Model		Even, R., Wu, B., Wu, Q., and Y. Cheng, "YANG Data Model
	for Composed VPN Service Delivery", Work in Progress,		for Composed VPN Service Delivery", Work in Progress,
	Internet-Draft, draft-evenwu-opsawg-yang-composed-vpn-03,		Internet-Draft, draft-evenwu-opsawg-yang-composed-vpn-03,
	8 March 2019, <https://datatracker.ietf.org/doc/html/		8 March 2019, <https://datatracker.ietf.org/doc/html/
End of changes. 21 change blocks.
	25 lines changed or deleted		27 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/