< draft-bernardos-raw-use-cases-03.txt   draft-bernardos-raw-use-cases-04.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: September 9, 2020 Cisco Expires: January 12, 2021 Cisco
F. Theoleyre F. Theoleyre
CNRS CNRS
CJ. Bernardos CJ. Bernardos
UC3M UC3M
March 8, 2020 July 11, 2020
RAW use cases RAW use cases
draft-bernardos-raw-use-cases-03 draft-bernardos-raw-use-cases-04
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 September 9, 2020. This Internet-Draft will expire on January 12, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 23 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Aeronautical Communications . . . . . . . . . . . . . . . . . 5 2. Aeronautical Communications . . . . . . . . . . . . . . . . . 5
2.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 5 2.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 5
2.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Challenges . . . . . . . . . . . . . . . . . . . . . . . 6 2.3. Challenges . . . . . . . . . . . . . . . . . . . . . . . 6
2.4. The Need for Wireless . . . . . . . . . . . . . . . . . . 7 2.4. The Need for Wireless . . . . . . . . . . . . . . . . . . 7
2.5. Requirements for RAW . . . . . . . . . . . . . . . . . . 7 2.5. Requirements for RAW . . . . . . . . . . . . . . . . . . 7
3. Amusement Parks . . . . . . . . . . . . . . . . . . . . . . . 7 3. Amusement Parks . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Use Case Description . . . . . . . . . . . . . . . . . . 7 3.1. Use Case Description . . . . . . . . . . . . . . . . . . 7
3.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 9 3.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 8
3.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 9 3.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 9
4. Wireless for Industrial Applications . . . . . . . . . . . . 10 4. Wireless for Industrial Applications . . . . . . . . . . . . 9
4.1. Use Case Description . . . . . . . . . . . . . . . . . . 10 4.1. Use Case Description . . . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . 13 5.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 12
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 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 . . . . . . . . . . . . . . . . . . 16 7.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 15
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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 9. Emergencies: Instrumented emergency vehicle . . . . . . . . . 17
10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9.1. Use Case Description . . . . . . . . . . . . . . . . . . 17
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 9.2. Specifics . . . . . . . . . . . . . . . . . . . . . . . . 18
12. Informative References . . . . . . . . . . . . . . . . . . . 18 9.3. The Need for Wireless . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 9.4. Requirements for RAW . . . . . . . . . . . . . . . . . . 18
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
11. Security Considerations . . . . . . . . . . . . . . . . . . . 19
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
13. Informative References . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
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 3, line 50 skipping to change at page 4, line 8
o multi-technology path with co-channel interference minimization, o multi-technology path with co-channel interference minimization,
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 on across a path is an effort to provide Deterministic Networking Mechanisms on across
that include a wireless physical layer. Making Wireless Reliable and a path that include a wireless physical layer. Making Wireless
Available is even more challenging than it is with wires, due to the Reliable and Available is even more challenging than it is with
numerous causes of loss in transmission that add up to the congestion wires, due to the numerous causes of loss in transmission that add up
losses and the delays caused by overbooked shared resources. to the congestion losses and the delays caused by overbooked 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 7, line 48 skipping to change at page 7, line 48
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
significantly the cost for maintaining the attractions. By significantly the cost for maintaining the attractions. Such
monitoring in real-time the machines, predictive maintenance will deployment is a mix between industrial automation (aka. Smart
help to reduce the repairing cost as well as the downtime. Besides, Factories) and multimedia entertainment applications.
the attractions may use wireless transmissions to interconnect
sensors and actuators, to privilege reconfigurability, and
standardization.
Attractions may rely on a large set of sensors and actuators, which Attractions may rely on a large set of sensors and actuators, which
react in real time. Typical applications comprise: react in real time. Typical applications comprise:
o Emergency: safety has to be preserved, and must stop the o Emergency: safety has to be preserved, and must stop the
attraction when a failure is detected. attraction when a failure is detected.
o Video: augmented and virtual realities are integrated in the o Video: augmented and virtual realities are integrated in the
attraction. Wearable devices (e.g., glasses, virtual reality attraction. Wearable mobile devices (e.g., glasses, virtual
headset) need to offload one part of the processing tasks. reality headset) need to offload one part of the processing tasks.
o Real-time interactions: visitors may interact with an attraction, o Real-time interactions: visitors may interact with an attraction,
like in a real-time video game. The visitors may virtually like in a real-time video game. The visitors may virtually
interact with their environment, triggering actions in the real interact with their environment, triggering actions in the real
world (through actuators) [robots]. world (through actuators) [robots].
o Geolocation: visitors are tracked with a personal wireless tag so o Geolocation: visitors are tracked with a personal wireless tag so
that their user experience is improved. that their user experience is improved.
o Predictive maintenance: statistics are collected to predict the o Predictive maintenance: statistics are collected to predict the
skipping to change at page 8, line 40 skipping to change at page 8, line 38
Amusement parks comprise a variable number of attractions, mostly Amusement parks comprise a variable number of attractions, mostly
outdoor, over a large geographical area. The IT infrastructure is outdoor, over a large geographical area. The IT infrastructure is
typically multi-scale: typically multi-scale:
o Local area: the sensors and actuators controlling the attractions o Local area: the sensors and actuators controlling the attractions
are co-located. Control loops trigger only local traffic, with a are co-located. Control loops trigger only local traffic, with a
small end-to-end delay, typically inferior than 10 milliseconds, small end-to-end delay, typically inferior than 10 milliseconds,
like classical industrial systems [ieee80211-rt-tig]. like classical industrial systems [ieee80211-rt-tig].
o Wearable devices are free to move in the park. They exchange o Wearable mobile devices are free to move in the park. They
traffic locally (identification, personalization, multimedia) or exchange traffic locally (identification, personalization,
globally (billing, child tracking). multimedia) or globally (billing, child tracking).
o Computationally intensive applications offload some tasks to a o Computationally intensive applications offload some tasks. Edge
cloud, and data analytics rely on a centralized infrastructure computing seems an efficient way to implement real-time
(predictive maintenance, marketing). applications with offloading. Some non time-critical tasks may
rather use the cloud (predictive maintenance, marketing).
3.3. The Need for Wireless 3.3. The Need for Wireless
Amusement parks cover large areas and a global interconnection would Amusement parks cover large areas and a global interconnection would
require a huge length of cables. Wireless also increases the require a huge length of cables. Wireless also increases the
reconfigurability, enabling to update cheaply the attractions. The reconfigurability, enabling to update cheaply the attractions. The
frequent renewal helps to increase customer loyalty. frequent renewal helps to increase customer loyalty.
Some parts of the attraction are mobile, e.g., trucks of a roller- Some parts of the attraction are mobile, e.g., trucks of a roller-
coaster, robots. Since cables are prone to frequent failures in this coaster, robots. Since cables are prone to frequent failures in this
skipping to change at page 9, line 33 skipping to change at page 9, line 26
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 [I-D.ietf-6tisch-architecture] already
proposes an architecture for synchronized, IEEE Std. 802.15.4 Time- proposes an architecture for synchronized, IEEE Std. 802.15.4 Time-
Slotted Channel Hopping (TSCH) networks, 6TiSCH does not address Slotted Channel Hopping (TSCH) networks, we still need multi-
real-time IPv6 flows. RAW might provide mechanisms helping to technology solutions, able to guarantee end-to-end requirements
automatically adapt the network (i.e., schedule appropriately the across heterogeneous technologies, with strict SLA requirements.
transmissions, across heterogeneous technologies, with strict SLA
requirements).
Nowadays, long-range wireless transmissions are used for best-effort Nowadays, long-range wireless transmissions are used mostly for best-
traffic, and [IEEE802.1TSN] is used for critical flows using Ethernet effort traffic. On the contrary, [IEEE802.1TSN] is used for critical
devices. However, we need an IP enabled technology to interconnect flows using Ethernet devices. However, we need an IP enabled
large areas, independent of the PHY and MAC layer to maximize the technology to interconnect large areas, independent of the PHY and
compliancy. 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
schedule appropriately the transmissions to limit the co-technology provide layer-3 mechanisms able to exploit multiple co-interfering
interference, so that an end-to-end delay across multiple technologies.
technologies can be guaranteed. It is needed to understand which
technologies RAW will cover and how they can be used cohabitating in
the same area.
4. Wireless for Industrial Applications 4. Wireless for Industrial Applications
4.1. Use Case Description 4.1. Use Case Description
A major use case for networking in Industrial environments is the A major use case for networking in Industrial environments is the
control networks where periodic control loops operate between a control networks where periodic control loops operate between a
sensor that measures a physical property such as the temperature of a sensor that measures a physical property such as the temperature of a
fluid, a Programmable Logic Controller (PLC) that decides an action fluid, a Programmable Logic Controller (PLC) that decides an action
such as warm up the mix, and an actuator that performs the required such as warm up the mix, and an actuator that performs the required
skipping to change at page 12, line 14 skipping to change at page 11, line 50
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
or a critical monitoring within a bounded latency. or a critical monitoring within a bounded latency. It is also
important to ensure that RAW solutions are interoperable with
existing wireless solutions in place, and with legacy equipment which
capabilities can be extended using retrofitting. Maintanability, as
a broader concept than reliability is also important in industrial
scenarios [square-peg].
5. Pro Audio and Video 5. Pro Audio and Video
5.1. Use Case Description 5.1. Use Case Description
Many devices support audio and video streaming by employing 802.11 Many devices support audio and video streaming by employing 802.11
wireless LAN. Some of these applications require low latency wireless LAN. Some of these applications require low latency
capability. For instance, when the application provides interactive capability. For instance, when the application provides interactive
play, or when the audio takes plays in real time (i.e. live) for play, or when the audio takes plays in real time (i.e. live) for
public addresses in train stations or in theme parks. public addresses in train stations or in theme parks.
skipping to change at page 17, line 34 skipping to change at page 17, line 31
8.4. Requirements for RAW 8.4. Requirements for RAW
The network infrastructure needs to support heterogeneous types of The network infrastructure needs to support heterogeneous types of
traffic, from robot control to video streaming. traffic, from robot control to video streaming.
When a given service is decomposed into functions -- hosted at When a given service is decomposed into functions -- hosted at
different robots -- chained, each link connecting two given functions different robots -- chained, each link connecting two given functions
would have a well-defined set of requirements (latency, bandwidth and would have a well-defined set of requirements (latency, bandwidth and
jitter) that have to be met. jitter) that have to be met.
9. IANA Considerations 9. Emergencies: Instrumented emergency vehicle
N/A. 9.1. Use Case Description
10. Security Considerations An instrumented ambulance would be one that has a LAN to which are
connected these end systems:
N/A. o vital signs sensors attached to the casualty in the ambulance.
Relay medical data to hospital emergency room,
11. Acknowledgments o radionavigation sensor to relay position data to various
destinations including dispatcher,
o voice communication for ambulance attendant (e.g. consult with ER
doctor),
o voice communication between driver and dispatcher,
o etc.
The LAN needs to be routed through radio-WANs to complete the
internetwork linkage.
9.2. Specifics
What we have today is multiple communications systems to reach the
vehicle:
o A dispatching system,
o a cellphone for the attendant,
o a special purpose telemetering system for medical data,
o etc.
This redundancy of systems, because of its stovepiping, does not
contribute to availability as a whole.
Most of the scenarios involving the use of an instrumented ambulance
are composed of many different flows, each of them with slightly
different requirements in terms of reliability and latency.
Destinations might be either at the ambulance itself (local traffic),
at a near edge cloud or at the general Internet/cloud.
9.3. The Need for Wireless
Local traffic between the first responders/ambulance staff and the
ambulance equipment cannot be doine via wireled connectivity as the
responders perform initial treatment outside of the ambulance. The
communications from the ambulance to external services has to be
wireless as well.
9.4. Requirements for RAW
We can derive some pertinent requirements from this scenario:
o High availability of the internetwork is required.
o The internetwork needs to operate in damaged state (e.g. during an
earthquake aftermath, heavy weather, wildfire, etc.). In addition
to continuity of operations, rapid restoral is a needed
characteristic.
o End-to-end security, both authenticity and confidentiality, is
required of traffic. All data needs to be authenticated; some
(such as medical) needs to be confidential.
o The radio-WAN has characteristics similar to cellphone -- the
vehicle will travel from one radio footprint to another.
10. IANA Considerations
This document has no IANA actions.
11. Security Considerations
This document covers a number of representative applications and
network scenarios that are expected to make use of RAW technologies.
Each of the potential RAW use cases will have security considerations
from both the use-specific perspective and the RAW technology
perspective. [I-D.ietf-detnet-security] provides a comprehensive
discussion of security considerations in the context of Deterministic
Networking, which are generally applicable also to RAW.
12. 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. communications section. Rex Buddenberg has also contributed to the
document, providing input to the Emergency: instrumented emergency
vehicle section.
The authors would like to thank Toerless Eckert, Xavi Vilajosana
Guillen and Rute Sofia for their valuable comments on previous
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).
12. Informative References 13. Informative References
[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/>.
[EIP] http://www.odva.org/, "EtherNet/IP provides users with the [EIP] http://www.odva.org/, "EtherNet/IP provides users with the
network tools to deploy standard Ethernet technology (IEEE network tools to deploy standard Ethernet technology (IEEE
802.3 combined with the TCP/IP Suite) for industrial 802.3 combined with the TCP/IP Suite) for industrial
automation applications while enabling Internet and automation applications while enabling Internet and
skipping to change at page 18, line 35 skipping to change at page 20, line 19
[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] [I-D.ietf-6tisch-architecture]
Thubert, P., "An Architecture for IPv6 over the TSCH mode Thubert, P., "An Architecture for IPv6 over the TSCH mode
of IEEE 802.15.4", draft-ietf-6tisch-architecture-28 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-28 (work
in progress), October 2019. in progress), October 2019.
[I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet-
security-10 (work in progress), May 2020.
[I-D.maeurer-raw-ldacs] [I-D.maeurer-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- Aeronautical Communications System (LDACS)", draft-
maeurer-raw-ldacs-01 (work in progress), March 2020. maeurer-raw-ldacs-04 (work in progress), July 2020.
[I-D.thubert-raw-technologies] [I-D.thubert-raw-technologies]
Thubert, P., Cavalcanti, D., Vilajosana, X., and C. Thubert, P., Cavalcanti, D., Vilajosana, X., Schmitt, C.,
Schmitt, "Reliable and Available Wireless Technologies", and J. Farkas, "Reliable and Available Wireless
draft-thubert-raw-technologies-04 (work in progress), Technologies", draft-thubert-raw-technologies-05 (work in
January 2020. progress), May 2020.
[ICAO18] International Civil Aviation Organization (ICAO), "L-Band [ICAO18] International Civil Aviation Organization (ICAO), "L-Band
Digital Aeronautical Communication System (LDACS)", Digital Aeronautical Communication System (LDACS)",
International Standards and Recommended Practices Annex 10 International Standards and Recommended Practices Annex 10
- Aeronautical Telecommunications, Vol. III - - Aeronautical Telecommunications, Vol. III -
Communication Systems , 2018. Communication Systems , 2018.
[IEEE802.1TSN] [IEEE802.1TSN]
IEEE standard for Information Technology, "IEEE IEEE standard for Information Technology, "IEEE
802.1AS-2011 - IEEE Standard for Local and Metropolitan 802.1AS-2011 - IEEE Standard for Local and Metropolitan
skipping to change at page 20, line 18 skipping to change at page 22, line 9
[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>.
[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]
Martinez, B., Cano, C., and X. Vilajosana, "A Square Peg
in a Round Hole: The Complex Path for Wireless in the
Manufacturing Industry", 2019,
<https://ieeexplore.ieee.org/document/8703476>.
Authors' Addresses Authors' Addresses
Georgios Z. Papadopoulos Georgios Z. Papadopoulos
IMT Atlantique IMT Atlantique
Office B00 - 114A Office B00 - 114A
2 Rue de la Chataigneraie 2 Rue de la Chataigneraie
Cesson-Sevigne - Rennes 35510 Cesson-Sevigne - Rennes 35510
FRANCE FRANCE
Phone: +33 299 12 70 04 Phone: +33 299 12 70 04
 End of changes. 29 change blocks. 
61 lines changed or deleted 159 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/