draft-ietf-6tisch-6top-interface-00.txt   draft-ietf-6tisch-6top-interface-01.txt 
6TiSCH Q. Wang, Ed. 6TiSCH Q. Wang, Ed.
Internet-Draft Univ. of Sci. and Tech. Beijing Internet-Draft Univ. of Sci. and Tech. Beijing
Intended status: Informational X. Vilajosana Intended status: Informational X. Vilajosana
Expires: September 28, 2014 Universitat Oberta de Catalunya Expires: January 5, 2015 Universitat Oberta de Catalunya
T. Watteyne T. Watteyne
Linear Technology Linear Technology
March 27, 2014 July 4, 2014
6TiSCH Operation Sublayer (6top) Interface 6TiSCH Operation Sublayer (6top) Interface
draft-ietf-6tisch-6top-interface-00 draft-ietf-6tisch-6top-interface-01
Abstract Abstract
This document defines a generic data model for the 6TiSCH Operation This document defines a generic data model for the 6TiSCH Operation
Sublayer (6top), using the YANG data modeling language. This data Sublayer (6top), using the YANG data modeling language. This data
model can be used for future network management solutions defined by model can be used for future network management solutions defined by
the 6TiSCH working group. This document also defines a list commands the 6TiSCH working group. This document also defines a list commands
internal to the 6top sublayer. internal to the 6top sublayer.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 28, 2014. This Internet-Draft will expire on January 5, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
skipping to change at page 2, line 18 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. 6TiSCH Operation Sublayer (6top) Overview . . . . . . . . . . 3 2. 6TiSCH Operation Sublayer (6top) Overview . . . . . . . . . . 3
2.1. Cell Model . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Cell Model . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1. hard cells . . . . . . . . . . . . . . . . . . . . . 6 2.1.1. hard cells . . . . . . . . . . . . . . . . . . . . . 6
2.1.2. soft cells . . . . . . . . . . . . . . . . . . . . . 6 2.1.2. soft cells . . . . . . . . . . . . . . . . . . . . . 6
2.2. Data Transfer Model . . . . . . . . . . . . . . . . . . . 6 2.2. Data Transfer Model . . . . . . . . . . . . . . . . . . . 6
3. Generic Data Model . . . . . . . . . . . . . . . . . . . . . 8 3. Generic Data Model . . . . . . . . . . . . . . . . . . . . . 8
3.1. YANG model of the 6top MIB . . . . . . . . . . . . . . . 8 3.1. YANG model of the 6top MIB . . . . . . . . . . . . . . . 8
3.2. YANG model of the IEEE802.15.4 PIB . . . . . . . . . . . 23 3.2. YANG model of the IEEE802.15.4 PIB . . . . . . . . . . . 24
3.3. YANG model of the IEEE802.15.4e PIB . . . . . . . . . . . 23 4. Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4. Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.1. Normative References . . . . . . . . . . . . . . . . . . 33
5.1. Normative References . . . . . . . . . . . . . . . . . . 27 5.2. Informative References . . . . . . . . . . . . . . . . . 33
5.2. Informative References . . . . . . . . . . . . . . . . . 27 5.3. External Informative References . . . . . . . . . . . . . 34
5.3. External Informative References . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
This document defines a generic data model for the 6TiSCH Operation This document defines a generic data model for the 6TiSCH Operation
Sublayer (6top), using the YANG data modeling language. This data Sublayer (6top), using the YANG data modeling language defined in
model can be used for future network management solutions defined by [RFC6020]. This data model can be used for future network management
the 6TiSCH working group. This document also defines a list commands solutions defined by the 6TiSCH working group. This document also
internal to the 6top sublayer. This data model gives access to defines a list commands internal to the 6top sublayer. This data
metrics (e.g. cell state), TSCH configuration and control procedures, model gives access to metrics (e.g. cell state), TSCH configuration
and support for the different scheduling mechanisms described in and control procedures, and support for the different scheduling
[I-D.ietf-6tisch-architecture]. The 6top sublayer addresses the set mechanisms described in [I-D.ietf-6tisch-architecture]. The 6top
of management information and functionalities described in sublayer addresses the set of management information and
[I-D.ietf-6tisch-tsch]. functionalities described in [I-D.ietf-6tisch-tsch].
For example, network formation in a TSCH network is handled by the For example, network formation in a TSCH network is handled by the
use of Enhanced Beacons (EB). EBs include information for joining use of Enhanced Beacons (EB). EBs include information for joining
nodes to be able to synchronize and set up an initial network nodes to be able to synchronize and set up an initial network
topology. However, [IEEE802154e] does not specify how the period of topology. However, [IEEE802154e] does not specify how the period of
EBs is configured, nor the rules for a node to select a particular EBs is configured, nor the rules for a node to select a particular
node to join. 6top offers a set of commands so control mechanisms can node to join. 6top offers a set of commands so control mechanisms can
be introduced on top of TSCH to configure nodes to join a specific be introduced on top of TSCH to configure nodes to join a specific
node and obtain a unique 16-bit identifier from the network. Once a node and obtain a unique 16-bit identifier from the network. Once a
network is formed, 6top maintains the network's health, allowing for network is formed, 6top maintains the network's health, allowing for
skipping to change at page 5, line 37 skipping to change at page 5, line 37
the node which initializes the process of creating the track, i.e., the node which initializes the process of creating the track, i.e.,
the owner of the track; and InstanceID is an instance identifier the owner of the track; and InstanceID is an instance identifier
given by the owner of the track. InstanceID comes from upper layer; given by the owner of the track. InstanceID comes from upper layer;
InstanceID could for example be the local instance ID defined in RPL. InstanceID could for example be the local instance ID defined in RPL.
If the TrackID is set to (0,0), the cell can be used by the best- If the TrackID is set to (0,0), the cell can be used by the best-
effort QoS configuration or as a Shared cell. If the TrackID is not effort QoS configuration or as a Shared cell. If the TrackID is not
set to (0,0), i.e., the cell belongs to a specific track, the cell set to (0,0), i.e., the cell belongs to a specific track, the cell
MUST not be set as Shared cell. MUST not be set as Shared cell.
6top allows an upper layer ask a node manage a a portion of a 6top allows an upper layer to ask a node to manage a portion of a
slotframe, which is named as chunk. Chunks can be delegated slotframe, which is named as chunk. Chunks can be delegated
explicitly by the PCE to a node, or claimed automatically by any node explicitly by the PCE to a node, or claimed automatically by any node
that participates to the distributed cell scheduling process. The that participates to the distributed cell scheduling process. The
resource in a chunk can be appropriated by the node, i.e. the owner resource in a chunk can be appropriated by the node, i.e. the owner
of the chunk. of the chunk.
Given this mechanism, 6top defines hard cells (which have been Given this mechanism, 6top defines hard cells (which have been
requested specifically) and soft cells (which can be reallocated requested specifically) and soft cells (which can be reallocated
dynamically). The hard/soft flag is introduced by the 6top sublayer dynamically). The hard/soft flag is introduced by the 6top sublayer
named as CellType, 0: soft cell, 1: hard cell. This option is named as CellType, 0: soft cell, 1: hard cell. This option is
mandatory; all cells are either hard or soft. mandatory; all cells are either hard or soft.
2.1.1. hard cells 2.1.1. hard cells
A hard cell is a cell that cannot be dynamically reallocated by 6top. A hard cell is a cell that cannot be dynamically reallocated by 6top.
A hard cell is uniquely identified by the following tuple: The CellType MUST be set to 1. The cell is installed by 6top given
specific slotframe ID, slotOffset, and channelOffset.
slotframe ID: ID of the slotframe this cell is part of.
slotOffset: the slotOffset for the cell.
channelOffset: the channelOffset for the cell.
LinkOption bitmap: bitmap as defined in [IEEE802154].
CellType: MUST be set to 1.
2.1.2. soft cells 2.1.2. soft cells
A soft cell is a cell that can be reallocated by 6top dynamically. A soft cell is a cell that can be reallocated by 6top dynamically.
The CellType MUST be set to 0. This cell is installed by 6top given The CellType MUST be set to 0. This cell is installed by 6top given
a specific bandwidth requirement. Soft cells are installed through a specific bandwidth requirement. Soft cells are installed through
the soft cell negotiation procedure described in the soft cell negotiation procedure described in
[I-D.wang-6tisch-6top-sublayer]. [I-D.wang-6tisch-6top-sublayer].
2.2. Data Transfer Model 2.2. Data Transfer Model
skipping to change at page 7, line 37 skipping to change at page 7, line 37
+---+ +---+
|PDU| |PDU|
+---+ +---+
| |
| TSCH MAC-payload | TSCH MAC-payload
| |
Figure 2 Figure 2
In Figure 2, Qi represents a queue, which is either broadcast or In Figure 2, Qi represents a queue, which is either broadcast or
unicast, and is assigned a priority. The number of queues is unicast, and has an assigned priority. The number of queues is
configurable. The relationship between queues and tracks is configurable. The relationship between queues and tracks is
configurable. For example, for a given queue, only one specific configurable. For example, for a given queue, only one specific
track can be used, all of the tracks can be used, or a subset of the track can be used, all of the tracks can be used, or a subset of the
tracks can be used. tracks can be used.
When 6top receives a packet to transmit through a Send.data command When 6top receives a packet to transmit through a Send.data command
(Section 4), the I-MUX module selects a queue in which to insert it. (Section 4), the I-MUX module selects a queue in which to insert it.
If the packet's destination address is a unicast (resp. broadcast) If the packet's destination address is a unicast (resp. broadcast)
address, it will be inserted into a unicast (resp. broadcast) queue. address, it will be inserted into a unicast (resp. broadcast) queue.
skipping to change at page 8, line 26 skipping to change at page 8, line 26
i.e., TrackID=(0,0), frames from a queue with a higher priority i.e., TrackID=(0,0), frames from a queue with a higher priority
MUST be sent before frames from a queue with a lower priority. MUST be sent before frames from a queue with a lower priority.
Further rules can be configured to satisfy specific QoS requirements. Further rules can be configured to satisfy specific QoS requirements.
3. Generic Data Model 3. Generic Data Model
This section presents the generic data model of the 6top sublayer, This section presents the generic data model of the 6top sublayer,
using the YANG data modeling langage. This data model can be used using the YANG data modeling langage. This data model can be used
for future network management solutions defined by the 6TiSCH working for future network management solutions defined by the 6TiSCH working
group. The dada model consists of three parts: 6top MIB, part of the group. The data model consists of the MIB (management information
[IEEE802154e] PIB, and part of the [IEEE802154] PIB. base) defined in 6top, and part of the PIB (personal area network
information base) defined in [IEEE802154e] and [IEEE802154].
3.1. YANG model of the 6top MIB 3.1. YANG model of the 6top MIB
list CellList { list CellList {
key "CellID"; key "CellID";
description description
"List of scheduled cells of a node with all of its neighbors, "List of scheduled cells of a node with all of its neighbors,
in all of its slotframes."; in all of its slotframes.";
leaf CellID { leaf CellID {
type uint16; type uint16;
description description
"Equal to Linkhandle in the linkTable of TSCH"; "Equal to Linkhandle in the linkTable of TSCH";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf SlotframeID { leaf SlotframeID {
type uint8; type uint8;
description description
skipping to change at page 8, line 46 skipping to change at page 8, line 48
leaf CellID { leaf CellID {
type uint16; type uint16;
description description
"Equal to Linkhandle in the linkTable of TSCH"; "Equal to Linkhandle in the linkTable of TSCH";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf SlotframeID { leaf SlotframeID {
type uint8; type uint8;
description description
"Equal to SlotframeHandle defined in TSCH"; "SlotframeID, one in SlotframeList, indicates the slotframe
the cell belongs to.";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf SlotOffset { leaf SlotOffset {
type uint16; type uint16;
description description
"Defined in IEEE802154e."; "Defined in IEEE802154e.";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
skipping to change at page 10, line 28 skipping to change at page 10, line 31
type uint64; type uint64;
description description
"Defined by 6top, but being constrained by TSCH "Defined by 6top, but being constrained by TSCH
macNodeAddress size, 2-octets. If using TSCH as MAC, macNodeAddress size, 2-octets. If using TSCH as MAC,
higher 6-octets should be filled with 0, and lowest higher 6-octets should be filled with 0, and lowest
2-octets is neighbor address"; 2-octets is neighbor address";
} }
leaf TrackID { leaf TrackID {
type uint16; type uint16;
description description
"A TrackID is a tuple (TrackOwnerAddr,InstanceID), where "A TrackID is one in the TrackList, pointing to a tuple
TrackOwnerAddr is the address of the node which initializes (TrackOwnerAddr,InstanceID) , where TrackOwnerAddr is the
the process of creating the track, i.e., the owner of the address of the node which initializes the process of
track; and InstanceID is an instance identifier given by creating the track, i.e., the owner of the track; and
the owner of the track."; InstanceID is an instance identifier given by the owner of
the track.";
} }
container Statistic { container Statistic {
leaf NumOfStatistic { leaf NumOfStatistic {
type uint8; type uint8;
description description
"Number of statistics collected on the cell"; "Number of statistics collected on the cell";
} }
list MeasureList { list MeasureList {
key "StatisticsMetricsID"; key "StatisticsMetricsID";
leaf StatisticsMetricsID{ leaf StatisticsMetricsID{
type uint16; type uint16;
description
"An index of StatisticsMetricList, which defines how
to collect data and get the statistice value";
} }
leaf StatisticsValue{ leaf StatisticsValue{
type uint16; type uint16;
config false; config false;
description
"updated by 6top according to the statistics methed
specified by StatisticsMetricsID";
} }
} }
} }
} }
list SlotframeList { list SlotframeList {
key "SlotframeID"; key "SlotframeID";
description
"List of all of the slotframes used by the node.";
leaf SlotframeID { leaf SlotframeID {
type uint8; type uint8;
description
"Equal to SlotframeHandle defined in TSCH";
reference
"IEEE802154e";
} }
leaf NumOfSlots { leaf NumOfSlots {
type uint16; type uint16;
description
"indicates how many timeslots in the slotframe";
} }
} }
list MonitoringStatusList { list MonitoringStatusList {
key "MonitoringStatusID"; key "MonitoringStatusID";
description
"List of the monitoring configuration and results per
slotframe and neighbor. Basically, it is used for Monitoring
Function of 6top to re-allocate softcells or initial the
softcell negotiation process to increase/decrease number of
softcells. Upper layer can use it also.";
leaf MonitoringStatusID { leaf MonitoringStatusID {
type uint16; type uint16;
} }
leaf SlotframeID { leaf SlotframeID {
type uint8; type uint8;
description
"SlotframeID, one in SlotframeList, indicates the slotframe
being monitored";
reference
"IEEE802154e";
} }
leaf TargetNodeAddress { leaf TargetNodeAddress {
type uint64; type uint64;
description
"Defined by 6top, but being constrained by TSCH
macNodeAddress size, 2-octets. If using TSCH as MAC,
higher 6-octets should be filled with 0, and lowest
2-octets is neighbor address. It indicates the communication
link being mornitored";
} }
leaf EnforcePolicy { leaf EnforcePolicy {
type enumeration { type enumeration {
enum DISABLE; enum DISABLE;
enum BESTEFFORT; enum BESTEFFORT;
enum STRICT; enum STRICT;
enum OVERPROVISION; enum OVERPROVISION;
} }
description description
"Currently enforced QoS policy"; "Currently enforced QoS policy. DISABLE-no QoS;
BESTEFFORT- best effort policy is used; STRICT- Strict
Priority Queueing; OVERPROVISION- cell overprovision";
} }
leaf AllocatedHard { leaf AllocatedHard {
type uint16; type uint16;
config false; config false;
description description
"Number of hard cells allocated"; "Number of hard cells allocated";
} }
leaf AllocatedSoft { leaf AllocatedSoft {
type uint16; type uint16;
config false; config false;
description description
"Number of soft cells allocated"; "Number of soft cells allocated";
} }
leaf OverProvision { leaf OverProvision {
type uint16; type uint16;
config false; config false;
description description
"Overprovisioned cells. 0 if CONFIGURE.qos enforce is "Overprovisioned cells. 0 if EnforcePolicy is
DISABLE"; DISABLE";
} }
leaf QoS { leaf QoS {
type uint16; type uint16;
config false; config false;
description description
"Current QoS including overprovisioned cells, i.e. the "Current QoS including overprovisioned cells, i.e. the
bandwidth obtained including the overprovisioned cells."; bandwidth obtained including the overprovisioned cells.";
} }
leaf NQoS { leaf NQoS {
type uint16; type uint16;
config false; config false;
description description
"Real QoS without provisioned cells, i.e. the actual "Real QoS without over provisioned cells, i.e. the actual
bandwidth without taking into account the overprovisioned bandwidth without taking into account the overprovisioned
cells."; cells.";
} }
} }
list StatisticsMetricsList { list StatisticsMetricsList {
key "StatisticsMetricsID"; key "StatisticsMetricsID";
description
"List of Statistics Metrics used in the node.";
leaf StatisticsMetricsID { leaf StatisticsMetricsID {
type uint16; type uint16;
} }
leaf SlotframeID { leaf SlotframeID {
type uint16; type uint16;
description description
"ID of the slotframe. If empty, monitors all slotframe IDs"; "SlotframeID, one in SlotframeList, specifies the slotframe to
which the statistics metrics applies to. If empty, applies to
all slotframes";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf SlotOffset { leaf SlotOffset {
type uint16; type uint16;
description description
"Specific slotOffset to be monitored. If empty all timeslots "Specific slotOffset to which the statistics metrics applies
are monitored"; to. If empty, applies to all timeslots";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf ChannelOffset { leaf ChannelOffset {
type uint8; type uint8;
description description
"Specific channelOffset to be monitored. If empty all "Specific channelOffset to which the statistics metrics applies
channels are monitored"; to. If empty, applies to all channels";
reference reference
"IEEE802154e"; "IEEE802154e";
} }
leaf TargetNodeAddress { leaf TargetNodeAddress {
type uint64; type uint64;
description description
"If empty, all neighbor nodes are monitored."; "Specific neighbor nodes to which the statistics metrics
applies to. If empty, applies to all neighbor nodes.";
} }
leaf Metrics { leaf Metrics {
type enumeration { type enumeration {
enum PDR; enum PDR;
enum ETX; enum ETX;
enum RSSI; enum RSSI;
enum LQI; enum LQI;
} }
description description
"The metric to be monitored."; "The metric to be monitored.";
skipping to change at page 13, line 28 skipping to change at page 14, line 26
leaf Window { leaf Window {
type uint16; type uint16;
description description
"measurement period, in Number of the slotframe size"; "measurement period, in Number of the slotframe size";
} }
leaf Enable { leaf Enable {
type enumeration { type enumeration {
enum DISABLE; enum DISABLE;
enum ENABLE; enum ENABLE;
} }
description
"indicates the StatisticsMetric is active or not";
} }
} }
list EBList { list EBList {
key "EbID"; key "EbID";
description
"List of information related with the EBs used by the node";
leaf EbID { leaf EbID {
type uint8; type uint8;
} }
leaf CellID { leaf CellID {
type uint16; type uint16;
description description
"Equal to LinkHandle in IEEE802154e"; "CellID, one in CellList, indicates the cell used to send
EB";
} }
leaf Peroid { leaf Peroid {
type uint16; type uint16;
description description
"The EBs period, in seconds"; "The EBs period, in seconds, indicates the interval between
two EB sendings";
} }
leaf Expiration { leaf Expiration {
type enumeration { type enumeration {
enum NEVERSTOP; enum NEVERSTOP;
enum EXPIRATION; enum EXPIRATION;
} }
description description
"Which Period to indicate when the EBs periodicity will "NEVERSTOP- the period of the EB never stops; EXPIRATION-
stop. If Zero the period never stops."; when the Period arrives, the EB will stop.";
} }
leaf Priority { leaf Priority {
type uint8; type uint8;
description description
"The joining priority model that will be used for "The joining priority model that will be used for
advertisements. Joining priority MAY be for example advertisements. Joining priority MAY be for example
SAME_AS_PARENT, RANDOM, BEST_PARENT+1 or SAME_AS_PARENT, RANDOM, BEST_PARENT+1 or
DAGRANK(rank)."; DAGRANK(rank).";
} }
} }
container TimeSource { container TimeSource {
description
"specify the timesource selection policy and some relative
statistics.";
leaf policy { leaf policy {
type enumeration { type enumeration {
enum ALLPARENT; enum ALLPARENT;
enum BESTCONNECTED; enum BESTCONNECTED;
enum LOWESTJOINPRIORITY; enum LOWESTJOINPRIORITY;
} }
description
"indicates the policy to choose timesource. ALLPARENT- choose
from all parents; BESTCONNECTED- choose the best-connected
node; LOWESTJOINPRIORITY- choose the node with lowest priority
in its EB.";
} }
leaf TargetNodeAddress { leaf TargetNodeAddress {
type uint64; type uint64;
description description
"Address of the time source neighbor"; "Address of the time source neighbor";
} }
leaf MinTimeCorrection { leaf MinTimeCorrection {
type uint16; type uint16;
config false;
description description
"In microsecond"; "measured in microsecond";
} }
leaf MaxTimeCorrection { leaf MaxTimeCorrection {
type uint16; type uint16;
config false;
description description
"In microsecond"; "measured in microsecond";
} }
leaf AveTimeCorrection { leaf AveTimeCorrection {
type uint16; type uint16;
config false;
description description
"In microsecond"; "measured and computed in microsecond";
} }
} }
typedef asntype { typedef asntype {
description description
"The type to store ASN. String of 5 bytes"; "The type to store ASN. String of 5 bytes";
type string { type string {
length "0..5"; length "0..5";
} }
} }
list NeighborList { list NeighborList {
key "TargetNodeAddress"; key "TargetNodeAddress";
description
"statistics per communication link.";
leaf TargetNodeAddress { leaf TargetNodeAddress {
type uint64; type uint64;
description description
"Address of the time source neighbor"; "Address of the time source neighbor";
} }
leaf RSSI { leaf RSSI {
type uint8; type uint8;
config false; config false;
description description
"The received signal strength"; "The received signal strength";
skipping to change at page 16, line 35 skipping to change at page 17, line 38
leaf LinkQuality { leaf LinkQuality {
type uint8; type uint8;
config false; config false;
description description
"The LQI metric"; "The LQI metric";
} }
leaf ASN { leaf ASN {
type asntype; type asntype;
config false; config false;
description description
"The 5 ASN bytes"; "The 5 ASN bytes, indicates the most recent timeslot when a
packet from the neighbor was received";
} }
} }
list QueueList { list QueueList {
key "QueueId"; key "QueueId";
description
"List of Queues, including configuration and statistics.";
leaf QueueId { leaf QueueId {
type uint8; type uint8;
description description
"Address of the time source neighbor"; "Queue Identifier";
} }
leaf TxqLength { leaf TxqLength {
type uint8; type uint8;
description description
"The TX queue length in number of packets"; "The TX queue length in number of packets";
} }
leaf RxqLength { leaf RxqLength {
type uint8; type uint8;
description description
"The RX queue length in number of packets"; "The RX queue length in number of packets";
skipping to change at page 17, line 40 skipping to change at page 18, line 48
leaf QueuePriority { leaf QueuePriority {
type uint8; type uint8;
description description
"The priority for this queue."; "The priority for this queue.";
} }
list TrackIds { list TrackIds {
key "TrackID"; key "TrackID";
leaf TrackID{ leaf TrackID{
type uint16; type uint16;
description description
"The TrackID."; "The TrackID, one in TrackList, indicates the Track is
associated with the Queue.";
} }
} }
leaf MinLenTXQueue { leaf MinLenTXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, lowest TX queue len registered in the window."; "Statistics, lowest TX queue length registered in the window.";
} }
leaf MaxLenTXQueue { leaf MaxLenTXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, largest TX queue len registered in the window."; "Statistics, largest TX queue length registered in the
window.";
} }
leaf AvgLenTXQueue { leaf AvgLenTXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, avg TX queue len registered in the window."; "Statistics, avg TX queue length registered in the window.";
} }
leaf MinLenRXQueue { leaf MinLenRXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, lowest RX queue len registered in the window."; "Statistics, lowest RX queue length registered in the window.";
} }
leaf MaxLenRXQueue { leaf MaxLenRXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, largest RX queue len registered in the window."; "Statistics, largest RX queue len registered in the window.";
} }
leaf AvgLenRXQueue { leaf AvgLenRXQueue {
type uint8; type uint8;
config false; config false;
description description
"Statistics, avg RX queue len "Statistics, avg RX queue length registered in the window.";
registered in the window.";
} }
leaf MinRetransmissions { leaf MinRetransmissions {
type uint8; type uint8;
config false; config false;
description description
"Statistics, lowest number of "Statistics, lowest number of retransmissions registered in
retransmissions registered in the window."; the window.";
} }
leaf MaxRetransmissions { leaf MaxRetransmissions {
type uint8; type uint8;
config false; config false;
description description
"Statistics, largest number of retransmissions registered "Statistics, largest number of retransmissions registered
in the window."; in the window.";
} }
leaf AvgRetransmissions { leaf AvgRetransmissions {
type uint8; type uint8;
skipping to change at page 20, line 4 skipping to change at page 21, line 8
for a packet in the queue during the observed window."; for a packet in the queue during the observed window.";
} }
leaf AvgBackoff { leaf AvgBackoff {
type uint8; type uint8;
config false; config false;
description description
"Statistics, in number of slotframes, average Backoff "Statistics, in number of slotframes, average Backoff
for a packet in the queue during the observed window."; for a packet in the queue during the observed window.";
} }
} }
list LabelSwitchList { list LabelSwitchList {
key "LabelSwitchID"; key "LabelSwitchID";
description
"List of Label switch' configuration on the node";
leaf LabelSwitchID { leaf LabelSwitchID {
type uint16; type uint16;
} }
list InputCellIds { list InputCellIds {
key "CellID"; key "CellID";
leaf CellID{ leaf CellID{
type uint16; type uint16;
description description
"The CellID."; "The CellID, indicates the Rx cell on which the packet will
come in.";
} }
} }
list OutputCellIds { list OutputCellIds {
key "CellID"; key "CellID";
leaf CellID{ leaf CellID{
type uint16; type uint16;
description description
"The CellID."; "The CellID, indicates the Tx cell on which the received
packet should be sent out.";
} }
} }
leaf LoadBalancingPolicy { leaf LoadBalancingPolicy {
type enumeration { type enumeration {
enum ROUNDROBIN; enum ROUNDROBIN;
enum OTHER; enum OTHER;
} }
description description
"The load-balancing policy."; "The load-balancing policy. ROUNDROBIN- Round robin algorithm
is used for forwarding scheduling.";
} }
} }
list TrackList { list TrackList {
key "TrackId"; key "TrackId";
description
"List of the tracks through the node.";
leaf TrackId { leaf TrackId {
type uint16; type uint16;
description
"Track Identifier, named locally. It is used to refer to the
tuple (TrackOwnerAddr, InstanceID).";
} }
leaf TrackOwnerAddr { leaf TrackOwnerAddr {
type uint64; type uint64;
description description
"The address of the node which initializes the process of "The address of the node which initializes the process of
creating the track, i.e., the owner of the track;"; creating the track, i.e., the owner of the track;";
} }
leaf InstanceID { leaf InstanceID {
type uint16; type uint16;
description description
"InstanceID is an instance identifier given by the owner of "InstanceID is an instance identifier given by the owner of
the track. InstanceID comes from upper layer; InstanceID could the track. InstanceID comes from upper layer; InstanceID could
for example be the local instance ID defined in RPL."; for example be the local instance ID defined in RPL.";
} }
} }
list ChunkList { list ChunkList {
key "ChunkId"; key "ChunkId";
description
"List of the chunks assigned to the node.";
leaf ChunkId{ leaf ChunkId{
type uint16; type uint16;
description description
"The id of a chunk"; "The identifier of a chunk";
} }
leaf SlotframeId{ leaf SlotframeId{
type uint8; type uint8;
description description
"The id of the slotframe that is mapped to this chunk"; "SlotframeID, one in SlotframeList, indicates the
slotframe to which the chunk belongs";
} }
leaf SlotBase { leaf SlotBase {
type uint16; type uint16;
description description
"the base slotOffset of the chunk"; "the base slotOffset of the chunk in the slotframe";
} }
leaf SlotStep { leaf SlotStep {
type uint8; type uint8;
description description
"the slot incremental of the chunk"; "the slot incremental of the chunk";
} }
leaf ChannelBase { leaf ChannelBase {
type uint8; type uint8;
description description
"the base channelOffset of the chunk"; "the base channelOffset of the chunk";
skipping to change at page 23, line 6 skipping to change at page 24, line 6
description description
"the number of cells in the chunk. The chunk is the set "the number of cells in the chunk. The chunk is the set
of (slotOffset(i), channelOffset(i)), of (slotOffset(i), channelOffset(i)),
i=0..Chunksize-1, i=0..Chunksize-1,
slotOffset(i)= (slotBase + i * slotStep) % slotframeLen, slotOffset(i)= (slotBase + i * slotStep) % slotframeLen,
channelOffset(i) = (channelBase + i * channelStep) % 16"; channelOffset(i) = (channelBase + i * channelStep) % 16";
} }
} }
list ChunkCellList { list ChunkCellList {
key "SlotOffset ChannelOffset"; key "SlotOffset ChannelOffset";
description
"List of all of the cells assigned to the node via the
assignment of chunks.";
leaf SlotOffset{ leaf SlotOffset{
type uint16; type uint16;
description description
"The slotoffset."; "The slotoffset of a cell which belongs to a Chunk";
} }
leaf ChannelOffset{ leaf ChannelOffset{
type uint16; type uint16;
description description
"The channeloffset."; "The channeloffset of a cell which belongs to a chunk.";
} }
leaf ChunkId { leaf ChunkId {
type uint16; type uint16;
description description
"Identifier of the chunk the cell belongs to"; "Identifier of the chunk the cell belongs to";
} }
leaf CellID{ leaf CellID{
type uint16; type uint16;
description description
"Initial value of CellID is 0xFFFF. When the cell is "Initial value of CellID is 0xFFFF. When the cell is
scheduled, the value of CellID is same as that in scheduled, the value of CellID is same as that in
CellList"; CellList";
} }
leaf ChunkCellStatus { leaf ChunkCellStatus {
type enumeration { type enumeration {
enum UNUSED; enum UNSCHEDULED;
enum USED; enum SCHEDULED;
} }
} }
} }
3.2. YANG model of the IEEE802.15.4 PIB 3.2. YANG model of the IEEE802.15.4 PIB
This section describes the YANG model of the part of [IEEE802154] PIB This section describes the YANG model of the part of PIB
used by 6top, such as security related attributes. This part of data ([IEEE802154] and [IEEE802154e]) used by 6top, such as security
will be accessed through the MLME-GET and MLME-SET [IEEE802154] related attributes, TSCH related attributes. This part of data will
primitive. be accessed through the MLME-GET and MLME-SET primitive [IEEE802154]
directly, instead of using 6top comannds.
TODO TODO the security related attributes will be added after 6TiSCH WG
has consensus on the security scheme of 6top
3.3. YANG model of the IEEE802.15.4e PIB container TSCHSpecificPIBAttributes {
description
"TSCH specific MAC PIB attributes.";
reference
"table 52b in IEEE802.15.4e-2012.";
This section describes the YANG model of the part of [IEEE802154e] leaf macMinBE {
PIB used in 6top, such as TSCH related attributes. This part of data type uint8;
will be accessed through the MLME-GET and MLME-SET [IEEE802154] description
primitive. "defined in Table 52b of IEEE802.15.4e-2012,
The minimum value of the backoff exponent (BE) in the
CSMA-CA algorithm or the TSCH-CA algorithm. default:
3-CSMA-CA, 1-TSCH-CA";
}
leaf macMaxBE {
type uint8;
description
"defined in Table 52b of IEEE802.15.4e-2012,
The maximum value of the backoff exponent (BE) in the
CSMA-CA algorithm or the TSCH-CA algorithm. default:
5-CSMA-CA, 7-TSCH-CA";
}
leaf macDisconnectTime {
type uint16;
description
"defined in Table 52b of IEEE802.15.4e-2012,
Time (in Timeslots) to send out Disassociate frames
before disconnecting, default: 0x00ff";
}
leaf macJoinPriority {
type uint8;
description
"defined in Table 52b of IEEE802.15.4e-2012,
The lowest join priority from the TSCH Synchronization
IE in an Enhanced beacon, default: 1";
}
leaf macASN {
type asntype;
description
"defined in Table 52b of IEEE802.15.4e-2012,
The Absolute Slot Number, i.e., the number of slots
that ha elapsed since the start of the network.";
}
leaf macNoHLBuffers {
type enumeration {
enum TRUE;
enum FALSE;
}
description
"defined in Table 52b of IEEE802.15.4e-2012,
If the value is TRUE, the higher layer receiving the
frame payload cannot buffer it, and the device should
acknowledge frames with a NACK; If FALSE, the higher
layer can accept the frame payload. default: FALSE";
}
}
TODO list TSCHmacTimeslotTemplate {
key "macTimeslotTemplateId";
description
"List of all timeslot templates used in the node.";
reference
"table 52e in IEEE802.15.4e-2012.";
leaf macTimeslotTemplateId {
type uint8;
description
"defined in Table 52e of IEEE802.15.4e-2012.
Identifier of Timeslot Template. default: 0";
}
leaf macTsCCAOffset {
type uint16;
description
"The time between the beginning of timeslot and start
of CCA operation, in microsecond. default: 1800";
}
leaf macTsCCA {
type uint16;
description
"Duration of CCA, in microsecond. default: 128";
}
leaf macTsTxOffset {
type uint16;
description
"The time between the beginning of the timeslot and
the start of frame transmission, in microsecond.
default: 2120";
}
leaf macTsRxOffset {
type uint16;
description
"Beginning of the timeslot to when the receiver shall
be listening, in microsecond. default: 1120";
}
leaf macTsRxAckDelay {
type uint16;
description
"End of frame to when the transmitter shall listen for
Acknowledgment, in microsecond. default: 800";
}
leaf macTsTxAckDelay {
type uint16;
description
"End of frame to start of Acknowledgment, in
microsecond.
default: 1000";
}
leaf macTsRxWait {
type uint16;
description
"The time to wait for start of frame, in microsecond.
default: 2200";
}
leaf macTsAckWait {
type uint16;
description
"The minimum time to wait for start of an
Acknowledgment, in microsecond. default: 400";
}
leaf macTsRxTx {
type uint16;
description
"Transmit to Receive turnaround, in microsecond.
default: 192";
}
leaf macTsMaxAck {
type uint16;
description
"Transmission time to send Acknowledgment,in
microsecond. default: 2400";
}
leaf macTsMaxTx {
type uint16;
description
"Transmission time to send the maximum length frame,
in microsecond. default: 4256";
}
leaf macTsTimeslotLength {
type uint16;
description
"The total length of the timeslot including any unused
time after frame transmission and Acknowledgment,
in microsecond. default: 10000";
}
}
list TSCHHoppingSequence {
key "macHoppingSequenceID";
description
"List of all channel hopping sequences used in the
nodes";
reference
"Table 52f of IEEE802.15.4e-2012";
leaf macHoppingSequenceID {
type uint8;
description
"defined in Table 52f of IEEE802.15.4e-2012.
Each hopping sequence has a unique ID. default: 0";
}
leaf macChannelPage {
type uint8;
description
"Corresponds to the 5 MSBs (b27, ..., b31) of a row
in phyChannelsSupported. Note this may not correspond
to the current channelPage in use.";
}
leaf macNumberOfChannels {
type uint16;
description
"Number of channels supported by the PHY on this
channelPage.";
}
leaf macPhyConfiguration {
type uint32;
description
"For channel pages 0 to 6, the 27 LSBs(b0, b1, ...,
b26) indicate the status (1 = to be used, 0 = not to
be used) for each of the up to 27 valid channels
available to the PHY. For pages 7 and 8, the 27 LSBs
indicate the configuration of the PHY, and the channel
list is contained in the extendedBitmap.";
}
leaf macExtendedBitmap {
type uint64;
description
"For pages 7 and 8, a bitmap of numberOfChannels bits,
where bk shall indicate the status of channel k for
each of the up to numberOfChannels valid channels
supported by that channel page and phyConfiguration.
Otherwise field is empty.";
}
leaf macHoppingSequenceLength {
type uint16;
description
"The number of channels in the Hopping Sequence.
Does not necessarily equal numberOfChannels.";
}
list macHoppingSequenceList {
key "HoppingChannelID";
leaf HoppingChannelID {
type uint16;
description
"channels to be hopped over";
}
}
leaf macCurrentHop {
type uint16;
config false;
description
"Index of the current position in the hopping sequence
list.";
}
}
4. Commands 4. Commands
6top provides a set of commands as the interface with the higher 6top provides a set of commands as the interface with the higher
layer. Most of these commands are related to the management of layer. Most of these commands are related to the management of
slotframes, cells and scheduling information. 6top also provides an slotframes, cells and scheduling information. 6top also provides an
interface allowing an upper layer to retrieve status information and interface allowing an upper layer to retrieve status information and
statistics. The command set aims to facilitate 6top implementation statistics. The command set aims to facilitate 6top implementation
by describing the main operations that higher layers may use to by describing the main operations that higher layers may use to
interact with 6top. The listed commands aim at providing semantics interact with 6top. The listed commands aim at providing semantics
skipping to change at page 26, line 6 skipping to change at page 31, line 26
READ.eb: Reads the EBs configuration from EBList (Section 3.1). READ.eb: Reads the EBs configuration from EBList (Section 3.1).
CONFIGURE.timesource: Configures the Time Source Neighbor CONFIGURE.timesource: Configures the Time Source Neighbor
selection process, i.e. configure TimeSource (Section 3.1). selection process, i.e. configure TimeSource (Section 3.1).
READ.timesource: Retrieves information about the time source READ.timesource: Retrieves information about the time source
neighbors of that node from TimeSource (Section 3.1). neighbors of that node from TimeSource (Section 3.1).
CREATE.neighbor: Creates an entry for a neighbor in the neighbor CREATE.neighbor: Creates an entry for a neighbor in the neighbor
table, i.e. NeighborList (Section 3.1). table, i.e. NeighborList (Section 3.1).
READ.all.neighbor: Returns the list of neighbors of that node READ.all.neighbor: Returns the list of neighbors of that node
according to NeighborList (Section 3.1). according to NeighborList (Section 3.1).
READ.neighbor: Returns the information of a specific neighbor of READ.neighbor: Returns the information of a specific neighbor of
that node specified by its neighbor address according to that node specified by its neighbor address according to
NeighborList (Section 3.1). NeighborList (Section 3.1).
UPDATE.neighbor: Updates the last status for a given UPDATE.neighbor: Updates the last status for a given
TargetNodeAddress in the NeighborList (Section 3.1). TargetNodeAddress in the NeighborList (Section 3.1).
skipping to change at page 26, line 44 skipping to change at page 32, line 16
QueueList (Section 3.1). QueueList (Section 3.1).
LabelSwitching.map: Maps an input cell or a bundle of input cells LabelSwitching.map: Maps an input cell or a bundle of input cells
to an output cell or a bundle of output cells, i.e. adds a entry to an output cell or a bundle of output cells, i.e. adds a entry
to the LabelSwitchList (Section 3.1). to the LabelSwitchList (Section 3.1).
LabelSwitching.unmap: Unmap one input cell or a bundle of input LabelSwitching.unmap: Unmap one input cell or a bundle of input
cells to an output cell or a bundle of output cells, i.e. modifies cells to an output cell or a bundle of output cells, i.e. modifies
the LabelSwitchList (Section 3.1). the LabelSwitchList (Section 3.1).
CREATE.chunk: Creates a chunk which consists of one or more unused CREATE.chunk: Creates a chunk which consists of one or more
cells, i.e. add an entry to the ChunkList (Section 3.1). unscheduled cells, i.e. add an entry to the ChunkList
(Section 3.1).
READ.chunk: Returns the information of a chunk given its ChunkID READ.chunk: Returns the information of a chunk given its ChunkID
from ChunkList (Section 3.1). from ChunkList (Section 3.1).
DELETE.chunk: For given ChunkId, removes a chunk from the DELETE.chunk: For given ChunkId, removes a chunk from the
ChunkList (Section 3.1), which also causes all of the scheduled ChunkList (Section 3.1), which also causes all of the scheduled
cells in the chunk to be deleted from the TSCH schedule and cells in the chunk to be deleted from the TSCH schedule and
CellList (Section 3.1). CellList (Section 3.1).
CREATE.hardcell.fromchunk: Creates one or more hard cells from a CREATE.hardcell.fromchunk: Creates one or more hard cells from a
chunk. 6top schedules the cell and marks it as a hard cell, chunk. 6top schedules the cell and marks it as a hard cell,
indicating that it cannot reschedule this cell. The cell will be indicating that it cannot reschedule this cell. The cell will be
added into the CellList (Section 3.1). In addition, 6top will added into the CellList (Section 3.1). In addition, 6top will
change the attributes corresponding to the cell in the change the attributes corresponding to the cell in the
ChunkCellList (Section 3.1), i.e. its CellID is changed to the ChunkCellList (Section 3.1), i.e. its CellID is changed to the
same CellID in the CellList, and its Status is changed to USED. same CellID in the CellList, and its Status is changed to
SCHEDULED.
READ.chunkcell: Returns the information of all cells in a chunk READ.chunkcell: Returns the information of all cells in a chunk
given its ChunkID from ChunkCellList (Section 3.1). given its ChunkID from ChunkCellList (Section 3.1).
DELETE.hardcell.fromchunk: To remove a hard cell which comes from DELETE.hardcell.fromchunk: To remove a hard cell which comes from
a chunk. This removes the hard cell from the node's schedule and a chunk. This removes the hard cell from the node's schedule and
CellList (Section 3.1). In addition, it changes the attributes CellList (Section 3.1). In addition, it changes the attributes
corresponding to the cell in the ChunkCellList (Section 3.1), i.e. corresponding to the cell in the ChunkCellList (Section 3.1), i.e.
its CellID is changed back to 0xFFFF, and its Status is changed to its CellID is changed back to 0xFFFF, and its Status is changed to
UNUSED. UNSCHEDULED.
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
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
skipping to change at page 27, line 47 skipping to change at page 33, line 24
[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 LLN context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-00 (work in Statement and Goals", draft-ietf-6tisch-tsch-00 (work in
progress), November 2013. progress), November 2013.
[I-D.ietf-6tisch-architecture] [I-D.ietf-6tisch-architecture]
Thubert, P., Watteyne, T., and R. Assimiti, "An Thubert, P., Watteyne, T., and R. Assimiti, "An
Architecture for IPv6 over the TSCH mode of IEEE Architecture for IPv6 over the TSCH mode of IEEE
802.15.4e", draft-ietf-6tisch-architecture-01 (work in 802.15.4e", draft-ietf-6tisch-architecture-02 (work in
progress), February 2014. progress), June 2014.
[I-D.ietf-6tisch-terminology] [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-ietf-6tisch-terminology-01 (work in 802.15.4e", draft-ietf-6tisch-terminology-01 (work in
progress), February 2014. progress), February 2014.
[I-D.ietf-6tisch-minimal] [I-D.ietf-6tisch-minimal]
Vilajosana, X. and K. Pister, "Minimal 6TiSCH Vilajosana, X. and K. Pister, "Minimal 6TiSCH
Configuration", draft-ietf-6tisch-minimal-00 (work in Configuration", draft-ietf-6tisch-minimal-01 (work in
progress), November 2013. 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] [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-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.
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) Amendment 1: MAC sublayer", April Networks (LR-WPANs) Amendment 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] Watteyne, T., Vilajosana, X., Kerkez, B., Chraim, F.,
<http://www.openwsn.org/>. Weekly, K., Wang, Q., Glaser, S., and K. Pister, "OpenWSN:
a Standards-Based Low-Power Wireless Development
Environment", Transactions on Emerging Telecommunications
Technologies , August 2012.
[morell04label] [morell04label]
Morell, A., Vilajosana, X., Lopez-Vicario, J., and T. Morell, A., Vilajosana, X., Lopez-Vicario, J., and T.
Watteyne, "Label Switching over IEEE802.15.4e Networks. Watteyne, "Label Switching over IEEE802.15.4e Networks.
Transactions on Emerging Telecommunications Technologies", Transactions on Emerging Telecommunications Technologies",
June 2013. June 2013.
Authors' Addresses Authors' Addresses
Qin Wang (editor) Qin Wang (editor)
Univ. of Sci. and Tech. Beijing Univ. of Sci. and Tech. Beijing
30 Xueyuan Road 30 Xueyuan Road
Beijing, Hebei 100083 Beijing, Hebei 100083
China China
Phone: +86 (10) 6233 4781 Phone: +86 (10) 6233 4781
Email: wangqin@ies.ustb.edu.cn Email: wangqin@ies.ustb.edu.cn
Xavier Vilajosana Xavier Vilajosana
 End of changes. 85 change blocks. 
102 lines changed or deleted 416 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/