1. IEEE 802.1 OmniRAN TG January 2019 F2F Meeting Hiroshima, Japan
Max Riegel, Nokia Bell Labs
(TG Chair)

2. January 2019 F2F Meeting Venue: OmniRAN TG sessions:
Hiroshima Oriental Hotel Hiroshima 6-10, Tanakamachi, Naka-ku, Hiroshima, Japan
OmniRAN TG sessions:
Mon, Jan 14th , 13:30-15:30
Meeting room: Themis (3F)
Tue, Jan 15th , 10:30-15:30
Wed, Jan 16th , 13:30-15:30

3. Further meeting logistics
Breaks Service
Morning Coffee/Tea 10:00 – 10:30
Afternoon Coffee/Tea and Snacks 15:30 – 16:00
Lunch Service
Lunch is provided at Rainbow Room (3F) 12:30 – 13:30
Internet:
SSID: 8021hiroshima
Password: Republic_of_Okonomi
Further information

4. Networking Social Information
Wednesday, January 16th, 19:00 – 21:00
Rainbow Room (3F)
Opening Ceremony “Kagamibiraki”
Breaking open a Sake Barrel
You can enjoy washoku meal served from each group;
Tsukidashi (Appetizers)
Zensai Moriawase (Hors d’oeuvre)
Owan (Soup-type Appetizer)
Otsukuri Moriawase (Sashimi)
Mushimono (Steamed dish)
Yakimono (Grilled dish)
Gohan (Rice with Miso Soup)
Desserts

5. January 2019 Agenda Graphics
Mon 1/14
Tue 1/15
Wed 1/16
Thu 1/17
Fri 1/18
08:00
10:00
Maintenance
10:30
12:30
802.1CQ w/ remote participation
Remote participation Nendica
13:30
15:30
OmniRAN opening
OmniRAN closing
16:00
18:00
19:00
21:00
Social

6. Agenda proposal for January 2019 F2F
Review of minutes
Reports
IEEE 802.1CF socialization activities
P802.1CQ contributions and discussions
Requirements and scenarios documentation
Security threats of dynamic local address assignment protocol
802.1 position on MAC randomization
Input to liaison response to ITU-T JCA-IMT2020
Potential Nendica related contributions preview
Potential new projects for OmniRAN TG
Conference calls until March 2019 F2F
Status report to IEEE 802 WGs
Next meeting
AOB

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

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

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

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

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

12. Business #1 Call Meeting to Order Minutes taker: Mandatory slides
Chair called meeting to order at 13:30
Minutes taker:
Hao volunteered to take notes.
Mandatory slides
Mandatory slides were presented, no announcements came up.
Roll Call
Name
Affiliation
Max Riegel
Nokia
Glenn Parson
Ericsson
Hao Wang
Fujitsu
Mick Seaman
self
Antonio de la Oliva
UC3M, IDCC
Roger Marks
EthAirNet Assoc.-rem
Amelia Andersdotter
Article 19

13. Agenda proposal for January 2019 F2F
Review of minutes
Reports
IEEE 802.1CF socialization activities
P802.1CQ contributions and discussions
Requirements and scenarios documentation
Security threats of dynamic local address assignment protocol
802.1 position on MAC randomization
Input to liaison response to ITU-T JCA-IMT2020
Potential Nendica related contributions preview
Potential new projects for OmniRAN TG
Conference calls until March 2019 F2F
Status report to IEEE 802 WGs
Next meeting
AOB

14. Schedules Mon, 13:30 – 15:30 Tue, 10:30 – 15:30 Wed, 13:30 – 15:30
Review of minutes
Reports
IEEE 802.1CF socialization activities
Potential Nendica related contributions preview
Input to liaison response to ITU-T JCA-IMT2020
Tue, 10:30 – 15:30
P802.1CQ contributions and discussions
Requirements and scenarios documentation
Security threats of dynamic local address assignment protocol
802.1 position on MAC randomization
Wed, 13:30 – 15:30
Potential new projects for OmniRAN TG
Conference calls until March 2019 F2F
Status report to IEEE 802 WGs
Next meeting
AOB

15. Business #2 Agenda approval Review of minutes Reports
Agenda approved without comments.
Review of minutes
Chair introduced minutes of previous F2F meeting and conference call.
No comments came up.
Reports
P802.1CF is ready for forwarding to REVCOM after conclusion of sponsor ballot in December. Conditional approval of submission to REVCOM has been provided by EC in the November plenary meeting.
Max will contact Walter to provide FrameMaker sources and .svg files of figures to Glenn Parson
Max asked Hao to provide figures sources to create zip archive of the source files of all figures. He will forward the zip archive to Glenn.
Submission deadline for the March 20th REVCOM meeting is February 8th.

16. Business #3 IEEE 802.1CF socialization activities
Discussion of initial channels to create awareness for IEEE 802.1CF:
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, and Hao; to be started soon to reach submission deadline for September issue
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.
Agreement to start with the first three items.
Potential Nendica related contributions preview
No contribution indicated
Input to liaison response to ITU-T JCA-IMT2020
Next two slides

17. Liaison letter from ITU-T JCA-IMT2020 Glenn Parson assigned creation of response proposal to OmniRAN TG
I Max, I am going to ask OmniRAN to respond to this liaison. I'll ask Scott to help you understand what additional info they are looking for. Glenn Original Message----- From: Law, David Sent: Thursday, November 08, :39 PM To: Paul Nikolich Cc: Adam Healey Glenn Parsons Subject: Liaison letter from ITU-T JCA-IMT2020 Hi Paul, I just wanted to let you know that IEEE 802.3, and IEEE , received a liaison letter from ITU-T JCA-IMT2020 inviting us to update the information in the IMT2020 roadmap, the letter is available at < While I note that there are IEEE , IEEE , IEEE and IEEE standards and projects listed on the roadmap under IEEE 802 < I don't see them on the 'for action' list on the letter, which I assume is also the list that the letter was sent to. I also note that IEEE 802.1, IEEE , IEEE and IEEE Working Group have separate listings in the roadmap, whereas the Working Groups I listed above are all under one listing for IEEE 802 < It seems to me that this letter maybe should be shared with all the IEEE 802 Chair so that they may have the opportunity to provide updates, if they wish. Best regards, David

18. IMT 2020 standards landscape database on https://www. itu
Plenty of IEEE 802 related issues:
IEEE 802 standards appearing on several different levels
Revision has to involve all 802 WGs
Description should reflect scope and purpose
Glenn will get in contact with to find out about their plans
The topic should be brought up to the EC to get all the other 802 WGs involved.
Max will draft a document showing the proposed edits of 802.1
Sending a liaison response requires approval, which could happen in March

19. Business #4 P802.1CQ contributions and discussions
Requirements and scenarios documentation
No contributions for discussion
Security threats of dynamic local address assignment protocol
Antonio presented his slides to security TG chair and OmniRAN showing the potential security threats leading to comprehensive discussions of potential threats
Recommendation not to mention potential vulnerabilities caused through inappropriate implementation of 802 standards
Such statements could lead to the wrong impression of security weaknesses in 802 standards.
Conclusion that local address assignment does not cause any new threats in addition to threats arising due to inappropriate implementations of the LAAP and LAAP components.
LAAP should avoid leakage of information through broadcast of responses, and should not add much overhead to the number of message exchanges for setting up a connection.
Antonio will create text contribution out of presented material and discussions results.
802.1 position on MAC randomization
Max walked through his slides providing a summary of MAC address usage as device identifier for network operations as brought up by WBA.
Agreement reached that WBA use cases are legitimate reasons to provide the possibility to assign static device identifier to stations for initiating the dynamic MAC address assignment
Static device identifier allow LAAP to assign fixed MAC addresses to devices.
Antonio will draft a protocol proposal for secure signaling of a static device identifier to the access network
Max will draft a section for the functional requirements describing the need to provide the possibility of fixed device identifiers.

20. MAC randomization
Randomized MAC address assignment became quite common in the wireless domain, mainly as a mean to prevent simple ways of tracking terminals.
The Wireless Broadband Alliance representing many of the operators of public Wi-Fi access sent in September 2018 a liaison letter to IEEE with the operational issues caused by randomized MAC addresses of Wi-Fi terminals:
The reviewed and discussed the liaison letter and created at the November plenary meeting a response to WBA explaining the mitigation of the operational issues from an perspective:
 Would concur with the statements of ?

21. Discussions about potential future work in OmniRAN
Business #5
Discussions about potential future work in OmniRAN ..

22. Business #6 Conference calls until March 2019 F2F..
Status report to IEEE 802 WGs
Next meeting
AOB
Meeting adjourned by chair at ..