< draft-ietf-detnet-yang-13.txt		draft-ietf-detnet-yang-14.txt >
	Network Working Group X. Geng		Network Working Group X. Geng
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track Y. Ryoo		Intended status: Standards Track Y. Ryoo
	Expires: 7 April 2022 ETRI		Expires: 25 April 2022 ETRI
	D. Fedyk		D. Fedyk
	LabN Consulting, L.L.C.		LabN Consulting, L.L.C.
	R. Rahman		R. Rahman
	Individual		Individual
	Z. Li		Z. Li
	China Mobile		China Mobile
	4 October 2021		22 October 2021
	Deterministic Networking (DetNet) YANG Model		Deterministic Networking (DetNet) YANG Model
	draft-ietf-detnet-yang-13		draft-ietf-detnet-yang-14
	Abstract		Abstract
	This document contains the specification for the Deterministic		This document contains the specification for the Deterministic
	Networking YANG Model for configuration and operational data for		Networking YANG Model for configuration and operational data for
	DetNet Flows. The model allows for provisioning of end-to-end DetNet		DetNet Flows. The model allows for provisioning of end-to-end DetNet
	service on devices along the path without dependency on any signaling		service on devices along the path without dependency on any signaling
	protocol. It also specifies operational status for flows. An		protocol. It also specifies operational status for flows. An
	operator or network controller programs the configuration of the		operator or network controller programs the configuration of the
	devices.		devices.
	The YANG module defined in this document conforms to the Network		The YANG module defined in this document conforms to the Network
	Management Datastore Architecture (NMDA).		Management Datastore Architecture (NMDA).
	Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 7 April 2022.		This Internet-Draft will expire on 25 April 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Simplified BSD License text
	as described in Section 4.e of the Trust Legal Provisions and are		as described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. DetNet YANG Module . . . . . . . . . . . . . . . . . . . . . 4		4. DetNet YANG Module . . . . . . . . . . . . . . . . . . . . . 3
	4.1. DetNet Application Flow YANG Attributes . . . . . . . . . 5		4.1. DetNet Application Flow YANG Attributes . . . . . . . . . 5
	4.2. DetNet Service Sub-layer YANG Attributes . . . . . . . . 5		4.2. DetNet Service Sub-layer YANG Attributes . . . . . . . . 5
	4.3. DetNet Forwarding Sub-layer YANG Attributes . . . . . . . 5		4.3. DetNet Forwarding Sub-layer YANG Attributes . . . . . . . 5
	5. DetNet Flow Aggregation . . . . . . . . . . . . . . . . . . . 6		5. DetNet Flow Aggregation . . . . . . . . . . . . . . . . . . . 6
	6. DetNet YANG Structure Considerations . . . . . . . . . . . . 7		6. DetNet YANG Structure Considerations . . . . . . . . . . . . 7
	7. DetNet Configuration YANG Structures . . . . . . . . . . . . 8		7. DetNet Configuration YANG Structures . . . . . . . . . . . . 8
	8. DetNet Configuration YANG Model . . . . . . . . . . . . . . . 9		8. DetNet Configuration YANG Model . . . . . . . . . . . . . . . 9
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 40		10. Security Considerations . . . . . . . . . . . . . . . . . . . 39
	11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 40		11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39
	12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41		12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 41		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
	13.1. Normative References . . . . . . . . . . . . . . . . . . 41		13.1. Normative References . . . . . . . . . . . . . . . . . . 40
	13.2. Informative References . . . . . . . . . . . . . . . . . 42		13.2. Informative References . . . . . . . . . . . . . . . . . 41
	Appendix A. DetNet Configuration YANG Tree . . . . . . . . . . . 43		Appendix A. DetNet Configuration YANG Tree . . . . . . . . . . . 42
	Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 52		Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 51
	B.1. Example A-1 JSON Configuration/Operational . . . . . . . 52		B.1. Example A-1 JSON Configuration/Operational . . . . . . . 51
	B.2. Example B-1 XML Config: Aggregation using a Forwarding		B.2. Example B-1 XML Config: Aggregation using a Forwarding
	Sub-layer . . . . . . . . . . . . . . . . . . . . . . . . 57		Sub-layer . . . . . . . . . . . . . . . . . . . . . . . . 56
	B.3. Example B-2 JSON Service Aggregation Configuration . . . 61		B.3. Example B-2 JSON Service Aggregation Configuration . . . 60
	B.4. Example C-1 JSON Relay Aggregation/Disaggregation		B.4. Example C-1 JSON Relay Aggregation/Disaggregation
	Configuration . . . . . . . . . . . . . . . . . . . . . . 67		Configuration . . . . . . . . . . . . . . . . . . . . . . 66
	B.5. Example C-2 JSON Relay Aggregation Service Sub-Layer . . 83		B.5. Example C-2 JSON Relay Aggregation Service Sub-Layer . . 83
	B.6. Example C-3 JSON Relay Service Sub-Layer Aggregation/		B.6. Example C-3 JSON Relay Service Sub-Layer Aggregation/
	Disaggregation . . . . . . . . . . . . . . . . . . . . . 96		Disaggregation . . . . . . . . . . . . . . . . . . . . . 95
	B.7. Example C-4 JSON Relay Service Sub-Layer Aggregation/		B.7. Example C-4 JSON Relay Service Sub-Layer Aggregation/
	Disaggregation . . . . . . . . . . . . . . . . . . . . . 110		Disaggregation . . . . . . . . . . . . . . . . . . . . . 109
	B.8. Example D-1 JSON Transit Forwarding Sub-Layer Aggregation/		B.8. Example D-1 JSON Transit Forwarding Sub-Layer Aggregation/
	Disaggregation . . . . . . . . . . . . . . . . . . . . . 126		Disaggregation . . . . . . . . . . . . . . . . . . . . . 126
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 133		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 133
	1. Introduction		1. Introduction
	DetNet (Deterministic Networking) provides a capability to carry		DetNet (Deterministic Networking) provides a capability to carry
	specified unicast or multicast data flows for real-time applications		specified unicast or multicast data flows for real-time applications
	with extremely low packet loss rates and assured maximum end-to-end		with extremely low packet loss rates and assured maximum end-to-end
	delivery latency. A description of the general background and		delivery latency. A description of the general background and
	skipping to change at page 9, line 49 ¶		skipping to change at page 9, line 7 ¶
	+--rw name string		+--rw name string
	+--rw traffic-profile? traffic-profile-ref		+--rw traffic-profile? traffic-profile-ref
	+--rw operation? forwarding-operations		+--rw operation? forwarding-operations
	+--rw incoming		+--rw incoming
	| ...		| ...
	+--rw outgoing		+--rw outgoing
	...		...
	8. DetNet Configuration YANG Model		8. DetNet Configuration YANG Model
	The following model has references to RFCs [RFC4303], [RFC8349],		This YANG model imports typedefs from [RFC6991], [RFC8519],
	[RFC8960], [RFC8964], and [IEEE8021Q].		[RFC8294], [RFC8343], and [IEEE8021Q]. This YANG model also has the
			folowing references to RFCs that are not in the document text body
			[RFC0791], [RFC4303], [RFC8349], [RFC8960], [RFC8964], and [RFC8200].
	<CODE BEGINS>		<CODE BEGINS> file "ietf-detnet@2021-10-20.yang"
	module ietf-detnet {		module ietf-detnet {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-detnet";		namespace "urn:ietf:params:xml:ns:yang:ietf-detnet";
	prefix dnet;		prefix dnet;
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	reference		reference
	"RFC 6991 - Common YANG Data Types.";		"RFC 6991 - Common YANG Data Types.";
	}		}
	skipping to change at page 11, line 29 ¶		skipping to change at page 10, line 35 ¶
	<mailto:reshad@yahoo.com>		<mailto:reshad@yahoo.com>
	Editor: Mach Chen		Editor: Mach Chen
	<mailto:mach.chen@huawei.com>		<mailto:mach.chen@huawei.com>
	Editor: Zhenqiang Li		Editor: Zhenqiang Li
	<mailto:lizhenqiang@chinamobile.com>";		<mailto:lizhenqiang@chinamobile.com>";
	description		description
	"This YANG module describes the parameters needed		"This YANG module describes the parameters needed
	for DetNet flow configuration and flow status		for DetNet flow configuration and flow status
	reporting.		reporting. This YANG module conforms to the Network
			Management Datastore Architecture (NMDA).
	Copyright (c) 2021 IETF Trust and the persons identified as		Copyright (c) 2021 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		authors of the code. All rights reserved.
	Redistribution and use in source and binary forms, with or		Redistribution and use in source and binary forms, with or
	without modification, is permitted pursuant to, and subject to		without modification, is permitted pursuant to, and subject to
	the license terms contained in, the Simplified BSD License set		the license terms contained in, the Simplified BSD License set
	forth in Section 4.c of the IETF Trust's Legal Provisions		forth in Section 4.c of the IETF Trust's Legal Provisions
	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 XXXX		This version of this YANG module is part of RFC XXXX
	(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself		(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
	for full legal notices.		for full legal notices.";
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	'MAY', and 'OPTIONAL' in this document are to be interpreted as
	described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
	they appear in all capitals, as shown here. ";
	revision 2021-10-04 {		revision 2021-10-20 {
	description		description
	"initial revision";		"initial revision";
	reference		reference
	"RFC XXXX: Deterministic Networking (DetNet) YANG Model";		"RFC XXXX: Deterministic Networking (DetNet) YANG Model";
	}		}
	identity app-status {		identity app-status {
	description		description
	"Base identity from which all application-status		"Base identity from which all application-status
	status types are derived.";		status types are derived.";
	skipping to change at page 19, line 51 ¶		skipping to change at page 19, line 4 ¶
	}		}
	grouping source-ip-port-id {		grouping source-ip-port-id {
	description		description
	"The TCP/UDP port(source/destination) identification		"The TCP/UDP port(source/destination) identification
	information.";		information.";
	container source-port {		container source-port {
	uses packet-fields:port-range-or-operator;		uses packet-fields:port-range-or-operator;
	description		description
	"This grouping captures the source port fields.";		"This grouping captures the source port fields.";
	}
			}
	}		}
	grouping ip-flow-id {		grouping ip-flow-id {
	description		description
	"The IPv4/IPv6 packet header identification information.";		"The IPv4/IPv6 packet header identification information.";
	leaf src-ip-prefix {		leaf src-ip-prefix {
	type inet:ip-prefix;		type inet:ip-prefix;
	description		description
	"The source IP prefix.";		"The source IP prefix.";
	reference		reference
	skipping to change at page 24, line 51 ¶		skipping to change at page 24, line 4 ¶
	case ip {		case ip {
	leaf next-hop-address {		leaf next-hop-address {
	type inet:ip-address-no-zone;		type inet:ip-address-no-zone;
	description		description
	"This is the IP flow type next hop.";		"This is the IP flow type next hop.";
	}		}
	}		}
	case mpls {		case mpls {
	uses rt-types:mpls-label-stack;		uses rt-types:mpls-label-stack;
	}		}
	}
			}
	}		}
	}		}
	}		}
	}		}
	grouping detnet-forwarding-next-hop-content {		grouping detnet-forwarding-next-hop-content {
	description		description
	"Generic parameters of DetNet next hops. This follows the		"Generic parameters of DetNet next hops. This follows the
	principles for next hops in RFC 8349";		principles for next hops in RFC 8349";
	choice next-hop-options {		choice next-hop-options {
	skipping to change at page 25, line 52 ¶		skipping to change at page 25, line 4 ¶
	"This is an IP address as a next hop.";		"This is an IP address as a next hop.";
	}		}
	}		}
	case mpls-over-ip-encapsulation {		case mpls-over-ip-encapsulation {
	uses ip-header;		uses ip-header;
	}		}
	}		}
	}		}
	case mpls {		case mpls {
	uses rt-types:mpls-label-stack;		uses rt-types:mpls-label-stack;
	}
			}
	}		}
	}		}
	case next-hop-list {		case next-hop-list {
	description		description
	"Container for multiple next hops.";		"Container for multiple next hops.";
	list next-hop {		list next-hop {
	key "hop-index";		key "hop-index";
	description		description
	"An entry in a next-hop list.";		"An entry in a next-hop list.";
	leaf hop-index {		leaf hop-index {
	skipping to change at page 40, line 22 ¶		skipping to change at page 39, line 22 ¶
	Name: ietf-detnet		Name: ietf-detnet
	Maintained by IANA: N		Maintained by IANA: N
	Namespace: urn:ietf:params:xml:ns:yang:ietf-detnet		Namespace: urn:ietf:params:xml:ns:yang:ietf-detnet
	Prefix: dnet		Prefix: dnet
	Reference: This RFC when published.		Reference: This RFC when published.
	10. Security Considerations		10. Security Considerations
	Security considerations for DetNet are covered in the DetNet		Security considerations for DetNet are covered in the DetNet
	Archtiecture [RFC8655].		Archtiecture [RFC8655] and DetNet Security Considerations [RFC9055] .
	The YANG modules specified in this document define a schema for data		The YANG modules specified in this document define a schema for data
	that is designed to be accessed via network management protocols,		that is designed to be accessed via network management protocols,
	such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF		such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
	layer is the secure transport layer, and the mandatory-to-implement		layer is the secure transport layer, and the mandatory-to-implement
	secure transport is Secure Shell (SSH) [RFC6242]. The lowest		secure transport is Secure Shell (SSH) [RFC6242]. The lowest
	RESTCONF layer is HTTPS, and the mandatory-to-implement secure		RESTCONF layer is HTTPS, and the mandatory-to-implement secure
	transport is TLS [RFC8446].		transport is TLS [RFC8446].
	The Network Configuration Access Control Model (NACM) [RFC8341]		The Network Configuration Access Control Model (NACM) [RFC8341]
	skipping to change at page 41, line 15 ¶		skipping to change at page 40, line 15 ¶
	12. Acknowledgments		12. Acknowledgments
	The editors of this document would like to thank Lou Berger, Tom		The editors of this document would like to thank Lou Berger, Tom
	Petch and Xufeng Lui for their detailed comments.		Petch and Xufeng Lui for their detailed comments.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
	Requirement Levels", BCP 14, RFC 2119,		DOI 10.17487/RFC0791, September 1981,
	DOI 10.17487/RFC2119, March 1997,		<https://www.rfc-editor.org/info/rfc791>.
	<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004,
	<https://www.rfc-editor.org/info/rfc3688>.
	[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",		[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
	RFC 4303, DOI 10.17487/RFC4303, December 2005,		RFC 4303, DOI 10.17487/RFC4303, December 2005,
	<https://www.rfc-editor.org/info/rfc4303>.		<https://www.rfc-editor.org/info/rfc4303>.
	[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	the Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	DOI 10.17487/RFC6020, October 2010,		DOI 10.17487/RFC6020, October 2010,
	<https://www.rfc-editor.org/info/rfc6020>.		<https://www.rfc-editor.org/info/rfc6020>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<https://www.rfc-editor.org/info/rfc6241>.
	[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
	Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
	<https://www.rfc-editor.org/info/rfc6242>.
	[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",		[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
	RFC 6991, DOI 10.17487/RFC6991, July 2013,		RFC 6991, DOI 10.17487/RFC6991, July 2013,
	<https://www.rfc-editor.org/info/rfc6991>.		<https://www.rfc-editor.org/info/rfc6991>.
	[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",		[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
	RFC 7950, DOI 10.17487/RFC7950, August 2016,		RFC 7950, DOI 10.17487/RFC7950, August 2016,
	<https://www.rfc-editor.org/info/rfc7950>.		<https://www.rfc-editor.org/info/rfc7950>.
	[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF		[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,		(IPv6) Specification", STD 86, RFC 8200,
	<https://www.rfc-editor.org/info/rfc8040>.		DOI 10.17487/RFC8200, July 2017,
			<https://www.rfc-editor.org/info/rfc8200>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		"Common YANG Data Types for the Routing Area", RFC 8294,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		DOI 10.17487/RFC8294, December 2017,
			<https://www.rfc-editor.org/info/rfc8294>.
	[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration		[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
	Access Control Model", STD 91, RFC 8341,		Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
	DOI 10.17487/RFC8341, March 2018,		<https://www.rfc-editor.org/info/rfc8343>.
	<https://www.rfc-editor.org/info/rfc8341>.
	[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for		[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
	Routing Management (NMDA Version)", RFC 8349,		Routing Management (NMDA Version)", RFC 8349,
	DOI 10.17487/RFC8349, March 2018,		DOI 10.17487/RFC8349, March 2018,
	<https://www.rfc-editor.org/info/rfc8349>.		<https://www.rfc-editor.org/info/rfc8349>.
	[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol		[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
	Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,		Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
	<https://www.rfc-editor.org/info/rfc8446>.		<https://www.rfc-editor.org/info/rfc8446>.
			[RFC8519] Jethanandani, M., Agarwal, S., Huang, L., and D. Blair,
			"YANG Data Model for Network Access Control Lists (ACLs)",
			RFC 8519, DOI 10.17487/RFC8519, March 2019,
			<https://www.rfc-editor.org/info/rfc8519>.
	[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,		[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", RFC 8655,		"Deterministic Networking Architecture", RFC 8655,
	DOI 10.17487/RFC8655, October 2019,		DOI 10.17487/RFC8655, October 2019,
	<https://www.rfc-editor.org/info/rfc8655>.		<https://www.rfc-editor.org/info/rfc8655>.
	[RFC8960] Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A		[RFC8960] Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
	YANG Data Model for MPLS Base", RFC 8960,		YANG Data Model for MPLS Base", RFC 8960,
	DOI 10.17487/RFC8960, December 2020,		DOI 10.17487/RFC8960, December 2020,
	<https://www.rfc-editor.org/info/rfc8960>.		<https://www.rfc-editor.org/info/rfc8960>.
	[RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant,		[RFC8964] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., Bryant,
	S., and J. Korhonen, "Deterministic Networking (DetNet)		S., and J. Korhonen, "Deterministic Networking (DetNet)
	Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January		Data Plane: MPLS", RFC 8964, DOI 10.17487/RFC8964, January
	2021, <https://www.rfc-editor.org/info/rfc8964>.		2021, <https://www.rfc-editor.org/info/rfc8964>.
			[RFC9016] Varga, B., Farkas, J., Cummings, R., Jiang, Y., and D.
			Fedyk, "Flow and Service Information Model for
			Deterministic Networking (DetNet)", RFC 9016,
			DOI 10.17487/RFC9016, March 2021,
			<https://www.rfc-editor.org/info/rfc9016>.
			[RFC9055] Grossman, E., Ed., Mizrahi, T., and A. Hacker,
			"Deterministic Networking (DetNet) Security
			Considerations", RFC 9055, DOI 10.17487/RFC9055, June
			2021, <https://www.rfc-editor.org/info/rfc9055>.
	13.2. Informative References		13.2. Informative References
	[IEEE8021Q]		[IEEE8021Q]
	IEEE, "IEEE Standard for Local and Metropolitan Area		IEEE, "IEEE Standard for Local and Metropolitan Area
	Networks--Bridges and Bridged Networks",		Networks--Bridges and Bridged Networks",
	DOI 10.1109/IEEESTD.2018.8403927, IEEE 802.1Q-2018, July		DOI 10.1109/IEEESTD.2018.8403927, IEEE 802.1Q-2018, July
	2018, <https://ieeexplore.ieee.org/document/8403927>.		2018, <https://ieeexplore.ieee.org/document/8403927>.
			[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
			DOI 10.17487/RFC3688, January 2004,
			<https://www.rfc-editor.org/info/rfc3688>.
			[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
			and A. Bierman, Ed., "Network Configuration Protocol
			(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
			<https://www.rfc-editor.org/info/rfc6241>.
			[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
			Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
			<https://www.rfc-editor.org/info/rfc6242>.
			[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
			Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
			<https://www.rfc-editor.org/info/rfc8040>.
	[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",		[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
	BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,		BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
	<https://www.rfc-editor.org/info/rfc8340>.		<https://www.rfc-editor.org/info/rfc8340>.
	[RFC9016] Varga, B., Farkas, J., Cummings, R., Jiang, Y., and D.		[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
	Fedyk, "Flow and Service Information Model for		Access Control Model", STD 91, RFC 8341,
	Deterministic Networking (DetNet)", RFC 9016,		DOI 10.17487/RFC8341, March 2018,
	DOI 10.17487/RFC9016, March 2021,		<https://www.rfc-editor.org/info/rfc8341>.
	<https://www.rfc-editor.org/info/rfc9016>.
	Appendix A. DetNet Configuration YANG Tree		Appendix A. DetNet Configuration YANG Tree
	This is the full YANG tree as described in [RFC8340].		This is the full YANG tree as described in [RFC8340].
	module: ietf-detnet		module: ietf-detnet
	+--rw detnet		+--rw detnet
	+--rw traffic-profile* [name]		+--rw traffic-profile* [name]
	| +--rw name string		| +--rw name string
	| +--rw traffic-requirements		| +--rw traffic-requirements
End of changes. 32 change blocks.
	76 lines changed or deleted		85 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/