draft-ietf-6tisch-tsch-00.txt		draft-ietf-6tisch-tsch-01.txt
	6TiSCH T. Watteyne, Ed.		6TiSCH T. Watteyne, Ed.
	Internet-Draft Linear Technology		Internet-Draft Linear Technology
	Intended status: Informational MR. Palattella		Intended status: Informational MR. Palattella
	Expires: May 25, 2014 University of Luxembourg		Expires: January 5, 2015 University of Luxembourg
	LA. Grieco		LA. Grieco
	Politecnico di Bari		Politecnico di Bari
	November 21, 2013		July 4, 2014
	Using IEEE802.15.4e TSCH in an LLN context:		Using IEEE802.15.4e TSCH in an LLN context:
	Overview, Problem Statement and Goals		Overview, Problem Statement and Goals
	draft-ietf-6tisch-tsch-00		draft-ietf-6tisch-tsch-01
	Abstract		Abstract
	This document describes the environment, problem statement, and goals		This document describes the environment, problem statement, and goals
	for using the IEEE802.15.4e TSCH MAC protocol in the context of LLNs.		for using the IEEE802.15.4e TSCH MAC protocol in the context of LLNs.
	The set of goals enumerated in this document form an initial set		The set of goals enumerated in this document form an initial set
	only.		only.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 37		skipping to change at page 1, line 37
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 May 25, 2014.		This Internet-Draft will expire on January 5, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. TSCH in the LLN Context . . . . . . . . . . . . . . . . . . . 4		2. TSCH in the LLN Context . . . . . . . . . . . . . . . . . . . 4
	3. Problems and Goals . . . . . . . . . . . . . . . . . . . . . 5		3. Problems and Goals . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Network Formation . . . . . . . . . . . . . . . . . . . . 6		3.1. Network Formation . . . . . . . . . . . . . . . . . . . . 6
	3.2. Network Maintenance . . . . . . . . . . . . . . . . . . . 6		3.2. Network Maintenance . . . . . . . . . . . . . . . . . . . 6
	3.3. Multi-Hop Topology . . . . . . . . . . . . . . . . . . . 7		3.3. Multi-Hop Topology . . . . . . . . . . . . . . . . . . . 7
	3.4. Routing and Timing Parents . . . . . . . . . . . . . . . 7		3.4. Routing and Timing Parents . . . . . . . . . . . . . . . 7
	3.5. Resource Management . . . . . . . . . . . . . . . . . . . 7		3.5. Resource Management . . . . . . . . . . . . . . . . . . . 7
	3.6. Dataflow Control . . . . . . . . . . . . . . . . . . . . 8		3.6. Dataflow Control . . . . . . . . . . . . . . . . . . . . 8
	3.7. Deterministic Behavior . . . . . . . . . . . . . . . . . 8		3.7. Deterministic Behavior . . . . . . . . . . . . . . . . . 8
	3.8. Scheduling Mechanisms . . . . . . . . . . . . . . . . . . 8		3.8. Scheduling Mechanisms . . . . . . . . . . . . . . . . . . 8
	3.9. Secure Communication . . . . . . . . . . . . . . . . . . 9		3.9. Secure Communication . . . . . . . . . . . . . . . . . . 9
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9		4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		5. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	5.1. Normative References . . . . . . . . . . . . . . . . . . 9		5.1. Normative References . . . . . . . . . . . . . . . . . . 9
	5.2. Informative References . . . . . . . . . . . . . . . . . 9		5.2. Informative References . . . . . . . . . . . . . . . . . 9
	5.3. External Informative References . . . . . . . . . . . . . 12		5.3. External Informative References . . . . . . . . . . . . . 12
	Appendix A. TSCH Protocol Highlights . . . . . . . . . . . . . . 14		Appendix A. TSCH Protocol Highlights . . . . . . . . . . . . . . 15
	A.1. Timeslots . . . . . . . . . . . . . . . . . . . . . . . . 14		A.1. Timeslots . . . . . . . . . . . . . . . . . . . . . . . . 15
	A.2. Slotframes . . . . . . . . . . . . . . . . . . . . . . . 15		A.2. Slotframes . . . . . . . . . . . . . . . . . . . . . . . 15
	A.3. Node TSCH Schedule . . . . . . . . . . . . . . . . . . . 15		A.3. Node TSCH Schedule . . . . . . . . . . . . . . . . . . . 15
	A.4. Cells and Bundles . . . . . . . . . . . . . . . . . . . . 15		A.4. Cells and Bundles . . . . . . . . . . . . . . . . . . . . 16
	A.5. Dedicated vs. Shared Cells . . . . . . . . . . . . . . . 16		A.5. Dedicated vs. Shared Cells . . . . . . . . . . . . . . . 16
	A.6. Absolute Slot Number . . . . . . . . . . . . . . . . . . 16		A.6. Absolute Slot Number . . . . . . . . . . . . . . . . . . 17
	A.7. Channel Hopping . . . . . . . . . . . . . . . . . . . . . 16		A.7. Channel Hopping . . . . . . . . . . . . . . . . . . . . . 17
	A.8. Time Synchronization . . . . . . . . . . . . . . . . . . 17		A.8. Time Synchronization . . . . . . . . . . . . . . . . . . 18
	A.9. Power Consumption . . . . . . . . . . . . . . . . . . . . 18		A.9. Power Consumption . . . . . . . . . . . . . . . . . . . . 18
	A.10. Network TSCH Schedule . . . . . . . . . . . . . . . . . . 18		A.10. Network TSCH Schedule . . . . . . . . . . . . . . . . . . 19
	A.11. Join Process . . . . . . . . . . . . . . . . . . . . . . 18		A.11. Join Process . . . . . . . . . . . . . . . . . . . . . . 19
	A.12. Information Elements . . . . . . . . . . . . . . . . . . 19		A.12. Information Elements . . . . . . . . . . . . . . . . . . 19
	A.13. Extensibility . . . . . . . . . . . . . . . . . . . . . . 19		A.13. Extensibility . . . . . . . . . . . . . . . . . . . . . . 20
	Appendix B. TSCH Gotchas . . . . . . . . . . . . . . . . . . . . 19		Appendix B. TSCH Gotchas . . . . . . . . . . . . . . . . . . . . 20
	B.1. Collision Free Communication . . . . . . . . . . . . . . 19		B.1. Collision Free Communication . . . . . . . . . . . . . . 20
	B.2. Multi-Channel vs. Channel Hopping . . . . . . . . . . . . 19		B.2. Multi-Channel vs. Channel Hopping . . . . . . . . . . . . 20
	B.3. Cost of (continuous) Synchronization . . . . . . . . . . 20		B.3. Cost of (continuous) Synchronization . . . . . . . . . . 20
	B.4. Topology Stability . . . . . . . . . . . . . . . . . . . 20		B.4. Topology Stability . . . . . . . . . . . . . . . . . . . 21
	B.5. Multiple Concurrent Slotframes . . . . . . . . . . . . . 20		B.5. Multiple Concurrent Slotframes . . . . . . . . . . . . . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
	1. Introduction		1. Introduction
	The IEEE802.15.4e standard [IEEE802154e] was published in 2012 as an		The IEEE802.15.4e standard [IEEE802154e] was published in 2012 as an
	amendment to the Medium Access Control (MAC) protocol defined by the		amendment to the Medium Access Control (MAC) protocol defined by the
	IEEE802.15.4-2011 [IEEE802154] standard. The Timeslotted Channel		IEEE802.15.4-2011 [IEEE802154] standard. The Timeslotted Channel
	Hopping (TSCH) mode of IEEE802.15.4e is the object of this document.		Hopping (TSCH) mode of IEEE802.15.4e is the object of this document.
	This document describes the main issues arising from the adoption of		This document describes the main issues arising from the adoption of
	the IEEE802.15.4e TSCH in the LLN context, following the terminology		the IEEE802.15.4e TSCH in the LLN context, following the terminology
	defined in [I-D.palattella-6tisch-terminology].		defined in [I-D.ietf-6tisch-terminology].
	TSCH was designed to "allow IEEE802.15.4 devices to support a wide		TSCH was designed to "allow IEEE802.15.4 devices to support a wide
	range of industrial applications" [IEEE802154e]. At its core is a		range of industrial applications" [IEEE802154e]. At its core is a
	medium access technique which uses time synchronization to achieve		medium access technique which uses time synchronization to achieve
	ultra low-power operation and channel hopping to enable high		ultra low-power operation and channel hopping to enable high
	reliability. This is very different from the "legacy" IEEE802.15.4		reliability. This is very different from the "legacy" IEEE802.15.4
	MAC protocol, and is therefore better described as a "redesign".		MAC protocol, and is therefore better described as a "redesign".
	TSCH does not amend the physical layer; i.e., it can operate on any		TSCH does not amend the physical layer; i.e., it can operate on any
	IEEE802.15.4-compliant hardware.		IEEE802.15.4-compliant hardware.
	skipping to change at page 3, line 35		skipping to change at page 3, line 38
	conditions as well as the stringent reliability, availability, and		conditions as well as the stringent reliability, availability, and
	security requirements for an LLN to operate in an industrial		security requirements for an LLN to operate in an industrial
	environment. Commercial networking solutions are available today in		environment. Commercial networking solutions are available today in
	which motes consume 10's of micro-amps on average [CurrentCalculator]		which motes consume 10's of micro-amps on average [CurrentCalculator]
	with end-to-end packet delivery ratios over 99.999%		with end-to-end packet delivery ratios over 99.999%
	[doherty07channel].		[doherty07channel].
	IEEE802.15.4e TSCH focuses on the MAC layer only. This clean		IEEE802.15.4e TSCH focuses on the MAC layer only. This clean
	layering allows for TSCH to fit under an IPv6 enabled protocol stack		layering allows for TSCH to fit under an IPv6 enabled protocol stack
	for LLNs, running 6LoWPAN [RFC6282], RPL [RFC6550] and CoAP		for LLNs, running 6LoWPAN [RFC6282], RPL [RFC6550] and CoAP
	[I-D.ietf-core-coap].		[RFC7252].
	Bringing industrial-like performance into the LLN stack developed by		Bringing industrial-like performance into the LLN stack developed by
	the 6LoWPAN, ROLL and CORE working groups opens up new application		the 6LoWPAN, ROLL and CORE working groups opens up new application
	domains for these networks. Sensors deployed in smart cities		domains for these networks. Sensors deployed in smart cities
	[RFC5548] will be able to be installed for years without needing		[RFC5548] will be able to be installed for years without needing
	battery replacement. "Umbrella" networks will interconnect smart		battery replacement. "Umbrella" networks will interconnect smart
	elements from different entities in smart buildings [RFC5867]. Peel-		elements from different entities in smart buildings [RFC5867]. Peel-
	and-stick switches will obsolete the need for costly conduits for		and-stick switches will obsolete the need for costly conduits for
	lighting solutions in smart homes [RFC5826].		lighting solutions in smart homes [RFC5826].
	skipping to change at page 6, line 15		skipping to change at page 6, line 18
	power MAC protocols because of its scheduled nature. TSCH defines		power MAC protocols because of its scheduled nature. TSCH defines
	the mechanisms to execute a communication schedule, yet it is the		the mechanisms to execute a communication schedule, yet it is the
	entity that sets up that schedule which controls the topology of the		entity that sets up that schedule which controls the topology of the
	network. This scheduling entity also controls the resources		network. This scheduling entity also controls the resources
	allocated to each link in that topology.		allocated to each link in that topology.
	How this entity should operate is out of scope of TSCH. The		How this entity should operate is out of scope of TSCH. The
	remainder of this section highlights the problems this entity needs		remainder of this section highlights the problems this entity needs
	to address. For simplicity, we will refer to this entity by the		to address. For simplicity, we will refer to this entity by the
	generic name "6TiSCH". Note that the 6top sublayer, currently being		generic name "6TiSCH". Note that the 6top sublayer, currently being
	defined in [I-D.wang-6tsch-6top], can be seen as an embodiment of		defined in [I-D.wang-6tisch-6top-sublayer], can be seen as an
	this generic "6TiSCH".		embodiment of this generic "6TiSCH".
	Some of the issues 6TiSCH needs to target might overlap with the		Some of the issues 6TiSCH needs to target might overlap with the
	scope of other protocols (e.g., 6LoWPAN, RPL, and RSVP). In this		scope of other protocols (e.g., 6LoWPAN, RPL, and RSVP). In this
	case, it is entailed that 6TiSCH will profit from the services		case, it is entailed that 6TiSCH will profit from the services
	provided by other protocols to pursue these objectives.		provided by other protocols to pursue these objectives.
	3.1. Network Formation		3.1. Network Formation
	6TiSCH needs to control the way the network is formed, including how		6TiSCH needs to control the way the network is formed, including how
	new motes join, and how already joined motes advertise the presence		new motes join, and how already joined motes advertise the presence
	skipping to change at page 9, line 38		skipping to change at page 9, line 38
	5. References		5. References
	5.1. Normative References		5.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	5.2. Informative References		5.2. Informative References
	[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet		[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
	Networks", RFC 2464, December 1998.		Application Protocol (CoAP)", RFC 7252, June 2014.
	[RFC3819] Karn, P., Bormann, C., Fairhurst, G., Grossman, D.,		[RFC6755] Campbell, B. and H. Tschofenig, "An IETF URN Sub-Namespace
	Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L.		for OAuth", RFC 6755, October 2012.
	Wood, "Advice for Internet Subnetwork Designers", BCP 89,
	RFC 3819, July 2004.
	[RFC4919] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6		[RFC6606] Kim, E., Kaspar, D., Gomez, C., and C. Bormann, "Problem
	over Low-Power Wireless Personal Area Networks (6LoWPANs):		Statement and Requirements for IPv6 over Low-Power
	Overview, Assumptions, Problem Statement, and Goals", RFC		Wireless Personal Area Network (6LoWPAN) Routing", RFC
	4919, August 2007.		6606, May 2012.
	[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,		[RFC6568] Kim, E., Kaspar, D., and JP. Vasseur, "Design and
	"Transmission of IPv6 Packets over IEEE 802.15.4		Application Spaces for IPv6 over Low-Power Wireless
	Networks", RFC 4944, September 2007.		Personal Area Networks (6LoWPANs)", RFC 6568, April 2012.
	[RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,		[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
	"Routing Requirements for Urban Low-Power and Lossy		Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
	Networks", RFC 5548, May 2009.		Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
			Lossy Networks", RFC 6550, March 2012.
	[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation		[RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6
	Routing Requirements in Low-Power and Lossy Networks", RFC		Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
	5826, April 2010.		September 2011.
	[RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen,		[RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen,
	"Building Automation Routing Requirements in Low-Power and		"Building Automation Routing Requirements in Low-Power and
	Lossy Networks", RFC 5867, June 2010.		Lossy Networks", RFC 5867, June 2010.
			[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation
			Routing Requirements in Low-Power and Lossy Networks", RFC
			5826, April 2010.
	[RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney,		[RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney,
	"Industrial Routing Requirements in Low-Power and Lossy		"Industrial Routing Requirements in Low-Power and Lossy
	Networks", RFC 5673, October 2009.		Networks", RFC 5673, October 2009.
	[RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6		[RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,
	Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,		"Routing Requirements for Urban Low-Power and Lossy
	September 2011.		Networks", RFC 5548, May 2009.
	[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,		[RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler,
	Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.		"Transmission of IPv6 Packets over IEEE 802.15.4
	Alexander, "RPL: IPv6 Routing Protocol for Low-Power and		Networks", RFC 4944, September 2007.
	Lossy Networks", RFC 6550, March 2012.
	[RFC6568] Kim, E., Kaspar, D., and JP. Vasseur, "Design and		[RFC4919] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6
	Application Spaces for IPv6 over Low-Power Wireless		over Low-Power Wireless Personal Area Networks (6LoWPANs):
	Personal Area Networks (6LoWPANs)", RFC 6568, April 2012.		Overview, Assumptions, Problem Statement, and Goals", RFC
			4919, August 2007.
	[RFC6606] Kim, E., Kaspar, D., Gomez, C., and C. Bormann, "Problem		[RFC3819] Karn, P., Bormann, C., Fairhurst, G., Grossman, D.,
	Statement and Requirements for IPv6 over Low-Power		Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L.
	Wireless Personal Area Network (6LoWPAN) Routing", RFC		Wood, "Advice for Internet Subnetwork Designers", BCP 89,
	6606, May 2012.		RFC 3819, July 2004.
	[RFC6755] Campbell, B. and H. Tschofenig, "An IETF URN Sub-Namespace		[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
	for OAuth", RFC 6755, October 2012.		Networks", RFC 2464, December 1998.
	[I-D.wang-6tsch-6top]		[I-D.ietf-6tisch-tsch]
	Wang, Q., Vilajosana, X., and T. Watteyne, "6TSCH		Watteyne, T., Palattella, M., and L. Grieco, "Using
	Operation Sublayer (6top)", draft-wang-6tsch-6top-00 (work		IEEE802.15.4e TSCH in an LLN context: Overview, Problem
	in progress), July 2013.		Statement and Goals", draft-ietf-6tisch-tsch-00 (work in
			progress), November 2013.
	[I-D.palattella-6tisch-terminology]		[I-D.ietf-6tisch-architecture]
			Thubert, P., Watteyne, T., and R. Assimiti, "An
			Architecture for IPv6 over the TSCH mode of IEEE
			802.15.4e", draft-ietf-6tisch-architecture-02 (work in
			progress), June 2014.
			[I-D.ietf-6tisch-terminology]
	Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,		Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
	"Terminology in IPv6 over the TSCH mode of IEEE		"Terminology in IPv6 over the TSCH mode of IEEE
	802.15.4e", draft-palattella-6tisch-terminology-00 (work		802.15.4e", draft-ietf-6tisch-terminology-01 (work in
	in progress), October 2013.		progress), February 2014.
			[I-D.ietf-6tisch-minimal]
			Vilajosana, X. and K. Pister, "Minimal 6TiSCH
			Configuration", draft-ietf-6tisch-minimal-01 (work in
			progress), June 2014.
			[I-D.ietf-6tisch-6top-interface]
			Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
			Operation Sublayer (6top) Interface", draft-ietf-6tisch-
			6top-interface-00 (work in progress), March 2014.
			[I-D.wang-6tisch-6top-sublayer]
			Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
			Operation Sublayer (6top)", draft-wang-6tisch-6top-
			sublayer-00 (work in progress), February 2014.
			[I-D.ietf-6tisch-coap]
			Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and
			Interaction using CoAP", draft-ietf-6tisch-coap-00 (work
			in progress), May 2014.
	[I-D.thubert-roll-forwarding-frags]		[I-D.thubert-roll-forwarding-frags]
	Thubert, P. and J. Hui, "LLN Fragment Forwarding and		Thubert, P. and J. Hui, "LLN Fragment Forwarding and
	Recovery", draft-thubert-roll-forwarding-frags-02 (work in		Recovery", draft-thubert-roll-forwarding-frags-02 (work in
	progress), September 2013.		progress), September 2013.
	[I-D.tsao-roll-security-framework]		[I-D.tsao-roll-security-framework]
	Tsao, T., Alexander, R., Daza, V., and A. Lozano, "A		Tsao, T., Alexander, R., Daza, V., and A. Lozano, "A
	Security Framework for Routing over Low Power and Lossy		Security Framework for Routing over Low Power and Lossy
	Networks", draft-tsao-roll-security-framework-02 (work in		Networks", draft-tsao-roll-security-framework-02 (work in
	skipping to change at page 11, line 39		skipping to change at page 12, line 19
	[I-D.ietf-roll-p2p-rpl]		[I-D.ietf-roll-p2p-rpl]
	Goyal, M., Baccelli, E., Philipp, M., Brandt, A., and J.		Goyal, M., Baccelli, E., Philipp, M., Brandt, A., and J.
	Martocci, "Reactive Discovery of Point-to-Point Routes in		Martocci, "Reactive Discovery of Point-to-Point Routes in
	Low Power and Lossy Networks", draft-ietf-roll-p2p-rpl-17		Low Power and Lossy Networks", draft-ietf-roll-p2p-rpl-17
	(work in progress), March 2013.		(work in progress), March 2013.
	[I-D.ietf-roll-trickle-mcast]		[I-D.ietf-roll-trickle-mcast]
	Hui, J. and R. Kelsey, "Multicast Protocol for Low power		Hui, J. and R. Kelsey, "Multicast Protocol for Low power
	and Lossy Networks (MPL)", draft-ietf-roll-trickle-		and Lossy Networks (MPL)", draft-ietf-roll-trickle-
	mcast-05 (work in progress), August 2013.		mcast-09 (work in progress), April 2014.
	[I-D.thubert-6lowpan-backbone-router]		[I-D.thubert-6lowpan-backbone-router]
	Thubert, P., "6LoWPAN Backbone Router", draft-thubert-		Thubert, P., "6LoWPAN Backbone Router", draft-thubert-
	6lowpan-backbone-router-03 (work in progress), February		6lowpan-backbone-router-03 (work in progress), February
	2013.		2013.
	[I-D.sarikaya-core-sbootstrapping]		[I-D.sarikaya-core-sbootstrapping]
	Sarikaya, B., Ohba, Y., Moskowitz, R., Cao, Z., and R.		Sarikaya, B., Ohba, Y., Moskowitz, R., Cao, Z., and R.
	Cragie, "Security Bootstrapping Solution for Resource-		Cragie, "Security Bootstrapping Solution for Resource-
	Constrained Devices", draft-sarikaya-core-		Constrained Devices", draft-sarikaya-core-
	skipping to change at page 12, line 17		skipping to change at page 12, line 44
	Object Security Workshop', 23rd March 2012, Paris,		Object Security Workshop', 23rd March 2012, Paris,
	France", draft-gilger-smart-object-security-workshop-00		France", draft-gilger-smart-object-security-workshop-00
	(work in progress), October 2012.		(work in progress), October 2012.
	[I-D.phinney-roll-rpl-industrial-applicability]		[I-D.phinney-roll-rpl-industrial-applicability]
	Phinney, T., Thubert, P., and R. Assimiti, "RPL		Phinney, T., Thubert, P., and R. Assimiti, "RPL
	applicability in industrial networks", draft-phinney-roll-		applicability in industrial networks", draft-phinney-roll-
	rpl-industrial-applicability-02 (work in progress),		rpl-industrial-applicability-02 (work in progress),
	February 2013.		February 2013.
	[I-D.ietf-core-coap]
	Shelby, Z., Hartke, K., and C. Bormann, "Constrained
	Application Protocol (CoAP)", draft-ietf-core-coap-18
	(work in progress), June 2013.
	5.3. External Informative References		5.3. External Informative References
	[IEEE802154e]		[IEEE802154e]
	IEEE standard for Information Technology, "IEEE std.		IEEE standard for Information Technology, "IEEE std.
	802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area		802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area
	Networks (LR-WPANs) Amendament 1: MAC sublayer", April		Networks (LR-WPANs) Amendament 1: MAC sublayer", April
	2012.		2012.
	[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", June 2011.		Wireless Personal Area Networks", June 2011.
	[OpenWSN] , "Berkeley's OpenWSN Project Homepage",		[OpenWSN] "Berkeley's OpenWSN Project Homepage",
	<http://www.openwsn.org/>.		<http://www.openwsn.org/>.
	[OpenWSNETT]		[OpenWSNETT]
	Watteyne, T., Vilajosana, X., Kerkez, B., Chraim, F.,		Watteyne, T., Vilajosana, X., Kerkez, B., Chraim, F.,
	Weekly, K., Wang, Q., Glaser, S., and K. Pister, "OpenWSN:		Weekly, K., Wang, Q., Glaser, S., and K. Pister, "OpenWSN:
	a standards-based low-power wireless development		a Standards-Based Low-Power Wireless Development
	environment", Transactions on Emerging Telecommunications		Environment", Transactions on Emerging Telecommunications
	Technologies 2012, August 2012, <http://		Technologies , August 2012.
	onlinelibrary.wiley.com/doi/10.1002/ett.2558/abstract>.
	[IPSO] , "IP for Smart Objects Alliance Homepage",		[IPSO] "IP for Smart Objects Alliance Homepage",
	<http://www.ipso-alliance.org/>.		<http://www.ipso-alliance.org/>.
	[CurrentCalculator]		[CurrentCalculator]
	Linear Technology, "Application Note: Using the Current		Linear Technology, "Application Note: Using the Current
	Calculator to Estimate Mote Power", August 2012, <http://		Calculator to Estimate Mote Power", August 2012,
	cds.linear.com/docs/en/application-note/Application_Note_-		<http://cds.linear.com/docs/en/application-note/
			Application_Note_-
	_Using_the_Current_Calculator_to_Estimate_Mote_Power.pdf>.		_Using_the_Current_Calculator_to_Estimate_Mote_Power.pdf>.
	[doherty07channel]		[doherty07channel]
	Doherty, L., Lindsay, W., and J. Simon, "Channel-Specific		Doherty, L., Lindsay, W., and J. Simon, "Channel-Specific
	Wireless Sensor Network Path Data", IEEE International		Wireless Sensor Network Path Data", IEEE International
	Conference on Computer Communications and Networks (ICCCN)		Conference on Computer Communications and Networks (ICCCN)
	2008, 2007.		2008, 2007.
	[tinka10decentralized]		[tinka10decentralized]
	Tinka, A., Watteyne, T., and K. Pister, "A Decentralized		Tinka, A., Watteyne, T., and K. Pister, "A Decentralized
	Scheduling Algorithm for Time Synchronized Channel		Scheduling Algorithm for Time Synchronized Channel
	Hopping", Ad Hoc Networks 2010, 2010, < http://		Hopping", Ad Hoc Networks 2010, 2010, <
	robotics.eecs.berkeley.edu/~pister/publications/2008/		http://robotics.eecs.berkeley.edu/~pister/
	TSMP%20DSN08.pdf>.		publications/2008/TSMP%20DSN08.pdf>.
	[watteyne09reliability]		[watteyne09reliability]
	Watteyne, T., Mehta, A., and K. Pister, "Reliability		Watteyne, T., Mehta, A., and K. Pister, "Reliability
	Through Frequency Diversity: Why Channel Hopping Makes		Through Frequency Diversity: Why Channel Hopping Makes
	Sense", International Conference on Performance Evaluation		Sense", International Conference on Performance Evaluation
	of Wireless Ad Hoc, Sensor, and Ubiquitous Networks (PE-		of Wireless Ad Hoc, Sensor, and Ubiquitous Networks (PE-
	WASUN) 2009, Oct. 2009, <http://www.ietf.org/mail-archive/		WASUN) 2009, Oct. 2009, <http://www.ietf.org/mail-
	web/roll/current/pdfa_EzmuDIv3.pdf>.		archive/web/roll/current/pdfa_EzmuDIv3.pdf>.
	[kerkez09feasibility]		[kerkez09feasibility]
	Kerkez, B., Watteyne, T., and M. Magliocco, "Feasibility		Kerkez, B., Watteyne, T., and M. Magliocco, "Feasibility
	analysis of controller design for adaptive channel		analysis of controller design for adaptive channel
	hopping", International Workshop on Performance		hopping", International Workshop on Performance
	Methodologies and Tools for Wireless Sensor Networks		Methodologies and Tools for Wireless Sensor Networks
	(WSNPERF) 2009, Oct. 2009, <http://www-		(WSNPERF) 2009, Oct. 2009, <http://www-
	bsac.eecs.berkeley.edu/publications/search/		bsac.eecs.berkeley.edu/publications/search/
	send_publication_pdf2client.php?pubID=1249681245>.		send_publication_pdf2client.php?pubID=1249681245>.
	[TASA-PIMRC]		[TASA-PIMRC]
	Palattella, MR., Accettura, N., Dohler, M., Grieco, LA.,		Palattella, MR., Accettura, N., Dohler, M., Grieco, LA.,
	and G. Boggia, "Traffic Aware Scheduling Algorithm for		and G. Boggia, "Traffic Aware Scheduling Algorithm for
	Multi-Hop IEEE 802.15.4e Networks", IEEE PIMRC 2012, Sept.		Multi-Hop IEEE 802.15.4e Networks", IEEE PIMRC 2012, Sept.
	2012, < http://www.cttc.es/resources/doc/120531-submitted-		2012, < http://www.cttc.es/resources/
	tasa-25511.pdf>.		doc/120531-submitted-tasa-25511.pdf>.
	[TASA-SENSORS]		[TASA-SENSORS]
	Palattella, MR., Accettura, N., Dohler, M., Grieco, LA.,		Palattella, MR., Accettura, N., Dohler, M., Grieco, LA.,
	and G. Boggia, "Traffic-Aware Time-Critical Scheduling In		and G. Boggia, "Traffic-Aware Time-Critical Scheduling In
	Heavily Duty-Cycled IEEE 802.15.4e For An Industrial IoT",		Heavily Duty-Cycled IEEE 802.15.4e For An Industrial IoT",
	IEEE SENSORS 2012, Oct. 2012, < http://www.cttc.es/		IEEE SENSORS 2012, Oct. 2012, <
	resources/doc/120821-sensors2012-4396981770946977737.pdf>.		http://www.cttc.es/resources/
			doc/120821-sensors2012-4396981770946977737.pdf>.
	[TASA-WCNC]		[TASA-WCNC]
	Accettura, N., Palattella, MR., Dohler, M., Grieco, LA.,		Accettura, N., Palattella, MR., Dohler, M., Grieco, LA.,
	and G. Boggia, "Standardized Power-Efficient and Internet-		and G. Boggia, "Standardized Power-Efficient and Internet-
	Enabled Communication Stack for Capillary M2M Networks",		Enabled Communication Stack for Capillary M2M Networks",
	IEEE WCNC 2012, Apr. 2012, < http://www.cttc.es/resources/		IEEE WCNC 2012, Apr. 2012, < http://www.cttc.es/resources/
	doc/120109-1569521283-submitted-58230.pdf>.		doc/120109-1569521283-submitted-58230.pdf>.
	[palattella12standardized]		[palattella12standardized]
	Palattella, MR., Accettura, N., Vilajosana, X., Watteyne,		Palattella, MR., Accettura, N., Vilajosana, X., Watteyne,
	T., Grieco, LA., Boggia, G., and M. Dohler, "Standardized		T., Grieco, LA., Boggia, G., and M. Dohler, "Standardized
	Protocol Stack For The Internet Of (Important) Things",		Protocol Stack For The Internet Of (Important) Things",
	IEEE Communications Surveys and Tutorials 2012, Dec. 2012,		IEEE Communications Surveys and Tutorials 2012, Dec. 2012,
	< http://www.cttc.es/resources/doc/121025		< http://www.cttc.es/resources/doc/121025-
	-completestackforiot-clean-4818610916636121981.pdf>.		completestackforiot-clean-4818610916636121981.pdf>.
	[PANA] Kanda, M., Ohba, Y., Das, S., and S. Chasko, "PANA		[PANA] Kanda, M., Ohba, Y., Das, S., and S. Chasko, "PANA
	applicability in constrained environments", Febr. 2012,		applicability in constrained environments", Febr. 2012, <h
	<http://www.lix.polytechnique.fr/hipercom/		ttp://www.lix.polytechnique.fr/hipercom/SmartObjectSecurit
	SmartObjectSecurity/papers/MitsuruKanda.pdf>.		y/papers/MitsuruKanda.pdf>.
	Appendix A. TSCH Protocol Highlights		Appendix A. TSCH Protocol Highlights
	This appendix gives an overview of the key features of the		This appendix gives an overview of the key features of the
	IEEE802.15.4e Timeslotted Channel Hopping (TSCH) amendment. It makes		IEEE802.15.4e Timeslotted Channel Hopping (TSCH) amendment. It makes
	no attempt at repeating the standard, but rather focuses on the		no attempt at repeating the standard, but rather focuses on the
	following:		following:
	o Concepts which are sufficiently different from traditional		o Concepts which are sufficiently different from traditional
	IEEE802.15.4 networking that they may need to be defined and		IEEE802.15.4 networking that they may need to be defined and
	skipping to change at page 20, line 23		skipping to change at page 20, line 51
	When there is traffic in the network, motes which are communicating		When there is traffic in the network, motes which are communicating
	implicitly re-synchronize using the data frames they exchange. In		implicitly re-synchronize using the data frames they exchange. In
	the absence of data traffic, motes are required to synchronize to		the absence of data traffic, motes are required to synchronize to
	their time source neighbor(s) periodically not to drift in time. If		their time source neighbor(s) periodically not to drift in time. If
	they have not been communicating for some time (typically 30s), motes		they have not been communicating for some time (typically 30s), motes
	can exchange an dummy data frame to re-synchronize. The frequency at		can exchange an dummy data frame to re-synchronize. The frequency at
	which such messages need to be transmitted depends on the stability		which such messages need to be transmitted depends on the stability
	of the clock source, and on how "early" each mote starts listening		of the clock source, and on how "early" each mote starts listening
	for data (the "guard time"). Theoretically, with a 10ppm clock and a		for data (the "guard time"). Theoretically, with a 10ppm clock and a
	1ms guard time, this period can be 100s. Assuming this exchange		1ms guard time, this period can be 100s. Assuming this exchange
	causes the mote's radio to be on for 5ms, this yields a radio duty		causes the mote's radio to be on for 5ms, this yields a radio duty
	cycle needed to keep synchronized of 5ms/100s=0.005%. While TSCH does		cycle needed to keep synchronized of 5ms/100s=0.005%. While TSCH does
	requires motes to resynchronize periodically, the cost of doing so is		requires motes to resynchronize periodically, the cost of doing so is
	very low.		very low.
	B.4. Topology Stability		B.4. Topology Stability
	The channel hopping nature of TSCH causes links to be very "stable".		The channel hopping nature of TSCH causes links to be very "stable".
	Wireless phenomena such as multi-path fading and external		Wireless phenomena such as multi-path fading and external
	interference impact a wireless link between two motes differently on		interference impact a wireless link between two motes differently on
End of changes. 45 change blocks.
	96 lines changed or deleted		123 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/