1. IEEE 802.1 OmniRAN TG February 6th , 2019 Conference Call
Max Riegel, Nokia Bell Labs
(TG Chair)

2. Conference Call Wednesday, February 6th , 2018 at 09:00-10:00am ET
September 2012
doc.: IEEE /0996r3
Conference Call
Wednesday, February 6th , 2018 at 09:00-10:00am ET
Join WebEx meeting
Meeting number:
Meeting password: OmniRAN
Join by phone
US Dallas
UK London
, China Beijing
Access code:
Global call-in numbers
Stephen McCann, RIM

3. Potential new standardization topic for OmniRAN TG Next meeting AOB
September 2012
doc.: IEEE /0996r3
Agenda proposal
Minutes
Reports
P802.1CF conclusion
P802.1CQ contributions
Potential new standardization topic for OmniRAN TG
Next meeting
AOB
Stephen McCann, RIM

4. Participants have a duty to inform the IEEE
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

5. Ways to inform IEEE
Cause an LOA to be submitted to the IEEE-SA 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.

6. 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 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 and Antitrust and Competition Policy: What You Need to Know at

7. Patent-related information
The patent policy and the procedures used to execute that policy are documented in the:
IEEE-SA Standards Board Bylaws
IEEE-SA Standards Board Operations Manual
Material about the patent policy is available at
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at

8. Participation in IEEE 802 Meetings
Dorothy Stanley, HP Enterprise
November 2016
doc.: ec EC
Participation in IEEE 802 Meetings
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. ( 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”. ( 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
section and
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.

9. Business #1 Call Meeting to Order Minutes taker: Mandatory slides
Chair called meeting to order at 0900 AM ET
Minutes taker:
Hao is taking notes.
Mandatory slides
Mandatory slides were presented, no IPR announcements came up.
Roll Call
Name
Affiliation
Max Riegel
Nokia
Hao Wang
Fujitsu
Roger Marks
EthAirNet Assoc.
Antonio de la Oliva
UC3M

10. Potential new standardization topic for OmniRAN TG Next meeting AOB
September 2012
doc.: IEEE /0996r3
Agenda
Minutes
Reports
P802.1CF conclusion
P802.1CQ contributions
Potential new standardization topic for OmniRAN TG
Next meeting
AOB
Stephen McCann, RIM

11. Business #2 Minutes Reports
No comments raised. Will finally be reviewed at the upcoming F2F meeting.
Reports
Discussions started about moving to the file space on mentor. Details and timeline open. Need for project specific document identifiers (project specific document groups)

12. Business #3 P802.1CF conclusion P802.1CQ contributions
Submission to REVCOM pending.
Deadline: February 8th for March 24th REVCOM meeting.
Roger provided guidance on procedural requirements.
Max will take actions and provide support to Glenn for required note to EC that conditions have been met.
P802.1CQ contributions
Antonio reported about preparation of a contribution to to amend contribution of Stephen Mcann
seems to propose specification text to for local address assignment without close cooperation with P802.1CQ. There is need for discussion and closer cooperation to make specifications fitting.
Both contributions will be discussed in upcoming OmniRAN call to determine impact and relation to P802.1CQ.
Max introduced his contribution on requirements for P802.1CQ derived from the WBA liaison on issues caused by randomized MAC addresses
It was pointed out that document should explicitly mention LAAP of P802.1CQ to show that requirements only apply to unicast addresses.
Content of document was generally welcome, and requirement statements may be included in the requirements section of the P802.1CQ specification
Max will provide revised version for further discussions. Finally, the document may represent the view of on the issues raised through the WBA liaison letter, as requested by the chair in early January.
Roger reported about the ambiguities regarding the use cases for multicast MAC address assignments. It is currently unclear to the group, why multicast MAC address assignment was included in the PAR.
Multicast MAC addresses are e.g. used for stream identification within Time Sensitive Networking. There is a standard IEEE 1722 for a Transport Protocol for Time-Sensitive Applications in Bridged Local Area Networks, which contains in Annex B the normative specification of a MAC address acquisition protocol.
Agreement that further investigations are necessary to determine whether IEEE 1722 may already contain a solution for multicast address assignment for the intended use cases.

13. Business #4 Potential new standardization topic for OmniRAN TG
No contributions received
Next meeting
Conference call on February 27th, 0900AM ET
AOB
Vancouver F2F planning
See following slides
Chair pointed out that OmniRAN meetings are scheduled on Monday PM1, Tuesday PM1, Wednesday PM1
Session time will mainly used for P802.1CQ
802.1 May 20-24th interim room request
Chair pointed out that there is need to co-locate OmniRAN interim F2F with wireless interim meeting to facilitate alignment between P802.1CQ approaches and P802.11md approaches. Possibility would be to hold May interim at the wireless interim on May in Atlanta.
Due to constraints with other meetings, chair would only be available for sessions in Salt Lake City on Wednesday afternoon and Thursday morning. Hao mentioned, that he might not be able to attend an OmniRAN interim meeting on May in Atlanta, GA.
Adjourned by chair at 10:04 AM ET.

14. March 2019 Agenda Graphics Mon 3/11 Tue 3/12 Wed 3/13 Thu 3/14
Fri 3/15
08:00
10:00
EC Opening
Maintenance
10:30
12:30
802.1 Opening
13:30
15:30
OmniRAN opening
OmniRAN closing
802.1 Closing
EC Closing
Starts at 13:00
16:00
18:00
19:00
21:00
Tutorials
Nendica
Social

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