< draft-ietf-raw-use-cases-01.txt		draft-ietf-raw-use-cases-02.txt >
	RAW G. Papadopoulos		RAW G. Papadopoulos
	Internet-Draft IMT Atlantique		Internet-Draft IMT Atlantique
	Intended status: Standards Track P. Thubert		Intended status: Standards Track P. Thubert
	Expires: August 26, 2021 Cisco		Expires: January 13, 2022 Cisco
	F. Theoleyre		F. Theoleyre
	CNRS		CNRS
	CJ. Bernardos		CJ. Bernardos
	UC3M		UC3M
	February 22, 2021		July 12, 2021
	RAW use cases		RAW use cases
	draft-ietf-raw-use-cases-01		draft-ietf-raw-use-cases-02
	Abstract		Abstract
	The wireless medium presents significant specific challenges to		The wireless medium presents significant specific challenges to
	achieve properties similar to those of wired deterministic networks.		achieve properties similar to those of wired deterministic networks.
	At the same time, a number of use cases cannot be solved with wires		At the same time, a number of use cases cannot be solved with wires
	and justify the extra effort of going wireless. This document		and justify the extra effort of going wireless. This document
	presents wireless use cases demanding reliable and available		presents wireless use cases demanding reliable and available
	behavior.		behavior.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 August 26, 2021.		This Internet-Draft will expire on January 13, 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		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 37 ¶		skipping to change at page 2, line 37 ¶
	4.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 10		4.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 10
	4.2.1. Control Loops . . . . . . . . . . . . . . . . . . . . 10		4.2.1. Control Loops . . . . . . . . . . . . . . . . . . . . 10
	4.2.2. Unmeasured Data . . . . . . . . . . . . . . . . . . . 10		4.2.2. Unmeasured Data . . . . . . . . . . . . . . . . . . . 10
	4.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 11		4.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 11
	4.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 11		4.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 11
	5. Pro Audio and Video . . . . . . . . . . . . . . . . . . . . . 12		5. Pro Audio and Video . . . . . . . . . . . . . . . . . . . . . 12
	5.1. Use Case Description . . . . . . . . . . . . . . . . . . 12		5.1. Use Case Description . . . . . . . . . . . . . . . . . . 12
	5.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 12		5.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 12
	5.2.1. Uninterrupted Stream Playback . . . . . . . . . . . . 12		5.2.1. Uninterrupted Stream Playback . . . . . . . . . . . . 12
	5.2.2. Synchronized Stream Playback . . . . . . . . . . . . 12		5.2.2. Synchronized Stream Playback . . . . . . . . . . . . 12
	5.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 12		5.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 13
	5.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 13		5.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 13
	6. Wireless Gaming . . . . . . . . . . . . . . . . . . . . . . . 13		6. Wireless Gaming . . . . . . . . . . . . . . . . . . . . . . . 13
	6.1. Use Case Description . . . . . . . . . . . . . . . . . . 13		6.1. Use Case Description . . . . . . . . . . . . . . . . . . 13
	6.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 14		6.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 14
	6.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 14		6.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 14
	6.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 14		6.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 14
	7. UAV platooning and control . . . . . . . . . . . . . . . . . 15		7. UAV and V2V platooning and control . . . . . . . . . . . . . 15
	7.1. Use Case Description . . . . . . . . . . . . . . . . . . 15		7.1. Use Case Description . . . . . . . . . . . . . . . . . . 15
	7.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 15		7.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 15
	7.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 15		7.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 16
	7.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 16		7.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 16
	8. Edge Robotics control . . . . . . . . . . . . . . . . . . . . 16		8. Edge Robotics control . . . . . . . . . . . . . . . . . . . . 16
	8.1. Use Case Description . . . . . . . . . . . . . . . . . . 16		8.1. Use Case Description . . . . . . . . . . . . . . . . . . 16
	8.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 17		8.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 17
	8.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 17		8.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 17
	8.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 17		8.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 17
	9. Emergencies: Instrumented emergency vehicle . . . . . . . . . 17		9. Emergencies: Instrumented emergency vehicle . . . . . . . . . 17
	9.1. Use Case Description . . . . . . . . . . . . . . . . . . 17		9.1. Use Case Description . . . . . . . . . . . . . . . . . . 17
	9.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 18		9.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 18
	9.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 18		9.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 18
	9.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 18		9.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 18
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19		10. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 19		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
	12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19		12. Security Considerations . . . . . . . . . . . . . . . . . . . 19
	13. Informative References . . . . . . . . . . . . . . . . . . . 19		13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		14. Informative References . . . . . . . . . . . . . . . . . . . 20
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	Based on time, resource reservation, and policy enforcement by		Based on time, resource reservation, and policy enforcement by
	distributed shapers, Deterministic Networking provides the capability		distributed shapers, Deterministic Networking provides the capability
	to carry specified unicast or multicast data streams for real-time		to carry specified unicast or multicast data streams for real-time
	applications with extremely low data loss rates and bounded latency,		applications with extremely low data loss rates and bounded latency,
	so as to support time-sensitive and mission-critical applications on		so as to support time-sensitive and mission-critical applications on
	a converged enterprise infrastructure.		a converged enterprise infrastructure.
	skipping to change at page 4, line 9 ¶		skipping to change at page 4, line 9 ¶
	o frame preemption and guard time mechanisms to ensure a worst-case		o frame preemption and guard time mechanisms to ensure a worst-case
	delay, and		delay, and
	o new traffic shapers within and at the edge to protect the network.		o new traffic shapers within and at the edge to protect the network.
	Wireless operates on a shared medium, and transmissions cannot be		Wireless operates on a shared medium, and transmissions cannot be
	fully deterministic due to uncontrolled interferences, including		fully deterministic due to uncontrolled interferences, including
	self-induced multipath fading. RAW (Reliable and Available Wireless)		self-induced multipath fading. RAW (Reliable and Available Wireless)
	is an effort to provide Deterministic Networking Mechanisms on across		is an effort to provide Deterministic Networking Mechanisms on across
	a path that include a wireless physical layer. Making Wireless		a multi-hop path that include a wireless physical layer. Making
	Reliable and Available is even more challenging than it is with		Wireless Reliable and Available is even more challenging than it is
	wires, due to the numerous causes of loss in transmission that add up		with wires, due to the numerous causes of loss in transmission that
	to the congestion losses and the delays caused by overbooked shared		add up to the congestion losses and the delays caused by overbooked
	resources.		shared resources.
	The wireless and wired media are fundamentally different at the		The wireless and wired media are fundamentally different at the
	physical level, and while the generic Problem Statement [RFC8557] for		physical level, and while the generic Problem Statement [RFC8557] for
	DetNet applies to the wired as well as the wireless medium, the		DetNet applies to the wired as well as the wireless medium, the
	methods to achieve RAW necessarily differ from those used to support		methods to achieve RAW necessarily differ from those used to support
	Time-Sensitive Networking over wires.		Time-Sensitive Networking over wires.
	So far, Open Standards for Deterministic Networking have prevalently		So far, Open Standards for Deterministic Networking have prevalently
	been focused on wired media, with Audio/Video Bridging (AVB) and Time		been focused on wired media, with Audio/Video Bridging (AVB) and Time
	Sensitive Networking (TSN) at the IEEE and DetNet [RFC8655] at the		Sensitive Networking (TSN) at the IEEE and DetNet [RFC8655] at the
	skipping to change at page 4, line 45 ¶		skipping to change at page 4, line 45 ¶
	This is now changing [I-D.thubert-raw-technologies]:		This is now changing [I-D.thubert-raw-technologies]:
	o IMT-2020 has recognized Ultra-Reliable Low-Latency Communication		o IMT-2020 has recognized Ultra-Reliable Low-Latency Communication
	(URLLC) as a key functionality for the upcoming 5G.		(URLLC) as a key functionality for the upcoming 5G.
	o IEEE 802.11 has identified a set of real-applications		o IEEE 802.11 has identified a set of real-applications
	[ieee80211-rt-tig] which may use the IEEE802.11 standards. They		[ieee80211-rt-tig] which may use the IEEE802.11 standards. They
	typically emphasize strict end-to-end delay requirements.		typically emphasize strict end-to-end delay requirements.
	o The IETF has produced an IPv6 stack for IEEE Std. 802.15.4		o The IETF has produced an IPv6 stack for IEEE Std. 802.15.4
	TimeSlotted Channel Hopping (TSCH) and an architecture		TimeSlotted Channel Hopping (TSCH) and an architecture [RFC9030]
	[I-D.ietf-6tisch-architecture] that enables Reliable and Available		that enables Reliable and Available Wireless (RAW) on a shared
	Wireless (RAW) on a shared MAC.		MAC.
	This draft extends the "Deterministic Networking Use Cases" document		This draft extends the "Deterministic Networking Use Cases" document
	[RFC8578] and describes a number of additional use cases which		[RFC8578] and describes a number of additional use cases which
	require "reliable/predictable and available" flows over wireless		require "reliable/predictable and available" flows over wireless
	links and possibly complex multi-hop paths called Tracks. This is		links and possibly complex multi-hop paths called Tracks. This is
	covered mainly by the "Wireless for Industrial Applications" use		covered mainly by the "Wireless for Industrial Applications" use
	case, as the "Cellular Radio" is mostly dedicated to the (wired)		case, as the "Cellular Radio" is mostly dedicated to the (wired)
	transport part of a Radio Access Network (RAN). Whereas the		transport part of a Radio Access Network (RAN). Whereas the
	"Wireless for Industrial Applications" use case certainly covers an		"Wireless for Industrial Applications" use case certainly covers an
	area of interest for RAW, it is limited to 6TiSCH, and thus its scope		area of interest for RAW, it is limited to 6TiSCH, and thus its scope
	skipping to change at page 7, line 36 ¶		skipping to change at page 7, line 36 ¶
	Different safety levels need to be supported, from extremely safety		Different safety levels need to be supported, from extremely safety
	critical ones requiring low latency, such as a WAKE warning - a		critical ones requiring low latency, such as a WAKE warning - a
	warning that two aircraft come dangerously close to each other - and		warning that two aircraft come dangerously close to each other - and
	high resiliency, to less safety critical ones requiring low-medium		high resiliency, to less safety critical ones requiring low-medium
	latency for services such as WXGRAPH - graphical weather data.		latency for services such as WXGRAPH - graphical weather data.
	Overhead needs to be kept at a minimum since aeronautical data links		Overhead needs to be kept at a minimum since aeronautical data links
	provide comparatively small data rates in the order of kbit/s.		provide comparatively small data rates in the order of kbit/s.
	Policy needs to be supported when selecting data links. The focus of		Policy needs to be supported when selecting data links. The focus of
	RAW here should be on the selectors, responsible for the routing path		RAW here should be on the selectors, responsible for the track a
	a packet takes to reach its end destination. This would minimize the		packet takes to reach its end destination. This would minimize the
	amount of routing information that has to travel inside the network		amount of routing information that has to travel inside the network
	because of precomputed routing tables with the selector being		because of precomputed routing tables with the selector being
	responsible for choosing the most appropriate option according to		responsible for choosing the most appropriate option according to
	policy and safety.		policy and safety.
	3. Amusement Parks		3. Amusement Parks
	3.1. Use Case Description		3.1. Use Case Description
	The digitalization of Amusement Parks is expected to decrease		The digitalization of Amusement Parks is expected to decrease
	skipping to change at page 9, line 24 ¶		skipping to change at page 9, line 24 ¶
	rely on more sophisticated wearable devices such as digital glasses		rely on more sophisticated wearable devices such as digital glasses
	or Virtual Reality (VR) headsets for an immersive experience.		or Virtual Reality (VR) headsets for an immersive experience.
	3.4. Requirements for RAW		3.4. Requirements for RAW
	The network infrastructure has to support heterogeneous traffic, with		The network infrastructure has to support heterogeneous traffic, with
	very different critical requirements. Thus, flow isolation has to be		very different critical requirements. Thus, flow isolation has to be
	provided.		provided.
	We have to schedule appropriately the transmissions, even in presence		We have to schedule appropriately the transmissions, even in presence
	of mobile devices. While the [I-D.ietf-6tisch-architecture] already		of mobile devices. While the [RFC9030] already proposes an
	proposes an architecture for synchronized, IEEE Std. 802.15.4 Time-		architecture for synchronized, IEEE Std. 802.15.4 Time-Slotted
	Slotted Channel Hopping (TSCH) networks, we still need multi-		Channel Hopping (TSCH) networks, we still need multi-technology
	technology solutions, able to guarantee end-to-end requirements		solutions, able to guarantee end-to-end requirements across
	across heterogeneous technologies, with strict SLA requirements.		heterogeneous technologies, with strict SLA requirements.
	Nowadays, long-range wireless transmissions are used mostly for best-		Nowadays, long-range wireless transmissions are used mostly for best-
	effort traffic. On the contrary, [IEEE802.1TSN] is used for critical		effort traffic. On the contrary, [IEEE802.1TSN] is used for critical
	flows using Ethernet devices. However, we need an IP enabled		flows using Ethernet devices. However, we need an IP enabled
	technology to interconnect large areas, independent of the PHY and		technology to interconnect large areas, independent of the PHY and
	MAC layers.		MAC layers.
	We expect to deploy several different technologies (long vs. short		We expect to deploy several different technologies (long vs. short
	range) which have to cohabit in the same area. Thus, we need to		range) which have to cohabit in the same area. Thus, we need to
	provide layer-3 mechanisms able to exploit multiple co-interfering		provide layer-3 mechanisms able to exploit multiple co-interfering
	skipping to change at page 10, line 29 ¶		skipping to change at page 10, line 29 ¶
	final product in cans and shipping them.		final product in cans and shipping them.
	In all those cases, a packet must flow reliably between the sensor		In all those cases, a packet must flow reliably between the sensor
	and the PLC, be processed by the PLC, and sent to the actuator within		and the PLC, be processed by the PLC, and sent to the actuator within
	the control loop period. In some particular use cases that inherit		the control loop period. In some particular use cases that inherit
	from analog operations, jitter might also alter the operation of the		from analog operations, jitter might also alter the operation of the
	control loop. A rare packet loss is usually admissible, but		control loop. A rare packet loss is usually admissible, but
	typically 4 losses in a row will cause an emergency halt of the		typically 4 losses in a row will cause an emergency halt of the
	production and incur a high cost for the manufacturer.		production and incur a high cost for the manufacturer.
			Additional use cases related to Industrial applications and their RAW
			requirements can be found at [I-D.sofia-raw-industrialreq].
	4.2.2. Unmeasured Data		4.2.2. Unmeasured Data
	A secondary use case deals with monitoring and diagnostics. This so-		A secondary use case deals with monitoring and diagnostics. This so-
	called unmeasured data is essential to improve the performances of a		called unmeasured data is essential to improve the performances of a
	production line, e.g., by optimizing real-time processing or		production line, e.g., by optimizing real-time processing or
	maintenance windows using Machine Learning predictions. For the lack		maintenance windows using Machine Learning predictions. For the lack
	of wireless technologies, some specific industries such as Oil and		of wireless technologies, some specific industries such as Oil and
	Gas have been using serial cables, literally by the millions, to		Gas have been using serial cables, literally by the millions, to
	perform their process optimization over the previous decades. But		perform their process optimization over the previous decades. But
	few industries would afford the associated cost and the Holy Grail of		few industries would afford the associated cost and the Holy Grail of
	skipping to change at page 11, line 36 ¶		skipping to change at page 11, line 39 ¶
	[RFC7554] is a promising technology for that purpose, mostly if the		[RFC7554] is a promising technology for that purpose, mostly if the
	scheduled operations enable to use the same network by asynchronous		scheduled operations enable to use the same network by asynchronous
	and deterministic flows in parallel.		and deterministic flows in parallel.
	4.4. Requirements for RAW		4.4. Requirements for RAW
	As stated by the "Deterministic Networking Problem Statement"		As stated by the "Deterministic Networking Problem Statement"
	[RFC8557], a Deterministic Network is backwards compatible with		[RFC8557], a Deterministic Network is backwards compatible with
	(capable of transporting) statistically multiplexed traffic while		(capable of transporting) statistically multiplexed traffic while
	preserving the properties of the accepted deterministic flows. While		preserving the properties of the accepted deterministic flows. While
	the [I-D.ietf-6tisch-architecture] serves that requirement, the work		the [RFC9030] serves that requirement, the work at 6TiSCH was focused
	at 6TiSCH was focused on best-effort IPv6 packet flows. RAW should		on best-effort IPv6 packet flows. RAW should be able to lock so-
	be able to lock so-called hard cells for use by a centralized		called hard cells for use by a centralized scheduler, and program so-
	scheduler, and program so-called end-to-end Tracks over those cells.		called end-to-end Tracks over those cells.
	Over the course of the recent years, major Industrial Protocols,		Over the course of the recent years, major Industrial Protocols,
	e.g., [ODVA] with EtherNet/IP [EIP] and [Profinet], have been		e.g., [ODVA] with EtherNet/IP [EIP] and [Profinet], have been
	migrating towards Ethernet and IP. In order to unleash the full		migrating towards Ethernet and IP. In order to unleash the full
	power of the IP hourglass model, it should be possible to deploy any		power of the IP hourglass model, it should be possible to deploy any
	application over any network that has the physical capacity to		application over any network that has the physical capacity to
	transport the industrial flow, regardless of the MAC/PHY technology,		transport the industrial flow, regardless of the MAC/PHY technology,
	wired or wireless, and across technologies. RAW mechanisms should be		wired or wireless, and across technologies. RAW mechanisms should be
	able to setup a Track over a wireless access segment such as TSCH and		able to setup a Track over a wireless access segment such as TSCH and
	a backbone segment such as Ethernet or WI-Fi, to report a sensor data		a backbone segment such as Ethernet or WI-Fi, to report a sensor data
	skipping to change at page 13, line 18 ¶		skipping to change at page 13, line 23 ¶
	5.4. Requirements for RAW		5.4. Requirements for RAW
	The network infrastructure needs to support heterogeneous types of		The network infrastructure needs to support heterogeneous types of
	traffic (including QoS).		traffic (including QoS).
	Content delivery with bounded (lowest possible) latency.		Content delivery with bounded (lowest possible) latency.
	The deployed network topology should allow for multipath. This will		The deployed network topology should allow for multipath. This will
	enable for multiple streams to have different (and multiple) paths		enable for multiple streams to have different (and multiple) paths
	through the network to support redundancy.		(tracks) through the network to support redundancy.
	6. Wireless Gaming		6. Wireless Gaming
	6.1. Use Case Description		6.1. Use Case Description
	The gaming industry includes [IEEE80211RTA] real-time mobile gaming,		The gaming industry includes [IEEE80211RTA] real-time mobile gaming,
	wireless console gaming and cloud gaming. For RAW, wireless console		wireless console gaming and cloud gaming. For RAW, wireless console
	gaming is the most relevant one. We next summarize the three:		gaming is the most relevant one. We next summarize the three:
	o Real-time Mobile Gaming: Different from traditional games, real		o Real-time Mobile Gaming: Different from traditional games, real
	skipping to change at page 15, line 7 ¶		skipping to change at page 15, line 10 ¶
	duplicate and joint.		duplicate and joint.
	o Admission Control. Congestion is a major cause of high/variable		o Admission Control. Congestion is a major cause of high/variable
	latency and it is well known that if the traffic load exceeds the		latency and it is well known that if the traffic load exceeds the
	capability of the link, QoS will be degraded. QoS degradation		capability of the link, QoS will be degraded. QoS degradation
	maybe acceptable for many applications today, however emerging		maybe acceptable for many applications today, however emerging
	time-sensitive applications are highly susceptible to increased		time-sensitive applications are highly susceptible to increased
	latency and jitter. In order to better control QoS, it is		latency and jitter. In order to better control QoS, it is
	important to control access to the network resources.		important to control access to the network resources.
	7. UAV platooning and control		7. UAV and V2V platooning and control
	7.1. Use Case Description		7.1. Use Case Description
	Unmanned Aerial Vehicles (UAVs) are becoming very popular for many		Unmanned Aerial Vehicles (UAVs) are becoming very popular for many
	different applications, including military and civil use cases. The		different applications, including military and civil use cases. The
	term drone is commonly used to refer to a UAV.		term drone is commonly used to refer to a UAV.
	UAVs can be used to perform aerial surveillance activities, traffic		UAVs can be used to perform aerial surveillance activities, traffic
	monitoring (e.g., Spanish traffic control has recently introduced a		monitoring (e.g., Spanish traffic control has recently introduced a
	fleet of drones for quicker reactions upon traffic congestion related		fleet of drones for quicker reactions upon traffic congestion related
	events), support of emergency situations, and even transportation of		events), support of emergency situations, and even transportation of
	small goods.		small goods.
	UAVs typically have various forms of wireless connectivity:		Similarly to UAVs/drones, other time of vehicles (such as cars) can
			also travel in platoons. Most of the considerations made for UAVs in
			this section apply to V2V scenarios.
			UAVs/vehicles typically have various forms of wireless connectivity:
	o cellular: for communication with the control center, for remote		o cellular: for communication with the control center, for remote
	maneuvering as well as monitoring of the drone;		maneuvering as well as monitoring of the drone;
	o IEEE 802.11: for inter-drone communications (e.g., platooning) and		o IEEE 802.11: for inter-drone communications (e.g., platooning) and
	providing connectivity to other devices (e.g., acting as Access		providing connectivity to other devices (e.g., acting as Access
	Point).		Point).
	7.2. Specifics		7.2. Specifics
	skipping to change at page 19, line 5 ¶		skipping to change at page 19, line 8 ¶
	to continuity of operations, rapid restoral is a needed		to continuity of operations, rapid restoral is a needed
	characteristic.		characteristic.
	o End-to-end security, both authenticity and confidentiality, is		o End-to-end security, both authenticity and confidentiality, is
	required of traffic. All data needs to be authenticated; some		required of traffic. All data needs to be authenticated; some
	(such as medical) needs to be confidential.		(such as medical) needs to be confidential.
	o The radio-WAN has characteristics similar to cellphone -- the		o The radio-WAN has characteristics similar to cellphone -- the
	vehicle will travel from one radio footprint to another.		vehicle will travel from one radio footprint to another.
	10. IANA Considerations		10. Summary
			This document enumarates several use cases and applications that need
			RAW technologies, focusing on the requirements from reliability,
			availability and latency. Whereas some use cases are latency-
			critical, there are also a number of applications that are non-
			latency critical, but that do pose strict reliability and
			availability requirements. Future revisions of this document will
			include specific text devoted to highlight this non-latency critical
			requirements.
			11. IANA Considerations
	This document has no IANA actions.		This document has no IANA actions.
	11. Security Considerations		12. Security Considerations
	This document covers a number of representative applications and		This document covers a number of representative applications and
	network scenarios that are expected to make use of RAW technologies.		network scenarios that are expected to make use of RAW technologies.
	Each of the potential RAW use cases will have security considerations		Each of the potential RAW use cases will have security considerations
	from both the use-specific perspective and the RAW technology		from both the use-specific perspective and the RAW technology
	perspective. [I-D.ietf-detnet-security] provides a comprehensive		perspective. [RFC9055] provides a comprehensive discussion of
	discussion of security considerations in the context of Deterministic		security considerations in the context of Deterministic Networking,
	Networking, which are generally applicable also to RAW.		which are generally applicable also to RAW.
	12. Acknowledgments		13. Acknowledgments
	Nils Maeurer, Thomas Graeupl and Corinna Schmitt have contributed		Nils Maeurer, Thomas Graeupl and Corinna Schmitt have contributed
	significantly to this document, providing input for the Aeronautical		significantly to this document, providing input for the Aeronautical
	communications section. Rex Buddenberg has also contributed to the		communications section. Rex Buddenberg has also contributed to the
	document, providing input to the Emergency: instrumented emergency		document, providing input to the Emergency: instrumented emergency
	vehicle section.		vehicle section.
	The authors would like to thank Toerless Eckert, Xavi Vilajosana		The authors would like to thank Toerless Eckert, Xavi Vilajosana
	Guillen and Rute Sofia for their valuable comments on previous		Guillen and Rute Sofia for their valuable comments on previous
	versions of this document.		versions of this document.
	The work of Carlos J. Bernardos in this draft has been partially		The work of Carlos J. Bernardos in this draft has been partially
	supported by the H2020 5Growth (Grant 856709) and 5G-DIVE projects		supported by the H2020 5Growth (Grant 856709) and 5G-DIVE projects
	(Grant 859881).		(Grant 859881).
	13. Informative References		14. Informative References
	[ACI19] Airports Council International (ACI), "Annual World		[ACI19] Airports Council International (ACI), "Annual World
	Aitport Traffic Report 2019", November 2019,		Aitport Traffic Report 2019", November 2019,
	<https://store.aci.aero/product/annual-world-airport-		<https://store.aci.aero/product/annual-world-airport-
	traffic-report-2019/>.		traffic-report-2019/>.
	[disney-VIP]		[disney-VIP]
	Wired, "Disney's $1 Billion Bet on a Magical Wristband",		Wired, "Disney's $1 Billion Bet on a Magical Wristband",
	March 2015,		March 2015,
	<https://www.wired.com/2015/03/disney-magicband/>.		<https://www.wired.com/2015/03/disney-magicband/>.
	skipping to change at page 20, line 18 ¶		skipping to change at page 20, line 30 ¶
	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>.
	[FAA20] U.S. Department of Transportation Federal Aviation		[FAA20] U.S. Department of Transportation Federal Aviation
	Administration (FAA), "Next Generation Air Transportation		Administration (FAA), "Next Generation Air Transportation
	System", 2019, <https://www.faa.gov/nextgen/ >.		System", 2019, <https://www.faa.gov/nextgen/ >.
	[I-D.ietf-6tisch-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-30 (work
	in progress), November 2020.
	[I-D.ietf-detnet-security]
	Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
	Networking (DetNet) Security Considerations", draft-ietf-
	detnet-security-13 (work in progress), December 2020.
	[I-D.ietf-raw-ldacs]		[I-D.ietf-raw-ldacs]
	Maeurer, N., Graeupl, T., and C. Schmitt, "L-band Digital		Maeurer, N., Graeupl, T., and C. Schmitt, "L-band Digital
	Aeronautical Communications System (LDACS)", draft-ietf-		Aeronautical Communications System (LDACS)", draft-ietf-
	raw-ldacs-06 (work in progress), January 2021.		raw-ldacs-07 (work in progress), February 2021.
			[I-D.sofia-raw-industrialreq]
			Sofia, R. C., Kovatsch, M., and P. M. Mendes,
			"Requirements for Reliable Wireless Industrial Services",
			draft-sofia-raw-industrialreq-00 (work in progress), March
			2021.
	[I-D.thubert-raw-technologies]		[I-D.thubert-raw-technologies]
	Thubert, P., Cavalcanti, D., Vilajosana, X., Schmitt, C.,		Thubert, P., Cavalcanti, D., Vilajosana, X., Schmitt, C.,
	and J. Farkas, "Reliable and Available Wireless		and J. Farkas, "Reliable and Available Wireless
	Technologies", draft-thubert-raw-technologies-05 (work in		Technologies", draft-thubert-raw-technologies-05 (work in
	progress), May 2020.		progress), May 2020.
	[IAC20] Iacus, S., Natale, F., Santamaria, C., Spyratos, S., and		[IAC20] Iacus, S., Natale, F., Santamaria, C., Spyratos, S., and
	V. Michele, "Estimating and projecting air passenger		V. Michele, "Estimating and projecting air passenger
	traffic during the COVID-19 coronavirus outbreak and its		traffic during the COVID-19 coronavirus outbreak and its
	skipping to change at page 22, line 24 ¶		skipping to change at page 22, line 29 ¶
	[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",		[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",
	RFC 8578, DOI 10.17487/RFC8578, May 2019,		RFC 8578, DOI 10.17487/RFC8578, May 2019,
	<https://www.rfc-editor.org/info/rfc8578>.		<https://www.rfc-editor.org/info/rfc8578>.
	[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>.
			[RFC9030] Thubert, P., Ed., "An Architecture for IPv6 over the Time-
			Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH)",
			RFC 9030, DOI 10.17487/RFC9030, May 2021,
			<https://www.rfc-editor.org/info/rfc9030>.
			[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>.
	[robots] Kober, J., Glisson, M., and M. Mistry, "Playing catch and		[robots] Kober, J., Glisson, M., and M. Mistry, "Playing catch and
	juggling with a humanoid robot.", 2012,		juggling with a humanoid robot.", 2012,
	<https://doi.org/10.1109/HUMANOIDS.2012.6651623>.		<https://doi.org/10.1109/HUMANOIDS.2012.6651623>.
	[square-peg]		[square-peg]
	Martinez, B., Cano, C., and X. Vilajosana, "A Square Peg		Martinez, B., Cano, C., and X. Vilajosana, "A Square Peg
	in a Round Hole: The Complex Path for Wireless in the		in a Round Hole: The Complex Path for Wireless in the
	Manufacturing Industry", 2019,		Manufacturing Industry", 2019,
	<https://ieeexplore.ieee.org/document/8703476>.		<https://ieeexplore.ieee.org/document/8703476>.
End of changes. 25 change blocks.
	52 lines changed or deleted		77 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/