6TSCH Webex 05/24/2013

Agenda BoF recap[5min] Webinar announcement[5min] Centralized routing requirements draft [10min + 5min Q&A] updated TSCH draft[5min] updated 6tus draft[10min] label switching discussion[15min] logo challenge![5min]

BoF Recap

Req posted May 17th BOF's full name and acronym in brackets: Deterministic IPv6 over IEEE e Timeslotted Channel Hopping (6TSCH) AREA under which Working Group or BOF appears INT (AD Ted Lemon) Chair(s) Name(s) and address(es) Thomas Watteyne, Pascal Thubert

Req posted May 17th Full Description of BOF WG creation BoF on Deterministic IPv6 over the TSCH mode of IEEE e. The WG will propose an architecture that supports centralized and distributed routing and resource allocation over a TSCH based mesh. The group will resolve the impacts on existing protocols such as RPL and 6LoWPAN. It will define a component that provides the expected link functionality for IPv6 over the TSCH MAC and a G-MPLS switching sublayer, and standardize the protocols and/or protocol extensions to establish time slots between peers and reserve resources along a path. Active drafts: tools.ietf.org/html/draft-thubert-6tsch-architecture tools.ietf.org/html/draft-wang-6tsch-6tus tools.ietf.org/html/draft-palattella-6tsch-terminology tools.ietf.org/html/draft-watteyne-6tsch-tsch-lln-context tools.ietf.org/html/draft-ohba-6tsch-security

Req posted May 17th Expected Attendance : 60 Number of sessions: 1 Length of session: 2 1/2 hours Agenda TSCH presentation 30mn Work items and mapping with existing work and WGs 1H Charter discussion 1H

Req posted May 17th special request : none ML: (135 members!!!) and archive archive/web/6tsch/current/maillist.html CONFLICTS to avoid INTAREA RTGAREA PCE ROLL CoAP (6MAN COMAN) Note: ROLL will not meet in Berlin

Webinar Announcement

June 10, 2013, 11:30 AM-12:30 PM ET Standardizing the Internet of (Important) Things –“OpenWSN: Standards based enabler for the Industrial Internet” [Xavi] –“IETF 6TSCH: a New Standardization Effort to Combine IPv6 Connectivity with Industrial Performance” [Thomas] Free, open to all (but register), GoToMeeting Hosted by the MEMS Industry Group dex.cfm?pageid=3446#upcoming_webinarhttp:// dex.cfm?pageid=3446#upcoming_webinar

IETF 87

Centralized Routing Requirements Draft

New draft JP Vasseur to become editor –PCE chair, co-author of PCEP –JP will not be with us in Berlin Expected sections (discussion please!) –Req on a protocol to expose links and metrics –Req on a protocol to compute, install, update and delete tracks –Req on a protocol to locate PCE / update location –Reqs on security and trust model (device to PCE) –Suggest changes in PCEP for light transport

draft-watteyne-6tsch-tsch-lln- context-02

draft-watteyne-6tsch-tsch-lln-context v.02 Updates Submitted on 13/05/23 Align tsch-lln-context-draft terminology to the 6tsc- terminology draft (i.e., cells, bounds, track, etc.) – clearly specified in the draft >I-D.palattella-6tsch-terminology incorporated Dominique's comments 3 authors, instead of 1 Ed. and 2 Contributors

draft-wang-6tsch-6tus-01

6tus Layer Specification Ver-01 1.Name Change from “6tus Adaptation Layer” to “6tus Layer” 2.Modify terminologies according to draft-palattella-6tsch-terminology 3.Change the execution procedure of Hard Cell command 4.Typo modification

Execution Procedure of Hard Cell Command PCE A B Hard Cell command Ver.00 PCE A B Hard Cell command Ver.01 Change in specification: 1) tus Opcode Information Element 2) Hard Cell Reservation Request packet 3) Hard Cell Remove Request packet 4)2.6.5 Create hard cell time sequence 5)2.6.6 Delete hard cell time sequence

Label Switching Discussion

Summary Each packet is associated an implicit label (cell) Label switching along a track if set up Ingress point maps packet to Label Switched Track –source node inside the LLN –BBR for a packet coming from outside

Hop limit Problem: –Hop limit not decremented along track Solutions: 1.Do nothing, i.e. tunneling 2.Have explicit hop limit carried inline (RFC3443) 3.Use other information to determine length of track before sending (RFC3034)

Load Balancing Multiple-in-Multiple-out: –Since we have incoming bundle and outgoing –Problem: statistics Solutions: 1.Enforce load balancing (e.g. round robin) 2.Minimize latency and buffering AB A->B 87% channelOffset slotOffset A->B 34% A->B 83%

Logo Challenge!

(1)(2) (3) (4) (5) (6) (7)(8) (2bis)