1 / 26

SC Report for Nov 2016 Session

This report provides an overview of the proceedings and discussions held during the Nov 2016 session of IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs).

solares
Download Presentation

SC Report for Nov 2016 Session

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title:[SC Report for Nov 2016 Session] Date Submitted: [8 Nov 2016] Source: [Patrick Kinney] Company [Kinney Consulting LLC] Address [Chicago area, IL, USA] Voice:[+1.847.960.3715], E-Mail:[pat.kinney@kinneyconsultingllc.org] Re:[SC Report for Nov 2016 Session.] Abstract:[Report for the Nov 2016 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. <Pat Kinney>, <Kinney Consulting LLC>

  2. Instructions for the WG Chair The IEEE-SA strongly recommends that at each WG meeting the chair or a designee: • Show slides #1 through #4 of this presentation • Advise the WG attendees that: • The IEEE’s patent policy is described in Clause 6 of the IEEE-SA Standards Board Bylaws; • Early identification of patent claims which may be essential for the use of standards under development is strongly encouraged; • There may be Essential Patent Claims of which the IEEE is not aware. Additionally, neither the IEEE, the WG, nor the WG chair can ensure the accuracy or completeness of any assurance or whether any such assurance is, in fact, of a Patent Claim that is essential for the use of the standard under development. • Instruct the WG Secretary to record in the minutes of the relevant WG meeting: • That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable) were shown; • That the chair or designee provided an opportunity for participants to identify patent claim(s)/patent application claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which the participant is personally aware and that may be essential for the use of that standard • Any responses that were given, specifically the patent claim(s)/patent application claim(s) and/or the holder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom. • The WG Chair shall ensure that a request is made to any identified holders of potential essential patent claim(s) to complete and submit a Letter of Assurance. • It is recommended that the WG chair review the guidance in IEEE-SA Standards Board Operations Manual 6.3.5 and in FAQs 14 and 15 on inclusion of potential Essential Patent Claims by incorporation or by reference. Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PAR approved by the IEEE-SA Standards Board. <Pat Kinney>, <Kinney Consulting LLC>

  3. Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. • Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2]: • “Shall inform the IEEE (or cause the IEEE to be informed)” of the identity of each “holder of any potential Essential Patent Claims of which they are personally aware” if the claims are owned or controlled by the participant or the entity the participant is from, employed by, or otherwise represents • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) • The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group • Early identification of holders of potential Essential Patent Claims is strongly encouraged • No duty to perform a patent search Slide #1 <Pat Kinney>, <Kinney Consulting LLC>

  4. Patent Related Links All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. Patent Policy is stated in these sources: IEEE-SA Standards Boards Bylaws http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/develop/policies/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/about/sasb/patcom/materials.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/about/sasb/patcom/index.html This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt Slide #2 <Pat Kinney>, <Kinney Consulting LLC>

  5. Call for Potentially Essential Patents • If anyone in this meeting is personally aware of the holder of any patent claims that are potentially essential to implementation of the proposed standard(s) under consideration by this group and that are not already the subject of an Accepted Letter of Assurance: • Either speak up now or • Provide the chair of this group with the identity of the holder(s) of any and all such claims as soon as possible or • Cause an LOA to be submitted Slide #3 <Pat Kinney>, <Kinney Consulting LLC>

  6. 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 focus • Don’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 <Pat Kinney>, <Kinney Consulting LLC>

  7. SCmaintenance/SCwng Officer Chair: Patrick Kinney Vice Chair Ben Rolfe Secretary Slide 7 <Pat Kinney>, <Kinney Consulting LLC>

  8. Chair’s Role http://ieee802.org/Mike_Spring_Article_on_Stds_Process.pdf …the chairperson of the working group is key to what and how fast a standard is produced. The chair of the committee acts as a facilitator with little power to legislate. The chair must be knowledgeable about the subject but also know how a standard may be used by various segments of the industry. A chairperson should be a leader-diplomat-observer, in equal proportions. Also, the chairperson should not be a doer, perfectionist or obstructionist. This is consistent with the view of the chairperson as a skilled leader with strong negotiation skills who delegates. Slide 8 <Pat Kinney>, <Kinney Consulting LLC>

  9. SC Meeting Goals (Agenda 15-16-0758-00) • SC Maintenance Thursday 10 Nov, PM2 • Discuss any issues with published standards • Discuss any issues with the Operations Manual • SC IETF Tuesday 8 Nov, PM2 • Status Update: 6tisch, Core, 6lo, Roll, Detnet, lp-wan, Ace, t2trg • Liaison communications status updates/requests/discussions • SC WNG Wednesday 9 Nov, AM2 • No Presentation scheduled Slide 9 <Pat Kinney>, <Kinney Consulting LLC>

  10. SC Maintenance • Agenda approval • Discussion on any issues with published standards • ? • Discussion on any issues with the Operations Manual • ? Slide 10 <Pat Kinney>, <Kinney Consulting LLC>

  11. SC IETF • Agenda approval • Status Updates • 6tisch • Core • 6lo • Roll • Detnet • lp-wan (bof) • t2trg • Ace • IEEE 802.15 and IETF liaison communications <Pat Kinney>, <Kinney Consulting LLC>

  12. SC IETF 6tisch • draft-ietf-6tisch-6top-protocol-03 • Abstract: enables distributed scheduling in 6TiSCH networks • draft-ietf-6tisch-6top-sf0-02 • Abstract: SF0 dynamically adapts the number of allocated cells between neighbor nodes, based on the amount of currently allocated cells and the neighbor nodes' cell requirements • draft-vucinic-6tisch-minimal-security-00 • Abstract: describes the minimal mechanisms required to support secure initial configuration in a device being added to a 6TiSCH network. The goal of this configuration is to set link-layer keys, and to establish a secure session between each joining node and the JCE who may use that to further configure the joining device • draft-richardson-6tisch-dtsecurity-secure-join-01 • Abstract: securing the join process and making that fit within the constraints of high latency, low throughput and small frame sizes that characterize IEEE802.15.4 TSCH <Pat Kinney>, <Kinney Consulting LLC>

  13. SC IETF Core • draft-ietf-core-coap-tcp-tls–05 • Abstract: CoAP over stream transports just finished WGLC, cap it here. • Objective: Feedback from WGLC, Status update • draft-silverajan-core-coap-protocol-negotiation • Abstract: When multiple transports exist for exchanging CoAP resource representations, this document introduces a way forward for CoAP endpoints to agree upon alternate transport and protocol configurations as well as URIs. • Objective: Present alternatives, obtain WG consensus and reviewers. • draft-ietf-core-object-security • Abstract: This memo defines Object Security of CoAP (OSCOAP), a method for application layer protection of message exchanges with CoAP and CBOR Object Signing (COSE). • Objective: Discuss Updates. Are we ready for an Implementation Draft? • draft-ietf-core-dynlink • Abstract: This document defines conditional observation attributes that work with Link Bindings or with simple CoAP Observe. • Objective: Update on document status. <Pat Kinney>, <Kinney Consulting LLC>

  14. SC IETF Core • draft-ietf-core-interfaces • Abstract: This document defines a set of reusable REST resource design patterns suitable for use in constrained environments. • Objective: Update on document status • draft-pritikin-coap-bootstrap • draft-vanderstok-core-coap-est • Objective: Discuss the use of CoAP and the security options • draft-tiloca-core-multicast-oscoap • Abstract:This document describes a method for application layer protection of messages exchanged with the CoAP in a group communication context, based on Object Security of CoAP (OSCOAP) and the CBOR Object Signing and Encryption (COSE) format. • Objective:present the work, ask for reviewers • draft-cao-core-delegated-observe • Abstract: One node can register an interest on behalf of someone else. • Objective: Present an idea <Pat Kinney>, <Kinney Consulting LLC>

  15. SC IETF Core • draft-groves-coap-webrtcdc • Abstract: Explains how to do CoAP over WebRTC Data Channels. • Objective: Present an idea • draft-ietf-core-senml • draft-groves-core-senml-bto • Abstract: This draft introduces a new base time offset attribute to SenML • Objective: To get the draft adopted. Also to discuss what should happen to the XML and EXI representations (they currently don’t seem to allow extension) • draft-ietf-core-yang-cbor (10) • draft-ietf-core-sid (10) • draft-vanderstok-core-comi (20) • Abstract: This document describes a network management interface for constrained devices, called CoMI. • Objective: Explain merge with CoOL and ask for WG adoption <Pat Kinney>, <Kinney Consulting LLC>

  16. SC IETF Core • draft-thaler-core-redirect • Abstract: Allow a CoAP server to redirect a client to a new URI. The primary use case is to allow a client using multicast CoAP discovery to learn a COAPS endpoint of the server, without the server revealing privacy-sensitive information. This improves security and privacy in environments with untrusted clients. • Objective: Ask for WG support. OCF wants to do this COAP extension either way, but having it be an IETF item is preferred so it isn’t OCF-specific • draft-vanderstok-core-yang-lwm2m–00 • Abstract: This document is an exercise on translating the LWM2M/IPSO Object model to YANG. • Objective: Comments, insights. • draft-jimenez-t2trg-coap-functionality-lwm2m • draft-groves-core-rfc6690up-latest • Abstract: This draft proposes an update to the RFC6690 IANA procedures to allow an organizational pre-fix to be assigned. • Objective: Discuss, possibly adopt <Pat Kinney>, <Kinney Consulting LLC>

  17. SC IETF 6lo • draft-ietf-6lo-nfc-05 • Abstract: IPv6 over NFC - Updates of the draft addressing comments • draft-gomez-6lo-blemesh-02 • Abstract: IPv6 over Bluetooth Low Energy Mesh Networks • Present the updates to the draft and comments from Bluetooth-SIG • draft-hong-6lo-use-cases • Abstract: 6lo Applicability and Use Cases • Updates and comments on the draft • draft-thubert-6lo-rfc6775-update-01 • Abstract: An Update to 6LoWPAN ND • Updates to the draft and Request for adoption • draft-ietf-6lo-privacy-considerations • Abstract: Designating 6LBR for IID Assignment • Updates from WG comments • draft-ietf-6lo-privacy-considerations • Abstract: Packet Expiration Time in 6lo Routing Header • First presentation of the draft • draft-gomez-6lo-optimized-fragmentation-header-00 • Abstract: Optimized 6LoWPAN Fragment Header • First presentation of the draft <Pat Kinney>, <Kinney Consulting LLC>

  18. SC IETF Roll • draft-ietf-roll-useofrplinfo/ • When to use RFC 6553, 6554 and IPv6-in-IPv6 • draft-ietf-roll-routing-dispatch-00 • 6LoWPAN Routing Header • WG: Submitted to IESG for Publication; IESG: AD Evaluation::Revised I-D Needed • draft-ietf-roll-applicability-ami/ • Applicability Statement for the Routing Protocol for Low Power and Lossy Networks (RPL) in AMI Networks • WG: Submitted to IESG for Publication; IESG: AD Evaluation::Revised I-D Needed • draft-satish-roll-aodv-rpl-02.txt • specifies a reactive P2P route discovery mechanism for hop-by-hop routing (storing mode) based on Ad Hoc On-demand Distance Vector Routing (AODV) based RPL protocol • draft-thubert-roll-dao-projection-03 • Root initiated routing state in RPL • draft-jadhav-roll-no-path-dao-ps-01 • No-Path DAO Problem Statement • draft-vanderstok-roll-mpl-forw-select-01 • MPL Forwarder Select (MPLFS) <Pat Kinney>, <Kinney Consulting LLC>

  19. SC IETF Detnet • https://tools.ietf.org/html/draft-ietf-detnet-use-cases-11 • Abstract: Use cases –update • https://tools.ietf.org/html/draft-varga-detnet-service-model-01 • Abstract: DetNet Service Model • http://www.ietf.org/proceedings/97/slides/slides-97-detnet-3 • Abstract: DetNet Data Plane • https://tools.ietf.org/html/draft-zha-detnet-flow-info-model-04 • Abstract: Deterministic Networking Flow Information Model <Pat Kinney>, <Kinney Consulting LLC>

  20. SC IETF lp-wan (bof) • https://datatracker.ietf.org/doc/draft-minaburo-lpwan-gap-analysis • Abstract: LPWAN Gap analysis • https://datatracker.ietf.org/doc/draft-farrell-lpwan-lora-overview/ • Abstract: LoRaWAN overview • https://datatracker.ietf.org/doc/draft-zuniga-lpwan-sigfox-system-description/ • Abstract: Sigfoxsystem description • https://datatracker.ietf.org/doc/draft-ratilainen-lpwan-nb-iot/ • Abstract: NB-IoT characteristics • ? • Abstract: WI-SUN overview <Pat Kinney>, <Kinney Consulting LLC>

  21. SC IETF lp-wan (bof) • https://datatracker.ietf.org/doc/draft-farrell-lpwan-overview/ • Abstract: LPWAN Overview • https://datatracker.ietf.org/doc/draft-toutain-lpwan-ipv6-static-context-hc/ • Abstract: LPWAN Static Context Header Compression (SCHC) for IPv6 and UDP (2 • https://datatracker.ietf.org/doc/draft-toutain-lpwan-coap-static-context-hc/ • Abstract: SCHC for CoAP If Time Allows: • https://datatracker.ietf.org/doc/draft-gomez-lpwan-fragmentation-header/ • Abstract: LPWAN Fragmentation Header • https://datatracker.ietf.org/doc/draft-minaburo-lpwan-rohc-applicability/ • Abstract: RoHC applicability in LPWAN <Pat Kinney>, <Kinney Consulting LLC>

  22. SC IETF Thing-to-Thing (t2trg) • W3C WoT Update by Matthias Kovatsch • draft-irtf-t2trg-iot-seccons-00 • Abstract: Security Considerations in the IP-based Internet of Things • draft-keranen-t2trg-rest-iot • Abstract: RESTful Design for Internet of Things Systems • draft-koster-t2trg-hsml • Abstract: Media Types for Hypertext Sensor Markup • draft-hartke-t2trg-coral • Abstract: The Constrained RESTful Application Language (CoRAL) • CoMI/YANG interaction model for IoT by Alexander Pelov <Pat Kinney>, <Kinney Consulting LLC>

  23. SC IETF Ace • draft-ietf-ace-oauth-authz-04 • Abstract: Authorization using OAuth 2.0 (ACE) • draft-ietf-ace-actors-04 • Abstract: An architecture for authorization in constrained environments • draft-ietf-ace-cbor-web-token-01 • Abstract: CBOR Web Token (CWT) • draft-somaraju-ace-multicast/ • Abstract: Security for Low-Latency Group Communication • draft-seitz-ace-ocsoap-profile/ • Abstract: OSCOAP profile of ACE • draft-selander-ace-cose-ecdhe/ • Abstract: Ephemeral Diffie-Hellman Over COSE • draft-gerdes-ace-dtls-authorize/ • Abstract: DTLS Profile for ACE • draft-navas-ace-secure-time-synchronization/ • Abstract: Lightweight Authenticated Time (LATe) Synchronization <Pat Kinney>, <Kinney Consulting LLC>

  24. SC IETF IEEE 802.15 and IETF liaison communications • lp-wan: SC IETF can identify solutions to numerous problems stated for lp-wan. SC IETF could produce a document describing the behaviors in 802.15.4 (LECIM) and 802.15.9 (KMP) that address the noted problems. • Status: no change • Responsible: Kinney • 6lo: SC IETF could identify header compression methods that apply to IP but could be extended to MAC and PHY by IEEE 802.15. • Status: no change • Responsible: <Pat Kinney>, <Kinney Consulting LLC>

  25. SC IETF IEEE 802.15 and IETF liaison communications • Effort to develop the concept of reduction of over-the-air header sizes for lp-wan type packets • Read “RoHC applicability in LPWAN draft-minaburo-lpwan-rohc-applicability-00” • Next meeting will discuss this option • Work with IETF lpwan BOF for a method of LoHC that works with 802.15.4 and then show results <Pat Kinney>, <Kinney Consulting LLC>

  26. SC maintenance motion Move that IEEE 802.15 WG approve the IEEE 802.15 WG Operations Manual document 15-10-0235-18. Moved by Pat Kinney; Seconded by Slide 28 <Pat Kinney>, <Kinney Consulting LLC>

More Related