< draft-ietf-6tisch-architecture-21.txt   draft-ietf-6tisch-architecture-22.txt >
6TiSCH P. Thubert, Ed. 6TiSCH P. Thubert, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational June 19, 2019 Intended status: Informational June 24, 2019
Expires: December 21, 2019 Expires: December 26, 2019
An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4 An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4
draft-ietf-6tisch-architecture-21 draft-ietf-6tisch-architecture-22
Abstract Abstract
This document describes a network architecture that provides low- This document describes a network architecture that provides low-
latency, low-jitter and high-reliability packet delivery. It latency, low-jitter and high-reliability packet delivery. It
combines a high-speed powered backbone and subnetworks using IEEE combines a high-speed powered backbone and subnetworks using IEEE
802.15.4 time-slotted channel hopping (TSCH) to meet the requirements 802.15.4 time-slotted channel hopping (TSCH) to meet the requirements
of LowPower wireless deterministic applications. of LowPower wireless deterministic applications.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 December 21, 2019. This Internet-Draft will expire on December 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 4 skipping to change at page 3, line 4
4.6.3. Complex Track with Replication and Elimination . . . 40 4.6.3. Complex Track with Replication and Elimination . . . 40
4.6.4. DetNet End-to-end Path . . . . . . . . . . . . . . . 40 4.6.4. DetNet End-to-end Path . . . . . . . . . . . . . . . 40
4.6.5. Cell Reuse . . . . . . . . . . . . . . . . . . . . . 41 4.6.5. Cell Reuse . . . . . . . . . . . . . . . . . . . . . 41
4.7. Forwarding Models . . . . . . . . . . . . . . . . . . . . 42 4.7. Forwarding Models . . . . . . . . . . . . . . . . . . . . 42
4.7.1. Track Forwarding . . . . . . . . . . . . . . . . . . 42 4.7.1. Track Forwarding . . . . . . . . . . . . . . . . . . 42
4.7.2. IPv6 Forwarding . . . . . . . . . . . . . . . . . . . 45 4.7.2. IPv6 Forwarding . . . . . . . . . . . . . . . . . . . 45
4.7.3. Fragment Forwarding . . . . . . . . . . . . . . . . . 45 4.7.3. Fragment Forwarding . . . . . . . . . . . . . . . . . 45
4.8. Advanced 6TiSCH Routing . . . . . . . . . . . . . . . . . 47 4.8. Advanced 6TiSCH Routing . . . . . . . . . . . . . . . . . 47
4.8.1. Packet Marking and Handling . . . . . . . . . . . . . 47 4.8.1. Packet Marking and Handling . . . . . . . . . . . . . 47
4.8.2. Replication, Retries and Elimination . . . . . . . . 48 4.8.2. Replication, Retries and Elimination . . . . . . . . 48
4.8.3. Differentiated Services Per-Hop-Behavior . . . . . . 50
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
6. Security Considerations . . . . . . . . . . . . . . . . . . . 50 6. Security Considerations . . . . . . . . . . . . . . . . . . . 50
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 51
7.1. Contributors . . . . . . . . . . . . . . . . . . . . . . 51 7.1. Contributors . . . . . . . . . . . . . . . . . . . . . . 51
7.2. Special Thanks . . . . . . . . . . . . . . . . . . . . . 52 7.2. Special Thanks . . . . . . . . . . . . . . . . . . . . . 52
7.3. And Do not Forget . . . . . . . . . . . . . . . . . . . . 52 7.3. And Do not Forget . . . . . . . . . . . . . . . . . . . . 53
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1. Normative References . . . . . . . . . . . . . . . . . . 53 8.1. Normative References . . . . . . . . . . . . . . . . . . 53
8.2. Informative References . . . . . . . . . . . . . . . . . 55 8.2. Informative References . . . . . . . . . . . . . . . . . 55
Appendix A. Related Work In Progress . . . . . . . . . . . . . . 61 Appendix A. Related Work In Progress . . . . . . . . . . . . . . 61
A.1. Chartered IETF work items . . . . . . . . . . . . . . . . 61 A.1. Chartered IETF work items . . . . . . . . . . . . . . . . 62
A.2. Unchartered IETF work items . . . . . . . . . . . . . . . 62 A.2. Unchartered IETF work items . . . . . . . . . . . . . . . 62
A.2.1. 6TiSCH Zerotouch security . . . . . . . . . . . . . . 62 A.2.1. 6TiSCH Zerotouch security . . . . . . . . . . . . . . 62
A.2.2. 6TiSCH Track Setup . . . . . . . . . . . . . . . . . 62 A.2.2. 6TiSCH Track Setup . . . . . . . . . . . . . . . . . 62
A.2.3. Using BIER in a 6TiSCH Network . . . . . . . . . . . 63 A.2.3. Using BIER in a 6TiSCH Network . . . . . . . . . . . 63
A.3. External (non-IETF) work items . . . . . . . . . . . . . 63 A.3. External (non-IETF) work items . . . . . . . . . . . . . 63
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 64
1. Introduction 1. Introduction
Wireless Networks enable a wide variety of devices of any size to get Wireless Networks enable a wide variety of devices of any size to get
skipping to change at page 45, line 20 skipping to change at page 45, line 20
matches that of the tunnel egress point. For that reason, the node matches that of the tunnel egress point. For that reason, the node
that injects a packet on a Track checks that the destination is that injects a packet on a Track checks that the destination is
effectively that of the tunnel egress point before it overwrites it effectively that of the tunnel egress point before it overwrites it
to broadcast. The 6top sublayer at the tunnel egress point reverts to broadcast. The 6top sublayer at the tunnel egress point reverts
that operation to the MAC address obtained from the tunnel that operation to the MAC address obtained from the tunnel
information. information.
4.7.2. IPv6 Forwarding 4.7.2. IPv6 Forwarding
As the packets are routed at Layer-3, traditional QoS and Active As the packets are routed at Layer-3, traditional QoS and Active
Queue Management (AQM) operations are expected to prioritize flows; Queue Management (AQM) operations are expected to prioritize flows.
the application of Differentiated Services is further discussed in
[I-D.svshah-tsvwg-lln-diffserv-recommendations].
| Packet flowing across the network ^ | Packet flowing across the network ^
+--------------+ | | +--------------+ | |
| IPv6 | | +-QoS+ +-QoS+ | | IPv6 | | +-QoS+ +-QoS+ |
+--------------+ | | | | | | +--------------+ | | | | | |
| 6LoWPAN HC | | | | | | | | 6LoWPAN HC | | | | | | |
+--------------+ | | | | | | +--------------+ | | | | | |
| 6top | | | | | | | | 6top | | | | | | |
+--------------+ | | | | | | +--------------+ | | | | | |
| TSCH MAC | | | | | | | | TSCH MAC | | | | | | |
skipping to change at page 50, line 32 skipping to change at page 50, line 32
| Node | rcv slotOffset | xmit slotOffset | | Node | rcv slotOffset | xmit slotOffset |
+------+---------------------+------------------------+ +------+---------------------+------------------------+
| I | N/A | (0 OR 1) AND (2 OR 3) | | I | N/A | (0 OR 1) AND (2 OR 3) |
| A | (0 OR 1) | (2 OR 3 OR 4) | | A | (0 OR 1) | (2 OR 3 OR 4) |
| B | (2 OR 3) | (4 OR 5 OR 6) | | B | (2 OR 3) | (4 OR 5 OR 6) |
| C | (2 OR 3 OR 4) | (5 OR 6) | | C | (2 OR 3 OR 4) | (5 OR 6) |
| D | (4 OR 5 OR 6) | (7 OR 8) | | D | (4 OR 5 OR 6) | (7 OR 8) |
| E | (5 OR 6 OR 7 OR 8) | N/A | | E | (5 OR 6 OR 7 OR 8) | N/A |
+------+---------------------+------------------------+ +------+---------------------+------------------------+
4.8.3. Differentiated Services Per-Hop-Behavior
A future document could define a PHB for Deterministic Flows, to be
indicated in the IANA registry where IETF-defined PHBs are listed.
5. IANA Considerations 5. IANA Considerations
This specification does not require IANA action. This specification does not require IANA action.
6. Security Considerations 6. Security Considerations
This architecture operates on IEEE Std 802.15.4 and expects Link- This architecture operates on IEEE Std 802.15.4 and expects Link-
Layer security to be enabled at all times between connected devices, Layer security to be enabled at all times between connected devices,
except for the very first step of the device join process, where a except for the very first step of the device join process, where a
joining device may need some initial, unsecured exchanges so as to joining device may need some initial, unsecured exchanges so as to
skipping to change at page 51, line 23 skipping to change at page 51, line 17
domain communication. domain communication.
For the join procedure, the pledge is helped by a Join Proxy (JP) For the join procedure, the pledge is helped by a Join Proxy (JP)
that relays the link-scope Join Request over the IP network to the that relays the link-scope Join Request over the IP network to the
Join Registrar/Coordinator (JRC) that can authenticate the pledge and Join Registrar/Coordinator (JRC) that can authenticate the pledge and
validate that it is attached to the appropriate network. As a result validate that it is attached to the appropriate network. As a result
of this exchange the pledge is in possession of a Link-Layer material of this exchange the pledge is in possession of a Link-Layer material
including a key and a short address, and all traffic is secured at including a key and a short address, and all traffic is secured at
the Link-Layer. the Link-Layer.
The operation of 6TiSCH Tracks inherits its high level operation from
DetNet and is subject to the observations in section 5 of
[I-D.ietf-detnet-architecture]. As discussed there, measures must be
taken to protect the time synchronization, and for 6TiSCH this
includes ensuring that the ASN, which is used for the computation of
NONCE, is not compromised. Also, the installation and maintenance of
6TiSCH Tracks depends in the availability of a controller with a PCE
to compute and push them in the network. When that connectivity is
lost, existing Tracks may continue to operate until the end of their
lifetime, but cannot be removed or updated, and new Tracks cannot be
installed. As with DetNet in general, the communication with the PCE
must be secured and should be protected against DoS attacks, and the
discussion on the security considerations defined for Abstraction and
Control of Traffic Engineered Networks (ACTN) in Section 9 of
RFC8453], applies equally to 6TiSCH.
7. Acknowledgments 7. Acknowledgments
7.1. Contributors 7.1. Contributors
The co-authors of this document are listed below: The co-authors of this document are listed below:
Robert Assimiti for his breakthrough work on RPL over TSCH and Robert Assimiti for his breakthrough work on RPL over TSCH and
initial text and guidance; initial text and guidance;
Kris Pister for creating it all and his continuing guidance through Kris Pister for creating it all and his continuing guidance through
skipping to change at page 52, line 35 skipping to change at page 52, line 48
Special thanks to Ted Lemon who was the INT Area A-D while this Special thanks to Ted Lemon who was the INT Area A-D while this
specification was initiated for his great support and help specification was initiated for his great support and help
throughout, and to Suresh Krishnan who took over with that kind throughout, and to Suresh Krishnan who took over with that kind
efficiency of his till publication. efficiency of his till publication.
Also special thanks to Ralph Droms who performed the first INT Area Also special thanks to Ralph Droms who performed the first INT Area
Directorate review, that was very deep and through and radically Directorate review, that was very deep and through and radically
changed the orientations of this document, and then to Eliot Lear and changed the orientations of this document, and then to Eliot Lear and
Carlos Pignataro who help finalize this document in preparation to Carlos Pignataro who help finalize this document in preparation to
the IESG reviews, and to Gorry Fairhurst who contributed to the final the IESG reviews, and to Gorry Fairhurst, David Mandelberg and Andrew
shaping of this document through the IESG review procedure. Malis who contributed to the final shaping of this document through
the IESG review procedure.
7.3. And Do not Forget 7.3. And Do not Forget
This specification is the result of multiple interactions, in This specification is the result of multiple interactions, in
particular during the 6TiSCH (bi)Weekly Interim call, relayed through particular during the 6TiSCH (bi)Weekly Interim call, relayed through
the 6TiSCH mailing list at the IETF. the 6TiSCH mailing list at the IETF.
The authors wish to thank in arbitrary order: Alaeddine Weslati, The authors wish to thank in arbitrary order: Alaeddine Weslati,
Chonggang Wang, Georgios Exarchakos, Zhuo Chen, Georgios Chonggang Wang, Georgios Exarchakos, Zhuo Chen, Georgios
Papadopoulos, Alfredo Grieco, Bert Greevenbosch, Cedric Adjih, Deji Papadopoulos, Alfredo Grieco, Bert Greevenbosch, Cedric Adjih, Deji
skipping to change at page 55, line 5 skipping to change at page 55, line 20
[RFC8180] Vilajosana, X., Ed., Pister, K., and T. Watteyne, "Minimal [RFC8180] Vilajosana, X., Ed., Pister, K., and T. Watteyne, "Minimal
IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH) IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH)
Configuration", BCP 210, RFC 8180, DOI 10.17487/RFC8180, Configuration", BCP 210, RFC 8180, DOI 10.17487/RFC8180,
May 2017, <https://www.rfc-editor.org/info/rfc8180>. May 2017, <https://www.rfc-editor.org/info/rfc8180>.
[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>.
[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for
Abstraction and Control of TE Networks (ACTN)", RFC 8453,
DOI 10.17487/RFC8453, August 2018,
<https://www.rfc-editor.org/info/rfc8453>.
[RFC8480] Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH [RFC8480] Wang, Q., Ed., Vilajosana, X., and T. Watteyne, "6TiSCH
Operation Sublayer (6top) Protocol (6P)", RFC 8480, Operation Sublayer (6top) Protocol (6P)", RFC 8480,
DOI 10.17487/RFC8480, November 2018, DOI 10.17487/RFC8480, November 2018,
<https://www.rfc-editor.org/info/rfc8480>. <https://www.rfc-editor.org/info/rfc8480>.
[RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C. [RFC8505] Thubert, P., Ed., Nordmark, E., Chakrabarti, S., and C.
Perkins, "Registration Extensions for IPv6 over Low-Power Perkins, "Registration Extensions for IPv6 over Low-Power
Wireless Personal Area Network (6LoWPAN) Neighbor Wireless Personal Area Network (6LoWPAN) Neighbor
Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018, Discovery", RFC 8505, DOI 10.17487/RFC8505, November 2018,
<https://www.rfc-editor.org/info/rfc8505>. <https://www.rfc-editor.org/info/rfc8505>.
skipping to change at page 57, line 48 skipping to change at page 58, line 15
[I-D.rahul-roll-mop-ext] [I-D.rahul-roll-mop-ext]
Jadhav, R. and P. Thubert, "RPL Mode of Operation Jadhav, R. and P. Thubert, "RPL Mode of Operation
extension", draft-rahul-roll-mop-ext-01 (work in extension", draft-rahul-roll-mop-ext-01 (work in
progress), June 2019. progress), June 2019.
[I-D.selander-ace-cose-ecdhe] [I-D.selander-ace-cose-ecdhe]
Selander, G., Mattsson, J., and F. Palombini, "Ephemeral Selander, G., Mattsson, J., and F. Palombini, "Ephemeral
Diffie-Hellman Over COSE (EDHOC)", draft-selander-ace- Diffie-Hellman Over COSE (EDHOC)", draft-selander-ace-
cose-ecdhe-13 (work in progress), March 2019. cose-ecdhe-13 (work in progress), March 2019.
[I-D.svshah-tsvwg-lln-diffserv-recommendations]
Shah, S. and P. Thubert, "Differentiated Service Class
Recommendations for LLN Traffic", draft-svshah-tsvwg-lln-
diffserv-recommendations-04 (work in progress), February
2015.
[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", draft-thubert-6lo-bier-dispatch-06
(work in progress), January 2019. (work in progress), January 2019.
[I-D.thubert-6lo-unicast-lookup] [I-D.thubert-6lo-unicast-lookup]
Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery
Unicast Lookup", draft-thubert-6lo-unicast-lookup-00 (work Unicast Lookup", draft-thubert-6lo-unicast-lookup-00 (work
in progress), January 2019. in progress), January 2019.
[I-D.thubert-bier-replication-elimination] [I-D.thubert-bier-replication-elimination]
Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER- Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER-
TE extensions for Packet Replication and Elimination TE extensions for Packet Replication and Elimination
Function (PREF) and OAM", draft-thubert-bier-replication- Function (PREF) and OAM", draft-thubert-bier-replication-
elimination-03 (work in progress), March 2018. elimination-03 (work in progress), March 2018.
[I-D.thubert-raw-technologies] [I-D.thubert-raw-technologies]
Thubert, P., Cavalcanti, D., and X. Vilajosana, "Reliable Thubert, P., Cavalcanti, D., and X. Vilajosana, "Reliable
and Available Wireless Technologies", draft-thubert-raw- and Available Wireless Technologies", draft-thubert-raw-
technologies-01 (work in progress), June 2019. technologies-02 (work in progress), June 2019.
[I-D.thubert-roll-bier] [I-D.thubert-roll-bier]
Thubert, P., "RPL-BIER", draft-thubert-roll-bier-02 (work Thubert, P., "RPL-BIER", draft-thubert-roll-bier-02 (work
in progress), July 2018. in progress), July 2018.
[IEC62439] [IEC62439]
IEC, "Industrial communication networks - High IEC, "Industrial communication networks - High
availability automation networks - Part 3: Parallel availability automation networks - Part 3: Parallel
Redundancy Protocol (PRP) and High-availability Seamless Redundancy Protocol (PRP) and High-availability Seamless
Redundancy (HSR) - IEC62439-3", 2012, Redundancy (HSR) - IEC62439-3", 2012,
skipping to change at page 61, line 36 skipping to change at page 61, line 45
[TEAS] IETF, "Traffic Engineering Architecture and Signaling", [TEAS] IETF, "Traffic Engineering Architecture and Signaling",
<https://dataTracker.ietf.org/doc/charter-ietf-teas/>. <https://dataTracker.ietf.org/doc/charter-ietf-teas/>.
[WirelessHART] [WirelessHART]
www.hartcomm.org, "Industrial Communication Networks - www.hartcomm.org, "Industrial Communication Networks -
Wireless Communication Network and Communication Profiles Wireless Communication Network and Communication Profiles
- WirelessHART - IEC 62591", 2010. - WirelessHART - IEC 62591", 2010.
Appendix A. Related Work In Progress Appendix A. Related Work In Progress
To control the complexity and the size of the 6TiSCH work, the . This document has been incremented as the work progressed
architecture and the associated IETF work are staged and the WG is following the evolution of the WG charter and the availability of
expected to recharter multiple times. This document is been dependent work. The intent was to publish when the WG concludes on
incremented as the work progressed following the evolution of the WG the covered items. At the time of publishing the following
charter and the availability of dependent work. The intent was to specification are still in progress and may affect the evolution of
publish when the WG concludes on the covered items. the stack in a 6TiSCH-aware node.
At the time of publishing the following specification are still in
progress and may affect the stack in a 6TiSCH-aware node.
A.1. Chartered IETF work items A.1. Chartered IETF work items
The operation of the Backbone Router [I-D.ietf-6lo-backbone-router] The operation of the Backbone Router [I-D.ietf-6lo-backbone-router]
is stable but the RFC is not published yet. The protection of is stable but the RFC is not published yet. The protection of
registered addresses against impersonation and take over will be registered addresses against impersonation and take over will be
guaranteed by Address Protected Neighbor Discovery for Low-power and guaranteed by Address Protected Neighbor Discovery for Low-power and
Lossy Networks [I-D.ietf-6lo-ap-nd], which is not yet published Lossy Networks [I-D.ietf-6lo-ap-nd], which is not yet published
either. either.
 End of changes. 14 change blocks. 
33 lines changed or deleted 39 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/