Minutes for 6TISCH at interim-2015-6tisch-9
minutes-interim-2015-6tisch-9-1

## THIS IS A DRAFT!!! ##

# Minutes, 05 June 2015 interim, 6TiSCH WG #

Note: timestamps in PST.

Connection details
------------------

* Webex:
https://ciscosales.webex.com/ciscosales/j.php?ED=219615007&UID=481905242&PW=NZTRkNDAwOTE1&RT=MiMyMw%3D%3D
* Etherpad: http://etherpad.tools.ietf.org:9000/p/6tisch?useMonospaceFont=true
* Topic: 6TiSCH Bi-Weekly * Time: 7:00 am, Pacific Daylight Time (San
Francisco, GMT-07:00) * Meeting Number: 206 802 913 * Meeting Password: sixtus
* CCM: +14085256800x206802913

Resources
---------

* Webex recording:
https://cisco.webex.com/ciscosales/lsr.php?RCID=77069df96ff7499cb324cf2b4c7a57d9
* Wiki: https://bitbucket.org/6tisch/meetings/wiki/150605_webex * Slides:
https://bitbucket.org/6tisch/meetings/src/master/150605_webex/slides_150605_webex.ppt

Taking notes _(using Etherpad)_
-------------------------------

1. Thomas
1. Pascal

Present _(alphabetically)_
--------------------------

1. Thomas Watteyne
1. Pascal Thubert
1. Alexandre Pelov
1. Elvis Vogli
1. Giuseppe Piro
1. Guillaume Gaillard
1. Kallol Das
1. Malisa Vucinic
1. Maria Rita Palattella
1. Michael Richardson
1. Michel Veillette
1. Nicola Accettura
1. Pat Kinney
1. Patrick Wetterwald
1. Pouria Zand
1. Qin Wang
1. Rene Struik
1. S.V.R.Anand
1. Sedat Gormus
1. Tamer Elzayyat
1. Xavi Vilajosana
1. Zuo Chen

Action Items
------------
Chairs to check announcements for 7 vs 8AM pacific
Xavi to sync with Nicolla on Ranks in the diagram by next Friday (June 12)
Malisa to start a thread on security settings for in MAC for K1 and K2 for text
to be included in example section
Xavi to publish 08 and Pascal to push to IESG by next Friday (June 12)

1. TODO

Agenda
------

* Administrivia _[4min]_
    * Approval agenda
    * Approval minutes last call
    * update IETF93
    * chair's statement on refocusing the work
* draft-ietf-6tisch-minimal
    * security text statement _[10min]_ (chairs)
    * update minimal with RPL DAGrank _[10min]_ (Nicola Accettura)
* draft-ietf-6tisch-coap
    * preparation: please read
    https://tools.ietf.org/html/draft-vanderstok-core-comi-06 * mail thread:
    YANG hash clashes & full extended name _[20min]_
* AOB _[1min]_

Minutes
-------

 * _[07.??]_ Meeting starts
    * Just received deck from Alex, added to the slides
    * René: meetings are announced at the old time (8AM) need to chage this in
    the future * Thomas todo for chairs, check the announcements
 * _[07.??]_ Administrivia _[4min]_
    * Approved agenda
    * Approved minutes last call
    * update IETF93
        * requested 2.5 hours early in the week
        * 17-18 July  plugtest
        * 19 July hackathon
        * need to publish preliminary agenda in 2 weeks
        * then draft cut off 2 week before IETF
    * chair's statement on refocusing the work
        * need to wrapup coap and interface document
        * need more attention. Proposal: a sprint
        * 2 weeks focus per document. Additional webex on 15th and 29th 4PM CET
        proposed to focus on the drafts * first interface, presenting at the
        interim * idea is a respin for each draft by IETF cutoff * Qin: find
        for me (Qin is in Pennsylvania)
    * news on detnet
        * BoF for WG forming (2h)
        * close to final charter
        * chairs for BoF have accepted
        * will be highly focused on problem statement
        * new draft: 6TiSCH requirements for detnet
        * idea: feed requirements
        * important link with interface/coap drafts
        * important to move forward quickly before interface draft published
        * 6TiSCH is a feed for detnet, pce/teas/ccamp is a technology provider

 * _[07.??]_ draft-ietf-6tisch-coap
    * preparation: please read
    https://tools.ietf.org/html/draft-vanderstok-core-comi-06 * mail thread:
    YANG hash clashes & full extended name _[20min]_
        * 75 emails in the past couple of weeks
        * 6TiSCH is positioned as having requirements to COMI
        * Thanks Michel, Alex and others
        * Thomas: 6TiSCH would like to avoid interactions with nodes as they
        come up, like fetch a file or a resource zero or whatever. This may
        saturate the limited bandwidth.
    * Alex: on goals, summarizing discussion with Micehland Andy
        * We want short ID sand no hash clash
        * Want 1 byte instead of 5 bytes for the hash and CBOR
        * Proposed  compression by zero elimination
        * IDs 1 to 255 -> yang and cbor result in 1 octet
        * how can we force that hashid start with 0?
        * propose to use these for hash aliases frequently used
        * e.g. cell id, channel id, time slots
        * assignment? one way is to say that alias 0 is meta resource, querying
        0 would tell you what's happening * can use POST to setup mapping *
        hash collisions: Michel's idea is to use managed module IDs and
        deterministic value. 20 bits module ID. Remaining 10 bits is datanode
        ID * Michel supports the proposal. Sadly missing people from COMI.. *
        Michel: in some situation the node must fetch both the list of module
        and ? * Thomas: do I need to retrieve the list of module? In the
        context of 6TiSCH, a node will have the 6TiSCH resources and 6TiSCH
        knows how to hit those whatever else is on the mote. No required
        discovery * Michel: yes but is another module augments the 6TiSCH
        model, this goes under the 6TiSCH model and we need the module list *
        Michel: can save up to 8 bytes on each request, makes a lot of
        difference * Thomas: 6TiSCH is a small subset of what COMI can do, let
        us keep it very simple. Q: can we retrieve a version number (like rfc
        nb) so I know which level of 6top interface and then I know exactly
        what that model exposes? * Michel: 2 problems. No versioning in COMI.
        NO notion of module. I create one for definitions but the names/hashes
        end up mixed in the same bucket. In Alex's proposal there is a module
        ID in the identifier. * Alex is we accept that 0 is the meta resource.
        GET to 0 will give a hash value of the alias assignment and if that
        hash is known, all set; else more introspection is required. * Michel:
        Alias does not solve all problem, there is also the node ID and we do
        not have that construct. * Thomas: in the slides, I'm showing what
        would be nice o have and versioning would be one such thing. * Thomas:
        Proposal for 6TiSCH to have well known alias and not use mg. * Michel:
        will work

 * _[07.??]_ draft-ietf-6tisch-minimal
    * security text statement _[10min]_ (chairs)
        * Thomas: to René's point we'd better stay on the Dallas text since we
        did not get consensus on update. We need this in for the plugtest *
        Rene: What is Dallas text * Thomas: the text that was submitted to the
        ML by Rene with the corrections pointed by Rene Struik. * from Rene
        Struik to Everyone:
http://www.ietf.org/mail-archive/web/6tisch/current/msg03094.html
        * from Michael Richardson to Everyone: works for me.
        * Pascal: can we have examples from Malisa's work
        * Malisa: will propose text
    * Status on minimal (Xavi)
            * correction on dagroot pointed out by Nicola
        * added a paragraph in section 10 example to explain little endian
        reading * Nicolla: there is still a mistake, node 1 should be 3 or 4 *
        Xavi: will fix * Thomas: can you please expose to Nicolla your final
        for validation * Maria Rita: We need to publish minimal before we
        publish plug test * Pascal: we want to push the draft to IESG by end of
        next week. Let us sove

 * _[07.??]_ AOB _[1min]_
 * _[08.??]_ Meeting ends