< draft-ietf-6tisch-terminology-05.txt		draft-ietf-6tisch-terminology-06.txt >
	6TiSCH MR. Palattella, Ed.		6TiSCH MR. Palattella, Ed.
	Internet-Draft SnT/Univ. of Luxembourg		Internet-Draft SnT/Univ. of Luxembourg
	Intended status: Informational P. Thubert		Intended status: Informational P. Thubert
	Expires: January 7, 2016 cisco		Expires: May 5, 2016 cisco
	T. Watteyne		T. Watteyne
	Linear Technology / Dust Networks		Linear Technology / Dust Networks
	Q. Wang		Q. Wang
	Univ. of Sci. and Tech. Beijing		Univ. of Sci. and Tech. Beijing
	July 6, 2015		November 2, 2015
	Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e		Terminology in IPv6 over the TSCH mode of IEEE 802.15.4e
	draft-ietf-6tisch-terminology-05		draft-ietf-6tisch-terminology-06
	Abstract		Abstract
	6TiSCH proposes an architecture for an IPv6 multi-link subnet that is		6TiSCH proposes an architecture for an IPv6 multi-link subnet that is
	composed of a high speed powered backbone and a number of		composed of a high speed powered backbone and a number of
	IEEE802.15.4e TSCH wireless networks attached and synchronized by		IEEE802.15.4e TSCH wireless networks attached and synchronized by
	backbone routers. This document extends existing terminology		backbone routers. This document extends existing terminology
	documents available for Low-power and Lossy Networks to provide		documents available for Low-power and Lossy Networks to provide
	additional terminology elements.		additional terminology elements.
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 January 7, 2016.		This Internet-Draft will expire on May 5, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 26 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 10		4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
	6.1. Normative References . . . . . . . . . . . . . . . . . . 10		6.1. Normative References . . . . . . . . . . . . . . . . . . 11
	6.2. Informative References . . . . . . . . . . . . . . . . . 11		6.2. Informative References . . . . . . . . . . . . . . . . . 12
	6.3. External Informative References . . . . . . . . . . . . . 12		6.3. External Informative References . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
	1. Introduction		1. Introduction
	The IEEE802.15.4 Medium Access Control (MAC) has evolved with		The IEEE802.15.4 Medium Access Control (MAC) has evolved with
	IEEE802.15.4e which provides in particular the Time Slotted Channel		IEEE802.15.4e which provides in particular the Time Slotted Channel
	Hopping (TSCH) mode for industrial-type applications. It provides		Hopping (TSCH) mode for industrial-type applications. It provides
	deterministic capabilities to the point that a packet that pertains		deterministic capabilities to the point that a packet that pertains
	to a certain flow crosses the network from node to node following a		to a certain flow crosses the network from node to node following a
	very precise schedule, like a train leaves intermediate stations at		very precise schedule, like a train leaves intermediate stations at
	precise times along its path.		precise times along its path.
	skipping to change at page 3, line 25 ¶		skipping to change at page 3, line 25 ¶
	allocation of resources; and (iii) the architecture to		allocation of resources; and (iii) the architecture to
	bind them together, for use in IPv6 TSCH based networks.		bind them together, for use in IPv6 TSCH based networks.
	6F: IPv6 Forwarding. One of the three forwarding models		6F: IPv6 Forwarding. One of the three forwarding models
	supported by 6TiSCH. Packets are routed at layer 3,		supported by 6TiSCH. Packets are routed at layer 3,
	where Quality of Service (QoS) and Active Queue		where Quality of Service (QoS) and Active Queue
	Management (e.g., Random Early Detection, RED, [RFC2309])		Management (e.g., Random Early Detection, RED, [RFC2309])
	operations are expected to prioritize flows with		operations are expected to prioritize flows with
	differentiated services.		differentiated services.
	6top: 6top is the adaptation sublayer between TSCH and upper		6top: The "6TiSCH Operation Sublayer" (6top) is the next
	layers like IPv6 over Low-Power Wireless Personal Area		highest layer of the IEEE802.15.4e TSCH medium access
	Networks (6LoWPANs) and IPv6 Routing Protocol for Low-		control layer. It implements and terminates the "6top
	Power and Lossy Networks (RPL). It is defined in		Protocol" (6P), and contains a "6top Scheduling Function"
	[I-D.wang-6tisch-6top-sublayer].		(SF). It is defined in [I-D.wang-6tisch-6top-sublayer].
	6top Data Convey Model: Model describing how the 6top adaptation		6top Data Convey Model: Model describing how the 6top adaptation
	layer feeds the data flow coming from upper layers into		layer feeds the data flow coming from upper layers into
	TSCH. It is composed by an I-MUX module, a MUX module, a		TSCH. It is composed by an I-MUX module, a MUX module, a
	set of priority queues, and a PDU (Payload Data Unit).		set of priority queues, and a PDU (Payload Data Unit).
	See [I-D.wang-6tisch-6top-sublayer].		See [I-D.wang-6tisch-6top-sublayer].
			SF: The "6top Scheduling Function" (SF) is the policy inside
			the "6TiSCH Operation Sublayer" (6top) which decides when
			to add/remove cells. It is defined in
			[I-D.wang-6tisch-6top-sublayer].
			SFID: The "6top Scheduling Function Identifier" (SFID) is a
			4-bit field identifying a SF. It is defined in
			[I-D.wang-6tisch-6top-sublayer].
			6P: The "6top Protocol" (6P) allows neighbor nodes to
			communicate to add/delete cells to one another in their
			TSCH schedule. It is defined in
			[I-D.wang-6tisch-6top-sublayer].
			6P Transaction: Part of the "6top Protocol" (6P), the action of two
			neighbors exchanging a 6P request message and the
			corresponding 6P response message. It is defined in
			[I-D.wang-6tisch-6top-sublayer].
	ARO: [RFC6775] defines a number of new Neighbor Discovery		ARO: [RFC6775] defines a number of new Neighbor Discovery
	options including the Address Registration Option (ARO).		options including the Address Registration Option (ARO).
	ASN: Absolute Slot Number, the total number of timeslots that		ASN: Absolute Slot Number, the total number of timeslots that
	has elapsed since the PAN coordinator has started the		has elapsed since the PAN coordinator has started the
	TSCH network. It is incremented by one at each timeslot.		TSCH network. It is incremented by one at each timeslot.
	It is wide enough to not roll over in practice. See		It is wide enough to not roll over in practice. See
	[IEEE802154e].		[IEEE802154e].
	Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e],		Blacklist of Frequencies: Simply defined Blacklist in [IEEE802154e],
	skipping to change at page 10, line 40 ¶		skipping to change at page 11, line 15 ¶
	5. Acknowledgments		5. Acknowledgments
	Thanks to the IoT6 European Project (STREP) of the 7th Framework		Thanks to the IoT6 European Project (STREP) of the 7th Framework
	Program (Grant 288445).		Program (Grant 288445).
	6. References		6. References
	6.1. Normative References		6.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, DOI 10.17487/
			RFC2119, March 1997,
			<http://www.rfc-editor.org/info/rfc2119>.
	[RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering,		[RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering,
	S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G.,		S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G.,
	Partridge, C., Peterson, L., Ramakrishnan, K., Shenker,		Partridge, C., Peterson, L., Ramakrishnan, K., Shenker,
	S., Wroclawski, J., and L. Zhang, "Recommendations on		S., Wroclawski, J., and L. Zhang, "Recommendations on
	Queue Management and Congestion Avoidance in the		Queue Management and Congestion Avoidance in the
	Internet", RFC 2309, April 1998.		Internet", RFC 2309, DOI 10.17487/RFC2309, April 1998,
			<http://www.rfc-editor.org/info/rfc2309>.
	[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between		[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
	Information Models and Data Models", RFC 3444, January		Information Models and Data Models", RFC 3444, DOI
	2003.		10.17487/RFC3444, January 2003,
			<http://www.rfc-editor.org/info/rfc3444>.
	[RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.		[RFC5191] Forsberg, D., Ohba, Y., Ed., Patil, B., Tschofenig, H.,
	Yegin, "Protocol for Carrying Authentication for Network		and A. Yegin, "Protocol for Carrying Authentication for
	Access (PANA)", RFC 5191, May 2008.		Network Access (PANA)", RFC 5191, DOI 10.17487/RFC5191,
			May 2008, <http://www.rfc-editor.org/info/rfc5191>.
	[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer		[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
	Security Version 1.2", RFC 6347, January 2012.		Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
			January 2012, <http://www.rfc-editor.org/info/rfc6347>.
	[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,		[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
	Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.		Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
	Alexander, "RPL: IPv6 Routing Protocol for Low-Power and		JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
	Lossy Networks", RFC 6550, March 2012.		Low-Power and Lossy Networks", RFC 6550, DOI 10.17487/
			RFC6550, March 2012,
			<http://www.rfc-editor.org/info/rfc6550>.
	[RFC6552] Thubert, P., "Objective Function Zero for the Routing		[RFC6552] Thubert, P., Ed., "Objective Function Zero for the Routing
	Protocol for Low-Power and Lossy Networks (RPL)", RFC		Protocol for Low-Power and Lossy Networks (RPL)", RFC
	6552, March 2012.		6552, DOI 10.17487/RFC6552, March 2012,
			<http://www.rfc-editor.org/info/rfc6552>.
	[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,		[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
	"Neighbor Discovery Optimization for IPv6 over Low-Power		Bormann, "Neighbor Discovery Optimization for IPv6 over
	Wireless Personal Area Networks (6LoWPANs)", RFC 6775,		Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC
	November 2012.		6775, DOI 10.17487/RFC6775, November 2012,
			<http://www.rfc-editor.org/info/rfc6775>.
	[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained		[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
	Application Protocol (CoAP)", RFC 7252, June 2014.		Application Protocol (CoAP)", RFC 7252, DOI 10.17487/
			RFC7252, June 2014,
			<http://www.rfc-editor.org/info/rfc7252>.
	[RFC7554] Watteyne, T., Palattella, M., and L. Grieco, "Using IEEE		[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
	802.15.4e Time-Slotted Channel Hopping (TSCH) in the		IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the
	Internet of Things (IoT): Problem Statement", RFC 7554,		Internet of Things (IoT): Problem Statement", RFC 7554,
	May 2015.		DOI 10.17487/RFC7554, May 2015,
			<http://www.rfc-editor.org/info/rfc7554>.
	6.2. Informative References		6.2. Informative References
	[I-D.chakrabarti-nordmark-6man-efficient-nd]		[I-D.chakrabarti-nordmark-6man-efficient-nd]
	Chakrabarti, S., Nordmark, E., Thubert, P., and M.		Chakrabarti, S., Nordmark, E., Thubert, P., and M.
	Wasserman, "IPv6 Neighbor Discovery Optimizations for		Wasserman, "IPv6 Neighbor Discovery Optimizations for
	Wired and Wireless Networks", draft-chakrabarti-nordmark-		Wired and Wireless Networks", draft-chakrabarti-nordmark-
	6man-efficient-nd-07 (work in progress), February 2015.		6man-efficient-nd-07 (work in progress), February 2015.
	[I-D.ietf-roll-terminology]		[I-D.ietf-roll-terminology]
	skipping to change at page 12, line 11 ¶		skipping to change at page 12, line 46 ¶
	Thubert, P. and P. Stok, "Requirements for an update to		Thubert, P. and P. Stok, "Requirements for an update to
	6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06		6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-06
	(work in progress), January 2015.		(work in progress), January 2015.
	[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.wang-6tisch-6top-sublayer]		[I-D.wang-6tisch-6top-sublayer]
	Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH		Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer
	Operation Sublayer (6top)", draft-wang-6tisch-6top-		(6top)", draft-wang-6tisch-6top-sublayer-02 (work in
	sublayer-01 (work in progress), July 2014.		progress), October 2015.
	6.3. External Informative References		6.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) Amendment 1: MAC sublayer", April		Networks (LR-WPANs) Amendment 1: MAC sublayer", April
	2012.		2012.
	Authors' Addresses		Authors' Addresses
End of changes. 20 change blocks.
	40 lines changed or deleted		72 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/