6top Protocol (6P)
draft-ietf-6tisch-6top-protocol-03

Document Type Active Internet-Draft (6tisch WG)
Last updated 2016-10-31
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document Apr 2016 Dec 2016
On Agenda 6tisch at IETF-98
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
6TiSCH                                                      Q. Wang, Ed.
Internet-Draft                           Univ. of Sci. and Tech. Beijing
Intended status: Standards Track                           X. Vilajosana
Expires: May 4, 2017                     Universitat Oberta de Catalunya
                                                        October 31, 2016

                           6top Protocol (6P)
                   draft-ietf-6tisch-6top-protocol-03

Abstract

   This document defines the 6top Protocol (6P), which enables
   distributed scheduling in 6TiSCH networks.  6P allows neighbor nodes
   in a 6TiSCH network to add/delete TSCH cells to one another.  6P is
   part of the 6TiSCH Operation Sublayer (6top), the next higher layer
   of the IEEE802.15.4 TSCH medium access control layer.  The 6top
   Scheduling Function (SF) decides when to add/delete cells, and
   triggers 6P Transactions.  Several SFs can be defined, each
   identified by a different 6top Scheduling Function Identifier (SFID).
   This document lists the requirements for an SF, but leaves the
   definition of the SF out of scope.  Different SFs are expected to be
   defined in future companion specifications.

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

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Wang & Vilajosana          Expires May 4, 2017                  [Page 1]
Internet-Draft            6tisch-6top-protocol              October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  TEMPORARY EDITORIAL NOTES . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  6TiSCH Operation Sublayer (6top)  . . . . . . . . . . . . . .   5
     3.1.  Hard/Soft Cells . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Using 6top with the Minimal 6TiSCH Configuration  . . . .   5
   4.  6top Protocol (6P)  . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  6top Transaction  . . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  2-step 6top Transaction . . . . . . . . . . . . . . .   7
       4.1.2.  3-step 6top Transaction . . . . . . . . . . . . . . .   8
     4.2.  Message Format  . . . . . . . . . . . . . . . . . . . . .  10
       4.2.1.  6top Information Element  . . . . . . . . . . . . . .  10
       4.2.2.  General Message Format  . . . . . . . . . . . . . . .  10
       4.2.3.  6P Message Types  . . . . . . . . . . . . . . . . . .  11
       4.2.4.  6P Command Identifiers  . . . . . . . . . . . . . . .  12
       4.2.5.  6P Return Codes . . . . . . . . . . . . . . . . . . .  12
       4.2.6.  6P CellOptions  . . . . . . . . . . . . . . . . . . .  13
       4.2.7.  6P Cell Format  . . . . . . . . . . . . . . . . . . .  15
       4.2.8.  6P ADD Request Format . . . . . . . . . . . . . . . .  15
       4.2.9.  6P DELETE Request Format  . . . . . . . . . . . . . .  16
       4.2.10. 6P STATUS Request Format  . . . . . . . . . . . . . .  17
       4.2.11. 6P LIST Request Format  . . . . . . . . . . . . . . .  17
       4.2.12. 6P CLEAR Request Format . . . . . . . . . . . . . . .  18
       4.2.13. 6P Response Format  . . . . . . . . . . . . . . . . .  19
Show full document text