draft-geng-detnet-conf-yang-04.txt		draft-geng-detnet-conf-yang-05.txt
	Network Working Group X. Geng		Network Working Group X. Geng
	Internet-Draft M. Chen		Internet-Draft M. Chen
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: March 14, 2019 Z. Li		Expires: April 20, 2019 Z. Li
	China Mobile		China Mobile
	R. Rahman		R. Rahman
	Cisco Systems		Cisco Systems
	September 10, 2018		October 17, 2018
	DetNet Configuration YANG Model		DetNet Configuration YANG Model
	draft-geng-detnet-conf-yang-04		draft-geng-detnet-conf-yang-05
	Abstract		Abstract
	This document defines a YANG data model for Deterministic Networking		This document defines a YANG data model for Deterministic Networking
	(DetNet), which includes the DetNet topology YANG module, DetNet flow		(DetNet), which includes the DetNet topology YANG module, DetNet flow
	configuration YANG module and DetNet Transport QoS YANG Module.		configuration YANG module and DetNet Transport QoS YANG Module.
	The YANG modules in this document conform to the Network Management		The YANG modules in this document conform to the Network Management
	Datastore Architecture (NMDA).		Datastore Architecture (NMDA).
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	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 March 14, 2019.		This Internet-Draft will expire on April 20, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 39 ¶		skipping to change at page 2, line 39 ¶
	4.1. DetNet Service Proxy Configuration Attributes . . . . . . 9		4.1. DetNet Service Proxy Configuration Attributes . . . . . . 9
	4.2. DetNet Service Layer Configuration Attributes . . . . . . 10		4.2. DetNet Service Layer Configuration Attributes . . . . . . 10
	4.3. DetNet Transport Layer Configuration Attributes . . . . . 12		4.3. DetNet Transport Layer Configuration Attributes . . . . . 12
	4.4. DetNet Flow Configuration Example . . . . . . . . . . . . 13		4.4. DetNet Flow Configuration Example . . . . . . . . . . . . 13
	5. DetNet Transport QoS Model . . . . . . . . . . . . . . . . . 14		5. DetNet Transport QoS Model . . . . . . . . . . . . . . . . . 14
	6. DetNet Yang Structure . . . . . . . . . . . . . . . . . . . . 15		6. DetNet Yang Structure . . . . . . . . . . . . . . . . . . . . 15
	6.1. DetNet Topology Model Tree Diagram . . . . . . . . . . . 15		6.1. DetNet Topology Model Tree Diagram . . . . . . . . . . . 15
	6.2. DetNet Flow Configuration Model Tree Diagram . . . . . . 17		6.2. DetNet Flow Configuration Model Tree Diagram . . . . . . 17
	7. DetNet YANG Model . . . . . . . . . . . . . . . . . . . . . . 22		7. DetNet YANG Model . . . . . . . . . . . . . . . . . . . . . . 22
	7.1. DetNet Topology YANG Model . . . . . . . . . . . . . . . 22		7.1. DetNet Topology YANG Model . . . . . . . . . . . . . . . 22
	7.2. DetNet Flow Configuration YANG Model . . . . . . . . . . 29		7.2. DetNet Flow Configuration YANG Model . . . . . . . . . . 28
	8. DetNet Configuration Model Classification . . . . . . . . . . 46		8. DetNet Configuration Model Classification . . . . . . . . . . 45
	8.1. Fully Distributed Configuration Model . . . . . . . . . . 46		8.1. Fully Distributed Configuration Model . . . . . . . . . . 45
	8.2. Fully Centralized Configuration Model . . . . . . . . . . 46		8.2. Fully Centralized Configuration Model . . . . . . . . . . 46
	8.3. Hybrid Configuration Model . . . . . . . . . . . . . . . 47		8.3. Hybrid Configuration Model . . . . . . . . . . . . . . . 46
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48		9. Open issues . . . . . . . . . . . . . . . . . . . . . . . . . 47
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 48		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48		11. Security Considerations . . . . . . . . . . . . . . . . . . . 48
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 48		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 48
	12.1. Normative References . . . . . . . . . . . . . . . . . . 48		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
	12.2. Informative References . . . . . . . . . . . . . . . . . 49		13.1. Normative References . . . . . . . . . . . . . . . . . . 48
			13.2. Informative References . . . . . . . . . . . . . . . . . 49
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51
	1. Introduction		1. Introduction
	Deterministic Networking (DetNet) [I-D.ietf-detnet-architecture] is		Deterministic Networking (DetNet) [I-D.ietf-detnet-architecture] is
	defined to provide high-quality network service with extremely low		defined to provide high-quality network service with extremely low
	packet loss rate, bounded low latency and jitter.		packet loss rate, bounded low latency and jitter.
	DetNet flow information is defined		DetNet flow information is defined
	in[I-D.ietf-detnet-flow-information-model], and the DetNet models are		in[I-D.ietf-detnet-flow-information-model], and the DetNet models are
	skipping to change at page 24, line 7 ¶		skipping to change at page 24, line 7 ¶
	module with DetNet related capabilities and		module with DetNet related capabilities and
	parameters.";		parameters.";
	revision "2018-09-10" {		revision "2018-09-10" {
	description "Initial revision";		description "Initial revision";
	reference "RFC XXXX: draft-geng-detnet-config-yang-05";		reference "RFC XXXX: draft-geng-detnet-config-yang-05";
	}		}
	grouping detnet-queuing-algorithms {		grouping detnet-queuing-algorithms {
	description		description
	"Candidate DetNet queuing management algorithms.";		"Relationship with IEEE 802.1 TSN YANG models is TBD.";
	leaf credit-based-shaping {
	type boolean;
	description
	"Indicates whether credit based shaping is
	supported.";
	reference
	"IEEE P802.1 Qav";
	}
	leaf time-aware-shaping {
	type boolean;
	description
	"Indicates whether time aware shaping is
	supported.";
	reference
	"IEEE P802.1 Qbv";
	}
	leaf cyclic-queuing-and-forwarding {
	type boolean;
	description
	"Indicates whether cyclic queuing and
	forwarding is supported.";
	reference
	"IEEE P802.1 Qch";
	}
	leaf asynchronous-traffic-shaping {
	type boolean;
	description
	"Indicates whether asynchronous traffic
	shaping is supported.";
	reference
	"IEEE P802.1 Qcr";
	}
	}		}
	grouping detnet-node-attributes{		grouping detnet-node-attributes{
	description		description
	"DetNet node related attributes.";		"DetNet node related attributes.";
	leaf minimum-packet-processing-delay{		leaf minimum-packet-processing-delay{
	type uint32;		type uint32;
	description		description
	"Minimum packet processing delay		"Minimum packet processing delay
	in a node. The unit of the delay		in a node. The unit of the delay
	skipping to change at page 48, line 22 ¶		skipping to change at page 47, line 32 ¶
	more typical scenarios and give a practical solution.		more typical scenarios and give a practical solution.
	2. [IEEE802.1Qcc] also defines three TSN configuration models:		2. [IEEE802.1Qcc] also defines three TSN configuration models:
	fully-centralized model, fully-distributed model, centralized Network		fully-centralized model, fully-distributed model, centralized Network
	/ distributed User Model. This section defines the configuration		/ distributed User Model. This section defines the configuration
	model roughly the same, to keep the design of L2 and L3 in the same		model roughly the same, to keep the design of L2 and L3 in the same
	structure. Hybrid configuration model is slightly different from the		structure. Hybrid configuration model is slightly different from the
	'centralized Network / distributed User Model'. The hybrid		'centralized Network / distributed User Model'. The hybrid
	configuration model intends to contain more variations.		configuration model intends to contain more variations.
	9. IANA Considerations		9. Open issues
			There are some open issues that are still under disccusion:
			o The Relationship with 802.1 TSN YANG models is TBD. The possible
			problems include: what is the relationship between DetNet YANG and
			TSN YANG that will be defined in IEEE 802.1 CBcv, whether a common
			YANG model should be defined to be shared by both TSN and DetNet,
			and so on.
			o DetNet Transport QoS Model is TBD. The possible problem is how to
			provide an interface to use the queuing management algorithms
			defined in IEEE.
			These issues will be resolved in the following versions of the draft.
			10. IANA Considerations
	This document makes no request of IANA.		This document makes no request of IANA.
	Note to RFC Editor: this section may be removed on publication as an		Note to RFC Editor: this section may be removed on publication as an
	RFC.		RFC.
	10. Security Considerations		11. Security Considerations
	<TBD>		<TBD>
	11. Acknowledgements		12. Acknowledgements
	12. References		13. References
	12.1. Normative References		13.1. Normative References
	[I-D.finn-detnet-bounded-latency]		[I-D.finn-detnet-bounded-latency]
	Finn, N., Boudec, J., Mohammadpour, E., Varga, B., and J.		Finn, N., Boudec, J., Mohammadpour, E., Varga, B., and J.
	Farkas, "DetNet Bounded Latency", draft-finn-detnet-		Farkas, "DetNet Bounded Latency", draft-finn-detnet-
	bounded-latency-01 (work in progress), July 2018.		bounded-latency-01 (work in progress), July 2018.
	[I-D.ietf-detnet-architecture]		[I-D.ietf-detnet-architecture]
	Finn, N., Thubert, P., Varga, B., and J. Farkas,		Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", draft-ietf-		"Deterministic Networking Architecture", draft-ietf-
	detnet-architecture-07 (work in progress), August 2018.		detnet-architecture-08 (work in progress), September 2018.
	[I-D.ietf-detnet-dp-sol-ip]		[I-D.ietf-detnet-dp-sol-ip]
	Korhonen, J. and B. Varga, "DetNet IP Data Plane		Korhonen, J. and B. Varga, "DetNet IP Data Plane
	Encapsulation", draft-ietf-detnet-dp-sol-ip-00 (work in		Encapsulation", draft-ietf-detnet-dp-sol-ip-00 (work in
	progress), July 2018.		progress), July 2018.
	[I-D.ietf-detnet-dp-sol-mpls]		[I-D.ietf-detnet-dp-sol-mpls]
	Korhonen, J. and B. Varga, "DetNet MPLS Data Plane		Korhonen, J. and B. Varga, "DetNet MPLS Data Plane
	Encapsulation", draft-ietf-detnet-dp-sol-mpls-00 (work in		Encapsulation", draft-ietf-detnet-dp-sol-mpls-00 (work in
	progress), July 2018.		progress), July 2018.
	skipping to change at page 49, line 34 ¶		skipping to change at page 49, line 13 ¶
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[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>.
	12.2. Informative References		13.2. Informative References
	[I-D.geng-detnet-info-distribution]		[I-D.geng-detnet-info-distribution]
	Geng, X., Chen, M., and Z. Li, "IGP-TE Extensions for		Geng, X., Chen, M., and Z. Li, "IGP-TE Extensions for
	DetNet Information Distribution", draft-geng-detnet-info-		DetNet Information Distribution", draft-geng-detnet-info-
	distribution-02 (work in progress), March 2018.		distribution-02 (work in progress), March 2018.
	[I-D.ietf-detnet-use-cases]		[I-D.ietf-detnet-use-cases]
	Grossman, E., "Deterministic Networking Use Cases", draft-		Grossman, E., "Deterministic Networking Use Cases", draft-
	ietf-detnet-use-cases-17 (work in progress), June 2018.		ietf-detnet-use-cases-18 (work in progress), September
			2018.
	[I-D.ietf-teas-yang-te]		[I-D.ietf-teas-yang-te]
	Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and		Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
	I. Bryskin, "A YANG Data Model for Traffic Engineering		I. Bryskin, "A YANG Data Model for Traffic Engineering
	Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work		Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work
	in progress), July 2018.		in progress), July 2018.
	[I-D.ietf-teas-yang-te-topo]		[I-D.ietf-teas-yang-te-topo]
	Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and		Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
	O. Dios, "YANG Data Model for Traffic Engineering (TE)		O. Dios, "YANG Data Model for Traffic Engineering (TE)
End of changes. 15 change blocks.
	56 lines changed or deleted		41 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/