1. 6 March 2015 Webex IPv6 over the TSCH mode of IEEE 802.15.4e Chairs:
Pascal Thubert
Thomas Watteyne
Etherpad for minutes:

2. Note Well
This summary is only meant to point you in the right direction, and doesn't have all the nuances. The IETF's IPR Policy is set forth in BCP 79; please read it carefully.
The brief summary:
By participating with the IETF, you agree to follow IETF processes.
If you are aware that a contribution of yours (something you write, say, or discuss in any IETF context) is covered by patents or patent applications, you need to disclose that fact.
You understand that meetings might be recorded, broadcast, and publicly archived.
For further information, talk to a chair, ask an Area Director, or review the following:
BCP 9 (on the Internet Standards Process)
BCP 25 (on the Working Group processes)
BCP 78 (on the IETF Trust)
BCP 79 (on Intellectual Property Rights in the IETF) 2 2

3. Reminder: Minutes are taken. This meeting is recorded
Reminder: Minutes are taken * This meeting is recorded ** Presence is logged ***
* Scribe; please contribute online to the minutes at
** Recordings and Minutes are public and may be subject to discovery in the event of litigation.
*** From the Webex login 3 3 3 3

4. Agenda Administrivia [2min] Update plugtest [15min]
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]
OTF: shared vs. dedicated cells [TP]
AOB [3min] 4 4 4 4 4

5. Administrivia

6. Admin is trivia
Approval Agenda
Approval minutes last call 6 6 6 6

7. Update plugtest

8. ETSI 1st 6TiSCH Plugtests Update
Miguel Angel Reina Ortega
Centre for Testing and Interoperability , March
© ETSI All rights reserved

9. Agenda 1st 6TiSCH Plugtests – Basics Technical organization
Logistic information
Next steps
© ETSI All rights reserved

10. Basics
Scope – To test interoperability of 6TiSCH implementations based on draft-ietf-6tisch-minimal specification
When – July 2015
Where - At IETF#93 (Prague) (waiting for the name of the room)
© ETSI All rights reserved

11. Technical organization (1/2)
Group of experts has been formed (members cannot be announced yet until contracts formalized)
Tasks of experts group:
1) 6TiSCH test spec development
2) Implementation of a golden device for pre-testing purposes
3) Plugtests technical support
4) 6TiSCH Technical report. A summary of results and findings to feedback 6TiSCH WG
© ETSI All rights reserved

12. Technical organization (2/2)
Work planning:
Milestone 1 (20th  March). First draft of test specs available for feedback at IETF#92
Milestone 2. ( 1st June). Stable draft of test spec for feedback. Golden device ready for pre-testing.  
Milestone 3 (10th July). Final draft of test spec.
Milestone 4 (17-19 July). ETSI 1st 6TiSCH Plugtests
Milestone 4. (28 August). 6TiSCH Technical report ready
© ETSI All rights reserved

13. Logistic organization
Website will be launched by IETF#92 at
General information about the event
Registration information
Logistic information
Registration to the event:
will open 27th March 2015
will close 26th June 2015
© ETSI All rights reserved

14. Next steps Survey on 2nd 6TiSCH ETSI Plugtests: When: What:
At IETF#94 (Japan)?
At IETF#95 (Argentina)?
What:
Security ?
To be discussed ...
© ETSI All rights reserved

15. Contact Thank you! Miguel Angel Reina Ortega Technical Expert
Centre for Testing and Interoperability (CTI)
European Telecommunications Standards Institute
650 Route des Lucioles
F-06921, Sophia Antipolis
Tel: +33 (0)
Mob: +33 (0)
Thank you!
© ETSI All rights reserved

16. IETF92 Dallas meeting
goals, agenda

17. IETF92
Final agenda published
2 6TiSCH sessions:
CDT Monday Afternoon Session II (1.5h)
CDT Thursday Morning Session I (2.5h)
Important dates;
(Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
(Friday): Early Bird registration and payment cut-off at UTC 23:59.
(Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.

18. Goals
Monday
DetNet: Gap analysis - need for IETF work, problem statement and architecture, requirement drafts
IoT PCE: Gap analysis vs. 6TiSCH needs, Barcelona workshop highlights, 6TiSCH requirements for PCE and TEAS.
Dynamic Scheduling: OTF draft status, local vs. distributed optimizations, chunk appropriation and fairness.
Rechartering: what of the above should be suggested as charter items. Call for intent to actually produce related work.
Thursday
Last calls on TSCH and architecture drafts.
Minimal draft publication
Status on 6top related drafts, chartered and non-chartered
ETSI plugtest coverage. What's basic support and what's stretched
Security: Status of join process work. Suggestions for chartered work. Positioning vs. SEC area WGs.
More rechartering: summary of the Monday session. Same questions including the items above.
5/27/2018

19. Agenda 4 Monday (draft)
Distributed Scheduling OTF (Diego) [30 min] DetNet Architecture (Norm) [20 min] Pro Audio Reqs (Craig) [10 min] Utilities reqs (Patrick) [10 min] 6TiSCH reqs (Chonggang) [10 min] Wrap up for rechartering [10 min]
5/27/2018

20. Agenda 4 Thursday (p1) Last Call Status [40 mins]
TSCH (Thomas)
Minimal (Xavi)
Archie (Pascal)
Terminology (Pascal)
Other Drafts [30 mins]
6top Interface
6top
coap
5/27/2018

21. Agenda 4 Thursday (p2) Plugtest [10 mins] Security [30 mins]
DT status and design goals (Michael)
Archi considerations (René)
Rechartering [40 mins]
Summary of Monday
Scheduling goals and deliverables
Security goals and deliverables
5/27/2018

22. Architecture Draft Last Call

23. Archie status
Passed last call No major issues, plenty of great reviews Agreed on the term ‘volumes’ Addressed all issues but - René vs. Jonathan on security - Some remaining issues from Michael Will publish by Monday

24. Minimal Draft Wrap-up

25. Final Open Questions Header compression Security
Relationship with plugtest

26. OTF: shared vs. dedicated cells

27. Background
New version (-05) of the draft coming soon Request only cell reservation. Bundles are managed by 6top OTF uses best-effort track Two or more node pairs may schedule the same cell independently, possibly generating a collision

28. Questions
Option A: We use shared cells, so two nodes may transmit, but there is a contention mechanism to solve this condition Option B: We use dedicated TX-RX cells, contention-free, but there may be a collision if two node pairs schedule the same cell Best effort track can include dedicated cells?

29. AOB ?

30. Thank you!