1 / 20

IEEE 802.1 OmniRAN TG June 21 st , 2016 Conference Call

IEEE 802.1 OmniRAN TG June 21 st , 2016 Conference Call. 2016-06-21 Max Riegel, Nokia (TG Chair). Tuesday, June 21 st , 2016 at 09:30-11:00am ET Join WebEx meeting: https:// nokiameetings.webex.com/nokiameetings/j.php?MTID=mb5d33a04fdf3b6622dcb295f00cd8a42 Meeting number: 954 102 294

davishenry
Télécharger la présentation

IEEE 802.1 OmniRAN TG June 21 st , 2016 Conference Call

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IEEE 802.1 OmniRAN TGJune 21st, 2016 Conference Call 2016-06-21Max Riegel, Nokia (TG Chair)

  2. Tuesday, June 21st, 2016 at 09:30-11:00am ET Join WebEx meeting: https://nokiameetings.webex.com/nokiameetings/j.php?MTID=mb5d33a04fdf3b6622dcb295f00cd8a42 Meeting number: 954 102 294 Meeting password: n9aJGy75 Join by phone Access code: 959 869 785 +1 972 445 9814 United States (Dallas) Global call-in numbers https://nokiameetings.webex.com/nokiameetings/globalcallin.php?serviceType=MC&ED=432983242&tollFree=0 Conference Call

  3. 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

  4. 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 Bylawshttp://standards.ieee.org/develop/policies/bylaws/sect6-7.html#6 • IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/develop/policies/opman/sect6.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

  5. 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 Call for Potentially Essential Patents

  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, 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.

  7. 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

  8. Review of minutes Budapest F2F minutes Reports 5G SC status P802.1CF contributions Review and acceptance of updated contributions Revision of 802.1CF editor's draft Conclusion on updated content Further plans Agenda for the upcoming F2F meeting AOB Agenda proposal

  9. Business#1 • Call Meeting to Order • Meeting called to order by chair at 09:30 AM ET • Minutes taker: • Walter is taking notes • Roll Call

  10. 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 Nobody spoke up Call for Potentially Essential Patents

  11. Review of minutes Budapest F2F minutes https://mentor.ieee.org/omniran/dcn/16/omniran-16-0034-00-00TG-may-2016-f2f-meeting-minutes.docx Reports 5G SC status P802.1CF contributions Review and acceptance of updated contributions https://mentor.ieee.org/omniran/dcn/16/omniran-16-0039-00-CF00-key-concepts-of-accounting-and-monitoring.pptx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0038-00-CF00-sdn-chapter.docx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-00-CF00-an-setup-over-unlicensed-band.docx https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-00-CF00-network-function-virtualization.docx Revision of 802.1CF editor's draft Conclusion on updated content Further plans Agenda for the upcoming F2F meeting AOB Agenda

  12. Business #2 • Review of minutes • Budapest F2F minutes • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0034-00-00TG-may-2016-f2f-meeting-minutes.docx • No comments raised to the minutes when showing the document. • Reports • 5G SC status • Chair reported about the focus of 5G SC to only address option 4 (IMT-2020 submission of 802.11 together with external SDO) and a variant of option 1 making use of ITU-R WP-5A work item on RLAN to establish IEEE 802 technologies as non-IMT-2020 complement to 5G • A special session is being prepared for the upcoming San Diego F2F meeting to discussion WP-5A approach and potential specification demand on networking aspects. • Rich Kennedy (chair of RR-TAG) as well as Yonggang Fang (presenter of proposal at the Waikoloa meeting) have been invited for the special meeting. Final confirmation of Rich is pending. • Other reports • No other reports given

  13. Business #3 • P802.1CF contributions • Review and acceptance of updated contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0039-00-CF00-key-concepts-of-accounting-and-monitoring.pptx • Wang Hao presented through slides based on the functional description template his thoughts on the chapter content. The proposed content was well received with discussion coming up on how the chapter would describe performance management aspects going beyond plain layer 1&2 aspects of IEEE 802 technologies. • A written contribution based on the presented thoughts was invited for the San Diego meeting. Performance managements aspects will be more thoroughly discussed based on the written contribution. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0038-00-CF00-sdn-chapter.docx • The chair introduced the updated contribution of Antonio showing the amendments which were added due to the discussions in the Budapest F2F meeting. As all open issues has been addressed in the revision, the group agreed to include this contribution as complete replacement of the previous text in the editor’s draft D0.1

  14. Business #4 • P802.1CF contributions, cont. • Review and acceptance of updated contributions • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0036-00-CF00-an-setup-over-unlicensed-band.docx • Yonggang presented his proposal for text replacing the current section 7.1.4 with new text on Access network setup and release procedure as well as proposing a new chapter 7.1.5 on Virtual access network instantiation and release procedure. • Discussion of 7.1.4 text proposal brought up a few serious issues of making ambiguous use of terminology and references to non-defined network elements. Yonggang was asked to deliver a revision cleaning up the use of ‘service provider’ by replacing it where appropriate by ‘access network operator’ and by removing ‘SPN’ in all the messaging flows. Service provider related information may be made available by manual configuration in the NMS. • The group agreed to replace current chapter 7.1.4 by the proposed text when a revision is submitted within the next week addressing the discussed ambiguities. • No conclusion could be reached regarding proposal for 7.1.5 as during Budapest F2F it was concluded that network instantiation does not belong to the scope of chapter 7 functional description. However it was agreed to address the topic in an annex to the specification. Discussion on the content of such annex eventually adoption proposed text for 7.1.5 will continue in San Diego F2F. • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0037-00-CF00-network-function-virtualization.docx • The discussion of the text proposal on NFV was postponed to San Diego F2F due to running out of time. • Group agreed to extend the conference call by 30mins to allow for completion of urgent business.

  15. Business #5 • Revision of 802.1CF editor's draft • Conclusion on updated content • The following contributions will be adopted for the creation of D0.1: • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0008-04-CF00-text-proposal-for-fdm.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0025-03-CF00-nrm-for-nms-and-virtualization.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0038-00-CF00-sdn-chapter.docx • https://mentor.ieee.org/omniran/dcn/16/omniran-16-0006-00-CF00-jan-2016-d0-0-comment-resolution.xls • All issues marked by ‘for further discussions’ have been solved by dedicated contributions and can be considered as closed. Proposed remedies are contained in the related contributions. • Chapter 7.1.4 as provided by revision of Yonggang • For inclusion into D0.1 it is necessary to have revised and agreed text for 7.1.4 available latest July 3rd.

  16. Business #6 • Further plans • Create D0.1 until about July 8th • It was agreed that Walter would create D0.1 adopting the contributions as listed before until July 8th • Following a short editorial review by the contributors D0.1 will be uploaded to P802.1CF drafts directory http://www.ieee802.org/1/files/private/cf-drafts/ for public reference • Further input addressing deficiencies or empty sections of the D0.1 will be invited for July F2F on base of the D0.1 document • OmniRAN TG will agree on revised or new content for the specification during the San Diego plenary meeting. • Revised or new text contributions are expected for San Diego F2F on • Association and disassociation • Authentication and trust establishment • Accounting and monitoring • Authorization, QoS and policy control • It is planned to create D0.2 adopting agreed outcome of San Diego plenary until Aug 8th to start initial 30days TG ballot • Comment resolution will start in the September OmniRAN interim meeting (potentially in Warsaw) • A comment resolution committee might meet together with the other 802.1 TGs to address comments from 802.1 participants in F2F meetings in York

  17. Business #7 • Agenda for the upcoming F2F meeting • Agenda proposal and session graphics on next two slides • AOB • Chair will create short (less than 2000 words) OmniRAN contribution to IEEE Standards Education eZine until submission deadline on July 1st • Meeting adjourned by chair at 11:34AM

  18. July 2016 Agenda Graphics

  19. Agenda proposal for July 2016 F2F • Review of minutes • Reports • Review of 802.1CF-D0.1 editor’s draft • Contributions addressing issues of 802.1CF–D0.1 • Revised and new P802.1CF contributions • Contributions proposing new content • Plan for 802.1CF-D0.2 draft • Bug fixes • New content • Timeline and plan for initial TG ballot • Project planning • Timeline • External reviewers of 802.1CF-D0.2 • Contributions to 5G SC • Status report to IEEE 802 WGs • AOB

  20. Outline for eZine contribution>for further discussion< • Introduction • Evolving role of IEEE 802 technologies for access networks • 3-stage network standardization approach • Benefit of architectural description for deployments and standardization • Short overview of P802.1CF concepts • Benefits of P802.1CF SDN, NFV and for network management and operation • Conclusion and outlook

More Related