<Pat Kinney>, <Kinney Consulting LLC> - PowerPoint Presentation

Slide1

<Pat Kinney>, <Kinney Consulting LLC>

Slide 1

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Submission Title: [IG 6tisch Opening Report for May 2016 Session] Date Submitted: [15 May 2016] Source: [Patrick Kinney] Company [Kinney Consulting LLC]Address [Chicago area, IL, USA]Voice:[+1.847.960.3715], E-Mail:[pat.kinney@ieee.org] Re: [IG 6tisch Opening& Closing Report for May 2016 Session.] Abstract: [Opening Report for the May Session]Purpose: []Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

<May 2016>

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 2Slide 2IG 6T Meeting Goals (Agenda 15-16-0-00)Monday 16 May, PM2: 6tisch issues discussionCall for adoption for draft-wang-6tisch-6top-protocol-00Call for adoption for draft-dujovne-6tisch-6top-sf0-01Security – started again6tisch-802.15 liaison discussion

Administrative ItemsRequired noticesIEEE Code of Ethicshttp://www.ieee.org/about/corporate/governance/p7-8.html IEEE Standards Association (IEEE-SA) Affiliation FAQhttp://standards.ieee.org/faqs/affiliation.html Antitrust and Competition Policyhttp://standards.ieee.org/resources/antitrust-guidelines.pdf IEEE-SA Patent Committee FAQ & Patent slides

http://standards.ieee.org/board/pat/faq.pdfhttp://standards.ieee.org/board/pat/pat-slideset.ppt Letter of Assurance Formhttp://standards.ieee.org/board/pat/loa.pdf Chair and Secretary requestChair is Pat Kinney (Kinney Consulting)<Pat Kinney>, <Kinney Consulting LLC><May 2016>

Slide 3

<May 2016><Pat Kinney>, <Kinney Consulting LLC>Other Guidelines for IEEE WG Meetings

All IEEE-SA standards meetings shall be conducted in compliance with all applicable laws, including antitrust and competition laws. Don’t discuss the interpretation, validity, or essentiality of patents/patent claims. Don’t discuss specific license rates, terms, or conditions.Relative costs, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. Technical considerations remain primary focusDon’t discuss or engage in the fixing of product prices, allocation of customers, or division of sales markets.Don’t discuss the status or substance of ongoing or threatened litigation.Don’t be silent if inappropriate topics are discussed … do formally object.

--------------------------------------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.Slide 4

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 5Slide 56TISCH Issues DiscussionCall for 6tisch WG adoption of 6P and SF0 draftsdraft-wang-6tisch-6top-protocol-00draft-dujovne-6tisch-6top-sf0-01Recharter: adding Security matters to 6tisch802.15 liaison discussion

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 6Slide 66TISCH Issues DiscussionCall for 6tisch WG adoption of draft-wang-6tisch-6top-protocol-00AbstractThis document defines the 6top Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes in a 6TiSCH network to add/delete TSCH cells to one another. 6P is part of the 6TiSCH Operation Sublayer (6top), the next higher layer of the IEEE802.15.4 TSCH medium access control layer. The 6top Scheduling Function (SF) decides when to add/delete cells, and triggers 6P transactions. Several SFs can be defined, each identified by a different 6top Scheduling Function Identifier (SFID). This document lists the requirements for an SF, but leaves the definition of the SF out of scope. Different SFs are expected to be defined in future companion specifications.

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 7Slide 76TISCH Issues DiscussionCall for 6tisch WG adoption of draft-dujovne-6tisch-6top-sf0-01AbstractThis document defines a 6top Scheduling Function called "Scheduling Function Zero" (SF0). SF0 dynamically adapts the number of reserved cells between neighbor nodes, based on the currently allocated bandwidth and the neighbor nodes' requirements. Neighbor nodes negotiate in a distributed neighbor-to-neighbor basis the cell(s) to be added/deleted. SF0 uses the 6P signaling messages to add/delete cells in the schedule. Some basic rules for deciding when to add/delete cells and for selecting the cells to be added/deleted within the schedule are also provided.

Recharter – SecurityObject Security of COAP for 6tischJoin Coordination

EntityJOIN REQUEST / ACK

Secure configuration of K2 on JN Rate limitation for DoS mitigation (e.g. CoAP forward proxy)Mutual authentication of JN and JCE based on pre-established node credentialsEstablishment of security context (optional)Secure provisioning of network credentialsJoining Node

POST /join

CONFIG K2 / ACK

Join

Assistant

[

Intermediate

]

2.04 (Changed)

POST /6top/

…

2.04 (Changed)

OSCOAP / EDHOC

OSCOAP

start/end states (and costs) of 3 options

PSK

start state:each mote is pre-configured with a key, the same key is written in the JCE together with its MAC addressend state:the JCE has authenticated the mote; the mote has authenticated the JCEthe JCE has installed (through secure session with the JN) key K2. This key is then used for link-layer AUTH+ENV CCM*the PSK enables a session between the node and the JCE. The JCE uses that session to send commands to the mote to (1) rotate K2, (2) change PSKCost:4 packetsMemory: don’t knowProtocols:OSCOAP, EDHOC

Raw Public Key

start state:

???

end state:

???

Cost:

???

Protocols:

???

certs

start state:

???

end state:

???

Cost:

???

Protocols:

???

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 10Slide 106TISCH Issues Discussion – 802.15 liaison discussionAt our last meeting in Macau, it was agreed that the IG 6T should increase its scope to include all IETF matters for IEEE 802.15. Additionally, it would be appropriate to change the Interest Group to a Standing Committee.Proposed changes to Operations Manual7.8 IETF Liaison Standing Committee (SC IETF) 7.8.1 Function7.8.1.1 The SC IETF is an informal liaison of IEEE 802.15 with IETF to provide information about standards and ongoing activities within IEEE 802.15 to IETF, and to provide information on relevant IETF activities to the IEEE 802.15. 7.8.1.2 An additional function of the SC IETF is to coordinate joint IEEE 802.15 & IETF efforts to implement system and device architectures and interfaces to support an application space.7.8.2 OperationThe SC IETF shall meet at least once during every session and discuss relevant ongoing IETF activities and formulate any messages intended to be sent to the IETF. No messages to the IETF may be sent without approval of the IEEE 802.15 WG.

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 11Slide 11Meeting AccomplishmentsReviewed the call for adoption of two 6tisch draftsReviewed the security discussion in 6tischDiscussed the change of IG 6T to IETF SC along with a proposed charter

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 12Slide 12IETF 6TISCH Mailing List Information6tisch@ietf.orghttps://www.ietf.org/mailman/listinfo/6tisch

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 13Slide 13IETF 6TISCH call informationNext 3 dates: 10-Oct 08:00 PDT, 24-Oct 08:00 PDT, 07-Nov 08:00 PDTMeeting Number: 206 802 913Meeting Password: sixtusTo start the online meeting:1. Go to: https://ciscosales.webex.com/ciscosales/j.php?ED=219615007&UID=481905242&PW=NZTRkNDAwOTE1&RT=MiMyMw%3D%3D2. Log in to your account.3. Click "Start Now”4. Follow the instructions that appear on your screen5. Note: Local access numbers for the following areas are:San Jose/Milpitas (408) area: 525-6800RTP (919) area: 392-3330

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 14Slide 14IG 6TISCH reflector informationstds-802-15-ig6t@listserv.ieee.orghttp://grouper.ieee.org/groups/802/15/pub/Subscribe.html

<May 2016>

<Pat Kinney>, <Kinney Consulting LLC>

Slide 15Slide 15IETF 6tisch Working Group Scope6tisch Goal: The 6tisch Working Group is focused upon enabling IPv6 over the TSCH mode of the IEEE802.15.4e standard. The extent of the problem space for the WG is one or more Low Power and Lossy Networks (LLNs), eventually federated through a common backbone link via one or more LLN Border Routers (LBRs).Work Item 1: Produce "6TiSCH architecture" to describe the design of 6TiSCH networks. This document will highlight the different architectural blocks and signaling flows, including the operation of the network in the presence of multiple LBRs. Initially, the document will focus on distributed routing operation over a static TSCH schedule.Work Item 2: Produce an Information Model containing the management requirements of a 6TiSCH node. This includes describing how an entity can manage the TSCH schedule on a 6TiSCH node, and query timeslot information from that node. A data model mapping for an existing protocol (such as Concise Binary Object Representation (CBOR) over the Constrained Application Protocol (CoAP)) will be provided.Work Item 3: Produce "Minimal 6TiSCH Configuration" defining how to build a 6TiSCH network using the Routing Protocol for LLNs (RPL) and a static TSCH schedule. It is expected that RPL and the Objective Function 0 (OF0) will be reused as-is.