Clone wiki

meetings / 150306_webex

Minutes, 06 March 2015 interim, 6TiSCH WG

Note: timestamps in PST.

Connection details


Taking notes (using Etherpad)

  1. Xavi Vilajosana
  2. Pascal Thubert
  3. Thomas Watteyne

Present (alphabetically)

  1. Thomas Watteyne
  2. Pascal Thubert
  3. Chonggang Wang
  4. Deji Chen
  5. Diego Dujovne
  6. Nicola Accettura
  7. Pat Kinney
  8. Patrick Wetterwald
  9. Pouria Zand
  10. Qin Wang
  11. Raghuram Sudhaakar
  12. Rene Struik
  13. Savio Sciancalepore
  14. Xavi Vilajosana
  15. Sedat Gormus
  16. Zhuo Chen


  • Administrivia [2min]
    • Approval agenda
    • Approval minutes last call
  • update plugtest [15min]
  • IETF92 Dallas meeting: goals, agenda [20min]
  • architecture draft last call [10min]
  • minimal draft wrap-up [10min]
  • AOB [3min]


  • [07.05] Meeting starts
    • minutes starts
    • Pascal reminds Note Well
    • Objective of the meeting: preparation for the IETF meeting
  • Administrivia
    • Approval agenda

      Agenda is approved. No issues are raised.

    • Approval minutes last call

      Last call minutes are approved. No issues are raised.

  • [07.08] update plugtest
    • Thomas presents on behalf of Miguel.
    • Prague ETSI plugtest
    • First plugtest about the minimal draft
    • 17-19 july before IETF 93 (most likely in same hotel that IETF
    • group of experts*
    • task to be done:
      • develop the test list
      • develop and implement the golden board and code running there
      • technical support
    • Several milestones from now to july. objective to have everything ready by 17th of July.
      Report later.
    • Website will be hosted by ETSI.
    • Needs to register to the event. Registration opens the 27th of march, closes in June
    • 2nd plugtest ? Japan or Argentina (November or March). also need to discuss scope.
    • Questions are encouraged, can contact Miguel by email
  • [07.??] IETF92 Dallas meeting: goals, agenda
    • 2 sessions. monday afternoon. unchartered items. Thursday morning, chartered topics + security
    • cutoff date next monday.
    • goal is to define detnet. Gap analysis with PCE. Identify what is being done today and see what 6tisch covers.
    • figure out relation to other groups
    • dynamic scheduling in general. OTF
    • rechartering. what on that topic might be part of the new charter
    • regarding chartered items session
      • last call for tsch and architecture
      • discuss about what to do for header compression in minimal
      • plugtest
      • security
      • rechartering
    • The detnet hour will cover OTF and then discussion about centralized approaches.
    • Use cases and requirements for tracks.
    • 10min per draft in the chartered session 2.5h
    • 6top is core and needs to be complete.
    • second part, security and status from the security design team. Also ideas for rechartering

      ACTION: WG Chairs to Contact meetecho for remote meeting participants.

  • [07.27] architecture draft last call
    • the draft will be generated in volumes
    • the new security text in the architecture draft is not final. It still do not have the consensus from the security team.
    • needs feedback for that part.
    • will be published on Monday.
    • Rene: Changing 2 words on the section solves the issue (referring to suggested disposition of Jonathan Simon's comments on the architecture draft, which according to oral info on phone call, is to the commenter's satisfaction).
    • TW: Can this be resolved in the ML?
    • Rene: commented that there was low activity level on the ML
    • No proposal submitted by everybody on how to improve PSK problems.
    • Discuss of how the overall architecture of the overall joining process should be.
    • According to Rene. There is no technical justification about the comments made to ReneĀ“s proposal.
    • Rene: the text in Section 13 was what was provided by the 6TiSCH Security design team, with unanimous consensus by those who participated on the 6tisch security calls in January. For feedback on comments made on Section 13 of the architecture, please see the detailed technical rationale for disposition (this is not position-based arguing, simply comment disposition based on technical arguments).
    • PT: I was asking to Rene to describe how ISA100 works during a year.
    • TW: the idea of the next IETF meeting is to charter security.
    • Rene: does not support the removal of the section proposed by Rene in the architecture .
      [07.??] minimal draft wrap-up
    • Security in minimal: what to say
    • there will be a network wide network key.
    • The join process is only for autonomic and scalable network bootstrapping.
    • all the nodes have the same key or we have 2 keys? one for the beacon and one for the data.
    • how the keys get there is out of scope.
    • in a network we use 1 key for beacon and another for data
    • key for data and different key for data. data is authenticated.
  • [07.??] AOB

    OTF question about the use of shared cells on reservation. T

    • it seems a confusion with soft cells.
    • move to the ML and at the WG meeting.
    • No 6tisch call next time. INformal calls to synchronize slides.
    • Use case prepared for the track case.
  • [08.13] Meeting ends