draft-ietf-6tisch-terminology-08.txt   draft-ietf-6tisch-terminology-09.txt 
6TiSCH MR. Palattella, Ed. 6TiSCH MR. Palattella, Ed.
Internet-Draft LIST Internet-Draft LIST
Intended status: Informational P. Thubert Intended status: Informational P. Thubert
Expires: June 19, 2017 cisco Expires: December 21, 2017 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
December 16, 2016 June 19, 2017
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-08 draft-ietf-6tisch-terminology-09
Abstract Abstract
This document provides a glossary of terminology used in IPv6 over This document provides a glossary of terminology used in IPv6 over
the TSCH mode of IEEE 802.15.4e (6TiSCH). This document extends the TSCH mode of IEEE 802.15.4e (6TiSCH). This document extends
existing terminology documents for Low-power and Lossy Networks. existing terminology documents for Low-power and Lossy Networks.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
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 June 19, 2017. This Internet-Draft will expire on December 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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 4, line 26 skipping to change at page 4, line 26
are two bundles in node B, one incoming = (macA, macB, are two bundles in node B, one incoming = (macA, macB,
trackId) and one outgoing = (macB, macC, trackId). trackId) and one outgoing = (macB, macC, trackId).
CCA: Clear Channel Assessment. Mechanism defined in CCA: Clear Channel Assessment. Mechanism defined in
[IEEE802154-2015], section 6.2.5.2. In a TSCH network, [IEEE802154-2015], section 6.2.5.2. In a TSCH network,
CCA can be used to detect other radio networks in CCA can be used to detect other radio networks in
vicinity. Nodes listen the channel before sending, to vicinity. Nodes listen the channel before sending, to
detect other ongoing transmissions. Because the network detect other ongoing transmissions. Because the network
is synchronized, CCA cannot be used to detect colliding is synchronized, CCA cannot be used to detect colliding
transmission within the same network. CCA is necessary transmission within the same network. CCA is necessary
for the 6TiSCH minimal configuration for the 6TiSCH minimal configuration [RFC8180] in shared
[I-D.ietf-6tisch-minimal] in shared slots, and in slots, and in presence of multiple instances of 6TiSCH
presence of multiple instances of 6TiSCH networks. networks.
Cell: A single element in the TSCH schedule, identified by a Cell: A single element in the TSCH schedule, identified by a
slotOffset, a channelOffset, a slotframeHandle. A cell slotOffset, a channelOffset, a slotframeHandle. A cell
can be scheduled or unscheduled. can be scheduled or unscheduled.
Centralized Cell Reservation: A reservation of a cell done by a Centralized Cell Reservation: A reservation of a cell done by a
centralized entity (e.g., a PCE) in the network. centralized entity (e.g., a PCE) in the network.
Centralized Track Reservation: A reservation of a track done by a Centralized Track Reservation: A reservation of a track done by a
centralized entity (e.g., a PCE) in the network. centralized entity (e.g., a PCE) in the network.
skipping to change at page 6, line 12 skipping to change at page 6, line 12
(i.e., PHY channel). See [IEEE802154-2015] and (i.e., PHY channel). See [IEEE802154-2015] and
[RFC7554]. [RFC7554].
IE: Information Element, a Type-Length-Value containers IE: Information Element, a Type-Length-Value containers
placed at the end of the MAC header, used to pass data placed at the end of the MAC header, used to pass data
between layers or devices. Some IE identifiers are between layers or devices. Some IE identifiers are
managed by the IEEE [IEEE802154-2015]. Some IE managed by the IEEE [IEEE802154-2015]. Some IE
identifiers are managed by the IETF identifiers are managed by the IETF
[I-D.kivinen-802-15-ie]. [I-D.kivinen-802-15-ie].
JCE: The Join Coordination Entity (JCE) is a central entity JP: The Join Proxy (JP) is a one-hop neighbor of a joining
that coordinates the joining of new nodes in the network. node that may facilitate it to become meaningful part of
See [I-D.ietf-6tisch-minimal-security] and the network (e.g., by serving as a local connectivity
point to the remainder of the network). JP emits EBs,
used by Pledges to synchronize to the network. See
[I-D.ietf-6tisch-minimal-security] and
[I-D.ietf-6tisch-dtsecurity-secure-join]. [I-D.ietf-6tisch-dtsecurity-secure-join].
JA: The Join Assistant (JA) is a one-hop neighbor of a JRC: The Join Registrar/Coordinator (JRC) is a central entity
joining node that may facilitate it to become meaningful that coordinates the joining of new nodes in the network.
part of the network (e.g., by serving as a local
connectivity point to the remainder of the network). JA
emits EBs, used by JNs to synchronize to the network.
See [I-D.ietf-6tisch-minimal-security] and See [I-D.ietf-6tisch-minimal-security] and
[I-D.ietf-6tisch-dtsecurity-secure-join]. [I-D.ietf-6tisch-dtsecurity-secure-join].
JN: The Joining Node (JN) is a device attempting to join a
particular 6TiSCH network. See
[I-D.ietf-6tisch-minimal-security].
Join Protocol: The protocol which secures initial communication Join Protocol: The protocol which secures initial communication
between a joining node and the JCE. between a joining node and the JRC.
LBR: Low-power Lossy Network (LLN) Border Router. It is an LBR: Low-power Lossy Network (LLN) Border Router. It is an
LLN device, usually powered, that acts as a Border Router LLN device, usually powered, that acts as a Border Router
to the outside within the 6TiSCH architecture. to the outside within the 6TiSCH architecture.
Link: A communication facility or medium over which nodes can Link: A communication facility or medium over which nodes can
communicate at the link layer, i.e., the layer communicate at the link layer, i.e., the layer
immediately below IP. Thus, the IETF parlance for the immediately below IP. Thus, the IETF parlance for the
term "Link" is adopted, as opposed to the IEEE802.15.4e term "Link" is adopted, as opposed to the IEEE802.15.4e
terminology. terminology.
Operational Network: A IEEE802.15.4e network whose encryption/ Operational Network: A IEEE802.15.4e network whose encryption/
authentication keys are determined by some algorithms/ authentication keys are determined by some algorithms/
protocols. There may be network-wide group keys, or per- protocols. There may be network-wide group keys, or per-
link keys. link keys.
Pledge: The Pledge is a device attempting to join a particular
6TiSCH network. See [I-D.ietf-6tisch-minimal-security].
(to) Relocate a Cell: The action operated by the 6top sublayer of (to) Relocate a Cell: The action operated by the 6top sublayer of
changing the slotOffset and/or channelOffset of a soft changing the slotOffset and/or channelOffset of a soft
cell. cell.
(to) Schedule a Cell: The action of turning an unscheduled cell into (to) Schedule a Cell: The action of turning an unscheduled cell into
a scheduled cell. a scheduled cell.
Scheduled cell: A cell which is assigned a neighbor MAC address Scheduled cell: A cell which is assigned a neighbor MAC address
(broadcast address is also possible), and one or more of (broadcast address is also possible), and one or more of
the following flags: TX, RX, shared, timeskeeping. A the following flags: TX, RX, shared, timeskeeping. A
skipping to change at page 9, line 26 skipping to change at page 9, line 26
[RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and
Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January
2014, <http://www.rfc-editor.org/info/rfc7102>. 2014, <http://www.rfc-editor.org/info/rfc7102>.
[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>.
[RFC8180] Vilajosana, X., Ed., Pister, K., and T. Watteyne, "Minimal
IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH)
Configuration", BCP 210, RFC 8180, DOI 10.17487/RFC8180,
May 2017, <http://www.rfc-editor.org/info/rfc8180>.
4.2. Informative References 4.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-6tisch-6top-protocol] [I-D.ietf-6tisch-6top-protocol]
Wang, Q. and X. Vilajosana, "6top Protocol (6P)", draft- Wang, Q., Vilajosana, X., and T. Watteyne, "6top Protocol
ietf-6tisch-6top-protocol-03 (work in progress), October (6P)", draft-ietf-6tisch-6top-protocol-05 (work in
2016. progress), May 2017.
[I-D.ietf-6tisch-dtsecurity-secure-join] [I-D.ietf-6tisch-dtsecurity-secure-join]
Richardson, M., "6tisch Secure Join protocol", draft-ietf- Richardson, M., "6tisch Secure Join protocol", draft-ietf-
6tisch-dtsecurity-secure-join-00 (work in progress), 6tisch-dtsecurity-secure-join-01 (work in progress),
December 2016. February 2017.
[I-D.ietf-6tisch-minimal]
Vilajosana, X. and K. Pister, "Minimal 6TiSCH
Configuration", draft-ietf-6tisch-minimal-17 (work in
progress), November 2016.
[I-D.ietf-6tisch-minimal-security] [I-D.ietf-6tisch-minimal-security]
malisa.vucinic@st.com, m., Simon, J., and K. Pister, Vucinic, M., Simon, J., Pister, K., and M. Richardson,
"Minimal Security Framework for 6TiSCH", draft-ietf- "Minimal Security Framework for 6TiSCH", draft-ietf-
6tisch-minimal-security-00 (work in progress), December 6tisch-minimal-security-03 (work in progress), June 2017.
2016.
[I-D.ietf-detnet-architecture] [I-D.ietf-detnet-architecture]
Finn, N. and P. Thubert, "Deterministic Networking Finn, N., Thubert, P., Varga, B., and J. Farkas,
Architecture", draft-ietf-detnet-architecture-00 (work in "Deterministic Networking Architecture", draft-ietf-
progress), September 2016. detnet-architecture-01 (work in progress), March 2017.
[I-D.kivinen-802-15-ie] [I-D.kivinen-802-15-ie]
Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information Kivinen, T. and P. Kinney, "IEEE 802.15.4 Information
Element for IETF", draft-kivinen-802-15-ie-04 (work in Element for IETF", draft-kivinen-802-15-ie-06 (work in
progress), October 2016. progress), March 2017.
[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-07 6LoWPAN ND", draft-thubert-6lo-rfc6775-update-reqs-07
(work in progress), April 2016. (work in progress), April 2016.
[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.
 End of changes. 18 change blocks. 
39 lines changed or deleted 37 lines changed or added

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