Subject: [6tisch] Minutes, 10 June 2016 interim, 6TiSCH WG

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Fri, 10 Jun 2016 16:09:29 +0000

Note: timestamps in PDT.

Connection details

  *   Date: 7-8am Pacific: http://www.worldtimebuddy.com/?qm=1&lid=100,12,5392171,1850147&h=100&date=2016-06-10&sln=14-15
  *   Webex link: https://cisco.webex.com/ciscosales/j.php?MTID=md64a0958ae4154c0553f056bf42b756a
  *   Webex recording: https://cisco.webex.com/ciscosales/lsr.php?RCID=9b9e5f06335b468ab7652c1811ab7eed
     *   Recording password: MuyDH7gC
  *   Meeting Slides: https://bitbucket.org/6tisch/meetings/
  *   Wiki: https://bitbucket.org/6tisch/meetings/wiki/160610_webex
  *   Slides: https://bitbucket.org/6tisch/meetings/src/master/160610_webex/slides_160610_webex.ppt

Taking notes (using Etherpad)

  1.  Xavi Vilajosana
  2.  Jonathan Munoz
  3.  Pascal Thubert

Present (alphabetically)

  1.  Chonggang Wang
  2.  Esteban Municio
  3.  Goran Selander
  4.  Jonathan Munoz
  5.  Nicola Accettura
  6.  Pascal Thubert
  7.  Qin Wang
  8.  Rashid Sangi
  9.  S.V.R. Anand
  10. Satish Anamalamudi
  11. Sedat Gormus
  12. Tamer Elzayyat
  13. Tengfei Chang
  14. Thomas Watteyne
  15. Xavi Vilajosana
  16. Y Lee

Agenda

  *   Administrivia [2min]
     *   Approval agenda
     *   Approval minutes last call
  *   6TiSCH architecture update [10min]
  *   6TiSCH security update [10min]
  *   6TiSCH ML topics [10min]
  *   <draft-satish-6tisch-6top-sf1-00> [10min]
  *   IETF96 Berlin update [15min]
     *   plugtest update
     *   Agenda bashing
     *   Introduction to 6LPWA
  *   AOB [1min]

Minutes

*        Administrivia [2min]

     *   Approval agenda
     *   Approval minutes last call
     *   Agenda and last call minutes are approved. No issues raised.

*        6TiSCH architecture update [10min]

     *   new version published v10
     *   talking to Charlie Perkins. Reviewer of the minimal draft. He will do the review next week
     *   Next week we ship minimal to the IESG.
     *   second paragraph of section 4.2.2 indicates that SF may be seen as divided between upper and lower bw management.
     *   sublayer draft. How the technical contents are documented? do we need a new sublayer draft? should this go to the architecture dradt?
     *   something to describe what is the 6top layer is needed.
     *   6top is an architecture component and needs to be described how it is integrated with the SF, and the stack.
     *   TODO check if the text describing the 6top sublayer in the architecture draft covers everything.
     *   TW: the description of the sublayer it does not go to the 6top, its natural place is the architecture draft
     *   Where the SF goes, is entirely part of the 6top sublayer. It is an algorithm that deals with bw. Therefore, add a description of the SF module at the architecture.
     *   IEEE is interested on the IEs that we are going to use in 6p

*        6TiSCH security update [10min]

     *   6tisch security call next week. (Thursday or Friday) *

*        6TiSCH ML topics [10min]

     *   Start value for the ETX when we discover a neighbor.
        *   pick an average value.
     *   work related to ANIMA.CEBOT.

*        <draft-satish-6tisch-6top-sf1-00> [10min]

     *   SF0 is a 1hop scheduling protocol
     *   Satish presents SF1
     *   no well support of critical traffic flows. e.g. industrial control
     *   SF1 provides dedicated traffic flows.
     *   enables the scheduling of end to end L2 bundles between source and destination *Associates trackID to each L2-bundle
     *   Resource reservation is out scope but two approaches are possible.
        *   centralized
        *   distributed *sends track id in the 6top request
     *   the track id is in the metadata field of 6topo
     *   Pascal: the track id according to your presentation is the same for all the nodes in the track. the IP source addres, RPLinstanceId. the global RPL id in a network is unique, then the local instance ID is unique within the node. So what instance ID are you using? TW: focus on something specific. Focus on the distributed side. TW: can this SF use 6top protocol as is? does this approach require new features from 6top?
     *   Xavi: RSVP is like transport. That is separated from 6P that is Layer 2. The key is to think how SF1 can compute locally to achieve the ned to end bundle reservation.

*        IETF96 Berlin update [15min]

     *   plugtest update 15-17 july. Experts call closed. 8 companies already registered
     *   Agenda bashing 90 minutes for the 6tisch wg
     *   Introduction to 6LPWA group forming BoF. Happen in berlin. Monday or Tuesday. LoRa all hands meeting on Wed.

*        AOB [1min]

  *   f-interop project h2020. Develops a framework for interop. Requested for 1h slot to present the project.
  *   Next 6tisch call in 2 weeks. Will be the last one before the cut-off date. (8th of july is cut-off date). Make sure we do a clear state of the drafts.