PAW for TSCH
draft-thubert-paw-for-tisch-00

Document Type Active Internet-Draft (individual)
Last updated 2019-01-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PAW                                                      P. Thubert, Ed.
Internet-Draft                                                     Cisco
Intended status: Informational                          January 28, 2019
Expires: August 1, 2019

                              PAW for TSCH
                     draft-thubert-paw-for-tisch-00

Abstract

   This document builds on the 6TiSCH architecture that defines, among
   others, mechanisms to establish and maintain deterministic routing
   and scheduling in a centralized fashion.  The document details
   dependencies on DetNet and PCE controller to express topologies and
   capabilities, as well as abstract state that the controller must be
   able to program into the network devices to enable deterministic
   forwarding operations.

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 https://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 August 1, 2019.

Copyright Notice

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

Thubert                  Expires August 1, 2019                 [Page 1]
Internet-Draft                 paw-4-tisch                  January 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  6TiSCH Overview . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  SlotFrames and Priorities . . . . . . . . . . . . . . . .   7
     3.2.  Schedule Management by a PCE  . . . . . . . . . . . . . .   8
     3.3.  Track Scheduling Protocol . . . . . . . . . . . . . . . .   9
     3.4.  Track Forwarding  . . . . . . . . . . . . . . . . . . . .  10
       3.4.1.  Transport Mode  . . . . . . . . . . . . . . . . . . .  11
       3.4.2.  Tunnel Mode . . . . . . . . . . . . . . . . . . . . .  12
       3.4.3.  Tunnel Metadata . . . . . . . . . . . . . . . . . . .  13
       3.4.4.  OAM . . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Operations of Interest for DetNet and PCE . . . . . . . . . .  14
     4.1.  Packet Marking and Handling . . . . . . . . . . . . . . .  15
       4.1.1.  Tagging Packets for Flow Identification . . . . . . .  15
       4.1.2.  Replication, Retries and Elimination  . . . . . . . .  16
       4.1.3.  Differentiated Services Per-Hop-Behavior  . . . . . .  16
     4.2.  Topology and capabilities . . . . . . . . . . . . . . . .  17
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  17
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   The emergence of wireless technology has enabled a variety of new
   devices to get interconnected, at a very low marginal cost per
   device, at any distance ranging from Near Field to interplanetary,
   and in circumstances where wiring may not be practical, for instance
   on fast-moving or rotating devices.

   At the same time, a new breed of Time Sensitive Networks is being
   developed to enable traffic that is highly sensitive to jitter, quite
   sensitive to latency, and with a high degree of operational

Thubert                  Expires August 1, 2019                 [Page 2]
Show full document text