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

2. Agenda for: ARC SC, July 2016, San Diego, California, USA
Jan 2009
doc.: IEEE /1455r0
Abstract
Agenda for: ARC SC, July 2016, San Diego, California, USA
David Bagby, Calypso Ventures, Inc.

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

4. Tuesday, July 26th, AM2 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 – July 2016 Tuesday, July 26, AM2 Wednesday, July 27, AM1
Jan 2009
doc.: IEEE /1455r0
ARC Agenda – July 2016
Tuesday, July 26, AM2
Administrative: Minutes
Update on as a component in a (larger) system/5G/IMT-2020 (EC SC 5G)
IEEE 1588 mapping to IEEE Update, no action expected:
IETF/802 coordination: update, as apporpriate
802.1AC status update; TGak update; TGaq update
“What is an ESS?”
AP/DS/Portal architecture and 802 concepts /0720r0, 11-16/0457r1, 11-15/0454r0, 11-14/1213r1 (slides 9-11)
Wednesday, July 27, AM1
MIB attributes Design Pattern /0355r3, 11-15/0891r0
Drop Eligibility Indicator discussion (Ganesh) (11-16/0713r0)
Future sessions / SC activities
Future topic: Should we, and if so, how, add YANG models to ?
Joint session with TGak, Thursday, July 28, AM1
David Bagby, Calypso Ventures, Inc.

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

12. 802.11 as a “component” discussion
Work moved to EC Standing Committee (“EC SC 5G”)
Update on activities (Joe Levy)
Summary of position and inputs to the committee
Current status of 3GPP/ “integration”
Proposed way forward to work with 3GPP to better “integrate” as a RAT (or RIT in ITU vernacular)

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

14. IETF/802 coordination Dorothy Stanley present topics of interest:
Multicast traffic features of
Any update, or further action needed? – none
Draft is still being revised, goal is for September to be ready for review
CAPWAP
Draft for n has expired
Draft alternate tunnel - is unchanged and not clear status/will continue.
No actions requested at this time
Other?
Last IETF meeting: July 2016 – any last-minute updates/outputs?
Upcoming IETF meeting: Berlin; Leadership coord meeting: Sept 9
Request to update /.15 IETF Tutorial and projects underway, joint work – 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

15. 802.1AC revision Current Status:
Still waiting on the RAC to approve the Ethertype.
Other balloting completed – this is the last item to be done.
Presentations for discussion (to be updated, if/as presentations come in):
None

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

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

18. What is an ESS? Current definition depends on the relationship to LLC
“A set of one or more interconnected basic service sets (BSSs) that appears as a single BSS to the logical link control (LLC) layer at any station (STA) associated with one of those BSSs.”
That would mean a Bridged LAN (for example) creates an ESS. Probably not what we (802.11) meant.
We probably meant something about transparency of “location of attachment”/”mobility”, from whatever is using the MAC
and other entities, necessary to accomplish this? ESS == demarcation of this transparency??
Is it:
Transparent to whatever upper layer is above ?
Includes entities beyond (above?) ? (Like bridges in the 11ak scenario?)
The APs have to have some common/similar configuration settings? (SSID, at least. Probably other facilities (security, etc.) and policies?)
Changes to Figure 4-1: ‘BSS’s are just STAs. These ovals are BSAs. Also, should we be saying “OBSA”?

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

20. Wednesday, July 27th, AM1

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. Drop Eligibility Indicator discussion
- Ganesh Vankatesan
Mark Hamilton, Polycom, Inc.

23. 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
Monitor 5G/IMT-2020 activities of 802
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.

24. Planning for September 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
No teleconferences
May schedule with 10 days notice if discussion warrants

25. Thursday, July 28th, AM1
Joint session with TGak
See TGak for detailed agenda