< draft-ietf-6tisch-terminology-06.txt		draft-ietf-6tisch-terminology-07.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: May 5, 2016 cisco		Expires: September 22, 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
	November 2, 2015		March 21, 2016
	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-06		draft-ietf-6tisch-terminology-07
	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 May 5, 2016.		This Internet-Draft will expire on September 22, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	skipping to change at page 3, line 27 ¶		skipping to change at page 3, line 27 ¶
	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: The "6TiSCH Operation Sublayer" (6top) is the next		6top: The "6TiSCH Operation Sublayer" (6top) is the next
	highest layer of the IEEE802.15.4e TSCH medium access		highest layer of the IEEE802.15.4e TSCH medium access
	control layer. It implements and terminates the "6top		control layer in the 6TiSCH Architecture. It implements
	Protocol" (6P), and contains a "6top Scheduling Function"		and terminates the "6top Protocol" (6P), and contains one
	(SF). It is defined in [I-D.wang-6tisch-6top-sublayer].		or more "6top Scheduling Function" (SF). It is defined
			in [I-D.wang-6tisch-6top-protocol].
	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-protocol].
	SF: The "6top Scheduling Function" (SF) is the policy inside		SF: The "6top Scheduling Function" (SF) is the policy inside
	the "6TiSCH Operation Sublayer" (6top) which decides when		the "6TiSCH Operation Sublayer" (6top) which decides when
	to add/remove cells. It is defined in		to add/remove cells. General guidelines for designing a
	[I-D.wang-6tisch-6top-sublayer].		SF are provided in [I-D.wang-6tisch-6top-protocol].
	SFID: The "6top Scheduling Function Identifier" (SFID) is a		SFID: The "6top Scheduling Function Identifier" (SFID) is a
	4-bit field identifying a SF. It is defined in		1-byte field identifying a SF. It is defined in
	[I-D.wang-6tisch-6top-sublayer].		[I-D.wang-6tisch-6top-protocol].
	6P: The "6top Protocol" (6P) allows neighbor nodes to		6P: The "6top Protocol" (6P) allows neighbor nodes to
	communicate to add/delete cells to one another in their		communicate to add/delete cells to one another in their
	TSCH schedule. It is defined in		TSCH schedule. It is defined in
	[I-D.wang-6tisch-6top-sublayer].		[I-D.wang-6tisch-6top-protocol].
	6P Transaction: Part of the "6top Protocol" (6P), the action of two		6P Transaction: Part of the "6top Protocol" (6P), it consists in a
	neighbors exchanging a 6P request message and the		complete negotiation between two neighbor nodes. A
	corresponding 6P response message. It is defined in		transaction starts when a node wishes to add/delete one
	[I-D.wang-6tisch-6top-sublayer].		or more cells to one of its neighbors; it ends when the
			cell(s) have been added / deleted from the schedule of
			both neighbor, or when the transaction has failed. It is
			defined in [I-D.wang-6tisch-6top-protocol].
	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].
	skipping to change at page 5, line 43 ¶		skipping to change at page 5, line 45 ¶
	Chunk: A well-known list of cells, distributed in time and		Chunk: A well-known list of cells, distributed in time and
	frequency, within a CDU matrix; a chunk represents a		frequency, within a CDU matrix; a chunk represents a
	portion of a CDU matrix. The partition of the CDU in		portion of a CDU matrix. The partition of the CDU in
	chunks is globally known by all the nodes in the network		chunks is globally known by all the nodes in the network
	to support the appropriation process, which is a		to support the appropriation process, which is a
	negotiation between nodes within an interference domain.		negotiation between nodes within an interference domain.
	A node that manages to appropriate a chunk gets to decide		A node that manages to appropriate a chunk gets to decide
	which transmissions will occur over the cells in the		which transmissions will occur over the cells in the
	chunk within its interference domain (i.e., a parent node		chunk within its interference domain (i.e., a parent node
	will decide when the cells within the appropriated chunk		will decide when the cells within the appropriated chunk
	are used and by which node, among its children.		are used and by which node, among its children.)
	Communication Paradigm: It is Associated with the Information Model		Communication Paradigm: It is Associated with the Information Model
	[RFC3444] of the state that is exchanged, and indicates:		[RFC3444] of the state that is exchanged, and indicates:
	the location of that state (e.g., centralized vs.		the location of that state (e.g., centralized vs.
	distributed, RESTful, etc.), the numbers of parties		distributed, RESTful, etc.), the numbers of parties
	(e.g., point to point, P2P, vs. point to multi-point,		(e.g., point to point, P2P, vs. point to multi-point,
	P2MP) and the relationship between parties (e.g., master/		P2MP) and the relationship between parties (e.g., master/
	slave vs. peers) at a high level of protocol abstraction.		slave vs. peers) at a high level of protocol abstraction.
	Layer 5 client/server REST is a typical communication		Layer 5 client/server REST is a typical communication
	paradigm, but industrial protocols also use publish/		paradigm, but industrial protocols also use publish/
	skipping to change at page 7, line 16 ¶		skipping to change at page 7, line 18 ¶
	forwarding models supported by 6TiSCH. The 6LoWPAN		forwarding models supported by 6TiSCH. The 6LoWPAN
	Fragment is used as a label for switching at the 6LoWPAN		Fragment is used as a label for switching at the 6LoWPAN
	sublayer, as defined in		sublayer, as defined in
	[I-D.thubert-roll-forwarding-frags].		[I-D.thubert-roll-forwarding-frags].
	GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer		GMPLS: Generalized Multi-Protocol Label Switching, a 2.5 layer
	service that is used to forward packets based on the		service that is used to forward packets based on the
	concept of generalized labels.		concept of generalized labels.
	Hard Cell: A scheduled cell which the 6top sublayer cannot		Hard Cell: A scheduled cell which the 6top sublayer cannot
	reallocate. See [I-D.wang-6tisch-6top-sublayer].		reallocate. See [I-D.wang-6tisch-6top-protocol].
	Hopping Sequence: Ordered sequence of frequencies, identified by a		Hopping Sequence: Ordered sequence of frequencies, identified by a
	Hopping_Sequence_ID, used for channel hopping, when		Hopping_Sequence_ID, used for channel hopping, when
	translating the channel offset value into a frequency		translating the channel offset value into a frequency
	(i.e., PHY channel). See [IEEE802154e] and [RFC7554].		(i.e., PHY channel). See [IEEE802154e] and [RFC7554].
	IE: Information Elements, a list of Type-Length-Value		IE: Information Elements, a list of Type-Length-Value
	containers placed at the end of the MAC header, used to		containers placed at the end of the MAC header, used to
	pass data between layers or devices. A small number of		pass data between layers or devices. A small number of
	types are defined by [IEEE802154e], but a range of types		types are defined by [IEEE802154e], but a range of types
	is available for extensions, and thus, is exploitable by		is available for extensions, and thus, is exploitable by
	6TiSCH. See [IEEE802154e].		6TiSCH. See [IEEE802154e].
	I-MUX module: Inverse-Multiplexer, a classifier that receives		I-MUX module: Inverse-Multiplexer, a classifier that receives
	6LoWPAN frames and places them into priority queues. See		6LoWPAN frames and places them into priority queues. See
	[I-D.wang-6tisch-6top-sublayer].		[I-D.wang-6tisch-6top-protocol].
	Interaction Model: It is a particular way of implementing a		Interaction Model: It is a particular way of implementing a
	communication paradigm. Defined at a lower level of		communication paradigm. Defined at a lower level of
	abstraction, it includes protocol-specific details such		abstraction, it includes protocol-specific details such
	as a particular method (e.g., a REST GET) and a Data		as a particular method (e.g., a REST GET) and a Data
	Model for the state to be exchanged.		Model for the state to be exchanged.
	Interference Domain: The Interference Domain of a given		Interference Domain: The Interference Domain of a given
	(transmitter) node A includes all the nodes in its		(transmitter) node A includes all the nodes in its
	neighbourhood that can generate interference at its		neighbourhood that can generate interference at its
	skipping to change at page 9, line 48 ¶		skipping to change at page 9, line 48 ¶
	contains a series of timeslots of equal length and		contains a series of timeslots of equal length and
	priority. It is characterized by a slotframe_ID, and a		priority. It is characterized by a slotframe_ID, and a
	slotframe_size. Multiple slotframes can coexist in a		slotframe_size. Multiple slotframes can coexist in a
	node's schedule, i.e., a node can have multiple		node's schedule, i.e., a node can have multiple
	activities scheduled in different slotframes, based on		activities scheduled in different slotframes, based on
	the priority of its packets/traffic flows. The timeslots		the priority of its packets/traffic flows. The timeslots
	in the Slotframe are indexed by the SlotOffset; the first		in the Slotframe are indexed by the SlotOffset; the first
	timeslot is at SlotOffset 0.		timeslot is at SlotOffset 0.
	Soft Cell: A scheduled cell which the 6top sublayer can reallocate,		Soft Cell: A scheduled cell which the 6top sublayer can reallocate,
	as described in [I-D.wang-6tisch-6top-sublayer].		as described in [I-D.wang-6tisch-6top-protocol].
	TF: Track Forwarding. It is the simplest and fastest		TF: Track Forwarding. It is the simplest and fastest
	forwarding model supported by 6TiSCH. It is a GMPLS-like		forwarding model supported by 6TiSCH. It is a GMPLS-like
	forwarding model. The incoming bundle (and thus, the		forwarding model. The incoming bundle (and thus, the
	input cell) characterizes the flow and indicates the		input cell) characterizes the flow and indicates the
	outgoing bundle (and output cell).		outgoing bundle (and output cell).
	Timeslot: A basic communication unit in TSCH which allows a		Timeslot: A basic communication unit in TSCH which allows a
	transmitter node to send a frame to a receiver neighbor,		transmitter node to send a frame to a receiver neighbor,
	and that receiver neighbor to optionally send back an		and that receiver neighbor to optionally send back an
	skipping to change at page 11, line 15 ¶		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, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119,
	RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<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, DOI 10.17487/RFC2309, April 1998,		Internet", RFC 2309, DOI 10.17487/RFC2309, April 1998,
	<http://www.rfc-editor.org/info/rfc2309>.		<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, DOI		Information Models and Data Models", RFC 3444,
	10.17487/RFC3444, January 2003,		DOI 10.17487/RFC3444, January 2003,
	<http://www.rfc-editor.org/info/rfc3444>.		<http://www.rfc-editor.org/info/rfc3444>.
	[RFC5191] Forsberg, D., Ohba, Y., Ed., Patil, B., Tschofenig, H.,		[RFC5191] Forsberg, D., Ohba, Y., Ed., Patil, B., Tschofenig, H.,
	and A. Yegin, "Protocol for Carrying Authentication for		and A. Yegin, "Protocol for Carrying Authentication for
	Network Access (PANA)", RFC 5191, DOI 10.17487/RFC5191,		Network Access (PANA)", RFC 5191, DOI 10.17487/RFC5191,
	May 2008, <http://www.rfc-editor.org/info/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, DOI 10.17487/RFC6347,		Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
	January 2012, <http://www.rfc-editor.org/info/rfc6347>.		January 2012, <http://www.rfc-editor.org/info/rfc6347>.
	[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,		[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
	Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,		Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
	JP., and R. Alexander, "RPL: IPv6 Routing Protocol for		JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
	Low-Power and Lossy Networks", RFC 6550, DOI 10.17487/		Low-Power and Lossy Networks", RFC 6550,
	RFC6550, March 2012,		DOI 10.17487/RFC6550, March 2012,
	<http://www.rfc-editor.org/info/rfc6550>.		<http://www.rfc-editor.org/info/rfc6550>.
	[RFC6552] Thubert, P., Ed., "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)",
	6552, DOI 10.17487/RFC6552, March 2012,		RFC 6552, DOI 10.17487/RFC6552, March 2012,
	<http://www.rfc-editor.org/info/rfc6552>.		<http://www.rfc-editor.org/info/rfc6552>.
	[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.		[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
	Bormann, "Neighbor Discovery Optimization for IPv6 over		Bormann, "Neighbor Discovery Optimization for IPv6 over
	Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC		Low-Power Wireless Personal Area Networks (6LoWPANs)",
	6775, DOI 10.17487/RFC6775, November 2012,		RFC 6775, DOI 10.17487/RFC6775, November 2012,
	<http://www.rfc-editor.org/info/rfc6775>.		<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, DOI 10.17487/		Application Protocol (CoAP)", RFC 7252,
	RFC7252, June 2014,		DOI 10.17487/RFC7252, June 2014,
	<http://www.rfc-editor.org/info/rfc7252>.		<http://www.rfc-editor.org/info/rfc7252>.
	[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using		[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
	IEEE 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,
	DOI 10.17487/RFC7554, May 2015,		DOI 10.17487/RFC7554, May 2015,
	<http://www.rfc-editor.org/info/rfc7554>.		<http://www.rfc-editor.org/info/rfc7554>.
	6.2. Informative References		6.2. Informative References
	skipping to change at page 12, line 45 ¶		skipping to change at page 12, line 45 ¶
	[I-D.thubert-6lo-rfc6775-update-reqs]		[I-D.thubert-6lo-rfc6775-update-reqs]
	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-protocol]
			Wang, Q. and X. Vilajosana, "6top Protocol (6P)", draft-
			wang-6tisch-6top-protocol-00 (work in progress), March
			2016.
	[I-D.wang-6tisch-6top-sublayer]		[I-D.wang-6tisch-6top-sublayer]
	Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer		Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer
	(6top)", draft-wang-6tisch-6top-sublayer-02 (work in		(6top)", draft-wang-6tisch-6top-sublayer-04 (work in
	progress), October 2015.		progress), November 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. 23 change blocks.
	36 lines changed or deleted		45 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/