IEEE 802.1 OmniRAN TG March 2018 F2F Meeting Vancouver, BC, Canada

1. IEEE 802.1 OmniRAN TGMarch 2018 F2F MeetingVancouver, BC, Canada 2019-03-13 Max Riegel, Nokia Bell Labs (TG Chair)

2. March 2019 F2F Meeting • Venue: • FAIRMONT HOTEL VANCOUVER • 900 West Georgia StreetVancouver, BC V6C 2W6Canada • Information Website: https://www.fairmont.com/hotel-vancouver/ • OmniRAN TG sessions: • Mon, Mar 11th , 13:30-15:30 • Meeting room: Galiano, FHV Discovery level • Tue, Mar 12th , 13:30-15:30 • Meeting room: Galiano, FHV Discovery level • Wed, Mar 13th , 13:30-15:30 • Meeting room: Galiano, FHV Discovery level

3. Agenda proposal for March 2019 F2F • Review of minutes • Reports • IEEE 802.1CF socialization activities • P802.1CQ contributions and discussions • P802.1CQ ToCand specification text contributions • Potential new project for OmniRAN TG • Conference calls until July 2019 F2F • Status report to IEEE 802 WGs • Liaisons • Next meeting • AOB

4. March 2019 Agenda Graphics

5. Participants 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 Participants should inform the IEEE (or cause the IEEE to be informed) of the identity of any other holders of potential Essential Patent Claims Early identification of holders of potential Essential Patent Claims is encouraged Participants have a duty to inform the IEEE

6. Cause an LOA to be submitted to the IEEE-SA (patcom@ieee.org); 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 Speak up now and respond to this 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, please respond at this time by providing relevant information to the WG Chair. Ways to inform IEEE

7. 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 of different technical approaches that include relative costs of patent licensing terms may be discussed in standards development meetings. Technical considerations remain the 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. For more details, see IEEE-SA Standards Board Operations Manual, clause 5.3.10 and Antitrust and Competition Policy: What You Need to Know at http://standards.ieee.org/develop/policies/antitrust.pdf Other guidelines for IEEE WG meetings

8. Patent-related information • The patent policy and the procedures used to execute that policy are documented in the: • IEEE-SA Standards Board 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

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

10. Business #1 • Call Meeting to Order • Chair called meeting to order at 13:32 • Minutes taker: • Hao volunteered to take notes. • Mandatory slides • Mandatory slides were presented, no announcements came up. • Roll Call

11. Agenda proposal for March 2019 F2F • Review of minutes • Reports • IEEE 802.1CF socialization activities • P802.1CQ contributions and discussions • P802.1CQ ToC and specification text contributions • Potential new project for OmniRAN TG • Conference calls until July 2019 F2F • Status report to IEEE 802 WGs • Liaisons • Next meeting • AOB

12. Schedules • Mon, 13:30 – 15:30 • Review of minutes • Reports • P802.1CQ contributions and discussions • P802.1CQ ToC and specification text contributions • Tue, 13:30 – 15:30 • IEEE 802.1CF socialization activities • Potential new project for OmniRAN TG • Liaisons • Conference calls until July 2019 F2F • Motions to 802.1 closing plenary • Draft status report to IEEE 802 WGs • Wed, 13:30 – 15:30 • P802.1CQ contributions and discussions • IEEE 802.11 related discussions • Status report to IEEE 802 WGs • Next meeting • AOB

13. Business #2 • Agenda approval • Approved without further requests • Review of minutes • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0005-02-00TG-jan-2019-f2f-meeting-minutes.docx • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0008-00-00TG-feb-6th-confcall-minutes.docx • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0014-00-00TG-feb-27th-confcall-minutes.docx • No comments raised to any of the minutes. • Reports • P802.1CF is on RevCom agenda of Mar 20th meeting in Munich • Max will attend meeting in person • Jessy Rouyer requested adoption of new template for F2F meeting minutes. OmniRAN TG will adopt template for all its meetings amending the template with list of participants, detailed agenda, and clear attribution of discussions to agenda items. • Max will assist Hao for adoption of new meeting minutes template

14. Business #3 • P802.1CQ contributions and discussions • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0011-01-CQ00-maap-introduction.pptx • Antonio introduced the potential adoption of MAAP for unicast addresses. • The secretary of the dormant IEEE 1722 WG explained that it could be feasible to take over the maintenance of the MAAP from IEEE 1722 allowing for functional additions when keeping strict backward compatibility. A liaison to IEEE 1722 should be considered when the feasibility of adopting MAAP would mature. • Obstacles of adoption are the private ownership of the EtherType used for MAAP as well as the superfluous message structure. • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0017-00-CQ00-proposed-liaison-to-ieee-1722-working-group.pptx • Roger presented his proposed text of a liaison to IEEE 1722. • Text was discussed and a few small edits were introduced. • The chair uploaded the revision to mentor after the meeting. • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0017-01-CQ00-proposed-liaison-to-ieee-1722-working-group.pptx • The chair created a text document out of the pptx contribution and uploaded the liaison text document to mentor for WG approval • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0018-00-00TG-802-1-liaison-to-ieee-1722.docx

15. Business #4 • IEEE 802.1CF socialization activities • List of actions as discussed and agreed at Hiroshima meeting: • 100 word notice to IEEE Communications Standards Magazine • Max will create draft of notice for review in OmniRAN TG • Updated presentation on aim and content of standard • Max will update existing slide set to reflect final standards content • Article for IEEE Communications Standards Magazine • Joint work of Max, Walter, Antonio, and Hao; to be started soon to reach submission deadline for September issue • Contribution to the IEEE blog beyond standards • https://beyondstandards.ieee.org/beyond-standards/ • Contact IEEE staff for assistence • Potential IEEE 802 press release • Has to be approved by EC. Requires some customer quote, which may be challenging • Contribution to IEEE future networks (conference) • Multiple options for contributions to conferences; scope and timeline of conference must fit. For further considerations. • Conclusion in January was to start with the first three items. • It was recommended to add beyondstandards, as it was also used for publication purposes out of Nendica • Potential new project for OmniRAN TG • No contribution received.

16. Business #5 • Liaisons • 802.1 liaison response to ITU-T JCA IMT2020 • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0015-00-00TG-802-1-liaison-response-to-itu-t-jca-imt2020.docx • 802.1 liaison to IEEE 1722 regarding MAAP • Proposed liaison text • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0017-00-CQ00-proposed-liaison-to-ieee-1722-working-group.pptx • Conference calls until July 2019 F2F • Two conference calls agreed until May 2019 F2F • Friday, April 5th, 2019, 0900-1030AM ET • Friday, April 26th, 2019, 0900-1030AM ET • TG agreed not to hold a F2F meeting at the 802.1 interim in May • Main 802.1CQ contributor not available • Better to continue 802.1CQ on conference calls to allow all interested parties from OmniRAN, TSN, P60802, and 802.11 to participate • Unavailability of chair • Further conference calls will be announced with 14days preannouncement on the 802.1 mailing list. • Motions to 802.1 closing plenary • EC approval of liaison response • Teleconferences

17. Motion Approve https://mentor.ieee.org/omniran/dcn/19/omniran-19-0015-00-00TG-802-1-liaison-response-to-itu-t-jca-imt2020.docx as communication of IEEE 802.1 to ITU-T JCA IMT2020, granting the IEEE LMSC chair (or his delegate) editorial license. This approval is under LMSC OM “Procedure for communication with government bodies” • In the WG: proposed Max Riegel, second: Hao Wang • (y/n/a): <y>, <n>, <a> • In the EC: proposed: John Messenger, second: David Law • (y/n/a): <y>, <n>, <a>

18. Motion • Approve sending the following liaison to IEEE 1722 • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0018-00-00TG-802-1-liaison-to-ieee-1722.docx • Granting the IEEE 802.1 WG chair (or his delegate) editorial license. • In the WG (y/n/a): <y>,<n>,<a> • Proposed: Max Riegel Second: Roger Marks • In EC, for information

19. Business #6 • P802.1CQ contributions and discussions • P802.1CQ ToC and specification text contributions • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0016-00-CQ00-thoughts-on-toc.pptx • Antonio presented his proposal of a ToC structure. During the discussion the proposal on the slides was modified according to discussions. • Open questions were presented and potential conclusions discussed. • Agreement reached to start the drafting of the specification with the established ToC. Modifications may be introduced during the development as needed. • IEEE 802.11 related discussions • https://mentor.ieee.org/802.11/dcn/19/11-19-0286-03-000m-mac-address-policy-anqp-and-beacon-element.docx • Antonio presented a contribution to 802.11md addressing the address policy discovery, which will be discussed in 802.11 on Thursday. • The concept and dependencies to 802.1CQ were discussed and potential dependencies were considered. • Conclusion reached that the proposed amendment to 802.11md sufficiently covers the necessary additions to PAD.

20. Business #7 • Status report to IEEE 802 WGs • Chair presented proposal and during review some edits were applied. The resulted version was uploaded to mentor: • https://mentor.ieee.org/omniran/dcn/19/omniran-19-0019-00-00TG-mar-2019-report-to-ieee-802-wgs.pptx • Group agreed with the content of the report. • Next meeting • Conference call on April 5th, 09:00AM ET • AOB • None. Meeting adjourned by chair at 15:12.