omniran18 0012 01 00 TG IEEE 802 1

omniran-18 -0012 -01 -00 TG IEEE 802. 1 Omni. RAN TG February 13 th, 2018 Conference Call 2018 -02 -13 Max Riegel, Nokia Bell Labs (TG Chair) 1

omniran-18 -0012 -01 -00 TG Conference Call • Tuesday, February 13 th , 2018 at 09: 30 -11: 00 am ET • Join Web. Ex meeting – https: //nokiameetings. webex. com/nokiameetings/j. php? MTID=mef 8 ba 7 56240 e 21 ffec 839 ee 90 bbc 0661 – Meeting number: 951 008 293 – Meeting password: Omni. RAN • Join by phone – – – +19724459814 US Dallas +442036087616 UK London +861084056120, +861058965333 China Beijing Access code: 951 008 293 Global call-in numbers • https: //nokiameetings. webex. com/nokiameetings/globalcallin. php? service. Type=M C&ED=533523267&toll. Free=0 2

omniran-18 -0012 -01 -00 TG Agenda proposal • • Minutes Reports Procedural review of P 802. 1 CF/D 1. 0 WG ballot Action item list of Geneva comment resolution Official documentation of comment resolution Searchable figures Review of contributions addressing unresolved P 802. 1 CF/D 1. 0 comments • March 2018 F 2 F planning • Next meeting • Ao. B 3

omniran-18 -0012 -01 -00 TG 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 4

omniran-18 -0012 -01 -00 TG Ways to inform IEEE – 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. 5

omniran-18 -0012 -01 -00 TG 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 5. 3. 10 and Antitrust and Competition Policy: What You Need to Know at http: //standards. ieee. org/develop/policies/antitrust. pdf 6

omniran-18 -0012 -01 -00 TG 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/sect 6 -7. html#6 – IEEE-SA Standards Board Operations Manual http: //standards. ieee. org/develop/policies/opman/sect 6. 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 7

omniran-18 -0012 -01 -00 TG 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. (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: //ieee 802. org/PNP/approved/IEEE_802_WG_Pand. P_v 19. 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: //ieee 802. org/PNP/approved/IEEE_802_WG_Pand. P_v 19. 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. 8

omniran-18 -0012 -01 -00 TG Business #1 • Call Meeting to Order – Chair called meeting to order at 09: 30 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 Antonio de la Oliva UC 3 M Name Affiliation 9

omniran-18 -0012 -01 -00 TG Agenda • • Minutes Reports Procedural review of P 802. 1 CF/D 1. 0 WG ballot Action item list of Geneva comment resolution Official documentation of comment resolution Searchable figures Review of contributions addressing unresolved P 802. 1 CF/D 1. 0 comments • March 2018 F 2 F planning • Next meeting • Ao. B 10

omniran-18 -0012 -01 -00 TG Business #2 • Minutes – https: //mentor. ieee. org/omniran/dcn/18/omniran-18 -0011 -00 -00 TG-jan-2018 -f 2 fmeeting-minutes. docx • Review postponed to Mar F 2 F • Reports – Nothing reported in addition to agenda items • Procedural review of P 802. 1 CF/D 1. 0 WG ballot – https: //mentor. ieee. org/omniran/dcn/18/omniran-18 -0013 -00 -CF 00 -p 802 -1 cf-initial-wgballot-procedural-review. pptx • Slides presented references to the basic rules for comment resolution and recirculation of the WG ballot • Walter recommended to provide full 30 days review period for recirculation as full draft text is open for commenting and a few responders indicated that they couldn’t provide comments due to lack of time. • Action item list of Geneva comment resolution – https: //mentor. ieee. org/omniran/dcn/18/omniran-18 -0006 -03 -CF 00 -d 1 -0 -collectedcomments. xls • Walter is asked to review implementation of the accepted and revised comments, as it is not obvious from the table whethere is sufficient information for changes to the text given. 11

omniran-18 -0012 -01 -00 TG Business #3 • Official documentation of comment resolution – Max will trial use Java-based tool for handling comments with first results for review in next confcall. • Searchable figures – Walter experimented and svg is recommended. – MS Visio can create svg, as well as Omni Graffle • Max will provide most difficult PPTX figures to Walter for experimenting with conversion tools. – Antonio recommended to provide both, Visio should be provided both in native and in. svg – Conclusion about the final procedures in the next call. • Review of contributions addressing unresolved P 802. 1 CF/D 1. 0 comments – https: //mentor. ieee. org/omniran/dcn/18/omniran-18 -0014 -00 -CF 00 clause-7 -8 -fdm-amendment. docx • Max asked for being for specific when replacing. 3 ah and. 1 ag • Max provided hint to structure capabilities and configuration information under one common label ‘Capabilities and configurations’ with each information element amended with the network element, it belongs to, e. g. NAFDMCapabilities • Hao will bring up revised text in next call for final review. 12

omniran-18 -0012 -01 -00 TG Business #4 • March 2018 F 2 F planning – Meeting outline and proposed agenda on the following two slides. – Some of the meeting slots may be converted into sessions for editorial work. Technical contributions may not require 7 -8 slots for discussion. – Proposed outline and agenda proposal fine for public announcement. • Next meeting – Conference call on Feb 27 th, 0930 -1100 AM ET • AOB – Nothing brought up. Adjourned by chair at 10: 59 AM ET 13

omniran-18 -0012 -01 -00 TG Mar 2018 Agenda Graphics Mon 03/05 08: 00 802 EC Opening Tue 03/06 Wed 03/07 Thu 03/08 802. 11 WNG Fri 03/09 802. 11 Closing Plenary 10: 00 10: 30 802. 1 Opening 802. 11/802. 15 Mid-week Plenaries Plenary 802. 1 Closing Plenary 12: 30 802. 1 TF chairs meeting 13: 30 Omni. RAN 802 EC Closing 802. 1 Midweek Plenary opening Omni. RAN closing 15: 30 16: 00 Potential overflow time if needed 18: 00 Tutorials Joint 802. 1/802. 15 ICA NEND 14

omniran-18 -0012 -01 -00 TG Agenda proposal for Mar 2018 F 2 F • • • Review of minutes Reports IC NEND contributions review Status of P 802. 1 CF D 1. 0 comment resolution Documentation of P 802. 1 CF D 1. 0 comment resolution Review of contributions addressing unresolved P 802. 1 CF/D 1. 0 comments Plan for 802. 1 CF-D 1. 1 draft and recirculation ballot Conference calls until Jul 2018 F 2 F Status report to IEEE 802 WGs Next meeting AOB 15