< draft-ietf-raw-technologies-00.txt   draft-ietf-raw-technologies-01.txt >
RAW P. Thubert, Ed. RAW P. Thubert, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational D. Cavalcanti Intended status: Informational D. Cavalcanti
Expires: 23 April 2021 Intel Expires: 23 August 2021 Intel
X. Vilajosana X. Vilajosana
Universitat Oberta de Catalunya Universitat Oberta de Catalunya
C. Schmitt C. Schmitt
Research Institute CODE, UniBwM Research Institute CODE, UniBwM
J. Farkas J. Farkas
Ericsson Ericsson
20 October 2020 19 February 2021
Reliable and Available Wireless Technologies Reliable and Available Wireless Technologies
draft-ietf-raw-technologies-00 draft-ietf-raw-technologies-01
Abstract Abstract
This document presents a series of recent technologies that are This document presents a series of recent technologies that are
capable of time synchronization and scheduling of transmission, capable of time synchronization and scheduling of transmission,
making them suitable to carry time-sensitive flows with high making them suitable to carry time-sensitive flows with high
reliability and availbility. reliability and availability.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 23 April 2021. This Internet-Draft will expire on 23 August 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. On Scheduling . . . . . . . . . . . . . . . . . . . . . . . . 4 3. On Scheduling . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Benefits of Scheduling on Wires . . . . . . . . . . . . . 4 3.1. Benefits of Scheduling on Wires . . . . . . . . . . . . . 5
3.2. Benefits of Scheduling on Wireless . . . . . . . . . . . 5 3.2. Benefits of Scheduling on Wireless . . . . . . . . . . . 5
4. IEEE 802.11 . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. IEEE 802.11 . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Provenance and Documents . . . . . . . . . . . . . . . . 6 4.1. Provenance and Documents . . . . . . . . . . . . . . . . 6
4.2. 802.11ax High Efficiency (HE) . . . . . . . . . . . . . . 8 4.2. 802.11ax High Efficiency (HE) . . . . . . . . . . . . . . 8
4.2.1. General Characteristics . . . . . . . . . . . . . . . 8 4.2.1. General Characteristics . . . . . . . . . . . . . . . 8
4.2.2. Applicability to deterministic flows . . . . . . . . 9 4.2.2. Applicability to deterministic flows . . . . . . . . 9
4.3. 802.11be Extreme High Throughput (EHT) . . . . . . . . . 10 4.3. 802.11be Extreme High Throughput (EHT) . . . . . . . . . 11
4.3.1. General Characteristics . . . . . . . . . . . . . . . 10 4.3.1. General Characteristics . . . . . . . . . . . . . . . 11
4.3.2. Applicability to deterministic flows . . . . . . . . 11 4.3.2. Applicability to deterministic flows . . . . . . . . 11
4.4. 802.11ad and 802.11ay (mmWave operation) . . . . . . . . 12 4.4. 802.11ad and 802.11ay (mmWave operation) . . . . . . . . 12
4.4.1. General Characteristics . . . . . . . . . . . . . . . 12 4.4.1. General Characteristics . . . . . . . . . . . . . . . 13
4.4.2. Applicability to deterministic flows . . . . . . . . 13 4.4.2. Applicability to deterministic flows . . . . . . . . 13
5. IEEE 802.15.4 . . . . . . . . . . . . . . . . . . . . . . . . 13 5. IEEE 802.15.4 . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Provenance and Documents . . . . . . . . . . . . . . . . 13 5.1. Provenance and Documents . . . . . . . . . . . . . . . . 13
5.2. TimeSlotted Channel Hopping . . . . . . . . . . . . . . . 15 5.2. TimeSlotted Channel Hopping . . . . . . . . . . . . . . . 15
5.2.1. General Characteristics . . . . . . . . . . . . . . . 15 5.2.1. General Characteristics . . . . . . . . . . . . . . . 15
5.2.2. Applicability to Deterministic Flows . . . . . . . . 16 5.2.2. Applicability to Deterministic Flows . . . . . . . . 17
6. 5G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6. 5G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.1. Provenance and Documents . . . . . . . . . . . . . . . . 30 6.1. Provenance and Documents . . . . . . . . . . . . . . . . 31
6.2. General Characteristics . . . . . . . . . . . . . . . . . 32 6.2. General Characteristics . . . . . . . . . . . . . . . . . 33
6.3. Deployment and Spectrum . . . . . . . . . . . . . . . . . 33 6.3. Deployment and Spectrum . . . . . . . . . . . . . . . . . 34
6.4. Applicability to Deterministic Flows . . . . . . . . . . 34 6.4. Applicability to Deterministic Flows . . . . . . . . . . 35
6.4.1. System Architecture . . . . . . . . . . . . . . . . . 34 6.4.1. System Architecture . . . . . . . . . . . . . . . . . 35
6.4.2. Overview of The Radio Protocol Stack . . . . . . . . 36 6.4.2. Overview of The Radio Protocol Stack . . . . . . . . 37
6.4.3. Radio (PHY) . . . . . . . . . . . . . . . . . . . . . 37 6.4.3. Radio (PHY) . . . . . . . . . . . . . . . . . . . . . 38
6.4.4. Scheduling and QoS (MAC) . . . . . . . . . . . . . . 39 6.4.4. Scheduling and QoS (MAC) . . . . . . . . . . . . . . 40
6.4.5. Time-Sensitive Networking (TSN) Integration . . . . . 41 6.4.5. Time-Sensitive Networking (TSN) Integration . . . . . 42
6.5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 44 6.5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 45
7. L-band Digital Aeronautical Communications System . . . . . . 45 7. L-band Digital Aeronautical Communications System . . . . . . 46
7.1. Provenance and Documents . . . . . . . . . . . . . . . . 45 7.1. Provenance and Documents . . . . . . . . . . . . . . . . 47
7.2. General Characteristics . . . . . . . . . . . . . . . . . 46 7.2. General Characteristics . . . . . . . . . . . . . . . . . 48
7.3. Applicability to Deterministic Flows . . . . . . . . . . 47 7.3. Deployment and Spectrum . . . . . . . . . . . . . . . . . 49
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 7.4. Applicability to Deterministic Flows . . . . . . . . . . 49
9. Security Considerations . . . . . . . . . . . . . . . . . . . 48 7.4.1. System Architecture . . . . . . . . . . . . . . . . . 50
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 48 7.4.2. Overview of The Radio Protocol Stack . . . . . . . . 50
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49 7.4.3. Radio (PHY) . . . . . . . . . . . . . . . . . . . . . 51
12. Normative References . . . . . . . . . . . . . . . . . . . . 49 7.4.4. Scheduling, Frame Structure and QoS (MAC) . . . . . . 52
13. Informative References . . . . . . . . . . . . . . . . . . . 49 7.5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
9. Security Considerations . . . . . . . . . . . . . . . . . . . 55
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 55
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55
12. Normative References . . . . . . . . . . . . . . . . . . . . 55
13. Informative References . . . . . . . . . . . . . . . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64
1. Introduction 1. Introduction
When used in math or philosophy, the term "deterministic" generally When used in math or philosophy, the term "deterministic" generally
refers to a perfection where all aspect are understood and refers to a perfection where all aspect are understood and
predictable. A perfectly Deterministic Network would ensure that predictable. A perfectly Deterministic Network would ensure that
every packet reach its destination following a predetermined path every packet reach its destination following a predetermined path
along a predefined schedule to be delivered at the exact due time. along a predefined schedule to be delivered at the exact due time.
In a real and imperfect world, a Deterministic Network must highly In a real and imperfect world, a Deterministic Network must highly
predictable, which is a combination of reliability and availability. predictable, which is a combination of reliability and availability.
skipping to change at page 45, line 51 skipping to change at page 47, line 17
The development of LDACS has already made substantial progress in the The development of LDACS has already made substantial progress in the
Single European Sky ATM Research (SESAR) framework, and is currently Single European Sky ATM Research (SESAR) framework, and is currently
being continued in the follow-up program, SESAR2020 [RIH18]. A key being continued in the follow-up program, SESAR2020 [RIH18]. A key
objective of the SESAR activities is to develop, implement and objective of the SESAR activities is to develop, implement and
validate a modern aeronautical data link able to evolve with aviation validate a modern aeronautical data link able to evolve with aviation
needs over long-term. To this end, an LDACS specification has been needs over long-term. To this end, an LDACS specification has been
produced [GRA19] and is continuously updated; transmitter produced [GRA19] and is continuously updated; transmitter
demonstrators were developed to test the spectrum compatibility of demonstrators were developed to test the spectrum compatibility of
LDACS with legacy systems operating in the L-band [SAJ14]; and the LDACS with legacy systems operating in the L-band [SAJ14]; and the
overall system performance was analyzed by computer simulations, overall system performance was analyzed by computer simulations,
indicating that LDACS can fulfil the identified requirements [GRA11]. indicating that LDACS can fulfill the identified requirements
[GRA11].
LDACS standardization within the framework of the International Civil LDACS standardization within the framework of the International Civil
Aviation Organization (ICAO) started in December 2016. The ICAO Aviation Organization (ICAO) started in December 2016. The ICAO
standardization group has produced an initial Standards and standardization group has produced an initial Standards and
Recommended Practices (SARPs) document [ICAO18]. The SARPs document Recommended Practices (SARPs) document [ICAO18]. The SARPs document
defines the general characteristics of LDACS. The ICAO defines the general characteristics of LDACS. The ICAO
standardization group plans to produce an ICAO technical manual - the standardization group plans to produce an ICAO technical manual - the
ICAO equivalent to a technical standard - within the next years. ICAO equivalent to a technical standard - within the next years.
Generally, the group is open to input from all sources and develops Generally, the group is open to input from all sources and develops
LDACS in the open. LDACS in the open.
skipping to change at page 46, line 40 skipping to change at page 48, line 14
7.2. General Characteristics 7.2. General Characteristics
LDACS will become one of several wireless access networks connecting LDACS will become one of several wireless access networks connecting
aircraft to the Aeronautical Telecommunications Network (ATN). The aircraft to the Aeronautical Telecommunications Network (ATN). The
LDACS access network contains several ground stations, each of them LDACS access network contains several ground stations, each of them
providing one LDACS radio cell. The LDACS air interface is a providing one LDACS radio cell. The LDACS air interface is a
cellular data link with a star-topology connecting aircraft to cellular data link with a star-topology connecting aircraft to
ground-stations with a full duplex radio link. Each ground-station ground-stations with a full duplex radio link. Each ground-station
is the centralized instance controlling all air-ground communications is the centralized instance controlling all air-ground communications
within its radio cell. A ground-station supports up to 512 aircraft. within its radio cell.
The LDACS air interface protocol stack defines two layers, the The user data rate of LDACS is 315 kbit/s to 1428 kbit/s on the
physical layer and the data link layer. forward link, and 294 kbit/s to 1390 kbit/s on the reverse link,
depending on coding and modulation. Due to strong interference from
legacy systems in the L-band, the most robust coding and modulation
SHOULD be expected for initial deployment i.e. 315/294 kbit/s on the
forward/reverse link, respectively.
In addition to the communications capability, LDACS also offers a
navigation capability. Ranging data, similar to DME (Distance
Measuring Equipment), is extracted from the LDACS communication links
between aircraft and LDACS ground stations. This results in LDACS
providing an APNT (Alternative Position, Navigation and Timing)
capability to supplement the existing on-board GNSS (Global
Navigation Satellite System) without the need for additional
bandwidth. Operationally, there will be no difference for pilots
whether the navigation data are provided by LDACS or DME. This
capability was flight tested and proven during the MICONAV flight
trials in 2019 [BAT19].
In previous works and during the MICONAV flight campaign in 2019, it
was also shown, that LDACS can be used for surveillance capability.
Filip et al. [FIL19] shown passive radar capabilities of LDACS and
Automatic Dependence Surveillance - Contract (ADS-C) was demonstrated
via LDACS during the flight campaign 2019 [SCH19].
Since LDACS has been mainly designed for air traffic management
communication it supports mutual entity authentication, integrity and
confidentiality capabilities of user data messages and some control
channel protection capabilities [MAE18], [MAE191], [MAE192], [MAE20].
Overall this makes LDACS the world's first truly integrated CNS
system and is the worldwide most mature, secure, terrestrial long-
range CNS technology for civil aviation.
7.3. Deployment and Spectrum
LDACS has its origin in merging parts of the B-VHF [BRA06], B-AMC
[SCH08], TIA-902 (P34) [HAI09], and WiMAX IEEE 802.16e technologies
[EHA11]. In 2007 the spectrum for LDACS was allocated at the World
Radio Conference (WRC).
It was decided to allocate the spectrum next to Distance Measuring
Equipment (DME), resulting in an in-lay approach between the DME
channels for LDAC [SCH14].
LDACS is currently being standardized by ICAO and several roll-out
strategies are discussed:
The LDACS data link provides enhanced capabilities to existing
Aeronautical communications infrastructure enabling them to better
support user needs and new applications. The deployment scalability
of LDACS allows its implementation to start in areas where most
needed to Improve immediately the performance of already fielded
infrastructure. Later the deployment is extended based on
operational demand. An attractive scenario for upgrading the
existing VHF communication systems by adding an additional LDACS data
link is described below.
When considering the current VDL Mode 2 infrastructure and user base,
a very attractive win-win situation comes about, when the
technological advantages of LDACS are combined with the existing VDL
mode 2 infrastructure. LDACS provides at least 50 time more capacity
than VDL Mode 2 and is a natural enhancement to the existing VDL Mode
2 business model. The advantage of this approach is that the VDL
Mode 2 infrastructure can be fully reused. Beyond that, it opens the
way for further enhancements which can increase business efficiency
and minimize investment risk. [ICAO19]
7.4. Applicability to Deterministic Flows
As LDACS is a ground-based digital communications system for flight
guidance and communications related to safety and regularity of
flight, time-bounded deterministic arrival times for safety critical
messages are a key feature for its successful deployment and roll-
out.
7.4.1. System Architecture
Up to 512 Aircraft Station (AS) communicate to an LDACS Ground
Station (GS) in the Reverse Link (RL). GS communicate to AS in the
Forward Link (FL). Via an Access-Router (AC-R) GSs connect the LDACS
sub-network to the global Aeronautical Telecommunications Network
(ATN) to which the corresponding Air Traffic Services (ATS) and
Aeronautical Operational Control (AOC) end systems are attached.
7.4.2. Overview of The Radio Protocol Stack
The protocol stack of LDACS is implemented in the AS and GS: It
consists of the Physical Layer (PHY) with five major functional
blocks above it. Four are placed in the Data Link Layer (DLL) of the
AS and GS: (1) Medium Access Layer (MAC), (2) Voice Interface (VI),
(3) Data Link Service (DLS), and (4) LDACS Management Entity (LME).
The last entity resides within the Sub-Network Layer: Sub-Network
Protocol (SNP). The LDACS network is externally connected to voice
units, radio control units, and the ATN Network Layer.
Figure 14 shows the protocol stack of LDACS as implemented in the AS
and GS.
IPv6 Network Layer
|
|
+------------------+ +----+
| SNP |--| | Sub-Network
| | | | Layer
+------------------+ | |
| | LME|
+------------------+ | |
| DLS | | | Logical Link
| | | | Control Layer
+------------------+ +----+
| |
DCH DCCH/CCCH
| RACH/BCCH
| |
+--------------------------+
| MAC | Medium Access
| | Layer
+--------------------------+
|
+--------------------------+
| PHY | Physical Layer
+--------------------------+
|
|
((*))
FL/RL radio channels
separated by
Frequency Division Duplex
Figure 14: LDACS protocol stack in AS and GS
7.4.3. Radio (PHY)
The physical layer provides the means to transfer data over the radio The physical layer provides the means to transfer data over the radio
channel. The LDACS ground-station supports bi-directional links to channel. The LDACS ground-station supports bi-directional links to
multiple aircraft under its control. The forward link direction (FL; multiple aircraft under its control. The forward link direction (FL;
ground-to-air) and the reverse link direction (RL; air-to-ground) are ground-to-air) and the reverse link direction (RL; air-to-ground) are
separated by frequency division duplex. Forward link and reverse separated by frequency division duplex. Forward link and reverse
link use a 500 kHz channel each. The ground-station transmits a link use a 500 kHz channel each. The ground-station transmits a
continuous stream of OFDM symbols on the forward link. In the continuous stream of OFDM symbols on the forward link. In the
reverse link different aircraft are separated in time and frequency reverse link different aircraft are separated in time and frequency
using a combination of Orthogonal Frequency-Division Multiple-Access using a combination of Orthogonal Frequency-Division Multiple-Access
(OFDMA) and Time-Division Multiple-Access (TDMA). Aircraft thus (OFDMA) and Time-Division Multiple-Access (TDMA). Aircraft thus
transmit discontinuously on the reverse link with radio bursts sent transmit discontinuously on the reverse link with radio bursts sent
in precisely defined transmission opportunities allocated by the in precisely defined transmission opportunities allocated by the
ground-station. LDACS does not support beam-forming or Multiple ground-station. The most important service on the PHY layer of LDACS
Input Multiple Output (MIMO). is the PHY time framing service, which indicates that the PHY layer
is ready to transmit in a given slot and to indicate PHY layer
framing and timing to the MAC time framing service. LDACS does not
support beam-forming or Multiple Input Multiple Output (MIMO).
7.4.4. Scheduling, Frame Structure and QoS (MAC)
The data-link layer provides the necessary protocols to facilitate The data-link layer provides the necessary protocols to facilitate
concurrent and reliable data transfer for multiple users. The LDACS concurrent and reliable data transfer for multiple users. The LDACS
data link layer is organized in two sub-layers: The medium access data link layer is organized in two sub-layers: The medium access
sub-layer and the logical link control sub-layer. The medium access sub-layer and the logical link control sub-layer. The medium access
sub-layer manages the organization of transmission opportunities in sub-layer manages the organization of transmission opportunities in
slots of time and frequency. The logical link control sub-layer slots of time and frequency. The logical link control sub-layer
provides acknowledged point-to-point logical channels between the provides acknowledged point-to-point logical channels between the
aircraft and the ground-station using an automatic repeat request aircraft and the ground-station using an automatic repeat request
protocol. LDACS supports also unacknowledged point-to-point channels protocol. LDACS supports also unacknowledged point-to-point channels
and ground-to-air broadcast. and ground-to-air broadcast. Before going more into depth about the
LDACS medium access, the frame structure of LDACS is introduced:
The user data rate of LDACS is 315 kbit/s to 1428 kbit/s on the The LDACS framing structure for FL and RL is based on Super-Frames
forward link, and 294 kbit/s to 1390 kbit/s on the reverse link, (SF) of 240 ms duration. Each SF corresponds to 2000 OFDM symbols.
depending on coding and modulation. Due to strong interference from The FL and RL SF boundaries are aligned in time (from the view of the
legacy systems in the L-band, the most robust coding and modulation GS).
should be expected for initial deployment i.e. 315/294 kbit/s on the
forward/reverse link, respectively.
Since LDACS has been mainly designed for air traffic management In the FL, an SF contains a Broadcast Frame of duration 6.72 ms (56
communication it supports mutual entity authentication, integrity and OFDM symbols) for the Broadcast Control Channel (BCCH), and four
confidentiality capabilities of user data messages and some control Multi-Frames (MF), each of duration 58.32 ms (486 OFDM symbols).
channel protection capabilities [MAE19].
7.3. Applicability to Deterministic Flows In the RL, each SF starts with a Random Access (RA) slot of length
6.72 ms with two opportunities for sending RL random access frames
for the Random Access Channel (RACH), followed by four MFs. These
MFs have the same fixed duration of 58.32 ms as in the FL, but a
different internal structure
LDACS has been designed with applications related to the safety and Figure 15 and Figure 16 illustrate the LDACS frame structure.
regularity of the flight in mind. It has therefore been designed as
a deterministic wireless data link (as far as possible). ^
| +------+------------+------------+------------+------------+
| FL | BCCH | MF | MF | MF | MF |
F +------+------------+------------+------------+------------+
r <---------------- Super-Frame (SF) - 240ms ---------------->
e
q +------+------------+------------+------------+------------+
u RL | RACH | MF | MF | MF | MF |
e +------+------------+------------+------------+------------+
n <---------------- Super-Frame (SF) - 240ms ---------------->
c
y
|
----------------------------- Time ------------------------------>
|
Figure 15: SF structure for LDACS
^
| +-------------+------+-------------+
| FL | DCH | CCCH | DCH |
F +-------------+------+-------------+
r <---- Multi-Frame (MF) - 58.32ms -->
e
q +------+---------------------------+
u RL | DCCH | DCH |
e +------+---------------------------+
n <---- Multi-Frame (MF) - 58.32ms -->
c
y
|
-------------------- Time ------------------>
|
Figure 16: MF structure for LDACS
This fixed frame structure allows for a reliable and dependable
transmission of data. Next, the LDACS medium access layer is
introduced:
LDACS medium access is always under the control of the ground-station LDACS medium access is always under the control of the ground-station
of a radio cell. Any medium access for the transmission of user data of a radio cell. Any medium access for the transmission of user data
has to be requested with a resource request message stating the has to be requested with a resource request message stating the
requested amount of resources and class of service. The ground- requested amount of resources and class of service. The ground-
station performs resource scheduling on the basis of these requests station performs resource scheduling on the basis of these requests
and grants resources with resource allocation messages. Resource and grants resources with resource allocation messages. Resource
request and allocation messages are exchanged over dedicated request and allocation messages are exchanged over dedicated
contention-free control channels. contention-free control channels.
skipping to change at page 48, line 35 skipping to change at page 54, line 42
seen as a big problem since safety related message always go first in seen as a big problem since safety related message always go first in
any case. Scheduling of reverse link resources is done in physical any case. Scheduling of reverse link resources is done in physical
Protocol Data Units (PDU) of 112 bit (or larger if more aggressive Protocol Data Units (PDU) of 112 bit (or larger if more aggressive
coding and modulation is used). Scheduling on the forward link is coding and modulation is used). Scheduling on the forward link is
done Byte-wise since the forward link is transmitted continuously by done Byte-wise since the forward link is transmitted continuously by
the ground-station. the ground-station.
In order to support diversity, LDACS supports handovers to other In order to support diversity, LDACS supports handovers to other
ground-stations on different channels. Handovers may be initiated by ground-stations on different channels. Handovers may be initiated by
the aircraft (break-before-make) or by the ground-station (make- the aircraft (break-before-make) or by the ground-station (make-
before-break) if it is connected to an alternative ground-station via before-break). Beyond this, FCI diversity shall be implemented by
the same ground-station controller. Beyond this, FCI diversity shall the multi-link concept.
be implemented by the multi-link concept.
7.5. Summary
LDACS has been designed with applications related to the safety and
regularity of the flight in mind. It has therefore been designed as
a deterministic wireless data link (as far as possible).
It is a secure, scalable and spectrum efficient data link with
embedded navigation capability and thus, is the first truly
integrated CNS system recognized by ICAO. During flight tests the
LDACS capabilities have been successfully demonstrated. A viable
roll-out scenario has been developed which allows gradual
introduction of LDACS with immediate use and revenues. Finally, ICAO
is developing LDACS standards to pave the way for a successful roll-
out in the near future.
8. IANA Considerations 8. IANA Considerations
This specification does not require IANA action. This specification does not require IANA action.
9. Security Considerations 9. Security Considerations
Most RAW technologies integrate some authentication or encryption Most RAW technologies integrate some authentication or encryption
mechanisms that were defined outside the IETF. mechanisms that were defined outside the IETF.
skipping to change at page 49, line 44 skipping to change at page 56, line 20
[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", Work in Progress, "Deterministic Networking Architecture", Work in Progress,
Internet-Draft, draft-ietf-detnet-architecture-13, 6 May Internet-Draft, draft-ietf-detnet-architecture-13, 6 May
2019, <https://tools.ietf.org/html/draft-ietf-detnet- 2019, <https://tools.ietf.org/html/draft-ietf-detnet-
architecture-13>. architecture-13>.
[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", Work in Progress, Internet-Draft, of IEEE 802.15.4", Work in Progress, Internet-Draft,
draft-ietf-6tisch-architecture-29, 27 August 2020, draft-ietf-6tisch-architecture-30, 26 November 2020,
<https://tools.ietf.org/html/draft-ietf-6tisch- <https://tools.ietf.org/html/draft-ietf-6tisch-
architecture-29>. architecture-30>.
13. Informative References 13. Informative References
[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
JP., and R. Alexander, "RPL: IPv6 Routing Protocol for JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
Low-Power and Lossy Networks", RFC 6550, Low-Power and Lossy Networks", RFC 6550,
DOI 10.17487/RFC6550, March 2012, DOI 10.17487/RFC6550, March 2012,
<https://www.rfc-editor.org/info/rfc6550>. <https://www.rfc-editor.org/info/rfc6550>.
skipping to change at page 50, line 47 skipping to change at page 57, line 22
Chang, T., Vucinic, M., Vilajosana, X., Duquennoy, S., and Chang, T., Vucinic, M., Vilajosana, X., Duquennoy, S., and
D. Dujovne, "6TiSCH Minimal Scheduling Function (MSF)", D. Dujovne, "6TiSCH Minimal Scheduling Function (MSF)",
Work in Progress, Internet-Draft, draft-ietf-6tisch-msf- Work in Progress, Internet-Draft, draft-ietf-6tisch-msf-
18, 12 September 2020, 18, 12 September 2020,
<https://tools.ietf.org/html/draft-ietf-6tisch-msf-18>. <https://tools.ietf.org/html/draft-ietf-6tisch-msf-18>.
[I-D.pthubert-raw-architecture] [I-D.pthubert-raw-architecture]
Thubert, P., Papadopoulos, G., and R. Buddenberg, Thubert, P., Papadopoulos, G., and R. Buddenberg,
"Reliable and Available Wireless Architecture/Framework", "Reliable and Available Wireless Architecture/Framework",
Work in Progress, Internet-Draft, draft-pthubert-raw- Work in Progress, Internet-Draft, draft-pthubert-raw-
architecture-04, 6 July 2020, architecture-05, 15 November 2020,
<https://tools.ietf.org/html/draft-pthubert-raw- <https://tools.ietf.org/html/draft-pthubert-raw-
architecture-04>. architecture-05>.
[I-D.ietf-roll-nsa-extension] [I-D.ietf-roll-nsa-extension]
Koutsiamanis, R., Papadopoulos, G., Montavont, N., and P. Koutsiamanis, R., Papadopoulos, G., Montavont, N., and P.
Thubert, "Common Ancestor Objective Function and Parent Thubert, "Common Ancestor Objective Function and Parent
Set DAG Metric Container Extension", Work in Progress, Set DAG Metric Container Extension", Work in Progress,
Internet-Draft, draft-ietf-roll-nsa-extension-09, 26 Internet-Draft, draft-ietf-roll-nsa-extension-10, 29
September 2020, <https://tools.ietf.org/html/draft-ietf- October 2020, <https://tools.ietf.org/html/draft-ietf-
roll-nsa-extension-09>. roll-nsa-extension-10>.
[I-D.papadopoulos-paw-pre-reqs] [I-D.papadopoulos-paw-pre-reqs]
Papadopoulos, G., Koutsiamanis, R., Montavont, N., and P. Papadopoulos, G., Koutsiamanis, R., Montavont, N., and P.
Thubert, "Exploiting Packet Replication and Elimination in Thubert, "Exploiting Packet Replication and Elimination in
Complex Tracks in LLNs", Work in Progress, Internet-Draft, Complex Tracks in LLNs", Work in Progress, Internet-Draft,
draft-papadopoulos-paw-pre-reqs-01, 25 March 2019, draft-papadopoulos-paw-pre-reqs-01, 25 March 2019,
<https://tools.ietf.org/html/draft-papadopoulos-paw-pre- <https://tools.ietf.org/html/draft-papadopoulos-paw-pre-
reqs-01>. reqs-01>.
[I-D.thubert-bier-replication-elimination] [I-D.thubert-bier-replication-elimination]
skipping to change at page 51, line 39 skipping to change at page 58, line 11
[I-D.thubert-6lo-bier-dispatch] [I-D.thubert-6lo-bier-dispatch]
Thubert, P., Brodard, Z., Jiang, H., and G. Texier, "A Thubert, P., Brodard, Z., Jiang, H., and G. Texier, "A
6loRH for BitStrings", Work in Progress, Internet-Draft, 6loRH for BitStrings", Work in Progress, Internet-Draft,
draft-thubert-6lo-bier-dispatch-06, 28 January 2019, draft-thubert-6lo-bier-dispatch-06, 28 January 2019,
<https://tools.ietf.org/html/draft-thubert-6lo-bier- <https://tools.ietf.org/html/draft-thubert-6lo-bier-
dispatch-06>. dispatch-06>.
[I-D.ietf-bier-te-arch] [I-D.ietf-bier-te-arch]
Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering
for Bit Index Explicit Replication (BIER-TE)", Work in for Bit Index Explicit Replication (BIER-TE)", Work in
Progress, Internet-Draft, draft-ietf-bier-te-arch-08, 13 Progress, Internet-Draft, draft-ietf-bier-te-arch-09, 30
July 2020, October 2020,
<https://tools.ietf.org/html/draft-ietf-bier-te-arch-08>. <https://tools.ietf.org/html/draft-ietf-bier-te-arch-09>.
[I-D.ietf-6tisch-coap] [I-D.ietf-6tisch-coap]
Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and
Interaction using CoAP", Work in Progress, Internet-Draft, Interaction using CoAP", Work in Progress, Internet-Draft,
draft-ietf-6tisch-coap-03, 9 March 2015, draft-ietf-6tisch-coap-03, 9 March 2015,
<https://tools.ietf.org/html/draft-ietf-6tisch-coap-03>. <https://tools.ietf.org/html/draft-ietf-6tisch-coap-03>.
[I-D.svshah-tsvwg-deterministic-forwarding] [I-D.svshah-tsvwg-deterministic-forwarding]
Shah, S. and P. Thubert, "Deterministic Forwarding PHB", Shah, S. and P. Thubert, "Deterministic Forwarding PHB",
Work in Progress, Internet-Draft, draft-svshah-tsvwg- Work in Progress, Internet-Draft, draft-svshah-tsvwg-
skipping to change at page 55, line 5 skipping to change at page 61, line 23
project MICONAV", Proceedings of the Integrated project MICONAV", Proceedings of the Integrated
Communications, Navigation, Surveillance Conference Communications, Navigation, Surveillance Conference
(ICNS) Herndon, VA, USA, April 2018. (ICNS) Herndon, VA, USA, April 2018.
[SCH19] Schnell, M., "DLR tests digital communications [SCH19] Schnell, M., "DLR tests digital communications
technologies combined with additional navigation functions technologies combined with additional navigation functions
for the first time", 3 March 2019, for the first time", 3 March 2019,
<https://www.dlr.de/dlr/en/desktopdefault.aspx/tabid- <https://www.dlr.de/dlr/en/desktopdefault.aspx/tabid-
10081/151_read-32951/#/gallery/33877>. 10081/151_read-32951/#/gallery/33877>.
[MAE19] Mäurer, N. and C. Schmitt, "DLR tests digital
communications technologies combined with additional
navigation functions for the first time", Proceedings of
the Integrated Communications, Navigation, Surveillance
Conference (ICNS) Washington D.C., USA, April 2019.
[TR37910] "3GPP TR 37.910, Study on self evaluation towards IMT-2020 [TR37910] "3GPP TR 37.910, Study on self evaluation towards IMT-2020
submission", submission",
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=3190>. SpecificationDetails.aspx?specificationId=3190>.
[TR38824] "3GPP TR 38.824, Study on physical layer enhancements for [TR38824] "3GPP TR 38.824, Study on physical layer enhancements for
NR ultra-reliable and low latency case (URLLC)", NR ultra-reliable and low latency case (URLLC)",
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=3498>. SpecificationDetails.aspx?specificationId=3498>.
skipping to change at page 56, line 9 skipping to change at page 62, line 22
[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>.
[I-D.ietf-detnet-ip-over-tsn] [I-D.ietf-detnet-ip-over-tsn]
Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet Varga, B., Farkas, J., Malis, A., and S. Bryant, "DetNet
Data Plane: IP over IEEE 802.1 Time Sensitive Networking Data Plane: IP over IEEE 802.1 Time Sensitive Networking
(TSN)", Work in Progress, Internet-Draft, draft-ietf- (TSN)", Work in Progress, Internet-Draft, draft-ietf-
detnet-ip-over-tsn-03, 8 June 2020, detnet-ip-over-tsn-05, 13 December 2020,
<https://tools.ietf.org/html/draft-ietf-detnet-ip-over- <https://tools.ietf.org/html/draft-ietf-detnet-ip-over-
tsn-03>. tsn-05>.
[IEEE802.1TSN] [IEEE802.1TSN]
IEEE 802.1, "Time-Sensitive Networking (TSN) Task Group", IEEE 802.1, "Time-Sensitive Networking (TSN) Task Group",
<http://www.ieee802.org/1/pages/tsn.html>. <http://www.ieee802.org/1/pages/tsn.html>.
[IEEE802.1AS] [IEEE802.1AS]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks -- Timing and Synchronization for Time-Sensitive networks -- Timing and Synchronization for Time-Sensitive
Applications", IEEE 802.1AS-2020, Applications", IEEE 802.1AS-2020,
<https://standards.ieee.org/content/ieee-standards/en/ <https://standards.ieee.org/content/ieee-standards/en/
skipping to change at page 56, line 40 skipping to change at page 63, line 4
[IEEE802.1Qbv] [IEEE802.1Qbv]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks -- Bridges and Bridged Networks -- Amendment 25: networks -- Bridges and Bridged Networks -- Amendment 25:
Enhancements for Scheduled Traffic", IEEE 802.1Qbv-2015, Enhancements for Scheduled Traffic", IEEE 802.1Qbv-2015,
<https://ieeexplore.ieee.org/document/7440741>. <https://ieeexplore.ieee.org/document/7440741>.
[IEEE802.1Qcc] [IEEE802.1Qcc]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks -- Bridges and Bridged Networks -- Amendment 31: networks -- Bridges and Bridged Networks -- Amendment 31:
Stream Reservation Protocol (SRP) Enhancements and Stream Reservation Protocol (SRP) Enhancements and
Performance Improvements", IEEE 802.1Qcc-2018, Performance Improvements", IEEE 802.1Qcc-2018,
<https://ieeexplore.ieee.org/document/8514112>. <https://ieeexplore.ieee.org/document/8514112>.
[IEEE802.3] [IEEE802.3]
IEEE, "IEEE Standard for Ethernet", IEEE 802.3-2018, IEEE, "IEEE Standard for Ethernet", IEEE 802.3-2018,
<https://ieeexplore.ieee.org/document/8457469>. <https://ieeexplore.ieee.org/document/8457469>.
[ETR5GTSN] Farkas, J., Varga, B., Miklos, G., and J. Sachs, "5G-TSN [ETR5GTSN] Farkas, J., Varga, B., Miklos, G., and J. Sachs, "5G-TSN
integration meets networking requirements for industrial integration meets networking requirements for industrial
automation", Ericsson Technology Review, Volume 9, No 7, automation", Ericsson Technology Review, Volume 9, No 7,
August 2019, <https://www.ericsson.com/en/reports-and- August 2019, <https://www.ericsson.com/en/reports-and-
papers/ericsson-technology-review/articles/5g-tsn- papers/ericsson-technology-review/articles/5g-tsn-
integration-for-industrial-automation>. integration-for-industrial-automation>.
[MAE18] Maeurer, N. and A. Bilzhause, "A Cybersecurity
Architecture for the L-band Digital Aeronautical
Communications System (LDACS)", IEEE 37th Digital Avionics
Systems Conference (DASC), pp. 1-10, London, UK , 2017.
[MAE191] Maeurer, N. and C. Schmitt, "Towards Successful
Realization of the LDACS Cybersecurity Architecture: An
Updated Datalink Security Threat- and Risk Analysis", IEEE
Integrated Communications, Navigation and Surveillance
Conference (ICNS), pp. 1-13, Herndon, VA, USA , 2019.
[ICAO19] International Civil Aviation Organization (ICAO), "TLDACS
White Paper–A Roll-out Scenario", Working Paper
COMMUNICATIONS PANEL-DATA COMMUNICATIONS INFRASTRUCTURE
WORKING GROUP, Montreal, Canada , October 2019.
[MAE192] Maeurer, N., Graeupl, T., and C. Schmitt, "Evaluation of
the LDACS Cybersecurity Implementation", IEEE 38th Digital
Avionics Systems Conference (DACS), pp. 1-10, San Diego,
CA, USA , September 2019.
[MAE20] Maeurer, N., Graeupl, T., and C. Schmitt, "Comparing
Different Diffie-Hellman Key Exchange Flavors for LDACS",
IEEE 39th Digital Avionics Systems Conference (DACS), pp.
1-10, San Diego, CA, USA , October 2019.
[FIL19] Filip-Dhaubhadel, A. and D. Shutin, "LDACS- Based Non-
Cooperative Surveillance Multistatic Radar Design and
Detection Coverage Assessment", IEEE 38th Digital Avionics
Systems Conference (DACS), pp. 1-10, San Diego, CA, USA ,
September 2019.
[BAT19] Battista, G., Osechas, O., Narayanan, S., Crespillo, O.G.,
Gerbeth, D., Maeurer, N., Mielke, D., and T. Graeupl,
"Real-Time Demonstration of Integrated Communication and
Navigation Services Using LDACS", IEEE Integrated
Communications, Navigation and Surveillance Conference
(ICNS), pp. 1-12, Herndon, VA, USA , 2019.
[BRA06] Brandes, S., Schnell, M., Rokitansky, C.H., Ehammer, M.,
Graeupl, T., Steendam, H., Guenach, M., Rihacek, C., and
B. Haindl, "B-VHF -Selected Simulation Results and Final
Assessment", IEEE 25th Digital Avionics Systems Conference
(DACS), pp. 1-12, New York, NY, USA , September 2019.
[SCH08] Schnell, M., Brandes, S., Gligorevic, S., Rokitansky,
C.H., Ehammer, M., Graeupl, T., Rihacek, C., and M.
Sajatovic, "B-AMC - Broadband Aeronautical Multi-carrier
Communications", IEEE 8th Integrated Communications,
Navigation and Surveillance Conference (ICNS), pp. 1-13,
New York, NY, USA , April 2008.
[HAI09] Haindl, B., Rihacek, C., Sajatovic, M., Phillips, B.,
Budinger, J., Schnell, M., Kamiano, D., and W. Wilson,
"Improvement of L-DACS1 Design by Combining B-AMC with P34
and WiMAX Technologies", IEEE 9th Integrated
Communications, Navigation and Surveillance Conference
(ICNS), pp. 1-8, New York, NY, USA , May 2009.
[EHA11] Ehammer, M. and T. Graeupl, "AeroMACS - An Airport
Communications System", IEEE 30th Digital Avionics Systems
Conference (DACS), pp. 1-16, New York, NY, USA , September
2011.
[SCH14] Schnell, M., Epple, U., Shutin, D., and N.
Schneckenburger, "LDACS: Future Aeronautical
Communications for Air- Traffic Management", IEEE
Communications Magazine, 52(5), 104-110 , 2017.
Authors' Addresses Authors' Addresses
Pascal Thubert (editor) Pascal Thubert (editor)
Cisco Systems, Inc Cisco Systems, Inc
Building D Building D
45 Allee des Ormes - BP1200 45 Allee des Ormes - BP1200
06254 MOUGINS - Sophia Antipolis 06254 MOUGINS - Sophia Antipolis
France France
Phone: +33 497 23 26 34 Phone: +33 497 23 26 34
skipping to change at page 57, line 23 skipping to change at page 65, line 4
Pascal Thubert (editor) Pascal Thubert (editor)
Cisco Systems, Inc Cisco Systems, Inc
Building D Building D
45 Allee des Ormes - BP1200 45 Allee des Ormes - BP1200
06254 MOUGINS - Sophia Antipolis 06254 MOUGINS - Sophia Antipolis
France France
Phone: +33 497 23 26 34 Phone: +33 497 23 26 34
Email: pthubert@cisco.com Email: pthubert@cisco.com
Dave Cavalcanti Dave Cavalcanti
Intel Corporation Intel Corporation
2111 NE 25th Ave 2111 NE 25th Ave
Hillsboro, OR, 97124 Hillsboro, OR, 97124
United States of America United States of America
Phone: 503 712 5566 Phone: 503 712 5566
Email: dave.cavalcanti@intel.com Email: dave.cavalcanti@intel.com
Xavier Vilajosana Xavier Vilajosana
Universitat Oberta de Catalunya Universitat Oberta de Catalunya
156 Rambla Poblenou 156 Rambla Poblenou
08018 Barcelona Catalonia 08018 Barcelona Catalonia
Spain Spain
Email: xvilajosana@uoc.edu Email: xvilajosana@uoc.edu
Corinna Schmitt Corinna Schmitt
Research Institute CODE, UniBwM Research Institute CODE, UniBwM
Werner-Heisenberg-Weg 28 Werner-Heisenberg-Weg 39
85577 Neubiberg 85577 Neubiberg
Germany Germany
Email: corinna.schmitt@unibw.de Email: corinna.schmitt@unibw.de
Janos Farkas Janos Farkas
Ericsson Ericsson
Budapest Budapest
Magyar tudosok korutja 11 Magyar tudosok korutja 11
1117 1117
Hungary Hungary
Email: janos.farkas@ericsson.com Email: janos.farkas@ericsson.com
 End of changes. 35 change blocks. 
78 lines changed or deleted 339 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/