omniran17 0020 01 00 TG IEEE 802 1

omniran-17 -0020 -01 -00 TG IEEE 802. 1 Omni. RAN TG March 2017 F 2 F Meeting Vancouver, BC 2017 -03 -14 Max Riegel, Nokia Bell. Labs (TG Chair) 1

omniran-17 -0020 -01 -00 TG March 2017 F 2 F Meeting • Venue: – Fairmont Hotel Vancouver 900 West Georgia Street Vancouver, BC V 6 C 2 W 6 CANADA • Sessions: – Mon, Mar 13 th, 16: 00 -18: 00 • Meeting room: Cortes Island, Discovery Floor, Fairmont Hotel – Tue, Mar 14 th, 16: 00 -18: 00 • Meeting room: Gabriola, Discovery Floor, Fairmont Hotel – Wed, Mar 15 th, 13: 30 -15: 30 • Meeting room: Galiano Island, Discovery Floor, Fairmont Hotel – Wed, Mar 15 th, 16: 00 -18: 00 ICAID special session • Meeting room: Boardroom, Conference Floor, Fairmont Hotel – Thu, Mar 16 th, 10: 30 -12: 30 • Meeting room: Boardroom, Conference Floor, Fairmont Hotel 2

omniran-17 -0020 -01 -00 TG Agenda proposal for March 2017 F 2 F • • • Review of minutes Reports Industry Connections activity Comments’ resolution on P 802. 1 CF-D 0. 4 Revised and new P 802. 1 CF contributions Plan for 802. 1 CF-D 0. 5 draft Conference calls until Jul F 2 F Status report to IEEE 802 WGs AOB 3

omniran-17 -0020 -01 -00 TG Mar 2017 Agenda Graphics Mon 3/13 08: 00 802 EC Opening Tue 3/14 802. 11 WNG Wed 3/15 Thu 3/16 802. 11 ARC 802. 11/802. 15 Mid-week Plenaries Omni. RAN closing Fri 3/17 802. 11 Closing 10: 00 10: 30 802. 1 Opening Plenary 12: 30 802 EC Closing 13: 30 802. 11 ARC 802. 11 AANI 802. 1 Closing Plenary 15: 30 16: 00 Omni. RAN opening Omni. RAN ICAID Special Session 18: 00 Newcomers Intro Joint 802. 1/802. 15 4

omniran-17 -0020 -01 -00 TG Participants, Patents, and Duty to Inform All participants in this meeting have certain obligations under the IEEE-SA Patent Policy. • • Participants [Note: Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6. 2]: • “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 • “Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of potential Essential Patent Claims” (that is, third parties that are not affiliated with the participant, with the participant’s employer, or with anyone else that the participant is from or otherwise represents) The above does not apply if the patent claim is already the subject of an Accepted Letter of Assurance that applies to the proposed standard(s) under consideration by this group Early identification of holders of potential Essential Patent Claims is strongly encouraged No duty to perform a patent search 5

omniran-17 -0020 -01 -00 TG Patent Related Links • All participants should be familiar with their obligations under the IEEE-SA Policies & Procedures for standards development. • Patent Policy is stated in these sources: – IEEE-SA Standards Boards 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 or visit http: //standards. ieee. org/about/sasb/patcom/index. html This slide set is available at https: //development. standards. ieee. org/myproject/Public/mytools/mob/slideset. ppt 6

omniran-17 -0020 -01 -00 TG 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: – Either speak up now 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 – Cause an LOA to be submitted 7

omniran-17 -0020 -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-17 -0020 -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, including licensing costs of essential patent claims, of different technical approaches may be discussed in standards development meetings. • • Technical considerations remain 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. -------------------------------- See IEEE-SA Standards Board Operations Manual, clause 5. 3. 10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. 9

omniran-17 -0020 -01 -00 TG Resources – URLs • Link to IEEE Disclosure of Affiliation – http: //standards. ieee. org/faqs/affiliation. FAQ. html • Links to IEEE Antitrust Guidelines – http: //standards. ieee. org/resources/antitrust-guidelines. pdf • Link to IEEE Code of Ethics – http: //www. ieee. org/web/membership/ethics/code_ethics. html • Link to IEEE Patent Policy – http: //standards. ieee. org/board/pat-slideset. ppt 10

omniran-17 -0020 -01 -00 TG Business #1 • Call Meeting to Order – Chair called meeting to order at 16: 00 • Minutes taker: – Walter is taking notes. • Roll Call Name Affiliation Max Riegel Nokia Networks Tomoki Ohsawa BRID Wang Hao Fujitsu Satoko Itaya NICT Walter Pienciak IEEE Roger Marks Eth. Air. Net Assoc. Patrick Slaats IEEE-SA Su Yi Fujitsu Hyeong Ho Lee ETRI Juan Carlos Zuniga Sigfox Yunsong Yang Huawei Glenn Parson Ericsson Hajime Koto NICT 11

omniran-17 -0020 -01 -00 TG 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: – Either speak up now 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 – Cause an LOA to be submitted • Nothing brought up. 12

omniran-17 -0020 -01 -00 TG Agenda for March 2017 F 2 F • Review of minutes • • Reports Industry Connections activity – • – – https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0030 -00 -CF 00 -802 -1 cf-d 0 -4 -collectedcomments. xls https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0021 -00 -CF 00 -deployment-scenario-wi-firouter. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0022 -00 -CF 00 -deployment-scenario-enterprisenetwork. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0007 -01 -CF 00 -mapping-fdm-to-ieee-802 technologies. docx t. b. d. Revised and new P 802. 1 CF contributions – • • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0029 -00 -5 gaa-icaid-introduction. pptx Comments’ resolution on P 802. 1 CF-D 0. 4 – • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0015 -00 -00 TG-jan-2017 -f 2 f-meeting-minutes. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0018 -00 -00 TG-feb-7 th-confcall-minutes. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0028 -00 -CF 00 -data-model-for-fdm. pptx Plan for 802. 1 CF-D 0. 5 draft Conference calls until Jul F 2 F Status report to IEEE 802 WGs AOB 13

omniran-17 -0020 -01 -00 TG Schedules • Mon – – • Tue – – • Comments’ resolution on P 802. 1 CF-D 0. 4 • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0021 -00 -CF 00 -deployment-scenario-wi-fi-router. docx • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0022 -00 -CF 00 -deployment-scenario-enterprise-network. docx Revised and new P 802. 1 CF contributions • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0028 -00 -CF 00 -data-model-for-fdm. pptx Wed – – • Review of minutes • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0015 -00 -00 TG-jan-2017 -f 2 f-meeting-minutes. docx • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0018 -00 -00 TG-feb-7 th-confcall-minutes. docx Reports Industry Connections activity • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0029 -00 -5 gaa-icaid-introduction. pptx Comments’ resolution on P 802. 1 CF-D 0. 4 • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0030 -00 -CF 00 -802 -1 cf-d 0 -4 -collected-comments. xls • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0021 -00 -CF 00 -deployment-scenario-wi-fi-router. docx Comments’ resolution on P 802. 1 CF-D 0. 4 Revised and new P 802. 1 CF contributions Thu – – Plan for 802. 1 CF-D 0. 5 draft Conference calls until Jul F 2 F Status report to IEEE 802 WGs AOB 14

omniran-17 -0020 -01 -00 TG Business #2 Mon • Agenda approval – – • Review of minutes – – – • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0015 -00 -00 TG-jan-2017 -f 2 f-meetingminutes. docx https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0018 -00 -00 TG-feb-7 th-confcall-minutes. docx No comments raised. Reports – • It was agreed to run the meeting according to the presented agenda. Topics were roughly distributed across the week. Hao was fine to have the discussion on the data model for FDM on Tuesday afternoon. Agenda approved without comments. Aside of the ICAID discussion (next item), nothing was reported. Industry Connections activity • – – – https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0029 -00 -5 gaa-icaid-introduction. pptx Chair shortly introduced into the current status of the discussion, reported about the presentation and discussion of the topic in the opening 802. 1 plenary in the morning and about potentially open issues in the ICAID. The special session on Wed PM 2 will resolve the open issues and step into considerations regards the execution of the IC activity. Walter asked about the possibility to arrange a conference call with the IEEE SA staff liaison contacts to further evaluate the possibilities to stretch out into the vertical applications domain. The chair responded that such meeting could be arranged in the following week when the directions and the ICAID are finally settled. 15

omniran-17 -0020 -01 -00 TG Business #3 • Comments’ resolution on P 802. 1 CF-D 0. 4 – https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0030 -00 -CF 00 -802 -1 cf-d 0 -4 collected-comments. xls – The chair brought up the spreadsheet with the collected comments containing roughly 40 comments from Brian, Hao and Max – It was agreed to postpone the resolution of Brian’s comments to a time when Brian can attend the Omni. RAN meeting. – Comments were discussed and resolved in the order provided in the spreadsheet going through the specification from the beginning. – Resolution results were captured in the spread sheet. – Discussion with several hints for enhancements arose on the contribution about the proposed Wi-Fi router deployment scenario. Roger recommended to add some explanatory text on the purpose of the reference points to the LAN and WAN side. • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0021 -00 -CF 00 -deployment-scenario-wi-firouter. docx – Max included proposed text edits into a revision of the document and offered to introduce further amendments in a revision until the following day. – The chair uploaded the spreadsheet with the resolution results to mentor. • https: //mentor. ieee. org/omniran/dcn/17/omniran-17 -0030 -01 -CF 00 -802 -1 cf-d 0 -4 -collectedcomments. xls • Recess at 17: 50 16

omniran-17 -0020 -01 -00 TG Business #4 Tue: • Comments’ resolution on P 802. 1 CF-D 0. 4 – https: //mentor. ieee. org/omniran/dcn/17/omniran 17 -0030 -01 -CF 00 -802 -1 cf-d 0 -4 -collectedcomments. xls – https: //mentor. ieee. org/omniran/dcn/17/omniran 17 -0021 -01 -CF 00 -deployment-scenario-wi-firouter. docx – https: //mentor. ieee. org/omniran/dcn/17/omniran 17 -0022 -01 -CF 00 -deployment-scenarioenterprise-network. docx 17

omniran-17 -0020 -01 -00 TG Business #5 • Revised and new P 802. 1 CF contributions – https: //mentor. ieee. org/omniran/dcn/17/omnira n-17 -0028 -00 -CF 00 -data-model-for-fdm. pptx 18

omniran-17 -0020 -01 -00 TG Busines #6 • Wed – Comments’ resolution on P 802. 1 CF-D 0. 4 – Revised and new P 802. 1 CF contributions 19

omniran-17 -0020 -01 -00 TG Business #7 • Thu – Plan for 802. 1 CF-D 0. 5 draft – Conference calls until Jul F 2 F – Status report to IEEE 802 WGs – AOB 20