260 likes | 503 Views
OmniRAN EC SG Agenda and Meeting Slides November 2013 , Dallas, TX. 2013-11-14 Max Riegel (ECSG Chair). Tuesday , Nov 12 th , 13:30 – 15:30 Wednesday, Nov 13 th , 08:00 – 10:00 Wednesday, Nov 13 th , 13:30 – 15:30 Thursday, Nov 14 th , 08:00 – 10:00 Meeting Room:
E N D
OmniRAN EC SG Agenda and Meeting SlidesNovember 2013, Dallas, TX 2013-11-14 Max Riegel (ECSG Chair)
Tuesday, Nov 12th, 13:30 – 15:30 Wednesday, Nov 13th, 08:00 – 10:00 Wednesday, Nov 13th, 13:30 – 15:30 Thursday, Nov 14th, 08:00 – 10:00 Meeting Room: Cockrell Meetings
Call Meeting to Order Attendance recording, secretary Approval of minutes Reports Comment resolution and responses on PAR & 5C comments Presentation to closing EC meeting Conditional extension of OmniRAN EC SG Technical presentations on OmniRAN related matters AOB Adjourn Agenda Proposal for Nov 2013 F2F
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
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
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
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.”
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
Call Meeting to Order Meeting was called to order at 13:40 Attendance recording, secretary Nobody volunteered for secretary Juan Carlos taking notes Approval of agenda See next two slides Comment resolution will happen in Wed AM1 and PM1 meeting Technical presentation on Tue PM1 meeting Organizational requirements and liaison activities added to the agenda for Thu AM1 meeting Agenda approved without objections Approval of minutes https://mentor.ieee.org/omniran/dcn/13/omniran-13-0087-00-ecsg-meeting-minutes-for-10-october-2013-teleconference.docx Minutes of Oct 10th call approved without objections Business#1
Meetings Tuesday, Nov 12th, 13:30 – 15:30 Wednesday, Nov 13th, 08:00 – 10:00 Wednesday, Nov 13th, 13:30 – 15:30 Thursday, Nov 14th, 08:00 – 10:00 Meeting Room: Cockrell Approved Agenda: Call Meeting to Order Attendance recording, secretary Approval of minutes Reports Technical presentations on OmniRAN related matters Comment resolution and responses on PAR & 5C comments Organizational set-up requirements Liaison activity Presentation to closing EC meeting Conditional extension of OmniRAN EC SG AOB Adjourn OmniRAN EC SG Plan Nov 2013 F2F
Business #2 • Reports • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0090-00-ecsg-nov2013-opening-report-to-8021.pptx • To introduce OmniRAN to University Outreach participants chair went through complete slideset comprising also slides presented to EC and contained for reporting in this slide deck. • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0089-00-ecsg-nov2013-ec-opening-report.pptx • Short presentation to show content of report • Following reporting slides were skipped as already presented. • Paul Congdon gave verbal report about OmniRAN related activities in ONF • Juan Carlos gave short verbal report about OmniRAN related discussions in the previous IETF meeting.
OmniRAN EC SG Current Status and Objectives • OmniRAN EC SG submitted PAR proposal on ‘Recommended Practice for Network Reference Model and Functional Description of IEEE 802 Access Network’ on October 10th for consideration in the November plenary meeting • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0086-00-ecsg-proposed-par-and-5c.docx • More information on the following slides • It is proposed to run the project within 802.1 WG • No conclusion yet, how this would/should work within 802.1 WG • Technical discussions took place between OmniRAN EC SG and 802.1 (Security TG) in the September interim • OmniRAN EC SG will review comments on PAR proposal and will submit final proposal for the EC closing plenary. • Organizational arrangements of running the project in 802.1 will be discussed during the week (and in the EC workshop on Saturday)
OmniRAN EC SGTimeline Sep Oct Apr’11 May’2 Feb’28 Jun’20 Aug’7 ‘4 ‘17 ‘27 ‘4 ‘10 Initial meeting Use cases contributions Use cases harmonization Requirements within scope of IEEE 802 Gap analysis to existing solutions Socializing of gap analysis Potential standardization topics for IEEE 802 Refine scope of EC SG (crisp words) Plan for PAR proposal submission until Oct’11 Create draft PAR proposal Refine wording of draft PAR proposal Finalize PAR proposal Conf Call F2F meeting Nov’11 Oct’11 Jan Feb Mar Apr May Jun Jul Aug Sep Oct
Creation of the draft PAR proposal • The proposed PAR text was mainly drafted in the interim meeting in York on September 4th and refined by a series of conference calls from mid September to mid October with varying participation by a core team of about 9 people. • The core team represented good interest of big network vendors and operators and was guided by several experienced IEEE standardization professionals. • The PAR proposal was finally approved by the OmniRAN EC SG in a conference call on October 10th with 6 participants, after a call for review comments was send out on October 4th to the OmniRAN EC SG mailing list with about 50 subscribers. The call for comments led to two final comments, which were unanimously resolved in the final call with the commenters being present in the call.
Business #3 • Technical presentations on OmniRAN related matters • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0067-00-0000-omniran-architecture-suggestions.pptx • Presentation created discussions about relation and scope of OmniRAN • Proposal is not comprehensive in providing rationale for the split between control plane and management plane. • 3GPP related examples are out of scope of OmniRAN, as OmniRAN exclusively addresses existing IEEE 802 technologies • Comment resolution and responses on PAR & 5C comments starts in Wed AM1 meeting • Chair will assemble and sort received comments in spreadsheet. • Participants are kindly asked to browse spreadsheet and consider potential solutions before Wed AM1 meeting.
Business #4 • Comment resolution and responses on PAR & 5C comments, cont. • started in Wed AM1 meeting based on comments sheet • Concluded with revision of PAR and explanatory answers to the commenters. • Final motion, see following slide:
Motion #1 • The OmniRAN EC SG approves the documents • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0091-02-ecsg-nov-2013-collected-comments-on-draft-par-proposal.xlsx • https://mentor.ieee.org/omniran/dcn/13/omniran-13-0086-02-ecsg-proposed-par-and-5c.docx as the outcome and the conclusion of the comment resolution on the draft PAR proposal submitted to EC on Oct. 10th subject to editorial clean-up by the chair. Moved: Paul Congdon, Tallac Seconded: Jeffry Handal, LSU Motion carried by 10/0/2
Business #5 • Organizational set-up requirements • See following slides • Liaison activity • Communication should go out to • IETF, ONF, WFA, WBA, WiMAX Forum, ETSI NFV • No immediate need to inform about approval by the IEEE 802
Organizational Considerations • 802.1 is an excellent home for the project due to its competence and central role • The project can’ t be completed by 802.1 alone but requires active contributions from each of the other 802 WGs • So far, the topic was driven mainly by members of the wireless WGs • Question: How to ensure that the engaged people are able/willing to continue?
Organizational set-up • Group status • Project assigned to TG within 802.1 named ‘OmniRAN TG’ • Co-location of F2F sessions • OmniRAN TG SHOULD meet on interims with the wireless WGs • Depending on topic needs OmniRAN TG MAY decide to meet at interim with the other 802.1 TGs • Alignment of meeting schedules • Avoid scheduling OmniRAN at plenary meeting slots of the other WGs • Should meet during usual meeting hours during the day (not regularly pushed out in evening meetings) • Keep F2F meetings focused (usually max 4x 2-hours meetings during a F2F) • Conference calls • Should be used whenever feasible to allow participation out of other WGs • Using WebEX • Setting up an IEEE 802 wide calendar of electronic meetings to avoid collisions • Arrangement of agenda to enable ‘joint’ meetings • Specific text in agenda • Define precisely the question, which should be discussed and clarified • Solicitate participation of experts of other WGs
Organizational set-up • Mailing list • Maintain separate mailing list for OmniRAN • Move over current subscribers to the new list • Attendance credits • Initial voting rights in the TG when moving over to 802.1 to be set up • Attendance credits for teleconferences? • Reciprocal credits for F2F meetings • Communication to the WGs • Liaison person for each of the WGs • Only for communication, no special role in balloting process • Peer groups in the WGs • If peer groups are available (like 11ARC), they should be specifically addressed • Participation in ballots • Commenting in the TG/WG ballots open to whole 802 • Participation in the votings • Voting reserved to the members of 802.1 • Access to the documents • Keep mentor • Submission of documents • Can happen without interception by the TG chair • Maintain current templates
Business #6 • Presentation to closing EC meeting • Chair will put slides together based on material contained in this slide-deck • Extension of OmniRAN EC SG • What happens when PAR gets approved? • See Motion #2 • AOB • No other topics brought up • Adjourn • Adjourned at 10:33am
Outcome of OmniRAN EC SG • Draft PAR proposal (PAR + 5C) submitted to EC on Oct 10th • 44 comments received until Tue, 5pm CT • All comments addressed and resolved • Most leading to modifications in the text of PAR and 5C • Revised PAR proposal submitted to EC before Wed, 5pm CT • Presentation to 802.1 to support the idea that 802.1 is running the project • Discussions in OmniRAN EC SG how to keep interested people engaged in the project • EC SG participants mainly members of the wireless WGs • Results to be discussed with 802.1 and in the EC workshop • Motions:
Continuation of Work • Two options: • Extend OmniRAN EC SG until March 2014 to allow the group to further develop the foundation of the project until PAR is approved by NesCom. • Less preferred solution would be to establish Study Group in IEEE 802.1 to allow OmniRAN to to further develop the foundation of the project until PAR is approved by NesCom. • OmniRAN EC SG prefers to get extension until March because of established environment.
Motion #2 • Extend OmniRAN EC SG until March 2014 to allow the group to further develop the foundation of the project until PAR is approved by NesCom. • Moved: Harry Bims, Bims Labs. • Seconded: Juan Carlos Zuniga, Interdigital • Motion carries by 9y/0n/0a.