1 / 11

Participants, Patents, and Duty to Inform

This slide set provides guidelines for participants in IEEE-SA meetings regarding their obligations under the IEEE-SA Patent Policy. It includes information on identifying potential patent claims, submitting Letters of Assurance, and following antitrust and competition laws.

mpropp
Download Presentation

Participants, Patents, and Duty to Inform

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. 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

  2. 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

  3. 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

  4. 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

  5. Note • Red or Black text indicates new material • Blue text indicates previous material • AI == Action Item • Action Items are captured in-line with notes on the slides

  6. Agenda • Administrative • Guidelines • Topics • Discuss comments on 802.1Xck to re-design for NMDA • FYI on WG Last call in IETF TICTOC for IEEE Std 1588-2008 YANG • AoB • Workshop on Sunday Jan 28 2018 with ITU-T • Attendees

  7. Administrative • Website • http://ieee802dot1.wpengine.com/yangsters/ • Mailing List • STDS-802-YANG@listserv.ieee.org • Open Group • Mailing list is ready! • Meeting Time • Bridge: join.me/ieee802.1 • Wednesday, September 27, 2017 6:00 AM (PDT) – this Call • Wednesday, October 25, 2017 6:00 AM (PDT) • Plan for future meeting – • Wednesday, November 29, 2017 6:00 AM (PST) • Wednesday, January 31, 2018 6:00 AM (PST) – follow-up after IEEE plenary (or have a meeting during the plenary) • AI: Scott to send out agenda and reminder a week before the next YANGsters meeting • Reminder: • Daylight Savings Time ends in Europe on 29 October 2017 and in the USA/Canada on 5 November 2017

  8. Guidelines • http://ieee802dot1.wpengine.com/yangsters/yangsters-guidelines/ • Area created, time needed to populate • Duane sent info about the IETF NETMOD FAQ which should be included as background information • Structure • Example: How the IEEE YANG modules are organized • Example: Use of IETF NMDA • Coding • Example: Use of IEEE comment resolution process • Example: How revision dates are used • Naming • Example: naming conventions • Tooling • Example: repository usage, yang validation tools • AI (all): Generation of material for guidelines

  9. Topics • Discuss comments on 802.1Xck to re-design for NMDA • Not Discussed – Deferred • FYI on WG Last call in IETF TICTOC for IEEE Std 1588-2008 YANG • Information about transferring the YANG work from the IETF to IEEE 1588 • Appendix A Transferring YANG Work to IEEE 1588 WG (Informational) • This appendix describes a future plan to transition responsibility for IEEE 1588 YANG modules from the IETF TICTOC Working Group (WG) to the IEEE 1588 WG, which develops the time synchronization technology that the YANG modules are designed to manage. • https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588v2-yang/?include_text=1 • Discussed the difference between IETF Trust and the IEEE as it applies to who owns the IP of the work

  10. AoB • Discussed the proposal to have a workshop on Sunday January 28, 2018 with ITU-T YANG experts • Main goal is to discuss how to support linking the Model-driven YANG models (auto-generated from UML) and the hand-crafted YANG models of the IETF and IEEE

  11. Attendees • Meeting Attendees: • Scott Mansfield (Ericsson) • Rodney Cummings (NI)

More Related