1. ARC-SC-agenda-Mar-2016 Date: 2016-03-16 Authors: July 2009
doc.: IEEE /0840r0
ARC-SC-agenda-Mar-2016
Date:
Authors:
David Bagby, Calypso Ventures, Inc.

2. Agenda for: ARC SC, March 2016, Macau SAR, China
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, March 2016, Macau SAR, China
David Bagby, Calypso Ventures, Inc.

3. IEEE 802.11 Architecture Standing Committee
July 2009
doc.: IEEE /0840r0
IEEE Architecture Standing Committee
Agenda
March 2016 session
Chair: Mark Hamilton (Ruckus Wireless)
David Bagby, Calypso Ventures, Inc.

4. Monday, March 14th, PM2 July 2009 doc.: IEEE 802.11-09/0840r0
David Bagby, Calypso Ventures, Inc.

5. Attendance, etc. Reminders to attendees:
July 2009
doc.: IEEE /0840r0
Attendance, etc.
Reminders to attendees:
Sign in for .11 attendance credit
Noises off
No recordings
David Bagby, Calypso Ventures, Inc.

6. Participants, Patents, and Duty to Inform
July 2009
doc.: IEEE /0840r0
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
David Bagby, Calypso Ventures, Inc.

7. July 2009
doc.: IEEE /0840r0
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 Bylaws
IEEE-SA Standards Board Operations Manual
Material about the patent policy is available at
If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at or visit
This slide set is available at
David Bagby, Calypso Ventures, Inc.

8. Call for Potentially Essential Patents
July 2009
doc.: IEEE /0840r0
Call for Potentially Essential Patents
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
David Bagby, Calypso Ventures, Inc.

9. 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 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details.

10. ARC Agenda – March 2016 Monday, Mar 14, PM2 Wednesday, Mar 16, AM1
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – March 2016
Monday, Mar 14, PM2
Administrative: Minutes
as a component in a (larger) system/5G/IMT-2020: 11-15/0757r1, 11-15/0593r2, 11-15/0842r1, 11-15/1133r0, 11-15/1266r1, 11-15/1376r2
Wednesday, Mar 16, AM1
TGaq architecture discussion update 11-16/0239r3
as a component in a (larger) system/5G/IMT-2020: 11-15/0757r1, /0593r2, 11-15/0842r1, 11-15/1133r0, 11-15/1266r1, 11-15/1376r2
Wednesday, Mar 16, PM1
Updates, no action expected: IEEE 1588 mapping to IEEE
IETF/802 coordination: update on multicast over : 11-15/1261r2
802.1AC status update
AP/DS/Portal architecture and 802 concepts /0454r0, /1213r1 (slides 9-11)
TGak joint topics on architecture – 11-16/0457r0
MIB attributes Design Pattern /0355r3, 11-15/0891r0
Future sessions / SC activities
Joint session with TGak and 802.1, Thursday, Mar 17, AM1
David Bagby, Calypso Ventures, Inc.

11. Jan 2009
doc.: IEEE /1455r0
ARC Minutes
January Minutes:
David Bagby, Calypso Ventures, Inc.

12. as a “component”
Is usable as a component in a (larger?) system, or should it be:
“It should be possible to swap implementations of the component from different sources provided those implementations are compliant to the defined functions and external interfaces.”
How to capture data/control/management models, so is usable as a component
What is the goal/who is the customer, for this effort?
Start with requirements… Analyze current situation, gap… Then go!
as a “generic” component
as a 3GPP component
802/ as a RIT/SRIT in IMT-2020
Process/organization/structure discussions
Management of an ESS (as a ‘black box’)?
Especially incorporation of a locally managed ESS into a larger 5G system (management of quality, and timeliness; and tested) }
Are these all aligned,
in reality?

13. 802.11 as a “component” discussion
Broad use cases potentially, and/or focus on 3GPP/5G/IMT-2020
Relate to IEEE-SA work on ‘IEEE role in 5G’
Relate to IEEE ComSoc work on ‘IEEE role in 5G’
802 EC has kicked off a Standing Committee to discuss
If 802 doesn’t do a (joint) submission, could independently
Discussion of Joe Levy’s brainstorming presentation (11-16/376)

14. Wednesday, March 16th, AM1

15. OR: Is all this “Have 802.18 do their job?”
EC SC could consider:
“IEEE 5G”
Work with WP 5D (5G/IMT-2020) on:
Contribute to IMT-2020 as:
Single technology
Multiple technologies
One or more technologies via some other body (i.e., 3GPP)
[Add?]: Work with WP 5A directly, on spectrum usage
[Add?]: Work with Study Group 5/Task Group 5/1 on GHz allocations and sharing studies to use it
OR: Ask to have the SC just “figure out how to talk to ITU-R to reach the goal of getting appropriate spectrum”?
OR: Is all this “Have do their job?”

16. Wednesday, March 16th, PM1

17. IEEE 1588 mapping to IEEE
Update (?)

18. IETF/802 coordination Dorothy Stanley present topics of interest:
Multicast traffic features of
Any update, or further action needed? – none
Draft will be made available, goal is for April
CAPWAP
Draft for n has expired
Draft alternate tunnel - is unchanged and not clear status/will continue.
No actions requested at this time
Other?
Next meeting IETF 3-8 April 2016
Request to update /.15 IETF Tutorial and projects underway and work of joint interests – Dorothy and Charlie will be generating the document.
BOF sessions: ITS-related BOF at the April meeting, would be good to track/get report if possible

19. 802.1AC revision Current Status:
There hasn't been a new ballot.
Waiting on the RAC to approve the Ethertype.
Current ballot status: rejected for the second time. 
Presentations for discussion (to be updated, if/as presentations come in):
None

20. AP/DS/Portal architecture and 802 concepts
Presentations on architectural description(s)
None?
Reference presentations (previously reviewed, current status of thinking):

21. Design Pattern for MIB attributes
The WG11 Chair has requested that the ARC SC investigate and create a Design Pattern for MIB attributes of the form “*Implemented” and “*Activated”

22. General Links
Donald Eastlake present topics of interest from TGak and 802.1’s parallel work (802.1Qbz)
Topics for joint session on Thursday
arc-some-more-ds-architecture-concepts.pptx

23. 802.11aq (PAD)
Any updates, or further collaboration suggested?

24. ARC Future Activities & sessions
ARC SC meets when a specific focused task is requested of the SC for which the is sufficient volunteer interest.
Continue work on architectural models, and liaison with TGs in development of their architecture as appropriate
How to capture data/control/management models, so is usable as a component; consider standardized mgmt. accesses
Participate in 5G/IMT-2020 activities
Design Pattern for “*Implemented” and “*Activated” MIB attributes
Will also follow 802.1/ activities on links, bridging, and MAC Service definition, Comment on 802.1AC revision project changes/proposals
Monitor/report on IETF/802 activities, as needed
Monitor/report on IEEE 1588 activities, as needed
If you have ANY other topic that you would like ARC SC to consider, contact the SC chair.

25. Planning for May 2016 Plan for two individual meeting slots
Usual slot on Wed AM1
Another slot for standalone ARC work (Monday/Tuesday?)
Another slot joint with ak (Thursday’s slot)
Individuals interested in ARC work are encouraged to also attend other TGak or TGaq sessions, and monitor 5G/IMT-2020 activities
One teleconference
Date/time TBD
May schedule another with 10 days notice if discussion warrants

26. Thursday, March 17th, AM1
Joint session with TGak, 802.1
See TGak for detailed agenda