1. ARC-agenda-july-2015 Date: 2015-07-16 Authors: July 2009
doc.: IEEE /0840r0
ARC-agenda-july-2015
Date:
Authors:
David Bagby, Calypso Ventures, Inc.

2. Agenda for: ARC SC, July 2015, Waikoloa, HI, USA
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, July 2015, Waikoloa, HI, USA
David Bagby, Calypso Ventures, Inc.

3. IEEE 802.11 Architecture Standing Committee
Agenda
July 2015 session
Chair: Mark Hamilton (Ruckus Wireless)
Vice Chair: Joe Levy (InterDigital)

4. Monday, July 13th, PM2

5. Attendance, etc. Reminders to attendees:
Sign in for .11 attendance credit
Noises off
No recordings

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

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

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

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 – July 2015 Monday, July 13, PM2 Wednesday, July 15, AM1
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – July 2015
Monday, July 13, PM2
Administrative: Minutes
Updates, no action expected:
IEEE 1588 mapping to IEEE
IETF/802 coordination (PAWS, CAPWAP)
as a component in a (larger) system: 11-15/0593r0
in 5G /0842r1
Comments/updates to tutorial information (being presented tonight)?
MIB attributes Design Pattern /0355r3, 11-15/0891r0
Wednesday, July 15, AM1
DSAF concept, DS_SAP normative, Annex R updates: 11-15/0555r2
Updates to REVmc Figure 5-1, et al /0540r1
An AP doesn’t have a MAC SAP!?
802.1AC draft review/discussion, as needed
AP/DS/Portal architecture and 802 concepts
Future sessions / SC activities
Joint session with TGak and 802.1, Thursday, July 16, AM1
Architectural view of 11ak Bridged LAN /0454r0
David Bagby, Calypso Ventures, Inc.

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

12. IEEE 1588 mapping to IEEE
Update (Mark Hamilton)

13. IETF/802 coordination Dorothy Stanley present topics of interest:
PAWS update
CAPWAP draft(s) update
Other?

14. 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.”
Material for tutorial Monday EVE
feedback to presenters?

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

16. Wednesday, July 15th, AM1

17. REVmc DS_SAP normative update
Updates to new/moved Figure R-1
See arc-normative-ds-sap-proposal.docx

18. REVmc Clause 5 Updates to REVmc Figure 5-1, et al
Recap first (agreed) figures
Pick back up on AP role-specific behavior representation
An AP has no MAC SAP !!??
arc-updates-to-revmc docx

19. 802.1AC revision
Update on 802.1AC D2.1 WG Ballot (
Closed July 9
Results:
30 responses received on the D2.0 WG ballot (vs 27 on D1.0)
8 responses received on the D2.1 WG recirculation ballot
50 Voters – of which 30 have responded (60%)
16 Approve 89% (D1.0: 46%)
2 Disapprove 11% (D1.0: 54%)
12 Abstain 40%
got enough responses (60% > 50%)
passed (89% < 75%)
Comments and Resolution sheet:
Presentations for discussion (to be updated, as presentations come in):
None, as of yet?
Reference presentations (previously reviewed, current status of thinking):
Make DS_SAP normative?
More DS considerations:

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

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

22. 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
Design Pattern for “*Implemented” and “*Activated” MIB attributes
How to capture data/control/management models, so is usable as a component; consider standardized mgmt. accesses
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.

23. Planning for September 2015
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 sessions
No teleconferences – will schedule with 10 days notice if an ballot happens that needs a response/discussion

24. Thursday, July 16th, AM1
Joint session with TGak and 802.1
See TGak for detailed agenda