1. ARC-agenda-sep-2014 Date: 2014-09-15 Authors: July 2009
doc.: IEEE /0840r0
ARC-agenda-sep-2014
Date:
Authors:
David Bagby, Calypso Ventures, Inc.

2. Agenda for: ARC SC, September 2014, Athens, Greece
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, September 2014, Athens, Greece
David Bagby, Calypso Ventures, Inc.

3. IEEE 802.11 Architecture Standing Committee
Agenda
September 2014 session
Chair: Mark Hamilton (Spectralink)
Vice Chair: Joe Levy (InterDigital)

4. Monday, September 15th, EVE1

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:
“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
“Personal awareness” means that the participant “is personally aware that the holder may have a potential Essential Patent Claim,” even if the participant is not personally aware of the specific patents or patent claims
“Should inform the IEEE (or cause the IEEE to be informed)” of the identity of “any other holders of such 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
Quoted text excerpted from IEEE-SA Standards Board Bylaws subclause 6.2
Early identification of holders of potential Essential Patent Claims is strongly encouraged
No duty to perform a patent search

7. April 2009
doc.: IEEE /xxxxr0
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
Rich Kennedy, Research In Motion

8. Call for Potentially Essential Patents
April 2009
doc.: IEEE /xxxxr0
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
Rich Kennedy, Research In Motion

9. Other Documents and WebPages to Review
April 2009
doc.: IEEE /xxxxr0
Other Documents and WebPages to Review
Please review the documents at the following links: -  IEEE Patent Policy -  -  Patent FAQ -  -  LoA Form -  -  Affiliation FAQ -
-  Anti-Trust FAQ -  -  Ethics -  -  IEEE Working Group OM - 
New 802 WG P&P:
New 802 LMSC P&P:
New 802 LMSC OM:
Rich Kennedy, Research In Motion

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

11. ARC Agenda – Sept 2014 Monday, Sep 15, EVE1 Wednesday, Sep 17, AM1
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – Sept 2014
Monday, Sep 15, EVE1
Administrative: Minutes
Updates, no action expected:
IEEE 1588 mapping to IEEE
IETF/802 coordination (RFC 4441, PAWS, CAPWAP)
802.1AC revision
Review/Discussion of 802.1AC draft
DS and Portal architecture (and Annex R), with (802.1AC and Bridge) concepts
AP/DS/Portal architecture and 802 concepts
AP’s “Distribution System Access” function concept
Make DS_SAP normative?
Wednesday, Sep 17, AM1
Prepare for Joint TGak session (on Thursday)
MIB attributes Design Pattern
AP/DS/Portal architecture and 802 concepts, continued
Future sessions / SC activities
Joint session with TGak, Thursday, Sept 18, AM1
Architectural view of 11ak Bridged LAN
David Bagby, Calypso Ventures, Inc.

12. Jan 2009
doc.: IEEE /1455r0
ARC Minutes
July Minutes:
Teleconference Minutes:
David Bagby, Calypso Ventures, Inc.

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

14. IETF/802 coordination Dorothy Stanley present topics of interest:
PAWS update
RFC 4441 revision update
RFC 7241 published, obsoletes RFC 4441
CAPWAP draft(s) update
Other?

15. 802.1AC revision Update on 802.1AC D1.0 WG Ballot
Closed July 18
Results: ?? (unofficial: )
Presentations for discussion (to be updated, as presentations come in):
Make DS_SAP normative?

16. AP/DS/Portal architecture and 802 concepts
Presentations on architectural description(s)
Comment in REVmc to include 11-13/115r14’s “Figure 11-14/115-16” in the Standard

17. Wednesday, September 17th, AM1

18. General Links
Donald Eastlake present topics of interest from TGak and 802.1’s parallel work (802.1Qbz)

19. 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”
This is partly in reaction to a discussion of such attributes in TGai.
Discussion started on teleconference on August 26th. To be continued here…

20. 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
Comment on 802.1AC revision project changes/proposals
Design Pattern for “*Implemented” and “*Activated” MIB attributes
Will also follow 802.1/ activities on links, bridging, and MAC Service definition
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.

21. Planning for Nov 2014
Plan for one/two individual meeting slots, plus one slot joint with 802.1/802.11ak
Individuals interested in ARC work are encouraged to also attend other TGak sessions
ARC SC will schedule teleconferences if necessary, with 10 days notice
One telecon likely for Design Pattern work item

22. Thursday, September 18th, AM1
Joint session with TGak
See TGak for detailed agenda