Subject: [6tisch] Minutes of the 6TiSCH webex call, Friday may 9th 2014

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Fri, 9 May 2014 16:27:30 +0000

Webex CALL, May 9th, 2014
________________________________
Resources

  *   Webex recording<https://cisco.webex.com/ciscosales/lsr.php?RCID=e1b60fc0544244779dc1eb167646f9f1>
  *   Wiki<https://bitbucket.org/6tisch/meetings/wiki/140509_webex>: wiki page for this meeting
  *   slides<https://bitbucket.org/6tisch/meetings/src/master/140509_webex/slides_140509_webex.ppt>: slides shared during the call

Action items

  *   Raghu to start a thread on ack mechanism for the 6top blocks. Pat to describe the ack vs. Enhanced ack.
  *   Pouria to start a thread on which code is reused for managing the block retries.
  *   Pascal to doodle a plugfest time for the beginning of the plugfest on Sunday before IETF

Agenda

  1.  [10min] Administrivia
     *   Approval agenda
     *   Approval minutes last call
     *   IETF 90 in Toronto: Registration opened;
     *   PlugFest ? bits and bytes ?
     *   draft-ietf-6tisch-coap published
  2.  [10min] Status on 6top discussions
  3.  [20min] Slotframe structure in Minimal draft
  4.  [20min] Terminology discussion
  5.  [2min] Next meetings
  6.  [1min] AOB

Minutes

Meeting starts at 08.05 PST

Taking notes (using Etherpad)

  1.  Xavi Vilajosana
  2.  Pascal Thubert

Attendance (alphabetically)

  1.  Bryan Mc Laughlin
  2.  James Pylakutty
  3.  Kazushi Muraoka
  4.  Kuor Hsin Chang
  5.  Maria Rita Palattella
  6.  Michael Richardson
  7.  Nicola Accettura
  8.  Pascal Thubert
  9.  Pat Kinney
  10. Pouria Zand
  11. Qin Wang
  12. Raghuram Sudhaakar
  13. Rouhollah Nabati
  14. Xavi Vilajosana

Discussion

  1.  [8:05] Meeting starts

-recording starts

Agenda is approved. Last Call minutes are approved

[8:08] Update IETF 90 -registration is open.

[8:09]Coap Draft has been accepted as a WG document.

Milestones: WG documents adopted.

Bits and Bytes -to expose and show product demos -the subject of B&B is IoT

Plugfest As alternative Possible days: 1.Sunday Afternoon, 1.Monday Evening 1.Wed Evening 1.Friday

ACTION to contact other IETF groups to inform about plugfest.

Michael: Friday afternoon is no good since network is rapidly shut down. Late hours not good either people are tired.

Suggestion to do it on Sunday Morning.

ACTION: DOODLE at the ML.

6top status

Xavi: discussions on block option to fragment packet presented by Qin Wang, who presented what the wrapper IE looks like. The we discussed overhead and alternatives (fragments at app level. Result is that the block option already has everything we need, so better reuse. Overhead appears to be 17 out of 64 (see slides) Win also discussed whether the URI path is needed since it is supposed to be in each block. Unclear so far.

Pouria: Do we need to have the code for retransmission in 6Top.

Xavi: at MAC layer we do not know if parsing works so we need all the code in 6top

Raghu: I agree, should not use the MAC reliability mechanism at 6Top. Best to separate the mechanisms, they do not work exactly the same some not the exact same code. Code for IE part ans well as comm with PCE is the same to it is still advantageous.

Xaxi: 6top acks will be packets not mac layer ACK. Can we you the wrapper IE?

Raghu : Yes we need to explore that offline.

Pat Kinney: if we have a6Top ack on top of the ack we add a significant overhead

Raghu: agree but the concern is how the reassembly happens

Pat: let us off line the discussion, maybe we can change the MAC

Pascal: if the error is an exception then have an exception message not an additional ack every time.

Pat: there is the legacy ACK and the enhanced ack. The e-ack checks for the MIC on top of CRC, let us offline

Kuor Hsin: merging the acks is being discussed

Xavi: URI-host is definitely an option and we can elide it

Minimal Draft

Xavi : proposal to use OTF?

Pascal: This does not allow offseting multiple minimal networks in sytnc with a backbone interfereing in a same room. let us continue on the thread.

Xavi presents the minimal schedule. Problem is very low bandwidth and sync is all at teh same time. For PB2, we can space the slots uniformely to the sync interval is reduced to 300ms instead of 1.3s

difference between re-join and reboot. Pascal proposes to have an initial phase

Discuss terminology next meeting

1.     [9:03] AOB

     *   No other Business; adjourning.

2.     [8:59] Meeting ends
Pascal (acting for Thomas)