< draft-ietf-6tisch-terminology-02.txt   draft-ietf-6tisch-terminology-03.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 5, 2015 cisco Expires: July 12, 2015 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 4, 2014 January 8, 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-02 draft-ietf-6tisch-terminology-03
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 5, 2015. This Internet-Draft will expire on July 12, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 11
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . 9 6.1. Normative References . . . . . . . . . . . . . . . . . . 11
6.2. Informative References . . . . . . . . . . . . . . . . . 10 6.2. Informative References . . . . . . . . . . . . . . . . . 12
6.3. External Informative References . . . . . . . . . . . . . 11 6.3. External Informative References . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
A new breed of Time Sensitive Networks is being developed to enable A new breed of Time Sensitive Networks is being developed to enable
traffic that is highly sensitive to jitter and quite sensitive to traffic that is highly sensitive to jitter and quite sensitive to
latency. Such traffic is not limited to voice and video, but also latency. Such traffic is not limited to voice and video, but also
includes command and control operations such as in industrial includes command and control operations such as in industrial
automation or in-vehicle sensors and actuators. automation or in-vehicle sensors and actuators.
At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time At IEEE802.1, the "Audio/Video Task Group", was renamed TSN for Time
skipping to change at page 3, line 40 skipping to change at page 3, line 40
6top: 6top is the adaptation sublayer between TSCH and upper 6top: 6top is the adaptation sublayer between TSCH and upper
layers like 6LoWPAN and RPL. It is defined in layers like 6LoWPAN and RPL. It is defined in
[I-D.wang-6tisch-6top-sublayer]. [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).See set of priority queues, and a PDU (Payload Data Unit).See
[I-D.wang-6tisch-6top-sublayer]. [I-D.wang-6tisch-6top-sublayer].
ARO: [RFC6775] defines a number of new Neighbor Discovery
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 start of the network or an has elapsed since the start of the network or an
arbitrary start time (i.e., a timeslot counter, arbitrary start time (i.e., a timeslot counter,
incremented by one at each timeslot). It is wide enough incremented by one at each timeslot). It is wide enough
to not roll over in practice. See [IEEE802154e]. to not roll over in practice. See [IEEE802154e].
Blacklist: Set of frequencies which should not be used for Blacklist: Set of frequencies which should not be used for
communication. communication.
BBR: Backbone Router. In the 6TiSCH architecture, it is an BBR: Backbone Router. In the 6TiSCH architecture, it is an
skipping to change at page 4, line 21 skipping to change at page 4, line 26
which are scheduled for a same purpose, with the same which are scheduled for a same purpose, with the same
neighbor, with the same flags, and the same slotframe. neighbor, with the same flags, and the same slotframe.
The size of the bundle refers to the number of cells it The size of the bundle refers to the number of cells it
contains. Given the length of the slotframe, the size of contains. Given the length of the slotframe, the size of
the bundle translates directly into bandwidth. the bundle translates directly into bandwidth.
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.
ChannelOffset: Identifies a row in the TSCH slotframe. The number ChannelOffset: Identifies a row in the TSCH schedule. The number of
of available channelOffsets is equal to the number of available channelOffsets is equal to the number of
available frequencies. The channelOffset translates into available frequencies. The channelOffset translates into
a frequency when the communication takes place, resulting a frequency when the communication takes place, resulting
in channel hopping, as detailed in in channel hopping, as detailed in
[I-D.ietf-6tisch-tsch]. [I-D.ietf-6tisch-tsch].
Channel distribution/usage (CDU) matrix: : Matrix of height equal to Channel distribution/usage (CDU) matrix: : Matrix of height equal to
the number of available channels (i.e, ChannelOffsets), the number of available channels (i.e, ChannelOffsets),
representing the spectrum (channel) distribution among representing the spectrum (channel) distribution among
the different (RPL parent) nodes in the networks. Every the different (RPL parent) nodes in the networks. Every
single element of the matrix belongs to a specific chunk. single element of the matrix belongs to a specific chunk.
skipping to change at page 5, line 13 skipping to change at page 5, line 15
bootstrap. bootstrap.
Chunk ownership appropriation: The process by which an individual Chunk ownership appropriation: The process by which an individual
node obtains a chunk to manage based on peer-to-peer node obtains a chunk to manage based on peer-to-peer
interaction with its neighbors. interaction with its neighbors.
Chunk ownership delegation: The process by which an individual node Chunk ownership delegation: The process by which an individual node
obtains a chunk to manage based on point-to-point obtains a chunk to manage based on point-to-point
interaction with an external entity. interaction with an external entity.
CoAP: The Constrained Application Protocol (CoAP), defined in
[RFC7252] is an HTTP-like resource access protocol. CoAP
runs over UDP.
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., P2P vs. P2MP) and the relationship between parties (e.g., P2P vs. P2MP) and the relationship between parties
(e.g., master/slave vs. peers) at a high level of (e.g., master/slave vs. peers) at a high level of
protocol abstraction. Layer 5 client/server REST is a protocol abstraction. Layer 5 client/server REST is a
typical communication paradigm, but industrial protocols typical communication paradigm, but industrial protocols
also use publish/subscribe which is P2MP and source/sink also use publish/subscribe which is P2MP and source/sink
which is MP2MP and primarily used for alarms and alerts which is MP2MP and primarily used for alarms and alerts
at the application layer. At layer 3, basic flooding, at the application layer. At layer 3, basic flooding,
P2P synchronization and path-marking (RSVP-like) are P2P synchronization and path-marking (RSVP-like) are
commonly used paradigms, whereas at layer 2, master/slave commonly used paradigms, whereas at layer 2, master/slave
polling and peer-to-peer forwarding are classical polling and peer-to-peer forwarding are classical
examples. examples.
DAR/DAC: [RFC6775] defines the Duplicate Address Request (DAR) and
Duplicate Address Confirmation (DAC) options to turn the
multicast Duplicate Address Detection protocol into a
client/server process.
Dedicated Cell: A cell that is reserved for a given node to transmit Dedicated Cell: A cell that is reserved for a given node to transmit
to a specific neighbor. to a specific neighbor.
DevID: The secure DEVice IDentifier (DevID) defined in
[IEEE.802.1AR] is a device identifier that is
cryptographically bound to the device. It is composed of
the Secure Device Identifier Secret and the Secure Device
Identifier Credential.
Distributed cell reservation: A reservation of a cell done by one or Distributed cell reservation: A reservation of a cell done by one or
more in-network entities (typically a connection more in-network entities (typically a connection
endpoint). endpoint).
Distributed track reservation: A reservation of a track done by one Distributed track reservation: A reservation of a track done by one
or more in-network entities (typically a connection or more in-network entities (typically a connection
endpoint). endpoint).
DTLS: The datagram version of the Transport Layer Security
(TLS) Protocol, defined in [RFC6347], and which can be
used to secure CoAP in the same way that TLS secures
HTTP.
EARO: [I-D.thubert-6lo-rfc6775-update-reqs]extends the ARO
option to include some additional fields necessary to
distinguish duplicate addresses from nodes that have
moved networks when there are mulitple LLNs linked over a
backbone.
EB: Enhanced Beacon frame used by a node to announce the EB: Enhanced Beacon frame used by a node to announce the
presence of the network. It contains information about presence of the network. It contains information about
the timeslot length, the current ASN value, the the timeslot length, the current ASN value, the
slotframes and timeslots the beaconing mote is listening slotframes and timeslots the beaconing mote is listening
on, and a 1-byte join priority (i.e., number of hops on, and a 1-byte join priority (i.e., number of hops
separating the node sending the EB, and the PAN separating the node sending the EB, and the PAN
coordinator). coordinator).
FF: 6LoWPAN Fragment Forwarding. It is one of the three FF: 6LoWPAN Fragment Forwarding. It is one of the three
forwarding models supported by 6TiSCH. The 6LoWPAN forwarding models supported by 6TiSCH. The 6LoWPAN
skipping to change at page 6, line 18 skipping to change at page 6, line 47
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-sublayer].
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 (i.e., PHY channel). See [IEEE802154e] and
[I-D.ietf-6tisch-tsch]. [I-D.ietf-6tisch-tsch].
IDevID: The Initial secure DEVice IDentifier (IDevID) is the
Device Identifier which was installed on the device by
the manufacturer.
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-sublayer].
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.
KMP: Key Managment Protocol. JCE: The Join Coordination Entity (JCE) is a central entity
like the Path Computation Engine (PCE), that is in charge
of authorization to join a network. The JCE provides
security credentials to joining devices.
JA: The Join Assistant (JA) is a constrained node near the
joining node that will act as its first 6LR, and will
relay traffic to/from the joining node.
JN: The Joining Node (JN) leverages the JA and the JCE to
learn or refresh its knowledge of the network operational
state and to obtain security material to participate to
the production network.
Join Protocol: The protocol which secures initial communication
between the JN and the JCE.
KMP: Key Management Protocol.
LBR: LLN Border Router. It is an LLN device, usually powered, LBR: LLN Border Router. It is an LLN device, usually powered,
that acts as a Border Router to the outside within the that acts as a Border Router to the outside within the
6TiSCH architecture. 6TiSCH architecture.
LDevID: A Locally significant secure DEVice IDentifiers (LDevID)
is a Secure Device Identifier credential that is unique
in the local administrative domain in which the device is
used. The LDevID is usually a new certificate
provisioned by some local means, such as the 6top
sublayer [I-D.wang-6tisch-6top-sublayer].
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. In the context of the 6TiSCH architecture, terminology. In the context of the 6TiSCH architecture,
which applies to Low Power Lossy Networks (LLNs), an IPv6 which applies to Low Power Lossy Networks (LLNs), an IPv6
subnet is usually not congruent to a single link and subnet is usually not congruent to a single link and
techniques such as IPv6 Neighbor Discovery Proxying are techniques such as IPv6 Neighbor Discovery Proxying are
used to achieve reachability within the multilink subnet. used to achieve reachability within the multilink subnet.
A link is distinct from a track. In fact, link local A link is distinct from a track. In fact, link local
skipping to change at page 7, line 28 skipping to change at page 8, line 37
transmission. See [I-D.wang-6tisch-6top-sublayer]. transmission. See [I-D.wang-6tisch-6top-sublayer].
NEAR: Energy Aware Default Router, as defined in NEAR: Energy Aware Default Router, as defined in
[I-D.chakrabarti-nordmark-6man-efficient-nd]. [I-D.chakrabarti-nordmark-6man-efficient-nd].
NME: Network Management Entity, the entity in the network NME: Network Management Entity, the entity in the network
managing cells and other device resources. It may managing cells and other device resources. It may
cooperate with the PCE. It interacts with LLN nodes cooperate with the PCE. It interacts with LLN nodes
through the backbone router. through the backbone router.
Operational Network: A IEEE802.15.4e network whose encryption/
authentication keys are determined by some algorithms/
protocols. There may be network-wide group keys, or per-
link keys.
Operational Network Key: A Link-layer key known by all authorized
nodes, used for multicast messages.
PANA: Protocol for carrying Authentication for Network Access, PANA: Protocol for carrying Authentication for Network Access,
as defined in [RFC5191] . as defined in [RFC5191] .
PCE: Path Computation Element, the entity in the network which PCE: Path Computation Element, the entity in the network which
is responsible for building and maintaining the TSCH is responsible for building and maintaining the TSCH
schedule, when centralized scheduling is used. schedule, when centralized scheduling is used.
PCE cell reservation: The reservation of a cell done by the PCE. PCE cell reservation: The reservation of a cell done by the PCE.
PCE track reservation: The reservation of a track done by the PCE. PCE track reservation: The reservation of a track done by the PCE.
Per-Peer L2 Key: A key that results from an exchange (such as MLE)
that creates a pair-wise link-layer key which is known
only to the two nodes involved.
QoS: Quality of Service. QoS: Quality of Service.
(to) reallocate a cell: The action operated by the 6top sublayer of (to) reallocate 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.
SA: Security Association. SA: Security Association.
(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.
skipping to change at page 9, line 22 skipping to change at page 10, line 42
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 and a channelOffset. The TSCH schedule contains all the
scheduled cells from all slotframes and is sufficient to scheduled cells from all slotframes and is sufficient to
qualify the communication in the TSCH network. The qualify the communication in the TSCH network. The
"width of the matrix is equal to the number of scheduled "width of the matrix is equal to the number of scheduled
timeslots in all the concurrent active slotframes. The timeslots in all the concurrent active slotframes. The
number of channelOffset values (the "height" of the number of channelOffset values (the "height" of the
matrix) is equal to the number of available frequencies. matrix) is equal to the number of available frequencies.
unique join key: A key shared between a JN and the JCE. This key
supports smaller installations for which asymmetric
methods are considered too large.
unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH unscheduled cell: A cell which is not used by the IEEE802.15.4e TSCH
implementation. implementation.
3. IANA Considerations 3. IANA Considerations
This specification does not require IANA action. This specification does not require IANA action.
4. Security Considerations 4. Security Considerations
This specification is not found to introduce new security threats. This specification is not found to introduce new security threats.
skipping to change at page 10, line 13 skipping to change at page 11, line 40
Internet", RFC 2309, April 1998. Internet", RFC 2309, April 1998.
[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, January
2003. 2003.
[RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A. [RFC5191] Forsberg, D., Ohba, Y., Patil, B., Tschofenig, H., and A.
Yegin, "Protocol for Carrying Authentication for Network Yegin, "Protocol for Carrying Authentication for Network
Access (PANA)", RFC 5191, May 2008. Access (PANA)", RFC 5191, May 2008.
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security Version 1.2", RFC 6347, January 2012.
[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., [RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
Alexander, "RPL: IPv6 Routing Protocol for Low-Power and Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
Lossy Networks", RFC 6550, March 2012. Lossy Networks", RFC 6550, March 2012.
[RFC6552] Thubert, P., "Objective Function Zero for the Routing [RFC6552] Thubert, P., "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, March 2012.
[RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann,
"Neighbor Discovery Optimization for IPv6 over Low-Power
Wireless Personal Area Networks (6LoWPANs)", RFC 6775,
November 2012.
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014.
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-05 (work in progress), February 2014. 6man-efficient-nd-06 (work in progress), July 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.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-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.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-tsch] [I-D.ietf-6tisch-tsch]
Watteyne, T., Palattella, M., and L. Grieco, "Using Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an LLN context: Overview, Problem IEEE802.15.4e TSCH in an IoT context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-00 (work in Statement and Goals", draft-ietf-6tisch-tsch-04 (work in
progress), November 2013. progress), December 2014.
[I-D.ietf-roll-terminology] [I-D.ietf-roll-terminology]
Vasseur, J., "Terms used in Routing for Low power And Vasseur, J., "Terms used in Routing for Low power And
Lossy Networks", draft-ietf-roll-terminology-13 (work in Lossy Networks", draft-ietf-roll-terminology-13 (work in
progress), October 2013. progress), October 2013.
[I-D.thubert-6lo-rfc6775-update-reqs]
Thubert, P., "Requirements for an update to 6LoWPAN ND",
draft-thubert-6lo-rfc6775-update-reqs-05 (work in
progress), October 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.wang-6tisch-6top-sublayer] [I-D.wang-6tisch-6top-sublayer]
Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
Operation Sublayer (6top)", draft-wang-6tisch-6top- Operation Sublayer (6top)", draft-wang-6tisch-6top-
sublayer-00 (work in progress), February 2014. sublayer-01 (work in progress), July 2014.
6.3. External Informative References 6.3. External Informative References
[IEEE.802.1AR]
IEEE standard for Information Technology, "802.1AR-2009 -
IEEE Standard for Local and metropolitan area networks -
Secure Device Identity", 2009.
[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
Maria Rita Palattella (editor) Maria Rita Palattella (editor)
University of Luxembourg University of Luxembourg
 End of changes. 25 change blocks. 
42 lines changed or deleted 115 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/