draft-ietf-detnet-problem-statement-06.txt		draft-ietf-detnet-problem-statement-07.txt
	detnet N. Finn		DetNet N. Finn
	Internet-Draft Huawei Technologies Co. Ltd		Internet-Draft Huawei Technologies Co. Ltd
	Intended status: Informational P. Thubert		Intended status: Informational P. Thubert
	Expires: January 17, 2019 Cisco		Expires: April 6, 2019 Cisco
	July 16, 2018		October 3, 2018
	Deterministic Networking Problem Statement		Deterministic Networking Problem Statement
	draft-ietf-detnet-problem-statement-06		draft-ietf-detnet-problem-statement-07
	Abstract		Abstract
	This paper documents the needs in various industries to establish		This paper documents the needs in various industries to establish
	multi-hop paths for characterized flows with deterministic		multi-hop paths for characterized flows with deterministic
	properties.		properties.
	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
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	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 January 17, 2019.		This Internet-Draft will expire on April 6, 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 19 ¶		skipping to change at page 2, line 19 ¶
	3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6		3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Supported topologies . . . . . . . . . . . . . . . . . . 6		3.1. Supported topologies . . . . . . . . . . . . . . . . . . 6
	3.2. Flow Characterization . . . . . . . . . . . . . . . . . . 6		3.2. Flow Characterization . . . . . . . . . . . . . . . . . . 6
	3.3. Centralized Path Computation and Installation . . . . . . 6		3.3. Centralized Path Computation and Installation . . . . . . 6
	3.4. Distributed Path Setup . . . . . . . . . . . . . . . . . 7		3.4. Distributed Path Setup . . . . . . . . . . . . . . . . . 7
	3.5. Duplicated data format . . . . . . . . . . . . . . . . . 8		3.5. Duplicated data format . . . . . . . . . . . . . . . . . 8
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 8		4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
	7. Informative References . . . . . . . . . . . . . . . . . . . 9		7. Informative References . . . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	The Deterministic Networking Use Cases [I-D.ietf-detnet-use-cases]		The Deterministic Networking Use Cases [I-D.ietf-detnet-use-cases]
	document illustrates that beyond the classical case of industrial		document illustrates that beyond the classical case of industrial
	automation and control systems (IACS), there are in fact multiple		automation and control systems (IACS), there are in fact multiple
	industries with strong and yet relatively similar needs for		industries with strong and yet relatively similar needs for
	deterministic network services with latency guarantees and ultra-low		deterministic network services with latency guarantees and ultra-low
	packet loss.		packet loss.
	skipping to change at page 2, line 50 ¶		skipping to change at page 2, line 50 ¶
	2 control systems, whereas public infrastructures such as Electricity		2 control systems, whereas public infrastructures such as Electricity
	Automation require deterministic properties over the Wide Area. The		Automation require deterministic properties over the Wide Area. The
	realization is now coming that the convergence of IT and Operational		realization is now coming that the convergence of IT and Operational
	Technology (OT) networks requires Layer-3, as well as Layer-2,		Technology (OT) networks requires Layer-3, as well as Layer-2,
	capabilities.		capabilities.
	While the initial user base has focused almost entirely on Ethernet		While the initial user base has focused almost entirely on Ethernet
	physical media and Ethernet-based bridging protocol (from several		physical media and Ethernet-based bridging protocol (from several
	Standards Development Organizations), the need for Layer-3 expressed		Standards Development Organizations), the need for Layer-3 expressed
	above, must not be confined to Ethernet and Ethernet-like media, and		above, must not be confined to Ethernet and Ethernet-like media, and
	while such media must be encompassed by any useful DetNet		while such media must be encompassed by any useful Deterministic
	architecture, cooperation between IETF and other SDOs must not be		Networking (DetNet) Architecture, cooperation between IETF and other
	limited to IEEE or IEEE 802. Furthermore, while the work completed		SDOs must not be limited to IEEE or IEEE 802. Furthermore, while the
	and ongoing in other SDOs, and in IEEE 802 in particular, provide an		work completed and ongoing in other SDOs, and in IEEE 802 in
	obvious starting point for a DetNet architecture, we must not assume		particular, provide an obvious starting point for a DetNet
	that these other SDOs' work confines the space in which the DetNet		architecture, we must not assume that these other SDOs' work confines
	architecture progresses.		the space in which the DetNet architecture progresses.
	The properties of deterministic networks will have specific		The properties of deterministic networks will have specific
	requirements for the use of routed networks to support these		requirements for the use of routed networks to support these
	applications and a new model must be proposed to integrate		applications and a new model must be proposed to integrate
	determinism in IT technology. The proposed model should enable a		determinism in IT technology. The proposed model should enable a
	fully scheduled operation orchestrated by a central controller, and		fully scheduled operation orchestrated by a central controller, and
	may support a more distributed operation with probably lesser		may support a more distributed operation with probably lesser
	capabilities. In any fashion, the model should not compromise the		capabilities. In any fashion, the model should not compromise the
	ability of a network to keep carrying the sorts of traffic that is		ability of a network to keep carrying the sorts of traffic that is
	already carried today in conjunction with new, more deterministic		already carried today in conjunction with new, more deterministic
	flows.		flows. Forward note: The DetNet Architecture
			[I-D.ietf-detnet-architecture] is the document produced by the DetNet
			WG to describe that model.
	Once the abstract model is agreed upon, the IETF will need to specify		Once the abstract model is agreed upon, the IETF will need to specify
	the signaling elements to be used to establish a path and the tagging		the signaling elements to be used to establish a path and the tagging
	elements to be used identify the flows that are to be forwarded along		elements to be used identify the flows that are to be forwarded along
	that path. The IETF will also need to specify the necessary		that path. The IETF will also need to specify the necessary
	protocols, or protocol additions, based on relevant IETF		protocols, or protocol additions, based on relevant IETF
	technologies, to implement the selected model.		technologies, to implement the selected model.
	As a result of this work, it will be possible to establish a multi-		As a result of this work, it will be possible to establish a multi-
	hop path over the IP or MPLS network, for a particular flow with		hop path over the IP or MPLS network, for a particular flow with
	skipping to change at page 4, line 7 ¶		skipping to change at page 4, line 8 ¶
	The Internet is not the only digital network that has grown		The Internet is not the only digital network that has grown
	dramatically over the last 30-40 years. Video and audio		dramatically over the last 30-40 years. Video and audio
	entertainment, and control systems for machinery, manufacturing		entertainment, and control systems for machinery, manufacturing
	processes, and vehicles are also ubiquitous, and are now based almost		processes, and vehicles are also ubiquitous, and are now based almost
	entirely on digital technologies. Over the past 10 years, engineers		entirely on digital technologies. Over the past 10 years, engineers
	in these fields have come to realize that significant advantages in		in these fields have come to realize that significant advantages in
	both cost and in the ability to accelerate growth can be obtained by		both cost and in the ability to accelerate growth can be obtained by
	basing all of these disparate digital technologies on packet		basing all of these disparate digital technologies on packet
	networks.		networks.
	The goals of Deterministic Networking (DetNet) are to enable the		The goals of Deterministic Networking are to enable the migration of
	migration of applications with critical timing and reliability issues		applications with critical timing and reliability issues that
	that currently use special-purpose fieldbus technologies (HDMI,		currently use special-purpose fieldbus technologies (HDMI, CANbus,
	CANbus, ProfiBus, etc... even RS-232!) to packet technologies in		ProfiBus, etc... even RS-232!) to packet technologies in general, and
	general, and the Internet Protocol in particular, and to support both		the Internet Protocol in particular, and to support both these new
	these new applications, and existing packet network applications,		applications, and existing packet network applications, over the same
	over the same physical network.		physical network. In other words, a Deterministic Network is
			backwards compatible with - capable of transporting - statistically
			multiplexed traffic while preserving the properties of the accepted
			deterministic flows.
	Considerable experience ([ODVA]/[EIP],[AVnu],		Considerable experience ([ODVA]/[EIP],[AVnu],
	[Profinet],[HART],[IEC62439], [ISA100.11a] and [WirelessHART],		[Profinet],[HART],[IEC62439], [ISA100.11a] and [WirelessHART],
	etc...) has shown that these applications need a some or all of a		etc...) has shown that these applications need a some or all of a
	suite of features that includes:		suite of features that includes:
	1. Time synchronization of all host and network nodes (routers and/		1. Time synchronization of all host and network nodes (routers and/
	or bridges), accurate to something between 10 nanoseconds and 10		or bridges), accurate to something between 10 nanoseconds and 10
	microseconds, depending on the application.		microseconds, depending on the application.
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 12 ¶
	transmission schedule, or by a maximum bandwidth and packet		transmission schedule, or by a maximum bandwidth and packet
	size;		size;
	3. Multiple methods to schedule, shape, limit, and otherwise control		3. Multiple methods to schedule, shape, limit, and otherwise control
	the transmission of critical packets at each hop through the		the transmission of critical packets at each hop through the
	network data plane;		network data plane;
	4. Robust defenses against misbehaving hosts, routers, or bridges,		4. Robust defenses against misbehaving hosts, routers, or bridges,
	both in the data and control planes, with guarantees that a		both in the data and control planes, with guarantees that a
	critical flow within its guaranteed resources cannot be affected		critical flow within its guaranteed resources cannot be affected
	by other flows whatever the pressures on the network;		by other flows whatever the pressures on the network - more on
			the specific threats against DetNet in the DetNet Security
			Considerations [I-D.ietf-detnet-security] document;
	5. One or more methods to reserve resources in bridges and routers		5. One or more methods to reserve resources in bridges and routers
	to carry these flows.		to carry these flows.
	Time synchronization techniques need not be addressed by an IETF		Time synchronization techniques need not be addressed by an IETF
	Working Group; there are a number of standards available for this		Working Group; there are a number of standards available for this
	purpose, including IEEE 1588, IEEE 802.1AS, and more.		purpose, including IEEE 1588, IEEE 802.1AS, and more.
	The multicast, latency, loss ratio, and non-throttling needs are made		The multicast, latency, loss ratio, and non-throttling needs are made
	necessary by the algorithms employed by the applications. They are		necessary by the algorithms employed by the applications. They are
	skipping to change at page 9, line 4 ¶		skipping to change at page 9, line 11 ¶
	other flows at other times.		other flows at other times.
	The overall security of a deterministic system must cover:		The overall security of a deterministic system must cover:
	o the protection of the signaling protocol		o the protection of the signaling protocol
	o the authentication and authorization of the controlling nodes		o the authentication and authorization of the controlling nodes
	including plug-and-play participating end systems.		including plug-and-play participating end systems.
	o the identification and shaping of the flows		o the identification and shaping of the flows
	o the isolation of flows from leakage and other influences from any		o the isolation of flows from leakage and other influences from any
	activity sharing physical resources.		activity sharing physical resources.
			The specific threats against DetNet are further discussed in the
			DetNet Security Considerations [I-D.ietf-detnet-security] document.
	5. IANA Considerations		5. IANA Considerations
	This document does not require an action from IANA.		This document does not require an action from IANA.
	6. Acknowledgments		6. Acknowledgments
	The authors wish to thank Lou Berger, Stewart Bryant, Janos Farkas,		The authors wish to thank Lou Berger, Stewart Bryant, Janos Farkas,
	Andrew Malis, Jouni Korhonen, Erik Nordmark, George Swallow, Rudy		Andrew Malis, Jouni Korhonen, Erik Nordmark, George Swallow, Lou
	Klecka, Anca Zamfir, David Black, Thomas Watteyne, Shitanshu Shah,		Berger, Ines Robles, Shwetha Bhandari, Rudy Klecka, Anca Zamfir,
	Kiran Makhijani, Craig Gunther, Rodney Cummings, Wilfried Steiner,		David Black, Thomas Watteyne, Shitanshu Shah, Kiran Makhijani, Craig
	Marcel Kiessling, Karl Weber, Ethan Grossman, Patrick Wetterwald,		Gunther, Rodney Cummings, Wilfried Steiner, Marcel Kiessling, Karl
	Subha Dhesikan, Rudy Klecka and Pat Thaler for their various		Weber, Ethan Grossman, Patrick Wetterwald, Subha Dhesikan, Rudy
	contributions to this work.		Klecka and Pat Thaler for their various contributions to this work.
	7. Informative References		7. Informative References
	[AVnu] http://www.avnu.org/, "The AVnu Alliance tests and		[AVnu] http://www.avnu.org/, "The AVnu Alliance tests and
	certifies devices for interoperability, providing a simple		certifies devices for interoperability, providing a simple
	and reliable networking solution for AV network		and reliable networking solution for AV network
	implementation based on the IEEE Audio Video Bridging		implementation based on the IEEE Audio Video Bridging
	(AVB) and Time-Sensitive Networking (TSN) standards.".		(AVB) and Time-Sensitive Networking (TSN) standards.".
	[EIP] http://www.odva.org/, "EtherNet/IP provides users with the		[EIP] http://www.odva.org/, "EtherNet/IP provides users with the
	skipping to change at page 9, line 42 ¶		skipping to change at page 10, line 5 ¶
	automation applications while enabling Internet and		automation applications while enabling Internet and
	enterprise connectivity data anytime, anywhere.",		enterprise connectivity data anytime, anywhere.",
	<http://www.odva.org/Portals/0/Library/		<http://www.odva.org/Portals/0/Library/
	Publications_Numbered/		Publications_Numbered/
	PUB00138R3_CIP_Adv_Tech_Series_EtherNetIP.pdf>.		PUB00138R3_CIP_Adv_Tech_Series_EtherNetIP.pdf>.
	[HART] www.hartcomm.org, "Highway Addressable Remote Transducer,		[HART] www.hartcomm.org, "Highway Addressable Remote Transducer,
	a group of specifications for industrial process and		a group of specifications for industrial process and
	control devices administered by the HART Foundation".		control devices administered by the HART Foundation".
			[I-D.ietf-detnet-architecture]
			Finn, N., Thubert, P., Varga, B., and J. Farkas,
			"Deterministic Networking Architecture", draft-ietf-
			detnet-architecture-08 (work in progress), September 2018.
			[I-D.ietf-detnet-security]
			Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,
			J., Austad, H., Stanton, K., and N. Finn, "Deterministic
			Networking (DetNet) Security Considerations", draft-ietf-
			detnet-security-02 (work in progress), April 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.
	[IEC62439]		[IEC62439]
	IEC, "Industrial communication networks - High		IEC, "Industrial communication networks - High
	availability automation networks - Part 3: Parallel		availability automation networks - Part 3: Parallel
	Redundancy Protocol (PRP) and High-availability Seamless		Redundancy Protocol (PRP) and High-availability Seamless
	Redundancy (HSR) - IEC62439-3", 2012,		Redundancy (HSR) - IEC62439-3", 2012,
	<https://webstore.iec.ch/publication/7018>.		<https://webstore.iec.ch/publication/7018>.
	[IEEE802.1TSNTG]		[IEEE802.1TSNTG]
	IEEE Standards Association, "IEEE 802.1 Time-Sensitive		IEEE Standards Association, "IEEE 802.1 Time-Sensitive
End of changes. 14 change blocks.
	29 lines changed or deleted		52 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/