Scheduling Function One (SF1) for hop-by-hop Scheduling in 6tisch Networks
draft-satish-6tisch-6top-sf1-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-06-06
Stream (None)
Intended RFC status (None)
Formats plain text 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)
6tisch                                                    S. Anamalamudi
Internet-Draft                                                  M. Zhang
Intended status: Standards Track                     Huawei Technologies
Expires: December 8, 2016                                     C. Perkins
                                                               Futurewei
                                                             S.V.R.Anand
                                             Indian Institute of Science
                                                           June 06, 2016

   Scheduling Function One (SF1) for hop-by-hop Scheduling in 6tisch
                                Networks
                    draft-satish-6tisch-6top-sf1-00

Abstract

   This document defines a 6top Scheduling Function called "Scheduling
   Function One" (SF1) to schedule end-to-end dedicated L2-bundles hop-
   by-hop for each instance.  In addition, SF1 dynamically adapts the
   number of reserved cells in scheduled end-to-end L2-bundles of an
   ongoing instance through a Resource Reservation Protocol.  SF1 uses
   the 6P signaling messages with a TrackID to add/delete cells in end-
   to-end L2-bundles of each instance.

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 December 8, 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

Anamalamudi, et al.     Expires December 8, 2016                [Page 1]
Internet-Draft        draft-satish-6tisch-6top-sf1             June 2016

   (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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  End-to-end Track formation with paired L2-bundles . . . . . .   3
   3.  Scheduling Function Identifier  . . . . . . . . . . . . . . .   5
   4.  Rules to Create, Add/Delete Cells in end-to-end L2-bundles  .   5
     4.1.  SF1 Triggering Events . . . . . . . . . . . . . . . . . .   5
     4.2.  SF1 Bandwidth Allocation  . . . . . . . . . . . . . . . .   6
     4.3.  SF1 Allocation policy . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  References  . . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   With Scheduling Function Zero (SF0), on-the-fly cell scheduling (ADD/
   DELETE) to 1-hop neighbors can be achieved for aggregated (best-
   effort) traffic flows.  In other words, all the instances from nodeA
   to nodeB in Fig. 1 are scheduled in a single L3-bundle (IP link).

                  L3-bundle(Instance-1,Instance-2,...Instance-n)
               ------------------------------------------------->
         nodeA<-------------------------------------------------  nodeB
                  L3-bundle(Instance-1,Instance-2,...Instance-n)

    Figure 1: L3-bundle for aggregated traffic flows in 1-hop with SF0.

   Some applications (e.g.  Industrial M2M) require end-to-end dedicated
   L2-bundles to protect the control/data streams for time-critical
   applications [I-D.ietf-detnet-use-cases].  For such applications,
   per-instance L2-bundles need to be scheduled hop-by-hop between
   source and destination nodes [I-D.ietf-6tisch-architecture].  In
   addition, cells in the scheduled end-to-end L2-bundles of each
   instance have to be dynamically adapted for bursty time-critical
   traffic flows.  To achieve, end-to-end tracks have to be installed
Show full document text