1. OmniRAN EC SG Agenda and Meeting Slides September 2013, Nanjing, China
Michael Montemurro (BlackBerry)
acting on behalf of Max Riegel
(EC SG Chair)

2. Meeting Tuesday, Sept 17th, 19:30 – 21:30 Meeting Room: 307
September 2012
doc.: IEEE /0996r3
Meeting
Tuesday, Sept 17th, 19:30 – 21:30
Meeting Room:
307
Conference Call:
Call-in number: 1-(972) (US)
Global numbers:
Conference Code: #
WebEX
Meeting Number:
Meeting Password: omniRAN
Connect to WebEX:
Stephen McCann, RIM

3. 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 or visit
See IEEE-SA Standards Board Operations Manual, clause 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

4. Resources – URLs Link to IEEE Disclosure of Affiliation
September 2012
doc.: IEEE /0996r3
Resources – URLs
Link to IEEE Disclosure of Affiliation
Links to IEEE Antitrust Guidelines
Link to IEEE Code of Ethics
Link to IEEE Patent Policy
Clint Chaplin, Chair (Samsung)

5. September 2012
doc.: IEEE /0996r3
Meeting Etiquette
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.
The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control.
The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners.
It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form.
Stephen McCann, RIM

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

7. OmniRAN ECSG Resources
Website:
Document Archive on mentor:
reflector:
archive:
Attendance registration: Roll call to allow for remote participation

8. Agenda for September 2013 F2F
doc.: IEEE /0996r3
Agenda for September 2013 F2F
Call Meeting to Order
Secretary position
Attendance recording
Approval of agenda
Approval of minutes
Reports
Discussions with 802.1
Communication with IETF
Communication  with ONF
Content of ‘Stage 2’ document
Legacy guidance
WiMAX NWG Stage 2
Initial draft ToC of IEEE 802 ‘Stage 2’
PAR & 5C texting
Report to IEEE mid-week plenary
AOB
Adjourn
Stephen McCann, RIM

9. Business#1 Call Meeting to Order Secretary position:
Appointment of recording secretary:
Roll Call
Name
Affiliation
* denotes remote participation

10. Business #2 Approval of agenda: Approval of minutes: Reports:
IEEE 802 EC Geneva Jul 13 closing meeting decision
OmniRAN EC SG got extension for creation of PAR & 5C proposal (EC Motion passed by 13/0/1)
Tony Jeffree indicated that could be a “host” for this effort.
OmniRAN meeting planing for delivery of PAR & 5C proposal
See next slide

11. OmniRAN Meetings until November 2013 as agreed in Aug 7th conference call
Wed, Sep 4th, 2013, F2F Meeting York, UK w/ remote participation
Tue, Sep 17th, am ET/ Nanjing, F2F session w/ remote participation
Fri, Sep 27th, 2013, 09-11am ET: Confcall
Fri, Oct 4th, 2013, 09-11am ET: Confcall
Thu, Oct 10th, 2013, 09-11am ET: Confcall
Fri, Oct 11th, 2013, CoB: Submission deadline for PAR to EC list
Mon, Nov 11th, am CT: EC Opening Meeting Dallas F2F
Meeting announcements, agenda proposals and dial-in details for all meetings are published on OmniRAN web site.

12. Business #3 Reports Discussions with 802.1 Communication with IETF
Fruitful discussions on Sep 3rd PM with security group on both proposals
Plan to create more detailed functional description on ptp links by use of MACsec
Communication with IETF
Still pending, planned for mid September
Communication  with ONF
Approved communication to ONF to introduce OmniRAN SDN use case to
Word document and executive summary for formal submission created.
OmniRAN SDN use case proposal had to be submitted by way of ONF member companies (NSN (ECSG chair), NEC) as no formal way seems to exist to contribute to ONF discussions out of IEEE SA activities
Clarification necessary whether possibility exists, that OmniRAN can directly communicate into ONF discussion groups

13. Business #4 Content of ‘Stage 2’ document Legacy guidance
Overview by ETSI:
Staged approach for service network specification by ITU-T:
Specification, which was mainly referenced for Geneva presentations and discussions
Detailed description of Stage 2 by ITU-T:
Q.65 contains detailed description of pieces comprising a Stage 2 specification
The structure of a Stage 2 ToC can directly be derived from this specification
WiMAX NWG Stage 2
Example of Stage 2 specification build on generic requirements captured in tenets:
‘SHALLs’ as stated in the Tenets section of WMF NWG Stage 2 are not appropriate for an IEEE SA Recommended Practice. No single SHALL shall appear in a Recommended Practice

14. ‘Stage 2’ Definition by ITU-T Q.65
The Stage 2 defines
a functional model using functional entities,
the functional entity actions needed,
information flow or API calls between functional entities
recommendations for the allocation of functional entities to physical locations for a few examples.
The Stage 2 provides
a single functional specification which can be applied in a number of different physical realizations,
a precise definition of functional capabilities and their possible distribution in the network to support the required network capabilities,
a detailed description of what functions, information flows and API calls will be provided, but not how they are to be implemented,
requirements for protocol capabilities as input to Stage 3 of the method.
The output of Stage 2 is used by
protocol designers to specify the protocols between physical entities,
node designers to specify the functional requirements of the nodes,
network planners.

15. Business #5 Content of ‘Stage 2’ document, cont.
Initial draft ToC of IEEE 802 ‘Stage 2’
Introduction and Scope
Abbreviations/Acronyms, Definitions, and Conventions
References
Identifiers
Tenets for IEEE 802 Access Network Systems
Network Reference Model
Overview
Reference Points
Access Network to Core Internetworking Relationship
Functional Design and Decomposition
Network Discovery and Selection
Authentication
Link establishment
QoS and policy control
Link relocation
Link teardown
Accounting

16. IEEE 802 Network Reference Model with Reference Points
Terminal R2
Access
Ctrl
Internet R1 R3 R3
Authentication
Authorization
Accounting
Location
CoA
Mobility
Encapsulation
DataPath
Access
Core
Transport
Reference Points represent a bundle of functions between peer entities
Similar to real network interfaces
Functions are extensible but based on IEEE 802 specific attributes
Access R3
Access
Ctrl
Internet R3 R5 R4

17. IEEE 802 Access Network Functions
L2 Configuration
AAA Policy
DHCP
Application
Scanning
ANQP
Network Selection
Association
Authentication
Authorization
Link Establishment
Accounting
Host Configuration
Application
Policy Control
Link Relocation
Application
Host Config Release
Disassociation
Link Teardown
Accounting
Access Technology
Control I/f

18. Business #6 PAR and 5C texting Report to IEEE 802.11 mid-week plenary
Result out of York meeting uploaded to mentor after the meeting under
Further amendments proposed by
Report to IEEE mid-week plenary
AOB
Adjourn