| < draft-thubert-raw-technologies-03.txt | draft-thubert-raw-technologies-04.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: January 2, 2020 Intel | Expires: 9 July 2020 Intel | |||
| X. Vilajosana | X. Vilajosana | |||
| Universitat Oberta de Catalunya | Universitat Oberta de Catalunya | |||
| C. Schmitt | C. Schmitt | |||
| Universitaet der Bundeswehr Muenchen | Research Institute CODE, UniBwM | |||
| July 1, 2019 | 6 January 2020 | |||
| Reliable and Available Wireless Technologies | Reliable and Available Wireless Technologies | |||
| draft-thubert-raw-technologies-03 | draft-thubert-raw-technologies-04 | |||
| 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 requirements | making them suitable to carry time-sensitive flows with high | |||
| of both reliable delivery in bounded time, and availability at all | reliability and availbility. | |||
| times, regardless of packet transmission or individual equipement | ||||
| failures. | ||||
| 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 January 2, 2020. | This Internet-Draft will expire on 9 July 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 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/ | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | license-info) in effect on the date of publication of this document. | |||
| publication of this document. Please review these documents | Please review these documents carefully, as they describe your rights | |||
| carefully, as they describe your rights and restrictions with respect | and restrictions with respect to this document. Code Components | |||
| to this document. Code Components extracted from this document must | extracted from this document must include Simplified BSD License text | |||
| include Simplified BSD License text as described in Section 4.e of | as described in Section 4.e of the Trust Legal Provisions and are | |||
| the Trust Legal Provisions and are provided without warranty as | provided without warranty as described in the Simplified BSD License. | |||
| described in the Simplified BSD License. | ||||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. On Scheduling . . . . . . . . . . . . . . . . . . . . . . . . 4 | 3. On Scheduling . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.1. Benefits of Scheduling on Wires . . . . . . . . . . . . . 4 | 3.1. Benefits of Scheduling on Wires . . . . . . . . . . . . . 4 | |||
| 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 4.1. Provenance and Documents . . . . . . . . . . . . . . . . 6 | 4.1. Provenance and Documents . . . . . . . . . . . . . . . . 5 | |||
| 4.2. 802.11ax High Efficiency (HE) . . . . . . . . . . . . . . 8 | 4.2. 802.11ax High Efficiency (HE) . . . . . . . . . . . . . . 7 | |||
| 4.2.1. General Characteristics . . . . . . . . . . . . . . . 8 | 4.2.1. General Characteristics . . . . . . . . . . . . . . . 7 | |||
| 4.2.1.1. Multi-User OFDMA and Trigger-based Scheduled | 4.2.2. Applicability to deterministic flows . . . . . . . . 8 | |||
| Access . . . . . . . . . . . . . . . . . . . . . 8 | ||||
| 4.2.1.2. Improved PHY Robustness . . . . . . . . . . . . . 8 | ||||
| 4.2.1.3. Support for 6GHz band . . . . . . . . . . . . . . 9 | ||||
| 4.2.2. Applicability to deterministic flows . . . . . . . . 9 | ||||
| 4.2.2.1. 802.11 Managed network operation and admission | ||||
| control . . . . . . . . . . . . . . . . . . . . . 9 | ||||
| 4.2.2.2. Scheduling for bounded latency and diversity . . 10 | ||||
| 4.3. 802.11be Extreme High Throughput (EHT) . . . . . . . . . 10 | 4.3. 802.11be Extreme High Throughput (EHT) . . . . . . . . . 10 | |||
| 4.3.1. General Characteristics . . . . . . . . . . . . . . . 10 | 4.3.1. General Characteristics . . . . . . . . . . . . . . . 10 | |||
| 4.3.2. Applicability to deterministic flows . . . . . . . . 11 | 4.3.2. Applicability to deterministic flows . . . . . . . . 11 | |||
| 4.3.2.1. Enhanced scheduled operation for bounded latency 11 | ||||
| 4.3.2.2. Multi-AP coordination . . . . . . . . . . . . . . 11 | ||||
| 4.3.2.3. Multi-band operation . . . . . . . . . . . . . . 12 | ||||
| 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 . . . . . . . . . . . . . . . 12 | |||
| 4.4.2. Applicability to deterministic flows . . . . . . . . 12 | 4.4.2. Applicability to deterministic flows . . . . . . . . 12 | |||
| 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 . . . . . . . . . . . . . . . 14 | |||
| 5.2.1. General Characteristics . . . . . . . . . . . . . . . 15 | 5.2.1. General Characteristics . . . . . . . . . . . . . . . 14 | |||
| 5.2.2. Applicability to Deterministic Flows . . . . . . . . 16 | 5.2.2. Applicability to Deterministic Flows . . . . . . . . 16 | |||
| 5.2.2.1. Centralized Path Computation . . . . . . . . . . 16 | 6. 3GPP Ultra-Reliable Low-Latency Communication . . . . . . . . 29 | |||
| 5.2.2.2. 6TiSCH Tracks . . . . . . . . . . . . . . . . . . 23 | ||||
| 6. 3GPP Ultra-Reliable Low-Latency Communication . . . . . . . . 30 | ||||
| 7. L-band Digital Aeronautical Communications System . . . . . . 30 | 7. L-band Digital Aeronautical Communications System . . . . . . 30 | |||
| 7.1. Provenance and Documents . . . . . . . . . . . . . . . . 31 | 7.1. Provenance and Documents . . . . . . . . . . . . . . . . 30 | |||
| 7.2. General Characteristics . . . . . . . . . . . . . . . . . 31 | 7.2. General Characteristics . . . . . . . . . . . . . . . . . 31 | |||
| 7.3. Applicability to Deterministic Flows . . . . . . . . . . 33 | 7.3. Applicability to Deterministic Flows . . . . . . . . . . 32 | |||
| 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 | |||
| 9. Security Considerations . . . . . . . . . . . . . . . . . . . 34 | 9. Security Considerations . . . . . . . . . . . . . . . . . . . 33 | |||
| 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 34 | 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
| 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 34 | 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
| 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 | 12. Normative References . . . . . . . . . . . . . . . . . . . . 34 | |||
| 12.1. Normative References . . . . . . . . . . . . . . . . . . 34 | 13. Informative References . . . . . . . . . . . . . . . . . . . 34 | |||
| 12.2. Informative References . . . . . . . . . . . . . . . . . 35 | ||||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
| 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 | |||
| skipping to change at page 4, line 6 ¶ | skipping to change at page 3, line 37 ¶ | |||
| pure P2P. | pure P2P. | |||
| 2. Terminology | 2. Terminology | |||
| This specification uses several terms that are uncommon on protocols | This specification uses several terms that are uncommon on protocols | |||
| that ensure bets effort transmissions for stochastics flows, such as | that ensure bets effort transmissions for stochastics flows, such as | |||
| found in the traditional Internet and other statistically multiplexed | found in the traditional Internet and other statistically multiplexed | |||
| packet networks. | packet networks. | |||
| ARQ: Automatic Repeat Request, enabling an acknowledged transmission | ARQ: Automatic Repeat Request, enabling an acknowledged transmission | |||
| and retries. ARQ is a typical model at Layer-2 on a wireless | and retries. ARQ is a typical model at Layer-2 on a wireless | |||
| medium. It is typically avoided end-to-end on deterministic | medium. It is typically avoided end-to-end on deterministic flows | |||
| flows because it introduces excessive indetermination in | because it introduces excessive indetermination in latency, but a | |||
| latency, but a limited number of retries within a bounded time | limited number of retries within a bounded time may be used over a | |||
| may be used over a wireless link and yet respect end-to-end | wireless link and yet respect end-to-end constraints. | |||
| constraints. | ||||
| Available: That is exempt of unscheduled outage, the expectation for | Available: That is exempt of unscheduled outage, the expectation for | |||
| a network being that the flow is maintained in the face of any | a network being that the flow is maintained in the face of any | |||
| single breakage. | single breakage. | |||
| FEC: Forward error correction, sending redundant coded data to help | FEC: Forward error correction, sending redundant coded data to help | |||
| the receiver recover transmission errors without the delays | the receiver recover transmission errors without the delays | |||
| incurred with ARQ. | incurred with ARQ. | |||
| HARQ: Hybrid ARQ, a combination of FEC and ARQ. | HARQ: Hybrid ARQ, a combination of FEC and ARQ. | |||
| PCE: Path Computation Element. | PCE: Path Computation Element. | |||
| PAREO (functions): the wireless extension of DetNet PREOF. PAREO | PAREO (functions): the wireless extension of DetNet PREOF. PAREO | |||
| functions include scheduled ARQ at selected hops, and expect | functions include scheduled ARQ at selected hops, and expect the | |||
| the use of new operations like overhearing where available. | use of new operations like overhearing where available. | |||
| Reliable: That consistently performs as expected, the expectation | Reliable: That consistently performs as expected, the expectation | |||
| for a network being to always deliver a packet in due time. | for a network being to always deliver a packet in due time. | |||
| Track: A DODAG oriented to a destination, and that enables Packet | Track: A DODAG oriented to a destination, and that enables Packet | |||
| ARQ, Replication, Elimination, and Ordering Functions. | ARQ, Replication, Elimination, and Ordering Functions. | |||
| 3. On Scheduling | 3. On Scheduling | |||
| The operations of a Deterministic Network often rely on precisely | The operations of a Deterministic Network often rely on precisely | |||
| applying a tight schedule, in order to avoid collision loss and | applying a tight schedule, in order to avoid collision loss and | |||
| guarantee the worst-case time of delivery. To achieve this, there | guarantee the worst-case time of delivery. To achieve this, there | |||
| must be a shared sense of time throughout the network. The sense of | must be a shared sense of time throughout the network. The sense of | |||
| time is usually provided by the lower layer and is not in scope for | time is usually provided by the lower layer and is not in scope for | |||
| RAW. | RAW. | |||
| skipping to change at page 7, line 17 ¶ | skipping to change at page 6, line 47 ¶ | |||
| leadership, spectrum advocacy, and industry-wide collaboration. The | leadership, spectrum advocacy, and industry-wide collaboration. The | |||
| WFA work helps ensure that Wi-Fi devices and networks provide users | WFA work helps ensure that Wi-Fi devices and networks provide users | |||
| the interoperability, security, and reliability they have come to | the interoperability, security, and reliability they have come to | |||
| expect. | expect. | |||
| The following IEEE 802.11 specifications/certifications are relevant | The following IEEE 802.11 specifications/certifications are relevant | |||
| in the context of reliable and available wireless services and | in the context of reliable and available wireless services and | |||
| support for time-sensitive networking capabilities: | support for time-sensitive networking capabilities: | |||
| Time Synchronization: IEEE802.11-2016 with IEEE802.1AS; WFA TimeSync | Time Synchronization: IEEE802.11-2016 with IEEE802.1AS; WFA TimeSync | |||
| Certification. | Certification. | |||
| Congestion Control: IEEE802.11-2016 Admission Control; WFA Admission | Congestion Control: IEEE802.11-2016 Admission Control; WFA Admission | |||
| Control. | Control. | |||
| Security: WFA Wi-Fi Protected Access, WPA2 and WPA3. | Security: WFA Wi-Fi Protected Access, WPA2 and WPA3. | |||
| Interoperating with IEEE802.1Q bridges: IEEE802.11ak. | Interoperating with IEEE802.1Q bridges: IEEE802.11ak. | |||
| Stream Reservation Protocol (part of IEEE802.1Qat): | Stream Reservation Protocol (part of IEEE802.1Qat): | |||
| AIEEE802.11-2016. | AIEEE802.11-2016. | |||
| Scheduled channel access: IEEE802.11ad Enhancements for very | Scheduled channel access: IEEE802.11ad Enhancements for very high | |||
| high throughput in the 60 GHz band [IEEE80211ad]. | throughput in the 60 GHz band [IEEE80211ad]. | |||
| 802.11 Real-Time Applications: Topic Interest Group (TIG) | 802.11 Real-Time Applications: Topic Interest Group (TIG) ReportDoc | |||
| ReportDoc [IEEE_doc_11-18-2009-06]. | [IEEE_doc_11-18-2009-06]. | |||
| In addition, major amendments being developed by the IEEE802.11 | In addition, major amendments being developed by the IEEE802.11 | |||
| Working Group include capabilities that can be used as the basis for | Working Group include capabilities that can be used as the basis for | |||
| providing more reliable and predictable wireless connectivity and | providing more reliable and predictable wireless connectivity and | |||
| support time-sensitive applications: | support time-sensitive applications: | |||
| IEEE 802.11ax D4.0: Enhancements for High Efficiency (HE). [IEEE802 | IEEE 802.11ax D4.0: Enhancements for High Efficiency (HE). [IEEE8021 | |||
| 11ax] | 1ax] | |||
| IEEE 802.11be Extreme High Throughput (EHT). [IEEE80211be] | IEEE 802.11be Extreme High Throughput (EHT). [IEEE80211be] | |||
| IEE 802.11ay Enhanced throughput for operation in license-exempt | IEE 802.11ay Enhanced throughput for operation in license-exempt | |||
| bands above 45 GHz. [IEEE80211ay] | bands above 45 GHz. [IEEE8021 | |||
| 1ay] | ||||
| The main 802.11ax and 802.11be capabilities and their relevance to | The main 802.11ax and 802.11be capabilities and their relevance to | |||
| RAW are discussed in the remainder of this document. | RAW are discussed in the remainder of this document. | |||
| 4.2. 802.11ax High Efficiency (HE) | 4.2. 802.11ax High Efficiency (HE) | |||
| 4.2.1. General Characteristics | 4.2.1. General Characteristics | |||
| The next generation Wi-Fi (Wi-Fi 6) is based on the IEEE802.11ax | The next generation Wi-Fi (Wi-Fi 6) is based on the IEEE802.11ax | |||
| amendment [IEEE80211ax], which includes new capabilities to increase | amendment [IEEE80211ax], which includes new capabilities to increase | |||
| skipping to change at page 9, line 27 ¶ | skipping to change at page 9, line 7 ¶ | |||
| 4.2.2. Applicability to deterministic flows | 4.2.2. Applicability to deterministic flows | |||
| TSN capabilities, as defined by the IEEE 802.1 TSN standards, provide | TSN capabilities, as defined by the IEEE 802.1 TSN standards, provide | |||
| the underlying mechanism for supporting deterministic flows in a | the underlying mechanism for supporting deterministic flows in a | |||
| Local Area Network (LAN). The 802.11 working group has already | Local Area Network (LAN). The 802.11 working group has already | |||
| incorporated support for several TSN capabilities, so that time- | incorporated support for several TSN capabilities, so that time- | |||
| sensitive flow can experience precise time synchronization and | sensitive flow can experience precise time synchronization and | |||
| timeliness when operating over 802.11 links. TSN capabilities | timeliness when operating over 802.11 links. TSN capabilities | |||
| supported over 802.11 (which also extends to 802.11ax), include: | supported over 802.11 (which also extends to 802.11ax), include: | |||
| 1. 802.1AS based Time Synchronization (other time synchronization | 1. 802.1AS based Time Synchronization (other time synchronization | |||
| techniques may also be used) | techniques may also be used) | |||
| 2. Interoperating with IEEE802.1Q bridges | 2. Interoperating with IEEE802.1Q bridges | |||
| 3. Time-sensitive Traffic Stream identification | 3. Time-sensitive Traffic Stream identification | |||
| The exiting 802.11 TSN capabilities listed above, and the 802.11ax | The exiting 802.11 TSN capabilities listed above, and the 802.11ax | |||
| OFDMA and scheduled access provide a new set of tools to better | OFDMA and scheduled access provide a new set of tools to better | |||
| server time-sensitive flows. However, it is important to understand | server time-sensitive flows. However, it is important to understand | |||
| the tradeoffs and constraints associated with such capabilities, as | the tradeoffs and constraints associated with such capabilities, as | |||
| well as redundancy and diversity mechanisms that can be used to | well as redundancy and diversity mechanisms that can be used to | |||
| provide more predictable and reliable performance. | provide more predictable and reliable performance. | |||
| 4.2.2.1. 802.11 Managed network operation and admission control | 4.2.2.1. 802.11 Managed network operation and admission control | |||
| skipping to change at page 11, line 5 ¶ | skipping to change at page 10, line 35 ¶ | |||
| throughput (at least 30 Gbps), as well as enhancements to worst case | throughput (at least 30 Gbps), as well as enhancements to worst case | |||
| latency and jitter. It is also expected to improve the integration | latency and jitter. It is also expected to improve the integration | |||
| with 802.1 TSN to support time-sensitive applications over Ethernet | with 802.1 TSN to support time-sensitive applications over Ethernet | |||
| and Wireless LANs. | and Wireless LANs. | |||
| The 802.11be Task Group started its operation in May 2019, therefore, | The 802.11be Task Group started its operation in May 2019, therefore, | |||
| detailed information about specific features is not yet available. | detailed information about specific features is not yet available. | |||
| Only high level candidate features have been discussed so far, | Only high level candidate features have been discussed so far, | |||
| including: | including: | |||
| 1. 320MHz bandwidth and more efficient utilization of non- | 1. 320MHz bandwidth and more efficient utilization of non-contiguous | |||
| contiguous spectrum. | spectrum. | |||
| 2. Multi-band/multi-channel aggregation and operation. | 2. Multi-band/multi-channel aggregation and operation. | |||
| 3. 16 spatial streams and related MIMO enhancements. | 3. 16 spatial streams and related MIMO enhancements. | |||
| 4. Multi-Access Point (AP) Coordination. | 4. Multi-Access Point (AP) Coordination. | |||
| 5. Enhanced link adaptation and retransmission protocol, e.g. | 5. Enhanced link adaptation and retransmission protocol, e.g. | |||
| Hybrid Automatic Repeat Request (HARQ). | Hybrid Automatic Repeat Request (HARQ). | |||
| 6. Any required adaptations to regulatory rules for the 6 GHz | 6. Any required adaptations to regulatory rules for the 6 GHz | |||
| spectrum. | spectrum. | |||
| 4.3.2. Applicability to deterministic flows | 4.3.2. Applicability to deterministic flows | |||
| The 802.11 Real-Time Applications (RTA) Topic Interest Group (TIG) | The 802.11 Real-Time Applications (RTA) Topic Interest Group (TIG) | |||
| provided detailed information on use cases, issues and potential | provided detailed information on use cases, issues and potential | |||
| solution directions to improve support for time-sensitive | solution directions to improve support for time-sensitive | |||
| applications in 802.11. The RTA TIG report [IEEE_doc_11-18-2009-06] | applications in 802.11. The RTA TIG report [IEEE_doc_11-18-2009-06] | |||
| was used as input to the 802.11be project scope. | was used as input to the 802.11be project scope. | |||
| Improvements for worst-case latency, jitter and reliability were the | Improvements for worst-case latency, jitter and reliability were the | |||
| skipping to change at page 14, line 28 ¶ | skipping to change at page 14, line 17 ¶ | |||
| functions, and end-to-end secured IPv6/CoAP connectivity. | functions, and end-to-end secured IPv6/CoAP connectivity. | |||
| The 6TiSCH architecture [I-D.ietf-6tisch-architecture] identifies | The 6TiSCH architecture [I-D.ietf-6tisch-architecture] identifies | |||
| different models to schedule resources along so-called Tracks (see | different models to schedule resources along so-called Tracks (see | |||
| Section 5.2.2.2) exploiting the TSCH schedule structure however the | Section 5.2.2.2) exploiting the TSCH schedule structure however the | |||
| focus at 6TiSCH is on best effort traffic and the group was never | focus at 6TiSCH is on best effort traffic and the group was never | |||
| chartered to produce standard work related to Tracks. | chartered to produce standard work related to Tracks. | |||
| Useful References include: | Useful References include: | |||
| 1. IEEE Std 802.15.4: "IEEE Std. 802.15.4, Part. 15.4: Wireless | 1. IEEE Std 802.15.4: "IEEE Std. 802.15.4, Part. 15.4: Wireless | |||
| Medium Access Control (MAC) and Physical Layer (PHY) | Medium Access Control (MAC) and Physical Layer (PHY) | |||
| Specifications for Low-Rate Wireless Personal Area Networks" | Specifications for Low-Rate Wireless Personal Area Networks" | |||
| [IEEE802154]. The latest version at the time of this writing is | [IEEE802154]. The latest version at the time of this writing is | |||
| dated year 2015. | dated year 2015. | |||
| 2. Morell, A. , Vilajosana, X. , Vicario, J. L. and Watteyne, T. | 2. Morell, A. , Vilajosana, X. , Vicario, J. L. and Watteyne, T. | |||
| (2013), Label switching over IEEE802.15.4e networks. Trans. | (2013), Label switching over IEEE802.15.4e networks. Trans. | |||
| Emerging Tel. Tech., 24: 458-475. doi:10.1002/ett.2650" | Emerging Tel. Tech., 24: 458-475. doi:10.1002/ett.2650" | |||
| [morell13]. | [morell13]. | |||
| 3. De Armas, J., Tuset, P., Chang, T., Adelantado, F., Watteyne, | 3. De Armas, J., Tuset, P., Chang, T., Adelantado, F., Watteyne, T., | |||
| T., Vilajosana, X. (2016, September). Determinism through path | Vilajosana, X. (2016, September). Determinism through path | |||
| diversity: Why packet replication makes sense. In 2016 | diversity: Why packet replication makes sense. In 2016 | |||
| International Conference on Intelligent Networking and | International Conference on Intelligent Networking and | |||
| Collaborative Systems (INCoS) (pp. 150-154). IEEE. [dearmas16]. | Collaborative Systems (INCoS) (pp. 150-154). IEEE. [dearmas16]. | |||
| 4. X. Vilajosana, T. Watteyne, M. Vucinic, T. Chang and K. S. | 4. X. Vilajosana, T. Watteyne, M. Vucinic, T. Chang and K. S. | |||
| J. Pister, "6TiSCH: Industrial Performance for IPv6 Internet- | J. Pister, "6TiSCH: Industrial Performance for IPv6 Internet-of- | |||
| of-Things Networks," in Proceedings of the IEEE, vol. 107, no. | Things Networks," in Proceedings of the IEEE, vol. 107, no. 6, | |||
| 6, pp. 1153-1165, June 2019. [vilajosana19]. | pp. 1153-1165, June 2019. [vilajosana19]. | |||
| 5.2. TimeSlotted Channel Hopping | 5.2. TimeSlotted Channel Hopping | |||
| 5.2.1. General Characteristics | 5.2.1. General Characteristics | |||
| As a core technique in IEEE802.15.4, TSCH splits time in multiple | As a core technique in IEEE802.15.4, TSCH splits time in multiple | |||
| time slots that repeat over time. A set of timeslots constructs a | time slots that repeat over time. A set of timeslots constructs a | |||
| Slotframe (see Section 5.2.2.1.4). For each timeslot, a set of | Slotframe (see Section 5.2.2.1.4). For each timeslot, a set of | |||
| available frequencies can be used, resulting in a matrix-like | available frequencies can be used, resulting in a matrix-like | |||
| schedule (see Figure 1). | schedule (see Figure 1). | |||
| skipping to change at page 15, line 36 ¶ | skipping to change at page 15, line 26 ¶ | |||
| ... +-----+ | ... +-----+ | |||
| | | | | |||
| +-------------------------------------------------+ | | +-------------------------------------------------+ | | |||
| | | | | | | | | | | | +-----+ | | | | | | | | | | | | +-----+ | |||
| CH-15| |A->B| | | | |A->B| | | | | A | | CH-15| |A->B| | | | |A->B| | | | | A | | |||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |||
| +-------------------------------------------------+ +-----+ | +-------------------------------------------------+ +-----+ | |||
| ch. | ch. | |||
| offset | offset | |||
| Figure 1: Slotframe example with scheduled cells between nodes A, B | Figure 1: Slotframe example with scheduled cells between nodes A, | |||
| and C | B and C | |||
| This schedule represents the possible communications of a node with | This schedule represents the possible communications of a node with | |||
| its neighbors, and is managed by a Scheduling Function such as the | its neighbors, and is managed by a Scheduling Function such as the | |||
| Minimal Scheduling Function (MSF) [I-D.ietf-6tisch-msf]. Each cell | Minimal Scheduling Function (MSF) [I-D.ietf-6tisch-msf]. Each cell | |||
| in the schedule is identified by its slotoffset and channeloffset | in the schedule is identified by its slotoffset and channeloffset | |||
| coordinates. A cell's timeslot offset indicates its position in | coordinates. A cell's timeslot offset indicates its position in | |||
| time, relative to the beginning of the slotframe. A cell's channel | time, relative to the beginning of the slotframe. A cell's channel | |||
| offset is an index which maps to a frequency at each iteration of the | offset is an index which maps to a frequency at each iteration of the | |||
| slotframe. Each packet exchanged between neighbors happens within | slotframe. Each packet exchanged between neighbors happens within | |||
| one cell. The size of a cell is a timeslot duration, between 10 to | one cell. The size of a cell is a timeslot duration, between 10 to | |||
| skipping to change at page 17, line 30 ¶ | skipping to change at page 17, line 19 ¶ | |||
| added, modified, or removed, for instance if it appears that a Track | added, modified, or removed, for instance if it appears that a Track | |||
| does not perform as expected for, say, Packet Delivery Ratio (PDR). | does not perform as expected for, say, Packet Delivery Ratio (PDR). | |||
| For that case, the expectation is that a protocol that flows along a | For that case, the expectation is that a protocol that flows along a | |||
| Track (to be), in a fashion similar to classical Traffic Engineering | Track (to be), in a fashion similar to classical Traffic Engineering | |||
| (TE) [CCAMP], may be used to update the state in the devices. 6TiSCH | (TE) [CCAMP], may be used to update the state in the devices. 6TiSCH | |||
| provides means for a device to negotiate a timeSlot with a neighbor, | provides means for a device to negotiate a timeSlot with a neighbor, | |||
| but in general that flow was not designed and no protocol was | but in general that flow was not designed and no protocol was | |||
| selected and it is expected that DetNet will determine the | selected and it is expected that DetNet will determine the | |||
| appropriate end-to-end protocols to be used in that case. | appropriate end-to-end protocols to be used in that case. | |||
| Stream Management Entity | Stream Management Entity | |||
| Operational Control System and HMI | Operational Control System and HMI | |||
| -+-+-+-+-+-+-+ Northbound -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | -+-+-+-+-+-+-+ Northbound -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | |||
| PCE PCE PCE PCE | PCE PCE PCE PCE | |||
| -+-+-+-+-+-+-+ Southbound -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | -+-+-+-+-+-+-+ Southbound -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | |||
| --- 6TiSCH------6TiSCH------6TiSCH------6TiSCH-- | --- 6TiSCH------6TiSCH------6TiSCH------6TiSCH-- | |||
| 6TiSCH / Device Device Device Device \ | 6TiSCH / Device Device Device Device \ | |||
| Device- - 6TiSCH | Device- - 6TiSCH | |||
| \ 6TiSCH 6TiSCH 6TiSCH 6TiSCH / Device | \ 6TiSCH 6TiSCH 6TiSCH 6TiSCH / Device | |||
| ----Device------Device------Device------Device-- | ----Device------Device------Device------Device-- | |||
| Figure 2 | Figure 2 | |||
| 5.2.2.1.1. Packet Marking and Handling | 5.2.2.1.1. Packet Marking and Handling | |||
| Section "Packet Marking and Handling" of | Section "Packet Marking and Handling" of | |||
| [I-D.ietf-6tisch-architecture] describes the packet tagging and | [I-D.ietf-6tisch-architecture] describes the packet tagging and | |||
| marking that is expected in 6TiSCH networks. | marking that is expected in 6TiSCH networks. | |||
| 5.2.2.1.1.1. Tagging Packets for Flow Identification | 5.2.2.1.1.1. Tagging Packets for Flow Identification | |||
| For packets that are routed by a PCE along a Track, the tuple formed | For packets that are routed by a PCE along a Track, the tuple formed | |||
| skipping to change at page 18, line 41 ¶ | skipping to change at page 18, line 28 ¶ | |||
| S to reach R. A simple way to benefit from this topology could be to | S to reach R. A simple way to benefit from this topology could be to | |||
| use the two independent paths via nodes A, C, E and via B, D, F. But | use the two independent paths via nodes A, C, E and via B, D, F. But | |||
| more complex paths are possible as well. | more complex paths are possible as well. | |||
| (A) (C) (E) | (A) (C) (E) | |||
| source (S) (R) (destination) | source (S) (R) (destination) | |||
| (B) (D) (F) | (B) (D) (F) | |||
| Figure 3: A Typical Ladder Shape with Two Parallel Paths Toward the | Figure 3: A Typical Ladder Shape with Two Parallel Paths Toward | |||
| Destination | the Destination | |||
| By employing a Packet Replication function, each node forwards a copy | By employing a Packet Replication function, each node forwards a copy | |||
| of each data packet over two different branches. For instance, in | of each data packet over two different branches. For instance, in | |||
| Figure 4, the source node S transmits the data packet to nodes A and | Figure 4, the source node S transmits the data packet to nodes A and | |||
| B, in two different timeslots within the same TSCH slotframe. | B, in two different timeslots within the same TSCH slotframe. | |||
| ===> (A) => (C) => (E) === | ===> (A) => (C) => (E) === | |||
| // \\// \\// \\ | // \\// \\// \\ | |||
| source (S) //\\ //\\ (R) (destination) | source (S) //\\ //\\ (R) (destination) | |||
| \\ // \\ // \\ // | \\ // \\ // \\ // | |||
| ===> (B) => (D) => (F) === | ===> (B) => (D) => (F) === | |||
| Figure 4: Packet Replication: S transmits twice the same data packet, | Figure 4: Packet Replication: S transmits twice the same data | |||
| to its DP (A) and to its AP (B). | packet, to its DP (A) and to its AP (B). | |||
| By employing Packet Elimination function once a node receives the | By employing Packet Elimination function once a node receives the | |||
| first copy of a data packet, it discards the subsequent copies. | first copy of a data packet, it discards the subsequent copies. | |||
| Because the first copy that reaches a node is the one that matters, | Because the first copy that reaches a node is the one that matters, | |||
| it is the only copy that will be forwarded upward. | it is the only copy that will be forwarded upward. | |||
| Considering that the wireless medium is broadcast by nature, any | Considering that the wireless medium is broadcast by nature, any | |||
| neighbor of a transmitter may overhear a transmission. By employing | neighbor of a transmitter may overhear a transmission. By employing | |||
| the Promiscuous Overhearing function, nodes will have multiple | the Promiscuous Overhearing function, nodes will have multiple | |||
| opportunities to receive a given data packet. For instance, in | opportunities to receive a given data packet. For instance, in | |||
| skipping to change at page 19, line 35 ¶ | skipping to change at page 19, line 21 ¶ | |||
| 6TiSCH expects elimination and replication of packets along a complex | 6TiSCH expects elimination and replication of packets along a complex | |||
| Track, but has no position about how the sequence numbers would be | Track, but has no position about how the sequence numbers would be | |||
| tagged in the packet. | tagged in the packet. | |||
| As it goes, 6TiSCH expects that timeSlots corresponding to copies of | As it goes, 6TiSCH expects that timeSlots corresponding to copies of | |||
| a same packet along a Track are correlated by configuration, and does | a same packet along a Track are correlated by configuration, and does | |||
| not need to process the sequence numbers. | not need to process the sequence numbers. | |||
| The semantics of the configuration MUST enable correlated timeSlots | The semantics of the configuration MUST enable correlated timeSlots | |||
| to be grouped for transmit (and respectively receive) with a 'OR' | to be grouped for transmit (and respectively receive) with | |||
| relations, and then a 'AND' relation MUST be configurable between | a'OR'relations, and then a'AND'relation MUST be configurable between | |||
| groups. The semantics is that if the transmit (and respectively | groups. The semantics is that if the transmit (and respectively | |||
| receive) operation succeeded in one timeSlot in a 'OR' group, then | receive) operation succeeded in one timeSlot in a'OR'group, then all | |||
| all the other timeSLots in the group are ignored. Now, if there are | the other timeSLots in the group are ignored. Now, if there are at | |||
| at least two groups, the 'AND' relation between the groups indicates | least two groups, the'AND'relation between the groups indicates that | |||
| that one operation must succeed in each of the groups. | one operation must succeed in each of the groups. | |||
| On the transmit side, timeSlots provisioned for retries along a same | On the transmit side, timeSlots provisioned for retries along a same | |||
| branch of a Track are placed a same 'OR' group. The 'OR' relation | branch of a Track are placed a same'OR'group. The'OR'relation | |||
| indicates that if a transmission is acknowledged, then further | indicates that if a transmission is acknowledged, then further | |||
| transmissions SHOULD NOT be attempted for timeSlots in that group. | transmissions SHOULD NOT be attempted for timeSlots in that group. | |||
| There are as many 'OR' groups as there are branches of the Track | There are as many'OR'groups as there are branches of the Track | |||
| departing from this node. Different 'OR' groups are programmed for | departing from this node. Different'OR'groups are programmed for the | |||
| the purpose of replication, each group corresponding to one branch of | purpose of replication, each group corresponding to one branch of the | |||
| the Track. The 'AND' relation between the groups indicates that | Track. The'AND'relation between the groups indicates that | |||
| transmission over any of branches MUST be attempted regardless of | transmission over any of branches MUST be attempted regardless of | |||
| whether a transmission succeeded in another branch. It is also | whether a transmission succeeded in another branch. It is also | |||
| possible to place cells to different next-hop routers in a same 'OR' | possible to place cells to different next-hop routers in a | |||
| group. This allows to route along multi-path Tracks, trying one | same'OR'group. This allows to route along multi-path Tracks, trying | |||
| next-hop and then another only if sending to the first fails. | one next-hop and then another only if sending to the first fails. | |||
| On the receive side, all timeSlots are programmed in a same 'OR' | On the receive side, all timeSlots are programmed in a same'OR'group. | |||
| group. Retries of a same copy as well as converging branches for | Retries of a same copy as well as converging branches for elimination | |||
| elimination are converged, meaning that the first successful | are converged, meaning that the first successful reception is enough | |||
| reception is enough and that all the other timeSlots can be ignored. | and that all the other timeSlots can be ignored. | |||
| 5.2.2.1.1.3. Differentiated Services Per-Hop-Behavior | 5.2.2.1.1.3. Differentiated Services Per-Hop-Behavior | |||
| Additionally, an IP packet that is sent along a Track uses the | Additionally, an IP packet that is sent along a Track uses the | |||
| Differentiated Services Per-Hop-Behavior Group called Deterministic | Differentiated Services Per-Hop-Behavior Group called Deterministic | |||
| Forwarding, as described in | Forwarding, as described in | |||
| [I-D.svshah-tsvwg-deterministic-forwarding]. | [I-D.svshah-tsvwg-deterministic-forwarding]. | |||
| 5.2.2.1.2. Topology and capabilities | 5.2.2.1.2. Topology and capabilities | |||
| skipping to change at page 24, line 9 ¶ | skipping to change at page 23, line 34 ¶ | |||
| branches. PRE may be used to complement layer-2 Automatic Repeat | branches. PRE may be used to complement layer-2 Automatic Repeat | |||
| reQuest (ARQ) and receiver-end Ordering to form the PAREO functions. | reQuest (ARQ) and receiver-end Ordering to form the PAREO functions. | |||
| PAREO functions enable to meet industrial expectations in PDR within | PAREO functions enable to meet industrial expectations in PDR within | |||
| bounded delivery time over a Track that includes wireless links, even | bounded delivery time over a Track that includes wireless links, even | |||
| when the Track extends beyond the 6TiSCH network. | when the Track extends beyond the 6TiSCH network. | |||
| +-----+ | +-----+ | |||
| | IoT | | | IoT | | |||
| | G/W | | | G/W | | |||
| +-----+ | +-----+ | |||
| ^ <---- Elimination | ^ <---- Elimination | |||
| | | | | | | |||
| Track branch | | | Track branch | | | |||
| +-------+ +--------+ Subnet Backbone | +-------+ +--------+ Subnet Backbone | |||
| | | | | | | |||
| +--|--+ +--|--+ | +--|--+ +--|--+ | |||
| | | | Backbone | | | Backbone | | | | Backbone | | | Backbone | |||
| o | | | router | | | router | o | | | router | | | router | |||
| +--/--+ +--|--+ | +--/--+ +--|--+ | |||
| o / o o---o----/ o | o / o o---o----/ o | |||
| o o---o--/ o o o o o | o o---o--/ o o o o o | |||
| o \ / o o LLN o | o \ / o o LLN o | |||
| o v <---- Replication | o v <---- Replication | |||
| o | o | |||
| Figure 6: End-to-End deterministic Track | Figure 6: End-to-End deterministic Track | |||
| In the example above (see Figure 6), a Track is laid out from a field | In the example above (see Figure 6), a Track is laid out from a field | |||
| device in a 6TiSCH network to an IoT gateway that is located on a | device in a 6TiSCH network to an IoT gateway that is located on a | |||
| IEEE802.1 TSN backbone. | IEEE802.1 TSN backbone. | |||
| The Replication function in the field device sends a copy of each | The Replication function in the field device sends a copy of each | |||
| packet over two different branches, and a PCE schedules each hop of | packet over two different branches, and a PCE schedules each hop of | |||
| both branches so that the two copies arrive in due time at the | both branches so that the two copies arrive in due time at the | |||
| gateway. In case of a loss on one branch, hopefully the other copy | gateway. In case of a loss on one branch, hopefully the other copy | |||
| of the packet still makes it in due time. If two copies make it to | of the packet still makes it in due time. If two copies make it to | |||
| skipping to change at page 28, line 20 ¶ | skipping to change at page 27, line 44 ¶ | |||
| +--------------+ | | | +--------------+ | | | |||
| | 6LoWPAN HC | | | | | 6LoWPAN HC | | | | |||
| +--------------+ ingress egress | +--------------+ ingress egress | |||
| | 6top | sets +----+ +----+ restores | | 6top | sets +----+ +----+ restores | |||
| +--------------+ dmac to | | | | dmac to | +--------------+ dmac to | | | | dmac to | |||
| | TSCH MAC | brdcst | | | | self | | TSCH MAC | brdcst | | | | self | |||
| +--------------+ | | | | | | | +--------------+ | | | | | | | |||
| | LLN PHY | +-------+ +--...-----+ +-------+ | | LLN PHY | +-------+ +--...-----+ +-------+ | |||
| +--------------+ | +--------------+ | |||
| Figure 7: Track Forwarding, Transport Mode | Figure 7: Track Forwarding, Transport Mode | |||
| 5.2.2.2.2.2. Tunnel Mode | 5.2.2.2.2.2. Tunnel Mode | |||
| In tunnel mode, the frames originate from an arbitrary protocol over | In tunnel mode, the frames originate from an arbitrary protocol over | |||
| a compatible MAC that may or may not be synchronized with the 6TiSCH | a compatible MAC that may or may not be synchronized with the 6TiSCH | |||
| network. An example of this would be a router with a dual radio that | network. An example of this would be a router with a dual radio that | |||
| is capable of receiving and sending WirelessHART or ISA100.11a frames | is capable of receiving and sending WirelessHART or ISA100.11a frames | |||
| with the second radio, by presenting itself as an Access Point or a | with the second radio, by presenting itself as an Access Point or a | |||
| Backbone Router, respectively. | Backbone Router, respectively. | |||
| skipping to change at page 34, line 22 ¶ | skipping to change at page 33, line 42 ¶ | |||
| 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. | |||
| 10. Contributors | 10. Contributors | |||
| Georgios Z. Papadopoulos: Contributed to the TSCH section. | Georgios Z. Papadopoulos: Contributed to the TSCH section. | |||
| Nils Maeurer: Contributed to the LDACS section. | Nils Mäurer: Contributed to the LDACS section. | |||
| Thomas Graeupl: Contributed to the LDACS section. | Thomas Gräupl: Contributed to the LDACS section. | |||
| 11. Acknowledgments | 11. Acknowledgments | |||
| Many thanks to the participants of the RAW WG where a lot of the work | Many thanks to the participants of the RAW WG where a lot of the work | |||
| discussed here happened. | discussed here happened. | |||
| 12. References | 12. Normative References | |||
| 12.1. Normative References | ||||
| [I-D.ietf-6tisch-architecture] | ||||
| Thubert, P., "An Architecture for IPv6 over the TSCH mode | ||||
| of IEEE 802.15.4", draft-ietf-6tisch-architecture-23 (work | ||||
| in progress), June 2019. | ||||
| [I-D.ietf-detnet-architecture] | ||||
| Finn, N., Thubert, P., Varga, B., and J. Farkas, | ||||
| "Deterministic Networking Architecture", draft-ietf- | ||||
| detnet-architecture-13 (work in progress), May 2019. | ||||
| [RFC5673] Pister, K., Ed., Thubert, P., Ed., Dwars, S., and T. | [RFC8480] Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH | |||
| Phinney, "Industrial Routing Requirements in Low-Power and | Operation Sublayer (6top) Protocol (6P)", RFC 8480, | |||
| Lossy Networks", RFC 5673, DOI 10.17487/RFC5673, October | DOI 10.17487/RFC8480, November 2018, | |||
| 2009, <https://www.rfc-editor.org/info/rfc5673>. | <https://www.rfc-editor.org/info/rfc8480>. | |||
| [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | |||
| (IPv6) Specification", STD 86, RFC 8200, | (IPv6) Specification", STD 86, RFC 8200, | |||
| DOI 10.17487/RFC8200, July 2017, | DOI 10.17487/RFC8200, July 2017, | |||
| <https://www.rfc-editor.org/info/rfc8200>. | <https://www.rfc-editor.org/info/rfc8200>. | |||
| [RFC8480] Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH | [RFC5673] Pister, K., Ed., Thubert, P., Ed., Dwars, S., and T. | |||
| Operation Sublayer (6top) Protocol (6P)", RFC 8480, | Phinney, "Industrial Routing Requirements in Low-Power and | |||
| DOI 10.17487/RFC8480, November 2018, | Lossy Networks", RFC 5673, DOI 10.17487/RFC5673, October | |||
| <https://www.rfc-editor.org/info/rfc8480>. | 2009, <https://www.rfc-editor.org/info/rfc5673>. | |||
| 12.2. Informative References | ||||
| [Cavalcanti_2019] | [I-D.ietf-detnet-architecture] | |||
| Dave Cavalcanti et al., "Extending Time Distribution and | Finn, N., Thubert, P., Varga, B., and J. Farkas, | |||
| Timeliness Capabilities over the Air to Enable Future | "Deterministic Networking Architecture", Work in Progress, | |||
| Wireless Industrial Automation Systems, the Proceedings of | Internet-Draft, draft-ietf-detnet-architecture-13, 6 May | |||
| IEEE", June 2019. | 2019, <https://tools.ietf.org/html/draft-ietf-detnet- | |||
| architecture-13>. | ||||
| [CCAMP] IETF, "Common Control and Measurement Plane", | [I-D.ietf-6tisch-architecture] | |||
| <https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>. | Thubert, P., "An Architecture for IPv6 over the TSCH mode | |||
| of IEEE 802.15.4", Work in Progress, Internet-Draft, | ||||
| draft-ietf-6tisch-architecture-28, 29 October 2019, | ||||
| <https://tools.ietf.org/html/draft-ietf-6tisch- | ||||
| architecture-28>. | ||||
| [dearmas16] | 13. Informative References | |||
| Jesica de Armas et al., "Determinism through path | ||||
| diversity: Why packet replication makes sense", September | ||||
| 2016. | ||||
| [Ghasempour_2017] | [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., | |||
| Yasaman Ghasempour et al., "802.11ay: Next-Generation 60 | Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, | |||
| GHz Communications for 100 Gb/s Wi-Fi", December 2017. | JP., and R. Alexander, "RPL: IPv6 Routing Protocol for | |||
| Low-Power and Lossy Networks", RFC 6550, | ||||
| DOI 10.17487/RFC6550, March 2012, | ||||
| <https://www.rfc-editor.org/info/rfc6550>. | ||||
| [GRA11] Graeupl, T. and M. Ehammer, "L-DACS1 Data Link Layer | [RFC6551] Vasseur, JP., Ed., Kim, M., Ed., Pister, K., Dejean, N., | |||
| Evolution of ATN/IPS", Proceedings of the 30th IEEE/AIAA | and D. Barthel, "Routing Metrics Used for Path Calculation | |||
| Digital Avionics Systems Conference (DASC) Seattle, WA, | in Low-Power and Lossy Networks", RFC 6551, | |||
| USA, October 2011. | DOI 10.17487/RFC6551, March 2012, | |||
| <https://www.rfc-editor.org/info/rfc6551>. | ||||
| [GRA18] al., T. G. E., "L-band Digital Aeronautical Communications | [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, | |||
| System (LDACS) flight trials in the national German | D., and S. Mansfield, "Guidelines for the Use of the "OAM" | |||
| project MICONAV", Proceedings of the Integrated | Acronym in the IETF", BCP 161, RFC 6291, | |||
| Communications, Navigation, Surveillance Conference | DOI 10.17487/RFC6291, June 2011, | |||
| (ICNS) Herndon, VA, USA, April 2018. | <https://www.rfc-editor.org/info/rfc6291>. | |||
| [GRA19] Graeupl, T., Rihacek, C., and B. Haindl, "LDACS A/G | [RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. | |||
| Specification", SESAR2020 PJ14-02-01 D3.3.010, February | Weingarten, "An Overview of Operations, Administration, | |||
| 2019. | and Maintenance (OAM) Tools", RFC 7276, | |||
| DOI 10.17487/RFC7276, June 2014, | ||||
| <https://www.rfc-editor.org/info/rfc7276>. | ||||
| [I-D.ietf-6tisch-coap] | [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., | |||
| Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and | Przygienda, T., and S. Aldrin, "Multicast Using Bit Index | |||
| Interaction using CoAP", draft-ietf-6tisch-coap-03 (work | Explicit Replication (BIER)", RFC 8279, | |||
| in progress), March 2015. | DOI 10.17487/RFC8279, November 2017, | |||
| <https://www.rfc-editor.org/info/rfc8279>. | ||||
| [I-D.ietf-6tisch-msf] | [I-D.ietf-6tisch-msf] | |||
| 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)", | |||
| draft-ietf-6tisch-msf-03 (work in progress), April 2019. | Work in Progress, Internet-Draft, draft-ietf-6tisch-msf- | |||
| 10, 13 December 2019, | ||||
| [I-D.ietf-bier-te-arch] | <https://tools.ietf.org/html/draft-ietf-6tisch-msf-10>. | |||
| Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic | ||||
| Engineering for Bit Index Explicit Replication (BIER-TE)", | ||||
| draft-ietf-bier-te-arch-02 (work in progress), May 2019. | ||||
| [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, "RPL DAG Metric Container Node State and | Thubert, "Common Ancestor Objective Functions and Parent | |||
| Attribute object type extension", draft-ietf-roll-nsa- | Set DAG Metric Container Extension", Work in Progress, | |||
| extension-03 (work in progress), June 2019. | Internet-Draft, draft-ietf-roll-nsa-extension-05, 4 | |||
| November 2019, <https://tools.ietf.org/html/draft-ietf- | ||||
| roll-nsa-extension-05>. | ||||
| [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", draft-papadopoulos-paw-pre- | Complex Tracks in LLNs", Work in Progress, Internet-Draft, | |||
| reqs-01 (work in progress), March 2019. | draft-papadopoulos-paw-pre-reqs-01, 25 March 2019, | |||
| <https://tools.ietf.org/html/draft-papadopoulos-paw-pre- | ||||
| reqs-01>. | ||||
| [I-D.svshah-tsvwg-deterministic-forwarding] | [I-D.thubert-bier-replication-elimination] | |||
| Shah, S. and P. Thubert, "Deterministic Forwarding PHB", | Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER- | |||
| draft-svshah-tsvwg-deterministic-forwarding-04 (work in | TE extensions for Packet Replication and Elimination | |||
| progress), August 2015. | Function (PREF) and OAM", Work in Progress, Internet- | |||
| Draft, draft-thubert-bier-replication-elimination-03, 3 | ||||
| March 2018, <https://tools.ietf.org/html/draft-thubert- | ||||
| bier-replication-elimination-03>. | ||||
| [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", draft-thubert-6lo-bier-dispatch-06 | 6loRH for BitStrings", Work in Progress, Internet-Draft, | |||
| (work in progress), January 2019. | draft-thubert-6lo-bier-dispatch-06, 28 January 2019, | |||
| <https://tools.ietf.org/html/draft-thubert-6lo-bier- | ||||
| dispatch-06>. | ||||
| [I-D.thubert-bier-replication-elimination] | [I-D.ietf-bier-te-arch] | |||
| Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER- | Eckert, T., Cauchie, G., and M. Menth, "Traffic | |||
| TE extensions for Packet Replication and Elimination | Engineering for Bit Index Explicit Replication (BIER-TE)", | |||
| Function (PREF) and OAM", draft-thubert-bier-replication- | Work in Progress, Internet-Draft, draft-ietf-bier-te-arch- | |||
| elimination-03 (work in progress), March 2018. | 05, 1 November 2019, | |||
| <https://tools.ietf.org/html/draft-ietf-bier-te-arch-05>. | ||||
| [ICAO18] International Civil Aviation Organization (ICAO), "L-Band | [I-D.ietf-6tisch-coap] | |||
| Digital Aeronautical Communication System (LDACS)", | Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and | |||
| International Standards and Recommended Practices Annex 10 | Interaction using CoAP", Work in Progress, Internet-Draft, | |||
| - Aeronautical Telecommunications, Vol. III - | draft-ietf-6tisch-coap-03, 9 March 2015, | |||
| Communication Systems, July 2018. | <https://tools.ietf.org/html/draft-ietf-6tisch-coap-03>. | |||
| [I-D.svshah-tsvwg-deterministic-forwarding] | ||||
| Shah, S. and P. Thubert, "Deterministic Forwarding PHB", | ||||
| Work in Progress, Internet-Draft, draft-svshah-tsvwg- | ||||
| deterministic-forwarding-04, 30 August 2015, | ||||
| <https://tools.ietf.org/html/draft-svshah-tsvwg- | ||||
| deterministic-forwarding-04>. | ||||
| [IEEE802154] | ||||
| IEEE standard for Information Technology, "IEEE Std. | ||||
| 802.15.4, Part. 15.4: Wireless Medium Access Control (MAC) | ||||
| and Physical Layer (PHY) Specifications for Low-Rate | ||||
| Wireless Personal Area Networks". | ||||
| [IEEE80211] | [IEEE80211] | |||
| "IEEE Standard 802.11 - IEEE Standard for Information | "IEEE Standard 802.11 - IEEE Standard for Information | |||
| Technology - Telecommunications and information exchange | Technology - Telecommunications and information exchange | |||
| between systems Local and metropolitan area networks - | between systems Local and metropolitan area networks - | |||
| Specific requirements - Part 11: Wireless LAN Medium | Specific requirements - Part 11: Wireless LAN Medium | |||
| Access Control (MAC) and Physical Layer (PHY) | Access Control (MAC) and Physical Layer (PHY) | |||
| Specifications.". | Specifications.". | |||
| [IEEE80211ad] | ||||
| "802.11ad: Enhancements for very high throughput in the 60 | ||||
| GHz band". | ||||
| [IEEE80211ak] | [IEEE80211ak] | |||
| "802.11ak: Enhancements for Transit Links Within Bridged | "802.11ak: Enhancements for Transit Links Within Bridged | |||
| Networks", 2017. | Networks", 2017. | |||
| [IEEE80211ax] | [IEEE80211ax] | |||
| "802.11ax D4.0: Enhancements for High Efficiency WLAN". | "802.11ax D4.0: Enhancements for High Efficiency WLAN". | |||
| [IEEE80211ay] | [IEEE80211ay] | |||
| "802.11ay: Enhanced throughput for operation in license- | "802.11ay: Enhanced throughput for operation in license- | |||
| exempt bands above 45 GHz". | exempt bands above 45 GHz". | |||
| [IEEE80211ad] | ||||
| "802.11ad: Enhancements for very high throughput in the 60 | ||||
| GHz band". | ||||
| [IEEE80211be] | [IEEE80211be] | |||
| "802.11be: Extreme High Throughput". | "802.11be: Extreme High Throughput". | |||
| [IEEE802154] | ||||
| IEEE standard for Information Technology, "IEEE Std. | ||||
| 802.15.4, Part. 15.4: Wireless Medium Access Control (MAC) | ||||
| and Physical Layer (PHY) Specifications for Low-Rate | ||||
| Wireless Personal Area Networks". | ||||
| [IEEE8021Qat] | [IEEE8021Qat] | |||
| "802.1Qat: Stream Reservation Protocol". | "802.1Qat: Stream Reservation Protocol". | |||
| [IEEE8021Qcc] | [IEEE8021Qcc] | |||
| "802.1Qcc: IEEE Standard for Local and Metropolitan Area | "802.1Qcc: 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". | Performance Improvements". | |||
| [Cavalcanti_2019] | ||||
| Dave Cavalcanti et al., "Extending Time Distribution and | ||||
| Timeliness Capabilities over the Air to Enable Future | ||||
| Wireless Industrial Automation Systems, the Proceedings of | ||||
| IEEE", June 2019. | ||||
| [Nitsche_2015] | ||||
| Thomas Nitsche et al., "IEEE 802.11ad: directional 60 GHz | ||||
| communication for multi-Gigabit-per-second Wi-Fi", | ||||
| December 2014. | ||||
| [Ghasempour_2017] | ||||
| Yasaman Ghasempour et al., "802.11ay: Next-Generation 60 | ||||
| GHz Communications for 100 Gb/s Wi-Fi", December 2017. | ||||
| [IEEE_doc_11-18-2009-06] | [IEEE_doc_11-18-2009-06] | |||
| "802.11 Real-Time Applications (RTA) Topic Interest Group | "802.11 Real-Time Applications (RTA) Topic Interest Group | |||
| (TIG) Report", November 2018. | (TIG) Report", November 2018. | |||
| [IEEE_doc_11-19-0373-00] | [IEEE_doc_11-19-0373-00] | |||
| Kevin Stanton et Al., "Time-Sensitive Applications Support | Kevin Stanton et Al., "Time-Sensitive Applications Support | |||
| in EHT", March 2019. | in EHT", March 2019. | |||
| [morell13] Antoni Morell et al., "Label switching over IEEE802.15.4e | ||||
| networks", April 2013. | ||||
| [dearmas16] | ||||
| Jesica de Armas et al., "Determinism through path | ||||
| diversity: Why packet replication makes sense", September | ||||
| 2016. | ||||
| [vilajosana19] | ||||
| Xavier Vilajosana et al., "6TiSCH: Industrial Performance | ||||
| for IPv6 Internet-of-Things Networks", June 2019. | ||||
| [ISA100.11a] | [ISA100.11a] | |||
| ISA/IEC, "ISA100.11a, Wireless Systems for Automation, | ISA/IEC, "ISA100.11a, Wireless Systems for Automation, | |||
| also IEC 62734", 2011, < http://www.isa100wci.org/en- | also IEC 62734", 2011, <http://www.isa100wci.org/en- | |||
| US/Documents/PDF/3405-ISA100-WirelessSystems-Future-broch- | US/Documents/PDF/3405-ISA100-WirelessSystems-Future-broch- | |||
| WEB-ETSI.aspx>. | WEB-ETSI.aspx>. | |||
| [MAE19] Maeurer, N. and C. Schmitt, "DLR tests digital | [WirelessHART] | |||
| communications technologies combined with additional | www.hartcomm.org, "Industrial Communication Networks - | |||
| navigation functions for the first time", Proceedings of | Wireless Communication Network and Communication Profiles | |||
| the Integrated Communications, Navigation, Surveillance | - WirelessHART - IEC 62591", 2010. | |||
| Conference (ICNS) Washington D.C., USA, April 2019. | ||||
| [morell13] | ||||
| Antoni Morell et al., "Label switching over IEEE802.15.4e | ||||
| networks", April 2013. | ||||
| [Nitsche_2015] | ||||
| Thomas Nitsche et al., "IEEE 802.11ad: directional 60 GHz | ||||
| communication for multi-Gigabit-per-second Wi-Fi", | ||||
| December 2014. | ||||
| [PCE] IETF, "Path Computation Element", | [PCE] IETF, "Path Computation Element", | |||
| <https://dataTracker.ietf.org/doc/charter-ietf-pce/>. | <https://dataTracker.ietf.org/doc/charter-ietf-pce/>. | |||
| [RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu, | [CCAMP] IETF, "Common Control and Measurement Plane", | |||
| D., and S. Mansfield, "Guidelines for the Use of the "OAM" | <https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>. | |||
| Acronym in the IETF", BCP 161, RFC 6291, | ||||
| DOI 10.17487/RFC6291, June 2011, | ||||
| <https://www.rfc-editor.org/info/rfc6291>. | ||||
| [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., | ||||
| Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, | ||||
| JP., and R. Alexander, "RPL: IPv6 Routing Protocol for | ||||
| Low-Power and Lossy Networks", RFC 6550, | ||||
| DOI 10.17487/RFC6550, March 2012, | ||||
| <https://www.rfc-editor.org/info/rfc6550>. | ||||
| [RFC6551] Vasseur, JP., Ed., Kim, M., Ed., Pister, K., Dejean, N., | ||||
| and D. Barthel, "Routing Metrics Used for Path Calculation | ||||
| in Low-Power and Lossy Networks", RFC 6551, | ||||
| DOI 10.17487/RFC6551, March 2012, | ||||
| <https://www.rfc-editor.org/info/rfc6551>. | ||||
| [RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. | ||||
| Weingarten, "An Overview of Operations, Administration, | ||||
| and Maintenance (OAM) Tools", RFC 7276, | ||||
| DOI 10.17487/RFC7276, June 2014, | ||||
| <https://www.rfc-editor.org/info/rfc7276>. | ||||
| [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., | [TiSCH] IETF, "IPv6 over the TSCH mode over 802.15.4", | |||
| Przygienda, T., and S. Aldrin, "Multicast Using Bit Index | <https://dataTracker.ietf.org/doc/charter-ietf-6tisch/>. | |||
| Explicit Replication (BIER)", RFC 8279, | ||||
| DOI 10.17487/RFC8279, November 2017, | ||||
| <https://www.rfc-editor.org/info/rfc8279>. | ||||
| [RIH18] Rihacek, C., Haindl, B., Fantappie, P., Pierattelli, S., | [RIH18] Rihacek, C., Haindl, B., Fantappie, P., Pierattelli, S., | |||
| Graeupl, T., Schnell, M., and N. Fistas, "L-band Digital | Gräupl, T., Schnell, M., and N. Fistas, "L-band Digital | |||
| Aeronautical Communications System (LDACS) Activities in | Aeronautical Communications System (LDACS) Activities in | |||
| SESAR2020", Proceedings of the Integrated Communications | SESAR2020", Proceedings of the Integrated Communications | |||
| Navigation and Surveillance Conference (ICNS) Herndon, VA, | Navigation and Surveillance Conference (ICNS) Herndon, VA, | |||
| USA, April 2018. | USA, April 2018. | |||
| [SAJ14] Sajatovic, M., Guenzel, H., and S. Mueller, "WA04 D22 Test | [GRA19] Gräupl, T., Rihacek, C., and B. Haindl, "LDACS A/G | |||
| Specification", SESAR2020 PJ14-02-01 D3.3.010, February | ||||
| 2019. | ||||
| [SAJ14] Sajatovic, M., Günzel, H., and S. Müller, "WA04 D22 Test | ||||
| Report for Assessing LDACS1 Transmitter Impact upon DME/ | Report for Assessing LDACS1 Transmitter Impact upon DME/ | |||
| TACAN Receivers", April 2014. | TACAN Receivers", April 2014. | |||
| [SCH19] Schnell, M., "DLR tests digital communications | [GRA11] Gräupl, T. and M. Ehammer, "L-DACS1 Data Link Layer | |||
| technologies combined with additional navigation functions | Evolution of ATN/IPS", Proceedings of the 30th IEEE/AIAA | |||
| for the first time", March 2019, | Digital Avionics Systems Conference (DASC) Seattle, WA, | |||
| <https://www.dlr.de/dlr/en/desktopdefault.aspx/ | USA, October 2011. | |||
| tabid-10081/151_read-32951/#/gallery/33877>. | ||||
| [TiSCH] IETF, "IPv6 over the TSCH mode over 802.15.4", | [ICAO18] International Civil Aviation Organization (ICAO), "L-Band | |||
| <https://dataTracker.ietf.org/doc/charter-ietf-6tisch/>. | Digital Aeronautical Communication System (LDACS)", | |||
| International Standards and Recommended Practices Annex 10 | ||||
| - Aeronautical Telecommunications, Vol. III - | ||||
| Communication Systems, July 2018. | ||||
| [vilajosana19] | [GRA18] al., T. G. E., "L-band Digital Aeronautical Communications | |||
| Xavier Vilajosana et al., "6TiSCH: Industrial Performance | System (LDACS) flight trials in the national German | |||
| for IPv6 Internet-of-Things Networks", June 2019. | project MICONAV", Proceedings of the Integrated | |||
| Communications, Navigation, Surveillance Conference | ||||
| (ICNS) Herndon, VA, USA, April 2018. | ||||
| [WirelessHART] | [SCH19] Schnell, M., "DLR tests digital communications | |||
| www.hartcomm.org, "Industrial Communication Networks - | technologies combined with additional navigation functions | |||
| Wireless Communication Network and Communication Profiles | for the first time", 3 March 2019, | |||
| - WirelessHART - IEC 62591", 2010. | <https://www.dlr.de/dlr/en/desktopdefault.aspx/tabid- | |||
| 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. | ||||
| 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 | |||
| MOUGINS - Sophia Antipolis 06254 | 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 | |||
| USA | 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 | |||
| Barcelona, Catalonia 08018 | 08018 Barcelona Catalonia | |||
| Spain | Spain | |||
| Email: xvilajosana@uoc.edu | Email: xvilajosana@uoc.edu | |||
| Corinna Schmitt | Corinna Schmitt | |||
| Universitaet der Bundeswehr Muenchen | Research Institute CODE, UniBwM | |||
| Werner-Heisenberg-Weg 39 | Werner-Heisenberg-Weg 28 | |||
| Neubiberg 85577 | 85577 Neubiberg | |||
| Germany | Germany | |||
| Email: corinna.schmitt@unibw.de | Email: corinna.schmitt@unibw.de | |||
| End of changes. 99 change blocks. | ||||
| 297 lines changed or deleted | 297 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/ | ||||