Subject: [6tisch] Minutes, 13 May 2016 interim, 6TiSCH WG

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Fri, 13 May 2016 15:36:18 +0000

Connection details

  *   Date: 7-8am Pacific: http://www.worldtimebuddy.com/?qm=1&lid=100,12,5392171,1850147&h=100&date=2016-05-13&sln=14-15
  *   Webex link: https://cisco.webex.com/ciscosales/j.php?MTID=md64a0958ae4154c0553f056bf42b756a
  *   Webex recording: https://cisco.webex.com/ciscosales/lsr.php?RCID=8179723dd8324abfbd0548a5e6b3ed79
     *   Recording password: DqBDTJT2
  *   Meeting Slides: https://bitbucket.org/6tisch/meetings/
  *   Wiki: https://bitbucket.org/6tisch/meetings/wiki/160513_webex
  *   Slides: https://bitbucket.org/6tisch/meetings/src/master/160513_webex/slides_160513_webex.ppt https://bitbucket.org/6tisch/meetings/raw/95928ef96b228fe5dabeb0dd6d602347813b01d2/160513_webex/slides_160513_webex.ppt

Taking notes (using Etherpad)

Michael Richardson Xavi Vilajosana

Editor

  1.  Pascal Thubert

Present (alphabetically)

  1.  Chonggang Wang
  2.  C-Y Lee
  3.  Diego Dujovne
  4.  Dominique Barthel
  5.  Francesca Palombini
  6.  Göran Selander
  7.  Jonathan Muñoz
  8.  Malisa Vucinic
  9.  Michael Richardson
  10. Nicola Accettura
  11. Pascal Thubert
  12. Pat Kinney
  13. Rashid Sangi
  14. S.V.R. Anand
  15. Satish Anamalamudi
  16. Sedat Gormus
  17. Seema Kumar
  18. Sumankumar Panchal
  19. Suresh Krishnan
  20. Tamer Elzayyat
  21. Tengfei Chang
  22. Thomas Watteyne
  23. Xavi Vilajosana
  24. Zacharie Brodard

Action Items

  1.  Diego to send to the ML a proposal to add a response code indicating cells not available due to concurrent transaction
  2.  Diego to send to the ML a clarification on the bootsraping status and actions.
  3.  Xavi to propose text on ML, and get it done in one doc cycle
  4.  Thomas to update the terminology for the terms "Link" and "Ack"

Agenda

  *   Administrivia [2min]
     *   Approval agenda
     *   Approval minutes last call
  *   round-stable draft status [10min]
     *   update draft-ietf-6tisch-6top-protocol
     *   update draft-dujovne-6tisch-6top-sf0
     *   update draft-ietf-6tisch-minimal
  *   high-bandwidth forum for ML discussions [10min]
     *   "Doubts in 3-step transactions mentioned in draft-wang-6tisch-6top-protocol-00"
     *   "comments on latest terminology draft"
  *   outcome security DT meeting [20min]
  *   AOB [3min]

Minutes

·        Administrivia

     *   Approval agenda

The agenda is approved. No issues raised

     *   Approval minutes last call

The minutes of the last call are approved. No issues raised

·        round-stable draft status

     *   update draft-ietf-6tisch-6top-protocol
        *   6top adopted and v00 published
        *   minor typos to be corrected
        *   concurrent transactions require a locking mechanism in candidate list
        *   Pat Kinney: we need to enable retries if we want it to be more optimal
        *   Diego: Proposes to add a new response code to indicate no resources available while in concurrent transaction.

o   update draft-dujovne-6tisch-6top-sf0

        *   v00 published
        *   typos to be corrected
        *   envision more than one SF function. If some initial state is stored in the SF.
        *   How this is aggregated in the lower layers.
        *   all scheduling functions should do something at startup -> section about boot rules
        *   remove steps 5 and 6 and add over-provisioning

o   update draft-ietf-6tisch-minimal

        *   Clarify the use of RPL within the draft.
        *   Action to do a revision in 1month. Addressing all the comments from Charlie. *

·        high-bandwidth forum for ML discussions

     *   "Doubts in 3-step transactions mentioned in draft-wang-6tisch-6top-protocol-00"
        *   Satish proposes a new mechanism for the 3-way transaction
        *   the scheduling function decides what the cell list means.
        *   Seema: in the new proposal it is difficult to differentiate between the 2 step and the 3 step mechanism as the candidate list is present in the first message in both cases.
        *   The SF is the responsible of deciding what of the 6top mechanisms.
        *   the 6top protocol is the carrier of the data. the SF decides what if 2 or 3 steps are used. We have not considered that both models can be used at the same time. In case this is needed, the metadata field can be used to indicate that.
        *   Pascal: If the requester is a child, then it does not know which chunk is owned by the parent and it cannot propose a candidate list of cells. What it could do is propose a candidate list of slot offsets that are free in its schedule
     *   "comments on latest terminology draft"
        *   discussion about the concept of Link.
        *   Action: Thomas Watteyne to propose a link definition. define them as IETF links
        *   (discussed somewhat later but applying here)
           *   Pat Kinney: ack needs to be defined in the terminology according to the ietf meaning.
           *   Thomas Watteyne: we will use response.
           *   Pat: yes

·        outcome security DT meeting

     *   Michael Richardson had to leave 10:50.
     *   first meeting of the security meeting.
     *   minutes not completely collected.
     *   use of oscoap for 6tisch
     *   using object security at coap level, the join interaction can be managed.
     *   3 options. pre-shared keys, certificates, RPK.
     *   Goran presents OSCOAP slide. Looking for the minimal solution.
     *   Proposes an update to send key K2 as part of the first answer
     *   Pascal: getting K2 on the first exchange would be great. We could use K2 to protect the global IPv6 address in the ND registration, and carry the configuration flow in the ND registration so at the end of the second flow we have authenticated, obtained K2 and registered the IPv6 address securely
     *   PSK requires 2 flows of messages.

·        AOB

     *   new tutorials about 6tisch technology to be presented in the following days..
     *   Plugtest before the IETF Berlin meeting. Friday afternoon, Saturday and Sunday Morning.
     *   Announce the event in the following days.
     *   No other B.