Participants, Patents, and Duty to Inform

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 • Administrative • Next call scheduling • Guidelines • Examples from Duane that would help consistency between 802 IEEE modules • Topics • Ludwig 802.1Xck and impact on YANG work outside of 802 and/or IEEE • AoB • Workshops and meetings with ITU-T SG-15 in January 2018 • Attendees

6. Administrative • Website • http://ieee802dot1.wpengine.com/yangsters/ • Mailing List • STDS-802-YANG@listserv.ieee.org • Meeting Time • Bridge: join.me/ieee802.1 • Wednesday, October 25, 2017 6:00 AM (PDT) – this Call • 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) • (Need to request more slots at the 802.1 plenary meeting in Orlando) • Reminder: • Daylight Savings Time ends in Europe on 29 October 2017 and in the USA/Canada on 5 November 2017

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

8. Examples from Duane • In 802.3cf we are including the modules in the actual 802.3.2 draft standard. Some authors use tabs for indenting other use some number of spaces (2, or 3, or 4). Line length limit is inconsistent and therefore some lines wrapped in the draft causing the draft to be unreadable (imho). This is most noticeable in string arguments, which can get quite long. One thing I would suggest is that we remove all tab characters, enforce a consistent indenting size and limit line length where possible (not paths). • Another example is the use of the units keyword. Some authors will use quotes around the units and some will not. • Is            units “ns”; == units ns;     ?? The reader is left wondering. • I have similar issues with other keywords including: default, config, if-feature, type, etc.  I know these issues are somewhat picky points but I think a consistent style makes the code much more readable and more likely to be properly “debugged” during the review process.

9. Examples from Duane • Action Item for Scott to: • Gather information and pointers about the IETF formatting guidelines • Look into what checks the pyang tooling does when in IEEE mode • Discuss with Pete Anslow about the Framemaker template and determine if there is a way to format YANG so it fits nicely in the IEEE document template

10. Topics • Ludwig Presentation • Support of P802.1Xck, and more, on non-IEEE 802-specified interfaces • Issue related to interface modeling in cases where some IEEE specifications apply but not all IEEE specifications apply • Three options were given in the presentation. • Rob Wilton pointed out that this is a problem under study in the IETF • https://datatracker.ietf.org/doc/draft-wilton-netmod-interface-properties/ • Interface Properties for YANG Data Models • Will be discussed at IETF 100

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 • Johannas Specht • Ludwig Pauwels • Peter Jones • Rodney Cummings • Jessy Rouyer • Rob Wilton • Scott Mansfield