1. IEEE 802.1 OmniRAN TG March 20th, 2018 Conference Call
Max Riegel, Nokia Bell Labs
(TG Chair)

2. Conference Call Tuesday, March 20th, 2018 at 09:30-11:00am ET
September 2012
doc.: IEEE /0996r3
Conference Call
Tuesday, March 20th, 2018 at 09:30-11: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. Agenda proposal Minutes Reports P802.1CF-D1.0 comment resolution
September 2012
doc.: IEEE /0996r3
Agenda proposal
Minutes
Reports
Transfer of P802.1CQ to OmniRAN TG
P802.1CF-D1.0 comment resolution
Open issues of implementation of remedies
Documentation of proposed disposition
Review of information model revision (Clause 8.1)
Review of revision to Identifiers clause (Clause 6.7)
Review of other amendments
Plan for swapping to searchable figures (.svg)
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 09:40 AM ET
Minutes taker:
Hao is taking notes.
Mandatory slides
Mandatory slides were presented, no announcements came up.
Roll Call
Name
Affiliation
Max Riegel
Nokia
Hao Wang
Fujitsu
Walter Pienciak
IEEE
Roger Marks
EthAirNet Assoc.

10. Agenda Minutes Reports P802.1CF-D1.0 comment resolution Next meeting
September 2012
doc.: IEEE /0996r3
Agenda
Minutes
Reports
P802.1CF-D1.0 comment resolution
Open issues of implementation of remedies
Documentation of proposed disposition
Review of information model revision (Clause 8.1)
Review of revision to Identifiers clause (Clause 6.7)
Review of other amendments
Plan for swapping to searchable figures (.svg)
Next meeting
AoB
Stephen McCann, RIM

11. Business #2 Minutes Reports
Acceptance postponed to the next F2F
Reports
OmniRAN TG will take responsibility for P802.1CQ
Procedural questions will be discussed on the March 28th .1CQ call
OmniRAN mentor archive has new category for uploading .1CQ related contributions.
Review of information model revision (Clause 8.1)
Not available yet. Hao asked about a terminology issue of using ‘operation’ of ‘OAM’ with a broader meaning than used for network management.
Max recommended to use terminology with such broader scope for the contribution, and let the commenters of D2.0 decide whether such broader usage is appropriate.

12. Business #3 Review of revision to Identifiers clause (Clause 6.7)
Roger introduced his approach and findings for the identifiers section. During discussion some clarifications were added to the document in a revision. Max offered to check for the name of the information element in 802.1X containing the AN-ID used for The outcome of the discussion was uploaded to mentor
Review of other amendments
Hao introduced the text for the addition to clause 7.8 of a monitoring procedure delivering monitoring values to the NMS. It amends the accounting procedures of the clause. The contribution was appreciated by the group and accepted as remedy for CID#102
Max briefly showed the small modification to the figures of the proposed text to indicate that an Ethernet switch can also act as NA in addition to the aggregation functionality of the BH. With this small modification the contribution was accepted for inclusion into the next draft.
After presenting the deployment scenario of a virtualized WLAN access network for IoT devices at the Rosemont, IL face-to-face meeting, Max asked the group for any concerns to add the proposal to the upcoming draft. Hao expressed that he appreciates the contribution, which nicely shows the value of virtualized IEEE 802 access networks.

13. Business #4 Open issues of implementation of remedies
Walter is working on the implementation of the agreed remedies and had no open issues to clarify with the group.
Documentation of proposed disposition
Max currently updates the Java database of the comments with the remedies and conclusions of the comment resolution process to allow for documentation and the tracking of the implementation. He will hand-over the completed database to Walter for tracking the editorial process. Parallel to the entries into the Java database, the Excel containing the comments will be kept aligned. A snapshot of the updated comments spreadsheet was uploaded and presented. The spreadsheet also contains pointers to the remaining actions for delivering input.
Plan for swapping to searchable figures (.svg)
Max recommended to prepare all the necessary .svg figures for the next conference call on April 3rd to provide more time to resolve issues appearing during insertion.
Next meeting
.1CQ conference call on March 28th, 09:00 – 10:00 AM ET
.1CF conference call on April 3rd, 09:30 – 11:00 AM ET
AoB
None
Adjourned by chair at 11:03 AM ET