IEEE 802.1 OmniRAN TG December 12 th , 2017 Conference Call

1. IEEE 802.1 OmniRAN TGDecember 12th, 2017 Conference Call 2016-12-12Max Riegel, Nokia Bell Labs (TG Chair)

2. Tuesday, December 12th, 2017 at 09:30-11:00am ET Join WebEx meeting https://nokiameetings.webex.com/nokiameetings/j.php?MTID=m25067da6d9a2beb2555f14ae8905a06e Meeting number: 956 211 849 Meeting password: OmniRAN Join by phone +19724459814 US Dallas +442036087616 UK London +861084056120, +861058965333 China Beijing Access code: 956 211 849 Global call-in numbers https://nokiameetings.webex.com/nokiameetings/globalcallin.php?serviceType=MC&ED=533523267&tollFree=0 Conference Call

3. Review of minutes Reports Editorial review results of P802.1CF-D0.7 Corrections going into P802.1CF-D1.0 for WG ballot WG ballot plan Agenda proposal and plan for January 802.1 interim in Geneva, CH AOB Next meeting Agenda proposal

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

5. 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 Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 • IEEE-SA Standards Board Operations Manualhttp://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

6. 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 Call for Potentially Essential Patents

7. All participation in IEEE 802 Working Group meetings is on an individual basis Participants in the IEEE standards development individual process shall act based on their qualifications and experience. (https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1) IEEE 802 Working Group membership is by individual; “Working Group members shall participate in the consensus process in a manner consistent with their professional expert opinion as individuals, and not as organizational representatives”. (http://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf section 4.2.1) You have an obligation to act and vote as an individual and not under the direction of any other individual or group. Your obligation to act and vote as an individual applies in all cases, regardless of any external commitments, agreements, contracts, or orders. You shall not direct the actions or votes of any other member of an IEEE 802 Working Group or retaliate against any other member for their actions or votes within IEEE 802 Working Group meetings, see https://standards.ieee.org/develop/policies/bylaws/sb_bylaws.pdf section 5.2.1.3 and http://ieee802.org/PNP/approved/IEEE_802_WG_PandP_v19.pdf section 3.4.1, list item x By participating in IEEE 802 meetings, you accept these requirements. If you do not agree to these policies then you shall not participate. Participation in IEEE 802 Meetings

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

9. Link to IEEE Disclosure of Affiliation http://standards.ieee.org/faqs/affiliationFAQ.html Links to IEEE Antitrust Guidelines http://standards.ieee.org/resources/antitrust-guidelines.pdf Link to IEEE Code of Ethics http://www.ieee.org/web/membership/ethics/code_ethics.html Link to IEEE Patent Policy http://standards.ieee.org/board/pat/pat-slideset.ppt Resources – URLs

10. Business#1 • Call Meeting to Order • Meeting called to order by chair at 09:30 AM ET • Minutes taker: • Hao is taking notes • Roll Call

11. 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 Nothing brought up. Call for Potentially Essential Patents

12. Review of minutes Postponed to January F2F meeting Reports .. Editorial review results of P802.1CF-D0.7 Included into this slideset on slide 14 and 15 Corrections going into P802.1CF-D1.0 for WG ballot Conclusion on editorial review 6 contributions to correct specific attributes subsections WG ballot plan Agenda proposal and plan for January 802.1 interim in Geneva, CH AOB Next meeting Agenda

13. Business #2 • Review of minutes • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0096-00-00TG-dec-5th-confcall-minutes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0094-00-00TG-nov-28th-confcall-notes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0091-00-00TG-nov-2017-f2f-meeting-minutes.docx • Review postponed for the upcoming F2F meeting • Reports • Walter briefly reported about the IEEE SA awards ceremony in Piscataway, where 802.11 received an award for ‘emerging technology’. • Editorial review results of P802.1CF-D0.7 • Editorial review comments listed on the following 2 slides. • Shortly introduced the comments to the editor with going through the list and pointing to the demanded modifications in the document. • Implementation will be performed off-line through the editor.

14. Editorial review comments #1 • L463: replace chapter 4.2 by text given in https://mentor.ieee.org/omniran/dcn/17/omniran-17-0072-00-CF00-chap-4-2-conventions-amendment.docx • L1152: insert text as highlighted in https://mentor.ieee.org/omniran/dcn/17/omniran-17-0073-00-CF00-chap-7-1-terminology-amendment.docx • L1496: insert text as highlighted in https://mentor.ieee.org/omniran/dcn/17/omniran-17-0074-00-CF00-chap-7-2-figure-amendment.docx • L2254: should be itemized and indented; ‘TT traffic’ is a further item aside of BE traffic and RC traffic • L2297: figure 39 is not displayed properly. • L2299: The text ‘Streams …’ is a continuation of the text above the figure and requires indentation as the text flow above the figure. If challenging, the figure 39 could be moved to the end of the text. • L2368: should be ‘and guides fault diagnosis and maintenance’ • L2392: Figure title should be kept on same page as figure. • L2447: ‘E.g.’ belongs to the begin of the line • L2460: ‘E.g.’ belongs to the begin of the line • L2663: Text belongs to the indented text of ‘fully centralized TSN configuration model’ above and should be copied directly into line 2659.. • L2681: ‘ID’ changed to ‘ServiceFlow-ID’ • L2682: there is one new paragraph from DCN-0068-03, as follows, missing between L2681 and L2682. ”For time sensitive networking, service flows are denoted as ‘Streams’ starting at a ‘Talker’ and ending at a ‘Listener’. Talker and listener are end stations in the notation of IEEE 802 networking and are represented by Terminal and Access Router in this specification.”

15. Editorial review comments #2 • L2738: should be ‘QoS policy control should allow for both intserv, and diffserv as well as TSN QoS models.’ • L2758: should be ‘Usage limits (time, volume, delay)’ • L2781: the texts in chapter 7.6.7.1 is not up-to-date. (although figure 54 is good) Refer to DCN-0068-03 for inclusion the revisions. • L2800: the texts in chapter 7.6.7.2 is not up-to-date. • L2812: part of Figure 55 is not displayed. • L2841: figure 57 is not shown in complete. • L2854: figure 58 is not shown in complete. So is figure 59. • L2864: ‘This section’ should be ‘The following section’ • L3250: left part of figure 63 should be deleted. (keep the right part only) • L3508: Insert the introductory text for ‘8. Network softwarization functions’ as given by https://mentor.ieee.org/omniran/dcn/17/omniran-17-0075-01-CF00-chap-8-intro-amendment.docx • L3512: change ‘in sharing’ through ‘to provide’ • L3539: Figure 70 is cropped to its left side. Reduce size of picture to make it fully appearing on the page. • L3548: figure 72 is wrong, the correct one is the figure 8-4 in DCN0079-04 • L3569: Figure 77 is outdated; please insert instead figure 8-9 of https://mentor.ieee.org/omniran/dcn/17/omniran-17-0079-04-CF00-chap-8-1-information-model.docx • L3570: chapter 8.1.2 is not included: Refer to DCN-0079-04 for more details. • L3610: ‘Figure 74’ should reference to ‘Figure 78’ above. • L4344: Remove line; no PICS proforma in this document as explained in 5. Conformence • L4345: Remove Annex A, as there is no annex

16. Business #3 • Corrections going into P802.1CF-D1.0 for WG ballot • Walter will send out draft for review to Hao and Max before uploading the document to the private 802.1 filespace. • Hao and Max will respond to Walter through email with final hints for editorial clean-up, if necessary. • Corrections of the specific attributes sub-sections in chapter 7.2 – 7.7 • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0098-00-CF00-chap-7-2-5-nds-specific-attributes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0099-00-CF00-chap-7-3-5-association-specific-attributes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0100-00-CF00-chap-7-4-5-authentication-specific-attributes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0101-00-CF00-chap-7-5-5-datapath-specific-attributes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0102-00-CF00-chap-7-6-5-qos-policy-specific-attributes.docx • https://mentor.ieee.org/omniran/dcn/17/omniran-17-0103-00-CF00-chap-7-7-5-accounting-specific-attributes.docx • Agreed to be included into D1.0 by Walter.

17. Business #4 • WG ballot plan • Latest next Monday, if possible end of this week, to provide sufficient time for reviewers and make WG members aware who are leaving early for holidays. • Agenda proposal and plan for January 802.1 interim in Geneva, CH • See next two slides • Chair explained that OmniRAN session on Thursday depends on DCB demand for early start. • Agenda proposal agreed. No amendments brought up. • AOB • Next meeting • 22 - 25 January 2018, F2F meeting at ITU site in Geneva • FYI: IEEE 802 dress-code applies for the meeting. Adjourned by chair at 10:50 AM ET

18. January 2018 Agenda Graphics

19. Agenda proposal for Jan 2018 F2F • Review of minutes • Reports • Result of P802.1CF WG ballot • Comment resolution on P802.1CF-D1.0 • New content for P802.1CF • Plan for 802.1CF-D2.0 draft • IC NEND contributions review • Conference calls until Mar 2018 F2F • Status report to IEEE 802 WGs • Next meeting • AOB