1. ARC-agenda-minutes-july-2012
doc.: IEEE /0840r0
July 2012
ARC-agenda-minutes-july-2012
Date:
Authors:
Mark Hamilton, Polycom, Inc.
David Bagby, Calypso Ventures, Inc.

2. Jan 2009
doc.: IEEE /1455r0
July 2012
Abstract
Agenda, working document and minutes for ARC SC, July 2012, San Diego, US
Mark Hamilton, Polycom, Inc.
David Bagby, Calypso Ventures, Inc.

3. IEEE 802.11 Architecture Standing Committee
July 2012
IEEE Architecture Standing Committee
Agenda, working document & minutes
July 2012 session.
Mark Hamilton, Polycom, Inc.

4. Attendance, etc. Reminders to attendees:
July 2012
Attendance, etc.
Reminders to attendees:
Sign in for .11 attendance credit
Noises off
No recordings
Mark Hamilton, Polycom, Inc.

5. Participants, Patents, and Duty to Inform
July 2012
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
Mark Hamilton, Polycom, Inc

6. April 2009
doc.: IEEE /xxxxr0
Patent Related Links
July 2012
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
Mark Hamilton, Polycom, Inc
Rich Kennedy, Research In Motion

7. Call for Potentially Essential Patents
April 2009
doc.: IEEE /xxxxr0
Call for Potentially Essential Patents
July 2012
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
Mark Hamilton, Polycom, Inc
Rich Kennedy, Research In Motion

8. Other Documents and WebPages to Review
April 2009
doc.: IEEE /xxxxr0
July 2012
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:
Mark Hamilton, Polycom, Inc
Rich Kennedy, Research In Motion

9. Other Guidelines for IEEE WG Meetings
July 2012
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.
Mark Hamilton, Polycom, Inc

10. ARC Agenda – July 2012 Wednesday, AM1
Jan 2009
doc.: IEEE /1455r0
July 2012
ARC Agenda – July 2012 Wednesday, AM1
Administration
Policies
Attendance
Approve Agenda
Approve Teleconference minutes (12/759r0)
802 Overview & Architecture ballot
Preparation for Joint session on Thursday
“General links” discussion
802.1AC (MAC Service definition) update, discussion
Future sessions / SC activities
Mark Hamilton, Polycom, Inc.
David Bagby, Calypso Ventures, Inc.

11. ARC Agenda – July 2012 Thursday, AM1 – Joint session with 802.1/802.11
Jan 2009
doc.: IEEE /1455r0
July 2012
ARC Agenda – July 2012 Thursday, AM1 – Joint session with 802.1/802.11
“802.11’s MAC service, general links, and making cooperative with bridging”
Process for future sessions/interactions between and
Currently through TGaa, propose ARC/WNG
Liaisons (between 802.1, , IETF)
and bridging
TRILL liaison discussion
Mark Hamilton, Polycom, Inc.
David Bagby, Calypso Ventures, Inc.

12. 802 Organization & Architecture revision
July 2012
802 Organization & Architecture revision
Draft 1.4 is in the members area
Status:
Latest letter ballot completed, July 6. Comment resolution in process this week.
comments are in 12/756r1.
Responses can be found here: < not completely up-to-date>
All technical issues resolved on Monday, except one
One technical was rejected – will come back at appropriate time. Other two were accepted. Like to review in detail?
[ Chair update: actually all technical comments were agreed. See r2 of the response document. ]
Intending to request Conditional Approval for SB out of this meeting
Mark Hamilton, Polycom, Inc.

13. July 2012
Prepare for 802.1/ Joint
General theme: “802.11’s MAC service, general links, and making cooperative with bridging”
Liaison with is currently through TGaa
Process for future sessions/interactions between and 802.1
Proposal: Use ARC or WNG - Handle case-by-case.
Any remaining business related to 802.1AVB?
and bridging (Norm Finn presentation)
Other discussion topics:
Liaisons between 802, , and IETF (IESG meeting next week)
TRILL liaison discussion
Mark Hamilton, Polycom, Inc.

14. 802.11 “General Links” Donald Eastlake presentation July 2012
Mark Hamilton, Polycom, Inc.

15. 802.1AC – MAC Service Definition
July 2012
802.1AC – MAC Service Definition
Undergoing revision (in Sponsor Ballot process)
There are differences between general 802 MAC definition and definition
In particular, “drop_eligible” (cf TGaa)
Comment to REVmc to look at this for alignment
Any discussion or comments from this group?
Mark Hamilton, Polycom, Inc.

16. ARC Future Activities & sessions
July 2012
ARC Future Activities & sessions
SC Chair & WG Chair agree the ARC SC meets when a specific focused task is requested of the SC for which the is sufficient volunteer interest.
Ongoing, have been and will continue to follow 802 O&A balloting activities.
Will also follow 802 activities on links, bridging, MAC Service definition and TRILL liaison
If you have ANY other topic that you would like ARC SC assistance with, contact the SC chair.
Mark Hamilton, Polycom, Inc.

17. Planning for Sept 2012 Plan for one meeting slot
July 2012
Planning for Sept 2012
Plan for one meeting slot
ARC SC will schedule teleconferences with 10 days notice
To discuss any specific requests that arise
No teleconference anticipated at this time
Mark Hamilton, Polycom, Inc.

18. July session minutes July 2012 Wednesday July 18, 2012
Patent policy reviewed. Call for essential patent knowledge, no indications.
Minutes of teleconference approved as posted (12/759r0)
Noted that will hold a discussion of IEEE P on Thursday AM2
Reviewed status of 802 O&A ballot, per slide #12 above. Noted that we have several contacts in the Sponsor Pool: Mark, Jon, Bruce, Adrian, Hunter
Discussed joint meeting with tomorrow:
Yes, some 802.1AVB remaining issues, to fix discussion in 802.1Q about .11aa and .1AVB usage. Alex has put a comment into the 802.1Q corrigenda ballot on this.
What is the status of the 802.1Q corrigenda? Can we fix all the outdated .11 references? Alex and Bruce are in the ballot pool.
Ongoing, we should be more diligent about ballot pool invitations for 802/802.1 ballots (and could help point these out).
Why is 802.1AC being created? What is its balloting status? We had text updates to suggest for the text (related to the 802.1Q text, also).
Mark Hamilton, Polycom, Inc.

19. July session minutes (cont.)
Wednesday July 18, 2012 (continued)
General Links (Donald Eastlake presentation):
Reviewed presentation
Nobody expressed any concern with the technical concepts presented, nor the suggestion to form a Study Group
Both proposals (Donald’s and Norm Finn’s) could be considered by the Study Group.
We welcome and expect involvement in any Study Group on this
Reworded the proposed motion about forming a Study Group. Something like ‘a Study Group on general links that support bridging’. This was explicitly not saying or entities directly do bridging (are bridges), but it could be that. It could also be that is enhanced to enable bridges attached to a non-AP STA, for example. So, this includes both Donald’s and Norm’s ideas. Also added PBSS, to support ad.
Straw Poll:
Do you support a motion to: Request approval by IEEE 802 LMSC to form a Study Group on enabling the use of infrastructure, PBSS, and IBSS associations as general transit links capable of supporting bridging, with the intent of creating a PAR and five criteria?
Yes: 8 No: 0 Abstain: 0
802.1AC – agreed to defer this alignment to REVmc
Adrian noted that our MAC really has quite a bit of state shared by both ends of a link (TS, BA, etc.), so we are verging on being connection-oriented. Anyone interested in this topic should make a presentation.
Mark Hamilton, Polycom, Inc.

20. July session minutes (cont.)
Thursday July 19, 2012 (Joint session with 802.1)
Proposal for future collaboration between 802.1/ to come into through ARC or WNG is accepted.
Discussion on and bridging:
Norm Finn presented
Norm presented the concepts and models; and presented Issue 3 in particular. Noted that Donald Eastlake’s proposal has a different solution to Issue 3, but they agree that the issue is critical to solve
Norm also proposes a Study Group on this topic, somehow done to be coordinated with and involvement. Bruce Kraemer/Jon Rosdahl noted that this is in addition to other collaboration/coordination items between and
Collectively reworded the motion requesting the Study Group, to clarify the types of links (to consider, but not require, infrastructure BSS, PBSS, and IBSS). Both groups will consider this motion text (11-12/947r1) in their respective closing plenaries.
Mark Hamilton, Polycom, Inc.

21. July session minutes (cont.)
Thursday July 19, 2012 (continued)
TRILL liaison
Mark Hamilton requested feedback from on proceeding with a liaison to IETF on this subject
802.1 feedback can be summarized as “Need to start with a use case presentation, and if the use case is agreed, then proceeding with a liaison to TRILL can be considered. Individuals in with interest in this, should proceed in that order.”
Other coordination
802.1Q corrigendum is nearly done
802.1AC is ready to go to RevCom (basically done)
802.1Q revision will start soon (driven by the number of amendments that have queued up)
802.1 has a maintenance process, starts with entering issues on a form on the web site. Suggests that ’s specific “bugs found” issues be submitted this way.
Tony Jeffree is member of all Sponsor Ballot pools, and offers to be a conduit to submit any comments from non-pool members
Mark Hamilton, Polycom, Inc.