1 / 12

Participants, Patents, and Duty to Inform

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 ]:

kellyrmartin
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. Agenda • YANG Recap from IEEE 802 Plenary • 5-10 November 2017 Orlando • Topics • Is YANG a compelling use case for 802.1/802.3 to join the IEEE open source trial? • YANG work in other SDOs • Guidelines • Contributions needed • Administrative • Next call scheduling • AoB • Workshops and meetings with ITU-T SG-15 in January 2018 • Attendees

  6. YANG Recap from November Plenary • Reference • http://www.ieee802.org/1/files/public/minutes/2017-11-midweek-plenary-slides.pdf • YANG for Ethertypes • Conclusion? • Current Workload (slide 12)

  7. Topic 1 • Is YANG a compelling use case for 802.1/802.3 to join the IEEE open source trial? • Background • Pilot Questionnaire • https://mentor.ieee.org/802-ec/dcn/17/ec-17-0172-00-00EC-ieee-sa-update-on-open-source-activity.pdf • https://mentor.ieee.org/802-ec/dcn/17/ec-17-0103-00-00SA-ieee-open-source-offering.pdf • Action: • Scott to fill out Pilot Query based on discussion and circulate for consensus

  8. Topic 2 • YANG in other SDOs • Harmonization between tool generated YANG (based on UML) and hand-crafted YANG • IETF • IETF 100 Netmod Session • https://datatracker.ietf.org/meeting/100/materials/slides-100-netmod-sessb-intro-charter-wg-status/ • MEF • Published YANG modules for MEF 6.2 and MEF 10.3 EVC Services • Focused on Service Configuration and Activation • ITU-T • SG-15 Question 14 working on YANG based on G.8052 (Ethernet Equipment) • Interim meeting Week of 2 December 2017 • Coordination Workshop with IEEE in January • IISOMI Continues to meet • Automated UML to YANG tooling and discussions on common models

  9. Guidelines Need Contributions / Discussion • http://1.ieee802.org/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

  10. Administrative • Website • http://1.ieee802.org/yangsters/ • Host name and domain name changed • Mailing List • STDS-802-YANG@listserv.ieee.org • Meeting Time • Bridge: join.me/ieee802.1 • Wednesday, November 29, 2017 6:00 AM (US-Pacific) – this Call • Plan for future meeting – • Wednesday, November 29, 2017 6:00 AM (US-Pacific) • Wednesday, January 31, 2018 6:00 AM (US-Pacific) – follow-up after IEEE plenary (or have a meeting during the plenary) • Wednesday, December 27, 2017 6:00 AM (US-Pacific) • Last Wednesday of every month at 0600 US-Pacific • Reminder: • Regardless of daylight savings time, the time of the call is 0600 AM US-Pacific time

  11. AoB • Workshops with ITU-T • Joint IEEE 802 and ITU-T Study Group 15 workshop “Building Tomorrow’s Networks” • https://www.itu.int/en/ITU-T/Workshops-and-Seminars/20180127/Pages/default.aspx • 27 January 2018, Geneva • Q14/15 interim meeting inviting experts from IEEE 802.1 and IEEE 802.3 YANG projects to discuss mechanisms to ensure alignment of the IEEE YANG work • https://www.itu.int/net/itu-t/lists/rgmdetails.aspx?id=9088&Group=15 • Next MEF meeting is last week of January 2018 in Singapore

  12. Attendees • Meeting Attendees: • Duane Remein • Glenn Parsons • Jessy Rouyer • Johannes Specht • Lihao Chen • Ludwig Pauwels • Peter Jones • Rob Wilton • Rodney Cummings • Scott Mansfield

More Related