IEEE P802.15 SC Report Jan. 2017 Session

IEEE P802.15 SC Report Jan. 2017 Session
Slide Note
Embed
Share

Submission Slide 1 and 2 along with instructions for the WG chair regarding the IEEE-SA patent policy. Participants' obligations under the IEEE-SA Patent Policy are outlined, emphasizing the importance of early identification of potential Essential Patent Claims.

  • IEEE
  • SC Report
  • WG Chair
  • Patent Policy
  • Obligations

Uploaded on Apr 04, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. <Jan 2017> doc.: <15-17-0047-01-0mag> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [SC Report for Jan 2017 Session] Date Submitted: [19 Jan 2017] 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 Jan 2017 Session.] Abstract: [Report for the Jan 2017 Session] Purpose: [] Notice: 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. This document has been prepared to assist the IEEE P802.15. It is offered as a basis for Submission Slide 1 <Pat Kinney>, <Kinney Consulting LLC>

  2. Instructions for the WG Chair <Jan 2017> doc.: <15-17-0047-01-0mag> 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. Submission Slide 2 <Pat Kinney>, <Kinney Consulting LLC>

  3. <Jan 2017> doc.: <15-17-0047-01-0mag> 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 Submission Slide 3 <Pat Kinney>, <Kinney Consulting LLC> Slide #1

  4. <Jan 2017> doc.: <15-17-0047-01-0mag> 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 Submission Slide 4 <Pat Kinney>, <Kinney Consulting LLC> Slide #2

  5. <Jan 2017> doc.: <15-17-0047-01-0mag> 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 Submission Slide 5 <Pat Kinney>, <Kinney Consulting LLC> Slide #3

  6. <Jan 2017> doc.: <15-17-0047-01-0mag> 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. Submission Slide 6 <Pat Kinney>, <Kinney Consulting LLC> Slide #4

  7. <Jan 2017> doc.: <15-17-0047-01-0mag> SCmaintenance/SCwng Officer Chair: Patrick Kinney Vice Chair Ben Rolfe Secretary Submission Slide 7 Slide 7 <Pat Kinney>, <Kinney Consulting LLC>

  8. <Jan 2017> doc.: <15-17-0047-01-0mag> 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. Submission Slide 8 Slide 8 <Pat Kinney>, <Kinney Consulting LLC>

  9. <Jan 2017> doc.: <15-17-0047-01-0mag> SC Meeting Goals (Agenda 15-17-0024-00) SC Maintenance Thursday 19 Jan, PM1 Discuss any issues with published standards Discuss any issues with the Operations Manual SC IETF Tuesday 17 Jan, PM2 Status Update: 6tisch, Core, 6lo, Roll, Detnet, lp-wan, Ace, t2trg Liaison communications status updates/requests/discussions SC WNG Wednesday 18 Jan, AM2 No Presentation scheduled Submission Slide 9 Slide 9 <Pat Kinney>, <Kinney Consulting LLC>

  10. <Jan 2017> doc.: <15-17-0047-01-0mag> SC Maintenance Agenda approval Discussion on any issues with published standards ? Discussion on any issues with the Operations Manual ? Submission Slide 10 Slide 10 <Pat Kinney>, <Kinney Consulting LLC>

  11. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Agenda approval Status Updates 6tisch Core 6lo Roll Detnet lp-wan t2trg Ace IEEE 802.15 and IETF liaison communications Submission Slide 11 <Pat Kinney>, <Kinney Consulting LLC>

  12. <Jan 2017> doc.: <15-17-0047-01-0mag> 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-ietf-6tisch-minimal-17 Minimal 6TiSCH Configuration Waiting for Writeup:Revised I-D Needed for 23 days Submitted to IESG for Publication: 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-ietf-6tisch-dtsecurity-secure-join-00 6tisch Secure Join protocol 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 Slide 12 Submission <Pat Kinney>, <Kinney Consulting LLC>

  13. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Core (Constrained RESTful Environments) 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-ietf-core-http-mapping-17 Guidelines for HTTP-to-CoAP Mapping Implementation 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-01 Abstract: This document defines conditional observation attributes that work with Link Bindings or with simple CoAP Observe. Objective: Update on document status. Submission Slide 13 <Pat Kinney>, <Kinney Consulting LLC>

  14. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Core (Constrained RESTful Environments) draft-ietf-core-interfaces-07 Abstract: This document defines a set of reusable REST resource design patterns suitable for use in constrained environments. Objective: Update on document status draft-ietf-core-senml-04 Media Types for Sensor Measurement Lists (SenML) draft-ietf-core-yang-cbor-03 BOR Encoding of Data Modeled with YANG draft-ietf-core-resource-directory-09 CoRE Resource Directory Submission Slide 14 <Pat Kinney>, <Kinney Consulting LLC>

  15. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF 6lo draft-ietf-6lo-nfc-05 Abstract: IPv6 over NFC - Updates of the draft addressing comments draft-6lo-blemesh-00 IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP draft-ietf-6lo-use-cases Abstract: 6lo Applicability and Use Cases Updates and comments on the draft draft-ietf-6lo-rfc6775-update Abstract: An Update to 6LoWPAN ND Updates to the draft and Request for adoption draft-ietf-6lo-privacy-considerations-04 Abstract: Designating 6LBR for IID Assignment Updates from WG comments draft-ietf-6lo-dect-ule Transmission of IPv6 Packets over DECT Ultra Low Energy draft-ietf-6lo-nfc Transmission of IPv6 Packets over Near Field Communication draft-ietf-6lo-dispatch-iana-registry-07 6lowpan ESC Dispatch Code Points and Guidelines Submission Slide 15 <Pat Kinney>, <Kinney Consulting LLC>

  16. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF 6lo RFC 7973 (was draft-ietf-6lo-ethertype-request) Assignment of an Ethertype for IPv6 with Low-Power Wireless Personal Area Network (LoWPAN) Encapsulation draft-thubert-6lo-forwarding-fragments-04 LLN Fragment Forwarding and Recovery draft-ietf-6lo-6lobac-06 Transmission of IPv6 over MS/TP Networks Submission Slide 16 <Pat Kinney>, <Kinney Consulting LLC>

  17. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Roll draft-ietf-roll-useofrplinfo-10 When to use RFC 6553, 6554 and IPv6-in-IPv6 draft-ietf-roll-routing-dispatch-05 6LoWPAN Routing Header WG: Submitted to IESG for Publication; IESG: AD Evaluation::Revised I-D Needed draft-ietf-roll-dao-projection-00 Root initiated routing state in RPL draft-ietf-roll-aodv-rpl-00 Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs) draft-ietf-roll-mpl-forw-select-00 MPL Forwarder Select (MPLFS) Submission Slide 17 <Pat Kinney>, <Kinney Consulting LLC>

  18. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Detnet draft-ietf-detnet-architecture-00 Deterministic Networking Architecture draft-ietf-detnet-dp-alt-00 DetNet Data Plane Protocol and Solution Alternatives draft-ietf-detnet-problem-statement-01 Deterministic Networking Problem Statement draft-ietf-detnet-use-cases-11 Deterministic Networking Use Cases Submission Slide 18 <Pat Kinney>, <Kinney Consulting LLC>

  19. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF lp-wan draft-ietf-lpwan-coap-static-context-hc-00 6LPWA Static Context Header Compression (SCHC) for CoAP draft-ietf-lpwan-ipv6-static-context-hc-00 LPWAN Static Context Header Compression (SCHC) for IPv6 and UDP draft-ietf-lpwan-overview-00 LPWAN Overview draft-farrell-lpwan-lora-overview-01 LoRaWAN Overview draft-zuniga-lpwan-sigfox-system-description-01 SIGFOX System Description Submission Slide 19 <Pat Kinney>, <Kinney Consulting LLC>

  20. <Jan 2017> doc.: <15-17-0047-01-0mag> SC IETF Thing-to-Thing (t2trg) draft-irtf-t2trg-iot-seccons-00 Abstract: Security Considerations in the IP-based Internet of Things draft-keranen-t2trg-rest-iot-03 Abstract: RESTful Design for Internet of Things Systems draft-koster-t2trg-hsml-00 Abstract: Media Types for Hypertext Sensor Markup draft-hartke-t2trg-coral-01 Abstract: The Constrained RESTful Application Language (CoRAL) Submission Slide 20 <Pat Kinney>, <Kinney Consulting LLC>

  21. <Jan 2017> doc.: <15-17-0047-01-0mag> 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-02 Abstract: CBOR Web Token (CWT) Submission Slide 21 <Pat Kinney>, <Kinney Consulting LLC>

  22. <Jan 2017> doc.: <15-17-0047-01-0mag> 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: IG LPWA 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: Submission Slide 22 <Pat Kinney>, <Kinney Consulting LLC>

  23. <Jan 2017> doc.: <15-17-0047-01-0mag> 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 Submission Slide 25 Slide 25 <Pat Kinney>, <Kinney Consulting LLC>

Related


More Related Content