< draft-ietf-6tisch-architecture-28.txt		draft-ietf-6tisch-architecture-30.txt >
	6TiSCH P. Thubert, Ed.		6TiSCH P. Thubert, Ed.
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Informational 29 October 2019		Intended status: Informational 26 November 2020
	Expires: 1 May 2020		Expires: 30 May 2021
	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-28		draft-ietf-6tisch-architecture-30
	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 1 May 2020.		This Internet-Draft will expire on 30 May 2021.
	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 (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.
	skipping to change at page 2, line 15 ¶		skipping to change at page 2, line 15 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1. New Terms . . . . . . . . . . . . . . . . . . . . . . . . 5		2.1. New Terms . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 10		2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 10
	2.3. Related Documents . . . . . . . . . . . . . . . . . . . . 11		2.3. Related Documents . . . . . . . . . . . . . . . . . . . . 11
	3. High Level Architecture . . . . . . . . . . . . . . . . . . . 12		3. High Level Architecture . . . . . . . . . . . . . . . . . . . 12
	3.1. A Non-Broadcast Multi-Access Radio Mesh Network . . . . . 12		3.1. A Non-Broadcast Multi-Access Radio Mesh Network . . . . . 12
	3.2. A Multi-Link Subnet Model . . . . . . . . . . . . . . . . 14		3.2. A Multi-Link Subnet Model . . . . . . . . . . . . . . . . 14
	3.3. TSCH: A Deterministic MAC Layer . . . . . . . . . . . . . 15		3.3. TSCH: A Deterministic MAC Layer . . . . . . . . . . . . . 16
	3.4. Scheduling TSCH . . . . . . . . . . . . . . . . . . . . . 16		3.4. Scheduling TSCH . . . . . . . . . . . . . . . . . . . . . 17
	3.5. Distributed vs. Centralized Routing . . . . . . . . . . . 17		3.5. Distributed vs. Centralized Routing . . . . . . . . . . . 18
	3.6. Forwarding Over TSCH . . . . . . . . . . . . . . . . . . 18		3.6. Forwarding Over TSCH . . . . . . . . . . . . . . . . . . 19
	3.7. 6TiSCH Stack . . . . . . . . . . . . . . . . . . . . . . 19		3.7. 6TiSCH Stack . . . . . . . . . . . . . . . . . . . . . . 20
	3.8. Communication Paradigms and Interaction Models . . . . . 21		3.8. Communication Paradigms and Interaction Models . . . . . 22
	4. Architecture Components . . . . . . . . . . . . . . . . . . . 22		4. Architecture Components . . . . . . . . . . . . . . . . . . . 23
	4.1. 6LoWPAN (and RPL) . . . . . . . . . . . . . . . . . . . . 22		4.1. 6LoWPAN (and RPL) . . . . . . . . . . . . . . . . . . . . 23
	4.1.1. RPL-Unaware Leaves and 6LoWPAN ND . . . . . . . . . . 22		4.1.1. RPL-Unaware Leaves and 6LoWPAN ND . . . . . . . . . . 23
	4.1.2. 6LBR and RPL Root . . . . . . . . . . . . . . . . . . 23		4.1.2. 6LBR and RPL Root . . . . . . . . . . . . . . . . . . 24
	4.2. Network Access and Addressing . . . . . . . . . . . . . . 23		4.2. Network Access and Addressing . . . . . . . . . . . . . . 24
	4.2.1. Join Process . . . . . . . . . . . . . . . . . . . . 24		4.2.1. Join Process . . . . . . . . . . . . . . . . . . . . 25
	4.2.2. Registration . . . . . . . . . . . . . . . . . . . . 26		4.2.2. Registration . . . . . . . . . . . . . . . . . . . . 27
	4.3. TSCH and 6top . . . . . . . . . . . . . . . . . . . . . . 27		4.3. TSCH and 6top . . . . . . . . . . . . . . . . . . . . . . 28
	4.3.1. 6top . . . . . . . . . . . . . . . . . . . . . . . . 27		4.3.1. 6top . . . . . . . . . . . . . . . . . . . . . . . . 28
	4.3.2. Scheduling Functions and the 6top protocol . . . . . 29		4.3.2. Scheduling Functions and the 6top protocol . . . . . 30
	4.3.3. 6top and RPL Objective Function operations . . . . . 30		4.3.3. 6top and RPL Objective Function operations . . . . . 31
	4.3.4. Network Synchronization . . . . . . . . . . . . . . . 31		4.3.4. Network Synchronization . . . . . . . . . . . . . . . 32
	4.3.5. Slotframes and CDU matrix . . . . . . . . . . . . . . 32		4.3.5. Slotframes and CDU matrix . . . . . . . . . . . . . . 33
	4.3.6. Distributing the reservation of cells . . . . . . . . 33		4.3.6. Distributing the reservation of cells . . . . . . . . 34
	4.4. Schedule Management Mechanisms . . . . . . . . . . . . . 34		4.4. Schedule Management Mechanisms . . . . . . . . . . . . . 35
	4.4.1. Static Scheduling . . . . . . . . . . . . . . . . . . 34		4.4.1. Static Scheduling . . . . . . . . . . . . . . . . . . 35
	4.4.2. Neighbor-to-neighbor Scheduling . . . . . . . . . . . 35		4.4.2. Neighbor-to-neighbor Scheduling . . . . . . . . . . . 36
	4.4.3. Remote Monitoring and Schedule Management . . . . . . 36		4.4.3. Remote Monitoring and Schedule Management . . . . . . 37
	4.4.4. Hop-by-hop Scheduling . . . . . . . . . . . . . . . . 38		4.4.4. Hop-by-hop Scheduling . . . . . . . . . . . . . . . . 39
	4.5. On Tracks . . . . . . . . . . . . . . . . . . . . . . . . 38		4.5. On Tracks . . . . . . . . . . . . . . . . . . . . . . . . 39
	4.5.1. General Behavior of Tracks . . . . . . . . . . . . . 39		4.5.1. General Behavior of Tracks . . . . . . . . . . . . . 40
	4.5.2. Serial Track . . . . . . . . . . . . . . . . . . . . 39		4.5.2. Serial Track . . . . . . . . . . . . . . . . . . . . 40
	4.5.3. Complex Track with Replication and		4.5.3. Complex Track with Replication and Elimination . . . 41
	Elimination . . . . . . . . . . . . . . . . . . . . . 40		4.5.4. DetNet End-to-end Path . . . . . . . . . . . . . . . 41
	4.5.4. DetNet End-to-end Path . . . . . . . . . . . . . . . 40		4.5.5. Cell Reuse . . . . . . . . . . . . . . . . . . . . . 42
	4.5.5. Cell Reuse . . . . . . . . . . . . . . . . . . . . . 41		4.6. Forwarding Models . . . . . . . . . . . . . . . . . . . . 43
	4.6. Forwarding Models . . . . . . . . . . . . . . . . . . . . 42		4.6.1. Track Forwarding . . . . . . . . . . . . . . . . . . 43
	4.6.1. Track Forwarding . . . . . . . . . . . . . . . . . . 42		4.6.2. IPv6 Forwarding . . . . . . . . . . . . . . . . . . . 46
	4.6.2. IPv6 Forwarding . . . . . . . . . . . . . . . . . . . 45		4.6.3. Fragment Forwarding . . . . . . . . . . . . . . . . . 47
	4.6.3. Fragment Forwarding . . . . . . . . . . . . . . . . . 45		4.7. Advanced 6TiSCH Routing . . . . . . . . . . . . . . . . . 48
	4.7. Advanced 6TiSCH Routing . . . . . . . . . . . . . . . . . 47		4.7.1. Packet Marking and Handling . . . . . . . . . . . . . 48
	4.7.1. Packet Marking and Handling . . . . . . . . . . . . . 47		4.7.2. Replication, Retries and Elimination . . . . . . . . 49
	4.7.2. Replication, Retries and Elimination . . . . . . . . 48
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 50		6. Security Considerations . . . . . . . . . . . . . . . . . . . 52
	6.1. Availability of Remote Services . . . . . . . . . . . . . 50		6.1. Availability of Remote Services . . . . . . . . . . . . . 52
	6.2. Selective Jamming . . . . . . . . . . . . . . . . . . . . 51		6.2. Selective Jamming . . . . . . . . . . . . . . . . . . . . 52
	6.3. MAC-Layer Security . . . . . . . . . . . . . . . . . . . 51		6.3. MAC-Layer Security . . . . . . . . . . . . . . . . . . . 53
	6.4. Time Synchronization . . . . . . . . . . . . . . . . . . 52		6.4. Time Synchronization . . . . . . . . . . . . . . . . . . 53
	6.5. Validating ASN . . . . . . . . . . . . . . . . . . . . . 52		6.5. Validating ASN . . . . . . . . . . . . . . . . . . . . . 54
	6.6. Network Keying and Rekeying . . . . . . . . . . . . . . . 53		6.6. Network Keying and Rekeying . . . . . . . . . . . . . . . 55
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56
	7.1. Contributors . . . . . . . . . . . . . . . . . . . . . . 55		7.1. Contributors . . . . . . . . . . . . . . . . . . . . . . 56
	7.2. Special Thanks . . . . . . . . . . . . . . . . . . . . . 56		7.2. Special Thanks . . . . . . . . . . . . . . . . . . . . . 57
	7.3. And Do not Forget . . . . . . . . . . . . . . . . . . . . 56		7.3. And Do not Forget . . . . . . . . . . . . . . . . . . . . 58
	8. Normative References . . . . . . . . . . . . . . . . . . . . 57		8. Normative References . . . . . . . . . . . . . . . . . . . . 58
	9. Informative References . . . . . . . . . . . . . . . . . . . 61		9. Informative References . . . . . . . . . . . . . . . . . . . 62
	Appendix A. Related Work In Progress . . . . . . . . . . . . . . 67		Appendix A. Related Work In Progress . . . . . . . . . . . . . . 69
	A.1. Unchartered IETF work items . . . . . . . . . . . . . . . 67		A.1. Unchartered IETF work items . . . . . . . . . . . . . . . 69
	A.1.1. 6TiSCH Zerotouch security . . . . . . . . . . . . . . 67		A.1.1. 6TiSCH Zerotouch security . . . . . . . . . . . . . . 69
	A.1.2. 6TiSCH Track Setup . . . . . . . . . . . . . . . . . 67		A.1.2. 6TiSCH Track Setup . . . . . . . . . . . . . . . . . 69
	A.1.3. Using BIER in a 6TiSCH Network . . . . . . . . . . . 68		A.1.3. Using BIER in a 6TiSCH Network . . . . . . . . . . . 70
	A.2. External (non-IETF) work items . . . . . . . . . . . . . 68		A.2. External (non-IETF) work items . . . . . . . . . . . . . 70
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 69		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 71
	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
	interconnected, often at a very low marginal cost per device, at any		interconnected, often at a very low marginal cost per device, at any
	range, and in circumstances where wiring may be impractical, for		range, and in circumstances where wiring may be impractical, for
	instance on fast-moving or rotating devices.		instance on fast-moving or rotating devices.
	On the other hand, Deterministic Networking maximizes the packet		On the other hand, Deterministic Networking maximizes the packet
	delivery ratio within a bounded latency so as to enable mission-		delivery ratio within a bounded latency so as to enable mission-
	skipping to change at page 9, line 41 ¶		skipping to change at page 10, line 17 ¶
	unicast traffic. A Track enables replication, elimination and		unicast traffic. A Track enables replication, elimination and
	reordering functions on the way (more on those functions in		reordering functions on the way (more on those functions in
	[RFC8655]. A Track reservation locks physical resources such as		[RFC8655]. A Track reservation locks physical resources such as
	cells and buffers in every node along the DODAG. A Track is		cells and buffers in every node along the DODAG. A Track is
	associated with a owner that can be for instance the destination		associated with a owner that can be for instance the destination
	of the Track.		of the Track.
	TrackID: A TrackID is either globally unique, or locally unique to		TrackID: A TrackID is either globally unique, or locally unique to
	the Track owner, in which case the identification of the owner		the Track owner, in which case the identification of the owner
	must be provided together with the TrackID to provide a full		must be provided together with the TrackID to provide a full
	reference to the Track. If the Track owner is the destination of		reference to the Track. typically, the Track owner is the ingress
	the Track then the destination IP address of packets along the		of the Track then the IPv6 source address of packets along the
	Track can be used as identification of the owner and a local		Track can be used as identification of the owner and a local
	InstanceID [RFC6550] can be used as TrackID. In that case, a RPL		InstanceID [RFC6550] in the namespace of that owner can be used as
	Packet Information [RFC6550] in an IPv6 packet can unambiguously		TrackID. If the Track is reversible, then the owner is found in
	identify the Track and can be expressed in a compressed form using		the IPv6 destination address of a packet coming back along the
	[RFC8138].		Track. In that case, a RPL Packet Information [RFC6550] in an
			IPv6 packet can unambiguously identify the Track and can be
			expressed in a compressed form using [RFC8138].
	TSCH: A medium access mode of the IEEE Std. 802.15.4 [IEEE802154]		TSCH: A medium access mode of the IEEE Std. 802.15.4 [IEEE802154]
	standard which uses time synchronization to achieve ultra-low-		standard which uses time synchronization to achieve ultra-low-
	power operation, and channel hopping to enable high reliability.		power operation, and channel hopping to enable high reliability.
	TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset		TSCH Schedule: A matrix of cells, each cell indexed by a slotOffset
	and a channelOffset. The TSCH schedule contains all the scheduled		and a channelOffset. The TSCH schedule contains all the scheduled
	cells from all slotframes and is sufficient to qualify the		cells from all slotframes and is sufficient to qualify the
	communication in the TSCH network. The number of channelOffset		communication in the TSCH network. The number of channelOffset
	values (the "height" of the matrix) is equal to the number of		values (the "height" of the matrix) is equal to the number of
	skipping to change at page 43, line 5 ¶		skipping to change at page 44, line 5 ¶
	A data frame that is forwarded along a Track normally has a		A data frame that is forwarded along a Track normally has a
	destination MAC address that is set to broadcast - or a multicast		destination MAC address that is set to broadcast - or a multicast
	address depending on MAC support. This way, the MAC layer in the		address depending on MAC support. This way, the MAC layer in the
	intermediate nodes accepts the incoming frame and 6top switches it		intermediate nodes accepts the incoming frame and 6top switches it
	without incurring a change in the MAC header. In the case of IEEE		without incurring a change in the MAC header. In the case of IEEE
	Std. 802.15.4, this means effectively broadcast, so that along the		Std. 802.15.4, this means effectively broadcast, so that along the
	Track the short address for the destination of the frame is set to		Track the short address for the destination of the frame is set to
	0xFFFF.		0xFFFF.
	There are 2 modes for a Track, native mode and tunnel mode.		There are 2 modes for a Track, an IPv6 native mode and a protocol-
			independant tunnel mode.
	4.6.1.1. Native Mode		4.6.1.1. Native Mode
	In native mode, the Protocol Data Unit (PDU) is associated with flow-		In native mode, the Protocol Data Unit (PDU) is associated with flow-
	dependent meta-data that refers uniquely to the Track, so the 6top		dependent meta-data that refers uniquely to the Track, so the 6top
	sublayer can place the frame in the appropriate cell without		sublayer can place the frame in the appropriate cell without
	ambiguity. In the case of IPv6 traffic, this flow identification may		ambiguity. In the case of IPv6 traffic, this flow identification may
	be done using a 6-tuple as discussed in [I-D.ietf-detnet-ip]. In		be done using a 6-tuple as discussed in [I-D.ietf-detnet-ip]. In
	particular, implementations of this document should support		particular, implementations of this document should support
	identification of DetNet flows based on the IPv6 Flow Label field.		identification of DetNet flows based on the IPv6 Flow Label field.
	The flow identification may also be done using a dedicated RPL
			The flow follows a Track which identification is done using a RPL
	Instance (see section 3.1.3 of [RFC6550]), signaled in a RPL Packet		Instance (see section 3.1.3 of [RFC6550]), signaled in a RPL Packet
	Information (more in section 11.2.2.1 of [RFC6550]). The flow		Information (more in section 11.2.2.1 of [RFC6550]) and the
	identification is validated at egress before restoring the		destination address in the case of a local instance. One or more
			flows may be placed in a same Track and the Track identification
			(TrackID + owner) may be placed in an IP-in-IP encapsulation. The
			forwarding operation is based on the Track and does not depend on the
			flow therein.
			The Track identification is validated at egress before restoring the
	destination MAC address (DMAC) and punting to the upper layer.		destination MAC address (DMAC) and punting to the upper layer.
	Figure 12 illustrates the Track Forwarding operation which happens at		Figure 12 illustrates the Track Forwarding operation which happens at
	the 6top sublayer, below IP.		the 6top sublayer, below IP.
	| Packet flowing across the network ^		| Packet flowing across the network ^
	+--------------+ | |		+--------------+ | |
	| IPv6 | | |		| IPv6 | | |
	+--------------+ | |		+--------------+ | |
	| 6LoWPAN HC | | |		| 6LoWPAN HC | | |
	skipping to change at page 44, line 29 ¶		skipping to change at page 45, line 40 ¶
	+--------------+ | Packet flowing across the network |		+--------------+ | Packet flowing across the network |
	| TSCH MAC | | |		| TSCH MAC | | |
	+--------------+ | DMAC = | DMAC =		+--------------+ | DMAC = | DMAC =
	|ISA100/WiHART | | nexthop v nexthop		|ISA100/WiHART | | nexthop v nexthop
	+--------------+		+--------------+
	Source Ingress Egress Destination		Source Ingress Egress Destination
	Stack Layer Node Node Node Node		Stack Layer Node Node Node Node
	Figure 13: Track Forwarding, Tunnel Mode		Figure 13: Track Forwarding, Tunnel Mode
	In that case, the flow information that identifies the Track at the		In that case, the TrackID that identifies the Track at the ingress
	ingress 6TiSCH router is derived from the RX-cell. The DMAC is set		6TiSCH router is derived from the RX-cell. The DMAC is set to this
	to this node but the flow information indicates that the frame must		node but the TrackID indicates that the frame must be tunneled over a
	be tunneled over a particular Track so the frame is not passed to the		particular Track so the frame is not passed to the upper layer.
	upper layer. Instead, the DMAC is forced to broadcast and the frame		Instead, the DMAC is forced to broadcast and the frame is passed to
	is passed to the 6top sublayer for switching.		the 6top sublayer for switching.
	At the egress 6TiSCH router, the reverse operation occurs. Based on		At the egress 6TiSCH router, the reverse operation occurs. Based on
	tunneling information of the Track, which may for instance indicate		tunneling information of the Track, which may for instance indicate
	that the tunneled datagram is an IP packet, the datagram is passed to		that the tunneled datagram is an IP packet, the datagram is passed to
	the appropriate Link-Layer with the destination MAC restored.		the appropriate Link-Layer with the destination MAC restored.
	4.6.1.3. Tunneling Information		4.6.1.3. Tunneling Information
	Tunneling information coming with the Track configuration provides		Tunneling information coming with the Track configuration provides
	the destination MAC address of the egress endpoint as well as the		the destination MAC address of the egress endpoint as well as the
	skipping to change at page 47, line 33 ¶		skipping to change at page 48, line 40 ¶
	source to resend the missing fragments selectively. The first		source to resend the missing fragments selectively. The first
	fragment may be resent to carve a new path in case of a path failure.		fragment may be resent to carve a new path in case of a path failure.
	The ECN echo set indicates that the number of outstanding fragments		The ECN echo set indicates that the number of outstanding fragments
	should be reduced.		should be reduced.
	4.7. Advanced 6TiSCH Routing		4.7. Advanced 6TiSCH Routing
	4.7.1. Packet Marking and Handling		4.7.1. Packet Marking and Handling
	All packets inside a 6TiSCH domain must carry the RPLInstanceID that		All packets inside a 6TiSCH domain must carry the RPLInstanceID that
	identifies the 6TiSCH topology that is to be used for routing and		identifies the 6TiSCH topology (e.g., a Track) that is to be used for
	forwarding that packet. The location of that information must be the		routing and forwarding that packet. The location of that information
	same for all packets forwarded inside the domain.		must be the same for all packets forwarded inside the domain.
	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
	by the IPv6 source address and a local RPLInstanceID in the packet		by 1) (typically) the IPv6 source or (possibly) destination address
	identify uniquely the Track and associated transmit bundle.		in the IPv6 Header and 2) a local RPLInstanceID in the RPI that
			serves as TrackID, identify uniquely the Track and associated
			transmit bundle.
	For packets that are routed by RPL, that information is the		For packets that are routed by RPL, that information is the
	RPLInstanceID which is carried in the RPL Packet Information (RPI),		RPLInstanceID which is carried in the RPL Packet Information (RPI),
	as discussed in section 11.2 of [RFC6550], "Loop Avoidance and		as discussed in section 11.2 of [RFC6550], "Loop Avoidance and
	Detection". The RPI is transported by a RPL option in the IPv6 Hop-		Detection". The RPI is transported by a RPL option in the IPv6 Hop-
	By-Hop Header [RFC6553].		By-Hop Header [RFC6553].
	A compression mechanism for the RPL packet artifacts that integrates		A compression mechanism for the RPL packet artifacts that integrates
	the compression of IP-in-IP encapsulation and the Routing Header type		the compression of IP-in-IP encapsulation and the Routing Header type
	3 [RFC6554] with that of the RPI in a 6LoWPAN dispatch/header type is		3 [RFC6554] with that of the RPI in a 6LoWPAN dispatch/header type is
	skipping to change at page 59, line 49 ¶		skipping to change at page 61, line 37 ¶
	Model in Ad Hoc Networks", RFC 5889, DOI 10.17487/RFC5889,		Model in Ad Hoc Networks", RFC 5889, DOI 10.17487/RFC5889,
	September 2010, <https://www.rfc-editor.org/info/rfc5889>.		September 2010, <https://www.rfc-editor.org/info/rfc5889>.
	[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>.
	[MIN-SECURITY]		[MIN-SECURITY]
	Vucinic, M., Simon, J., Pister, K., and M. Richardson,		Vucinic, M., Simon, J., Pister, K., and M. Richardson,
	"Minimal Security Framework for 6TiSCH", Work in Progress,		"Constrained Join Protocol (CoJP) for 6TiSCH", Work in
	Internet-Draft, draft-ietf-6tisch-minimal-security-12, 29		Progress, Internet-Draft, draft-ietf-6tisch-minimal-
	July 2019, <https://tools.ietf.org/html/draft-ietf-6tisch-		security-15, 10 December 2019,
	minimal-security-12>.		<https://tools.ietf.org/html/draft-ietf-6tisch-minimal-
			security-15>.
	[6BBR-DRAFT]		[6BBR-DRAFT]
	Thubert, P., Perkins, C., and E. Levy-Abegnoli, "IPv6		Thubert, P., Perkins, C., and E. Levy-Abegnoli, "IPv6
	Backbone Router", Work in Progress, Internet-Draft, draft-		Backbone Router", Work in Progress, Internet-Draft, draft-
	ietf-6lo-backbone-router-13, 26 September 2019,		ietf-6lo-backbone-router-20, 23 March 2020,
	<https://tools.ietf.org/html/draft-ietf-6lo-backbone-		<https://tools.ietf.org/html/draft-ietf-6lo-backbone-
	router-13>.		router-20>.
	[RECOV-FRAG]		[RECOV-FRAG]
	Thubert, P., "6LoWPAN Selective Fragment Recovery", Work		Thubert, P., "6LoWPAN Selective Fragment Recovery", Work
	in Progress, Internet-Draft, draft-ietf-6lo-fragment-		in Progress, Internet-Draft, draft-ietf-6lo-fragment-
	recovery-05, 22 July 2019, <https://tools.ietf.org/html/		recovery-21, 23 March 2020, <https://tools.ietf.org/html/
	draft-ietf-6lo-fragment-recovery-05>.		draft-ietf-6lo-fragment-recovery-21>.
	[MIN-FRAG] Watteyne, T., Bormann, C., and P. Thubert, "6LoWPAN		[MIN-FRAG] Watteyne, T., Thubert, P., and C. Bormann, "On Forwarding
	Fragment Forwarding", Work in Progress, Internet-Draft,		6LoWPAN Fragments over a Multihop IPv6 Network", Work in
	draft-ietf-6lo-minimal-fragment-04, 2 September 2019,		Progress, Internet-Draft, draft-ietf-6lo-minimal-fragment-
	<https://tools.ietf.org/html/draft-ietf-6lo-minimal-		15, 23 March 2020, <https://tools.ietf.org/html/draft-
	fragment-04>.		ietf-6lo-minimal-fragment-15>.
	[AP-ND] Thubert, P., Sarikaya, B., Sethi, M., and R. Struik,		[AP-ND] Thubert, P., Sarikaya, B., Sethi, M., and R. Struik,
	"Address Protected Neighbor Discovery for Low-power and		"Address Protected Neighbor Discovery for Low-power and
	Lossy Networks", Work in Progress, Internet-Draft, draft-		Lossy Networks", Work in Progress, Internet-Draft, draft-
	ietf-6lo-ap-nd-12, 10 April 2019,		ietf-6lo-ap-nd-23, 30 April 2020,
	<https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-12>.		<https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-23>.
	[USEofRPLinfo]		[USEofRPLinfo]
	Robles, I., Richardson, M., and P. Thubert, "Using RPL		Robles, I., Richardson, M., and P. Thubert, "Using RPI
	Option Type, Routing Header for Source Routes and IPv6-in-		Option Type, Routing Header for Source Routes and IPv6-in-
	IPv6 encapsulation in the RPL Data Plane", Work in		IPv6 encapsulation in the RPL Data Plane", Work in
	Progress, Internet-Draft, draft-ietf-roll-useofrplinfo-31,		Progress, Internet-Draft, draft-ietf-roll-useofrplinfo-42,
	7 August 2019, <https://tools.ietf.org/html/draft-ietf-		12 November 2020, <https://tools.ietf.org/html/draft-ietf-
	roll-useofrplinfo-31>.		roll-useofrplinfo-42>.
	[RUL-DRAFT]		[RUL-DRAFT]
	Thubert, P. and M. Richardson, "Routing for RPL Leaves",		Thubert, P. and M. Richardson, "Routing for RPL Leaves",
	Work in Progress, Internet-Draft, draft-ietf-roll-unaware-		Work in Progress, Internet-Draft, draft-ietf-roll-unaware-
	leaves-04, 9 September 2019, <https://tools.ietf.org/html/		leaves-23, 10 November 2020, <https://tools.ietf.org/html/
	draft-ietf-roll-unaware-leaves-04>.		draft-ietf-roll-unaware-leaves-23>.
	[ENH-BEACON]		[ENH-BEACON]
	Dujovne, D. and M. Richardson, "IEEE802.15.4 Informational		Dujovne, D. and M. Richardson, "IEEE 802.15.4 Information
	Element encapsulation of 6tisch Join and Enrollment		Element encapsulation of 6TiSCH Join and Enrollment
	Information", Work in Progress, Internet-Draft, draft-		Information", Work in Progress, Internet-Draft, draft-
	ietf-6tisch-enrollment-enhanced-beacon-05, 16 September		ietf-6tisch-enrollment-enhanced-beacon-14, 21 February
	2019, <https://tools.ietf.org/html/draft-ietf-6tisch-		2020, <https://tools.ietf.org/html/draft-ietf-6tisch-
	enrollment-enhanced-beacon-05>.		enrollment-enhanced-beacon-14>.
	[MSF] Chang, T., Vucinic, M., Vilajosana, X., Duquennoy, S., and		[MSF] 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-
	07, 17 October 2019,		18, 12 September 2020,
	<https://tools.ietf.org/html/draft-ietf-6tisch-msf-07>.		<https://tools.ietf.org/html/draft-ietf-6tisch-msf-18>.
	9. Informative References		9. Informative References
	[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF		[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
	for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,		for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
	<https://www.rfc-editor.org/info/rfc5340>.		<https://www.rfc-editor.org/info/rfc5340>.
	[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility		[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
	Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July		Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
	2011, <https://www.rfc-editor.org/info/rfc6275>.		2011, <https://www.rfc-editor.org/info/rfc6275>.
	skipping to change at page 63, line 32 ¶		skipping to change at page 65, line 21 ¶
	V. Mercieca, "Ad Hoc On-demand Distance Vector Version 2		V. Mercieca, "Ad Hoc On-demand Distance Vector Version 2
	(AODVv2) Routing", Work in Progress, Internet-Draft,		(AODVv2) Routing", Work in Progress, Internet-Draft,
	draft-ietf-manet-aodvv2-16, 4 May 2016,		draft-ietf-manet-aodvv2-16, 4 May 2016,
	<https://tools.ietf.org/html/draft-ietf-manet-aodvv2-16>.		<https://tools.ietf.org/html/draft-ietf-manet-aodvv2-16>.
	[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",		[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",
	RFC 8578, DOI 10.17487/RFC8578, May 2019,		RFC 8578, DOI 10.17487/RFC8578, May 2019,
	<https://www.rfc-editor.org/info/rfc8578>.		<https://www.rfc-editor.org/info/rfc8578>.
	[I-D.ietf-detnet-ip]		[I-D.ietf-detnet-ip]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,		Varga, B., Farkas, J., Berger, L., Fedyk, D., and S.
	Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", Work		Bryant, "DetNet Data Plane: IP", Work in Progress,
	in Progress, Internet-Draft, draft-ietf-detnet-ip-01, 1		Internet-Draft, draft-ietf-detnet-ip-07, 3 July 2020,
	July 2019,		<https://tools.ietf.org/html/draft-ietf-detnet-ip-07>.
	<https://tools.ietf.org/html/draft-ietf-detnet-ip-01>.
	[I-D.ietf-anima-bootstrapping-keyinfra]		[I-D.ietf-anima-bootstrapping-keyinfra]
	Pritikin, M., Richardson, M., Eckert, T., Behringer, M.,		Pritikin, M., Richardson, M., Eckert, T., Behringer, M.,
	and K. Watsen, "Bootstrapping Remote Secure Key		and K. Watsen, "Bootstrapping Remote Secure Key
	Infrastructures (BRSKI)", Work in Progress, Internet-		Infrastructures (BRSKI)", Work in Progress, Internet-
	Draft, draft-ietf-anima-bootstrapping-keyinfra-28, 19		Draft, draft-ietf-anima-bootstrapping-keyinfra-45, 11
	September 2019, <https://tools.ietf.org/html/draft-ietf-		November 2020, <https://tools.ietf.org/html/draft-ietf-
	anima-bootstrapping-keyinfra-28>.		anima-bootstrapping-keyinfra-45>.
	[I-D.ietf-roll-aodv-rpl]		[I-D.ietf-roll-aodv-rpl]
	Anamalamudi, S., Zhang, M., Perkins, C., Anand, S., and B.		Anamalamudi, S., Zhang, M., Perkins, C., Anand, S., and B.
	Liu, "Asymmetric AODV-P2P-RPL in Low-Power and Lossy		Liu, "AODV based RPL Extensions for Supporting Asymmetric
	Networks (LLNs)", Work in Progress, Internet-Draft, draft-		P2P Links in Low-Power and Lossy Networks", Work in
	ietf-roll-aodv-rpl-07, 12 April 2019,		Progress, Internet-Draft, draft-ietf-roll-aodv-rpl-08, 7
	<https://tools.ietf.org/html/draft-ietf-roll-aodv-rpl-07>.		May 2020,
			<https://tools.ietf.org/html/draft-ietf-roll-aodv-rpl-08>.
	[I-D.ietf-lwig-6lowpan-virtual-reassembly]		[I-D.ietf-lwig-6lowpan-virtual-reassembly]
	Bormann, C. and T. Watteyne, "Virtual reassembly buffers		Bormann, C. and T. Watteyne, "Virtual reassembly buffers
	in 6LoWPAN", Work in Progress, Internet-Draft, draft-ietf-		in 6LoWPAN", Work in Progress, Internet-Draft, draft-ietf-
	lwig-6lowpan-virtual-reassembly-01, 11 March 2019,		lwig-6lowpan-virtual-reassembly-02, 9 March 2020,
	<https://tools.ietf.org/html/draft-ietf-lwig-6lowpan-		<https://tools.ietf.org/html/draft-ietf-lwig-6lowpan-
	virtual-reassembly-01>.		virtual-reassembly-02>.
	[I-D.ietf-roll-dao-projection]		[I-D.ietf-roll-dao-projection]
	Thubert, P., Jadhav, R., Gillmore, M., and J. Pylakutty,		Thubert, P., Jadhav, R., and M. Gillmore, "Root initiated
	"Root initiated routing state in RPL", Work in Progress,		routing state in RPL", Work in Progress, Internet-Draft,
	Internet-Draft, draft-ietf-roll-dao-projection-06, 24 May		draft-ietf-roll-dao-projection-14, 2 October 2020,
	2019, <https://tools.ietf.org/html/draft-ietf-roll-dao-		<https://tools.ietf.org/html/draft-ietf-roll-dao-
	projection-06>.		projection-14>.
	[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", Work in Progress, Internet-Draft, draft-rahul-		extension", Work in Progress, Internet-Draft, draft-rahul-
	roll-mop-ext-01, 9 June 2019,		roll-mop-ext-01, 9 June 2019,
	<https://tools.ietf.org/html/draft-rahul-roll-mop-ext-01>.		<https://tools.ietf.org/html/draft-rahul-roll-mop-ext-01>.
	[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)", Work in Progress,		Diffie-Hellman Over COSE (EDHOC)", Work in Progress,
	skipping to change at page 65, line 15 ¶		skipping to change at page 67, line 8 ¶
	[I-D.thubert-6man-unicast-lookup]		[I-D.thubert-6man-unicast-lookup]
	Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery		Thubert, P. and E. Levy-Abegnoli, "IPv6 Neighbor Discovery
	Unicast Lookup", Work in Progress, Internet-Draft, draft-		Unicast Lookup", Work in Progress, Internet-Draft, draft-
	thubert-6man-unicast-lookup-00, 29 July 2019,		thubert-6man-unicast-lookup-00, 29 July 2019,
	<https://tools.ietf.org/html/draft-thubert-6man-unicast-		<https://tools.ietf.org/html/draft-thubert-6man-unicast-
	lookup-00>.		lookup-00>.
	[I-D.pthubert-raw-problem-statement]		[I-D.pthubert-raw-problem-statement]
	Thubert, P. and G. Papadopoulos, "Reliable and Available		Thubert, P. and G. Papadopoulos, "Reliable and Available
	Wireless Problem Statement", Work in Progress, Internet-		Wireless Problem Statement", Work in Progress, Internet-
	Draft, draft-pthubert-raw-problem-statement-03, 8 October		Draft, draft-pthubert-raw-problem-statement-04, 23 October
	2019, <https://tools.ietf.org/html/draft-pthubert-raw-		2019, <https://tools.ietf.org/html/draft-pthubert-raw-
	problem-statement-03>.		problem-statement-04>.
	[I-D.tiloca-6tisch-robust-scheduling]		[I-D.tiloca-6tisch-robust-scheduling]
	Tiloca, M., Duquennoy, S., and G. Dini, "Robust Scheduling		Tiloca, M., Duquennoy, S., and G. Dini, "Robust Scheduling
	against Selective Jamming in 6TiSCH Networks", Work in		against Selective Jamming in 6TiSCH Networks", Work in
	Progress, Internet-Draft, draft-tiloca-6tisch-robust-		Progress, Internet-Draft, draft-tiloca-6tisch-robust-
	scheduling-02, 10 June 2019, <https://tools.ietf.org/html/		scheduling-02, 10 June 2019, <https://tools.ietf.org/html/
	draft-tiloca-6tisch-robust-scheduling-02>.		draft-tiloca-6tisch-robust-scheduling-02>.
	[I-D.ietf-ace-coap-est]		[I-D.ietf-ace-coap-est]
	Stok, P., Kampanakis, P., Richardson, M., and S. Raza,		Stok, P., Kampanakis, P., Richardson, M., and S. Raza,
	"EST over secure CoAP (EST-coaps)", Work in Progress,		"EST over secure CoAP (EST-coaps)", Work in Progress,
	Internet-Draft, draft-ietf-ace-coap-est-15, 1 October		Internet-Draft, draft-ietf-ace-coap-est-18, 6 January
	2019,		2020,
	<https://tools.ietf.org/html/draft-ietf-ace-coap-est-15>.		<https://tools.ietf.org/html/draft-ietf-ace-coap-est-18>.
	[I-D.ietf-anima-constrained-voucher]		[I-D.ietf-anima-constrained-voucher]
	Richardson, M., Stok, P., and P. Kampanakis, "Constrained		Richardson, M., Stok, P., and P. Kampanakis, "Constrained
	Voucher Artifacts for Bootstrapping Protocols", Work in		Voucher Artifacts for Bootstrapping Protocols", Work in
	Progress, Internet-Draft, draft-ietf-anima-constrained-		Progress, Internet-Draft, draft-ietf-anima-constrained-
	voucher-05, 8 July 2019, <https://tools.ietf.org/html/		voucher-09, 2 November 2020, <https://tools.ietf.org/html/
	draft-ietf-anima-constrained-voucher-05>.		draft-ietf-anima-constrained-voucher-09>.
	[IEEE802154]		[IEEE802154]
	IEEE standard for Information Technology, "IEEE Std.		IEEE standard for Information Technology, "IEEE Std.
	802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)		802.15.4, Part. 15.4: Wireless Medium Access Control (MAC)
	and Physical Layer (PHY) Specifications for Low-Rate		and Physical Layer (PHY) Specifications for Low-Rate
	Wireless Personal Area Networks", October 2019.		Wireless Personal Area Networks".
	[CCMstar] Struik, R., "Formal Specification of the CCM* Mode of		[CCMstar] Struik, R., "Formal Specification of the CCM* Mode of
	Operation", September 2004, <www.ieee802.org/15/		Operation", September 2004, <www.ieee802.org/15/
	pub/2004/15-04-0537-00-004b-formal-specification-ccm-star-		pub/2004/15-04-0537-00-004b-formal-specification-ccm-star-
	mode-operation.doc>.		mode-operation.doc>.
	[IEEE802154e]		[IEEE802154e]
	IEEE standard for Information Technology, "IEEE standard		IEEE standard for Information Technology, "IEEE standard
	for Information Technology, IEEE Std. 802.15.4, Part.		for Information Technology, IEEE Std. 802.15.4, Part.
	15.4: Wireless Medium Access Control (MAC) and Physical		15.4: Wireless Medium Access Control (MAC) and Physical
	skipping to change at page 66, line 19 ¶		skipping to change at page 68, line 12 ¶
	Networks (LR-WPANs) Amendment 1: MAC sublayer", April		Networks (LR-WPANs) Amendment 1: MAC sublayer", April
	2012.		2012.
	[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.
	[HART] www.hartcomm.org, "Highway Addressable remote Transducer,		[HART] www.hartcomm.org, "Highway Addressable remote Transducer,
	a group of specifications for industrial process and		a group of specifications for industrial process and
	control devices administered by the HART Foundation",		control devices administered by the HART Foundation".
	October 2019.
	[ISA100.11a]		[ISA100.11a]
	ISA/ANSI, "Wireless Systems for Industrial Automation:		ISA/ANSI, "Wireless Systems for Industrial Automation:
	Process Control and Related Applications - ISA100.11a-2011		Process Control and Related Applications - ISA100.11a-2011
	- IEC 62734", 2011, <http://www.isa.org/Community/		- IEC 62734", 2011, <http://www.isa.org/Community/
	SP100WirelessSystemsforAutomation>.		SP100WirelessSystemsforAutomation>.
	[ISA100] ISA/ANSI, "ISA100, Wireless Systems for Automation",		[ISA100] ISA/ANSI, "ISA100, Wireless Systems for Automation",
	October 2019, <https://www.isa.org/isa100/>.		<https://www.isa.org/isa100/>.
	[TEAS] IETF, "Traffic Engineering Architecture and Signaling",		[TEAS] IETF, "Traffic Engineering Architecture and Signaling",
	October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-teas/>.		<https://dataTracker.ietf.org/doc/charter-ietf-teas/>.
	[ANIMA] IETF, "Autonomic Networking Integrated Model and		[ANIMA] IETF, "Autonomic Networking Integrated Model and
	Approach", October 2019,		Approach",
	<https://dataTracker.ietf.org/doc/charter-ietf-anima/>.		<https://dataTracker.ietf.org/doc/charter-ietf-anima/>.
	[PCE] IETF, "Path Computation Element", October 2019,		[PCE] IETF, "Path Computation Element",
	<https://dataTracker.ietf.org/doc/charter-ietf-pce/>.		<https://dataTracker.ietf.org/doc/charter-ietf-pce/>.
	[CCAMP] IETF, "Common Control and Measurement Plane", October		[CCAMP] IETF, "Common Control and Measurement Plane",
	2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>.		<https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>.
	[AMI] US Department of Energy, "Advanced Metering Infrastructure		[AMI] US Department of Energy, "Advanced Metering Infrastructure
	and Customer Systems", 2006,		and Customer Systems", 2006,
	<https://www.energy.gov/sites/prod/files/2016/12/f34/		<https://www.energy.gov/sites/prod/files/2016/12/f34/
	AMI%20Summary%20Report_09-26-16.pdf>.		AMI%20Summary%20Report_09-26-16.pdf>.
	[S-ALOHA] Roberts, L. G., "ALOHA Packet System With and Without		[S-ALOHA] Roberts, L. G., "ALOHA Packet System With and Without
	Slots and Capture", doi 10.1145/1024916.1024920, April		Slots and Capture", doi 10.1145/1024916.1024920, April
	1975, <https://dl.acm.org/citation.cfm?id=1024920>.		1975, <https://dl.acm.org/citation.cfm?id=1024920>.
	skipping to change at page 69, line 18 ¶		skipping to change at page 71, line 9 ¶
	management of resources that are controlled by heterogeneous		management of resources that are controlled by heterogeneous
	protocols such as ISA100.11a [ISA100.11a], WirelessHART		protocols such as ISA100.11a [ISA100.11a], WirelessHART
	[WirelessHART], and 6TiSCH. Interestingly, the establishment of		[WirelessHART], and 6TiSCH. Interestingly, the establishment of
	6TiSCH Deterministic paths, called Tracks, are also in scope, and		6TiSCH Deterministic paths, called Tracks, are also in scope, and
	ISA100.20 is working on requirements for DetNet.		ISA100.20 is working on requirements for DetNet.
	Author's Address		Author's Address
	Pascal Thubert (editor)		Pascal Thubert (editor)
	Cisco Systems, Inc		Cisco Systems, Inc
	Building D, 45 Allee des Ormes - BP1200		Building D
			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
End of changes. 43 change blocks.
	150 lines changed or deleted		161 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/