OmniRAN EC SG Agenda and Meeting Slides March 2014, Beijing, China

1. OmniRAN EC SG Agenda and Meeting SlidesMarch 2014, Beijing, China 2014-03-16 EC SG Chair Max Riegel, NSN

2. Tuesday, Mar 18st, 09:00 – 10:00 Tuesday, Mar 18st, 10:30 – 12:30 Thursday, Mar 20th, 08:00 – 10:00 Wireless SDN BoF Thursday, Mar 20th, 10:30 – 12:30 Meeting Room: Function Room 5 Meetings

3. Mar 2014 Remote Participation • Teleconference: • Dial-in information for all meetings: • Conference Code: 433 819 2102 • Call-in number: 1-(972) 445 9673 (US)
Show global numbers: http://www.nsn.com/nvc • WebEx: • Tue, 2014-03-18 09:00-10:00 Beijing, China / Mon, 2014-03-17 09:00 - 10:00 PM ET • Meeting Number: 709 002 318, Meeting Password: OmniRAN • Go to https://nsn.webex.com/nsn/j.php?J=709002318&PW=NYzFhZWVlOGY2 • Tue, 2014-03-18 10:30-12:30 Beijing, China / Mon, 2014-03-17 10:30PM - 12:30AM ET • Meeting Number: 704 175 522, Meeting Password: OmniRAN • Go to https://nsn.webex.com/nsn/j.php?J=704175522&PW=NMzYyM2E3ZGY1 • Thu, 2014-03-20 08:00-10:00 Beijing, China / Wed, 2014-03-19 08:00 - 10:00 PM ET • Meeting Number: 703 027 008, Meeting Password: OmniRAN • Go to https://nsn.webex.com/nsn/j.php?J=703027008&PW=NMDQ3ZGViN2Yx • Thu, 2014-03-20 10:30-12:30 Beijing, China / Wed, 2014-03-19 10:30PM - 12:30AM ET • Meeting Number: 700 607 134, Meeting Password: OmniRAN • Go to https://nsn.webex.com/nsn/j.php?J=700607134&PW=NZDg1NzRjZWU4

4. Agenda Proposal for March 2014 Session • Approval of minutes • Reports • Example contributions to the intended specification • Outline of the intended specification • Organization of the work • Cooperation with the other IEEE 802 WGs • Operation within IEEE 802.1 • Location of May 2014 session • Conference calls until May 2014 session • Motion to extend the ECSG until July 2014 • Liaison report to IEEE 802 WGs • AOB

5. Guidelines for IEEE-SA 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. --------------------------------------------------------------- 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 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. This slide set is available at https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.ppt

6. Link to IEEE Disclosure of Affiliation http://standards.ieee.org/faqs/affiliationFAQ.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/pat-slideset.ppt Resources – URLs

7. IEEE 802 is a world-wide professional technical organization Meetings are to be conducted in an orderly and professional manner in accordance with the policies and procedures governed by the organization. Individuals are to address the “technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter. Meeting Etiquette

8. LMSC Operations Manual 4.3 Study groups 4.3.1 Study group operation Progress of each Study Group shall be presented at the closing Sponsor meeting of each IEEE 802 LMSC plenary session by the appropriate WG, TAG, or ECSG Chair. Study Groups may elect officers other than the Chair, if necessary, and will follow the general operating procedures for WGs specified in the IEEE 802 LMSC WG P&P. Because of the limited time duration of a Study Group, no letter ballots are permitted. 4.3.2 Voting at study group meetings Any person attending a Study Group meeting may vote on all motions (including recommending approval of a PAR). A vote is carried by 75% of those present and voting “Approve” or “Disapprove.”

9. OmniRAN ECSGResources • Website:http://www.ieee802.org/OmniRANsg/ • Document Archive on mentor: https://mentor.ieee.org/omniran/documents • Email reflector: ecsg-802-omniran@listserv.ieee.org • Email archive: http://grouper.ieee.org/groups/802/OmniRANsg/email/ • Attendance:Paper list (normative) + IMAT • IMAT mandatory for participants seeking attendence credits • Reciprocal rights for most WGs

10. Agenda for March 2014 Session • Approval of minutes • Reports • Example contributions to the intended specification • Outline of the intended specification • Organization of the work • Cooperation with the other IEEE 802 WGs • Operation within IEEE 802.1 • Location of May 2014 session • Conference calls until May 2014 session • Motion to extend the ECSG until July 2014 • Liaison report to IEEE 802 WGs • AOB

11. Mar 2014 Agenda Graphics

12. Call Meeting to Order Attendance recording Attendance recording done by paper sheet IMAT attendance recording for the purpose to gain attendance credit in the home WG Secretary position Nobody volunteered; remains open Juan Carlos volunteered to create minutes Approval of agenda See slide 10 Opening, technical topics on Tue, SDN in SDN BoF, project organization and motions on Thur AM2 Agenda proposal was approved without modifications. Approval of minutes https://mentor.ieee.org/omniran/dcn/14/omniran-14-0018-00-ecsg-minutes-of-omniran-ec-sg-teleconference-of-2014-02-26.docx Minutes approved without comments brought up. Reports Chair reported about short presentation and discussion in IEEE 802.1 on Monday morning. https://mentor.ieee.org/omniran/dcn/14/omniran-14-0021-00-ecsg-mar-2014-802-1-opening-report.pptx Essential slides of the presenation contained in this slide deck on the following 2 pages Discussion concluded that a motion should be brought up in the closing 802.1 plenary on Thursday to establish OmniRAN P802.1CF as a task group in IEEE 802.1. Business #1

13. OmniRAN EC SG Status and Outlook • OmniRAN PAR proposal on IEEE 802.1CF Recommended Practice: ‘Network Reference Model and Functional Description of IEEE 802 Access Network’ was approved by IEEE 802 EC on November 15th, 2013 • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0096-00-ecsg-approved-par-clean.pdf • The PAR is on the NesCom agenda for approval on March 26th, 2014 • IEEE 802.1CF project starts after NesCom approval • OmniRAN EC SG was extended in November 2013 until March 2014 to take care of the PAR approval by NesCom. • OmniRAN EC SG will ask for another extension in the EC closing plenary, just for the case that NesCom asks for additional input. • BTW: A Study Group is disbanded upon approval of the PAR by the IEEE-SA Standards Board.

14. OmniRAN after the approval of the P802.1CF PAR • The Executive Committee Study Group is disbanded by the NesCom approval of the PAR. • The OmniRAN group of people likes to avoid ‘hibernation’ between March 26 and the July 2014 IEEE 802 plenary and seeks to continue the work on the following topics: • Network Detection and Selection • Discussions with 802.1 Sec TG, 802.3, 802.11 and 802.15 • Point-to-point links across bridged infrastructures • P802.1AEcg: Ethernet Data Encryption devices (Mick Seaman) • Using PBB-TE (with and without MiM) w/ OpenFlow or SNMP for control (Paul Bottorff) • Scope of specification work on SDN in P802.1CF • How to enable continuation of the work in IEEE 802.1? • Can the chair of 802.1 establish the P802.1CF project and appoint an interim chair, when the PAR is approved? • Should we come up with some motion in the 802.1 closing plenary on Thursday?

15. Business #2 • Example contributions to the intended specification • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0024-00-0000-an-setup.pptx • Slides should make explicit reference to 802.19.1 • First showing functions in legacy environment, SDN scenarios added after • Only functions to be shown which are available by existing IEEE 802 standards • Gaps may be indicated only for informational purposes • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0019-01-0000-example-network-detection-selection-and-point-to-point-link-text.pdf • Format of the document is inappropriate for an individual contribution • Word template with formatting according to the IEEE specification formatting required • Should show usual individual contribution disclaimer sheet as first page • Only own content to be resubmitted in new template as .docx file to allow reuse • Proposed text is not complete yet. Specification to be focused on Layer 2 connectivity between terminal/station and DL SAP at the first hop router. • Outline of the intended specification • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0013-01-0000-omniran-toc-update.pptx • Proposals require further discussions • Introducing Reference Points as separate sections seems to be redundant as already contained in network reference model • Grouping of functions discussed but no final agreement reached • Consensus on the need for further discussions. Agreement on ToC is not yet reached.

16. Business #3 • Organization of the work • Cooperation with the other IEEE 802 WGs • Chair reported about presentation to 802.11 ARC on Tue 0800-0900 • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0023-00-0000-omniran-cross-wg-cooperation-example-nds.pptx • Discussion in 802.11 brought up a couple of technical issues • necessity of exposing ANI • Support of multilink operation (terminals with multiple IEEE 802 interfaces) • Demand for support by 802.11 subject matter experts received, but ARC requires more detailed input for coming to a conclusion • Operation within IEEE 802.1 • Location of May 2014 session • Conference calls until May 2014 session • The three preceeding topics were handled together by the following slides: • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0027-00-ecsg-omniran-ecsg-proposals-towards-ieee-802-1.pptx • Group agreed to meet with 802.1 TGs at the interim in Norfolk • Discussion of proposed slide set let to a revision with multiple amendments. • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0027-01-ecsg-omniran-ecsg-proposals-towards-ieee-802-1.pptx • Motion to forward the document to 802.1 unanimously approved.

17. Business #4 • Motion to extend the ECSG until July 2014 • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0028-00-ecsg-mar-2014-ec-closing-motion.pptx • EC SG unanimously approved to forward motion to EC closing meeting. The amended document was send to the EC: • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0028-01-ecsg-mar-2014-ec-closing-motion.pptx • Liaison report to IEEE 802 WGs • A draft of the liaison report was assembled containing a slide on the OmniRAN EC SG status, a slide on the future set-up in 802.1 (to be finalized after the 802.1 closing plenary), a slide on the envisioned activities until July plenary and a slide on the Wireless SDN BoF. • Chair will create final report after the 802.1 closing plenary with latest information. • AOB • Chair brought up the ITU-R liaison on future communication network architectures to announce a discussion in the next teleconference on a potential response of IEEE 802. • https://mentor.ieee.org/omniran/dcn/14/omniran-14-0014-00-0000-itu-r-347rev2e-ls-eos.docx • Adjourn • The session was adjourned at 12:27.