1 / 10

OmniRAN EC SG Proposals towards IEEE 802.1

OmniRAN EC SG Proposals towards IEEE 802.1. OmniRAN EC SG Chair: Max Riegel (NSN). OmniRAN EC SG Status and Outlook.

catrin
Download Presentation

OmniRAN EC SG Proposals towards IEEE 802.1

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. OmniRAN EC SG Proposalstowards IEEE 802.1 OmniRAN EC SG Chair: Max Riegel (NSN)

  2. 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. • A Study Group is disbanded upon approval of the PAR by the IEEE-SA Standards Board. • How to establish the OmniRAN P802.1CF within IEEE 802.1?

  3. OmniRAN P802.1CF provides a kind of ‘Stage 2’ Specification for IEEE 802 • The ITU-T defined in its Rec. I.130 a sequential 3 stage process, which is nowadays commonly used in most telecommunication network standardization activities. • A ‘Stage 2’ specification provides a mapping of the existing IEEE 802 protocols to a functional network model, which facilitates easier evaluation and better understanding of end-to-end behavior. ‘External’ requirements from the service/deployment perspective Develop a logical/functional model for evaluation of those requirements Available IEEE 802 specifications of protocols and attributes. ?

  4. Potential ToC of the P802.1CF specification • Introduction and Scope • Abbreviations, Acronyms, Definitions, and Conventions • References • Network Reference Model • Overview • Reference Points • Access Network Control Architecture • Multiple deployment scenarios • Functional Design and Decomposition • Network Discovery and Selection • Association • Authentication and Authorization • Link establishment, relocation and teardown • QoS and policy control • Disassociation • Accounting • SDN Abstraction • Terminal • Access and Backhaul • Annex: • Tenets (Informative) Network Reference Model Functional Description SDN

  5. Example Chapter Structure • Functional Design and Decomposition • Network Discovery and Selection • Generic functional requirements and information flows • Ethernet functional design <- 802.3 • WPAN functional design <- 802.15 • WLAN functional design <- 802.11 • WMAN functional design <- 802.16 • WRAN functional design <- 802.22 • Authentication • Link establishment • QoS and policy control • Link relocation • Link teardown • Accounting

  6. OmniRAN Specification Workspace • The P802.1CF specification provides a kind of functional framework across all IEEE 802 access technologies. • The creation of the OmniRAN P802.1CF specification requires close cooperation with nearly all of the IEEE 802 WGs. • Subject matter experts of the individual WGs should create technology specific input for P802.1CF • A well structured approach (devide and conquer;-) may be necessary to reduce the necessary effort for the individuals. • P802.1CF will have many contributors and part-time participants who are not members of 802.1 • Joint sessions with the other WGs are required to ‘socialize’ the content of the specification to engage review and subject matter experts.

  7. Motion to IEEE 802.1 • Establish the P802.1CF project within a dedicated Task Group to facilitate the appropriate working environment for successful completion of the project.

  8. Further Recommendations to IEEE 802.1 • To leverage the momentum created by the OmniRAN EC SG the new IEEE 802.1 TG dealing with the P802.1CF should • be named ‘OmniRAN TG’ • continue with the OmniRAN filespace on mentor for convenient exchange of documents with members of the other IEEE 802 WGs • be allowed to arrange for reciprocal attendence credits with other WGs • meet when appropriate at interims with the wireless working groups

  9. Envisioned activities of OmniRAN until July F2F • 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) • What kind of specification on SDN in P802.1CF • Meetings, teleconferences • Teleconference (late April, date t.b.d.) • 2 full days F2F meeting in Norfolk, VA • Teleconference (mid June, date t.b.d.)

  10. Motion to IEEE 802.1 • Approve that the upcoming OmniRAN TG can held two teleconferences until the July plenary meeting. The teleconferences have to be announced at least 21 days in advance on the IEEE 802.1 reflector.

More Related