210 likes | 428 Views
TGmb Agenda, November 2008. Authors:. Date: 2008-11-10. Abstract. Agenda for the TGmb meeting held in Dallas, TX, USA from November 10-14, 2008. Agenda. Call Meeting to Order Review schedule Respond to Interpretation Request Make PAR changes for approval
E N D
TGmb Agenda, November 2008 Authors: Date: 2008-11-10 Matthew Gast, Trapeze Networks
Abstract Agenda for the TGmb meeting held in Dallas, TX, USA from November 10-14, 2008. Matthew Gast, Trapeze Networks
Agenda • Call Meeting to Order • Review schedule • Respond to Interpretation Request • Make PAR changes for approval • Review issues inputs to TGmb revision Matthew Gast, Trapeze Networks
Tuesday • Call Meeting to Order / Administrivia • Agenda review • attendance recording & meeting resources • Policies & procedures (including patent policy) • Approval of prior meeting minutes • TGmb revision status & schedule • Interpretation request • Issue review & resolution Matthew Gast, Trapeze Networks
Attendance recording • Attendance • 11-08-0058-00-0000-opening-network-information-attendance-and-documentation-for-january-2008-session.ppt • https://murphy.events.ieee.org/imat • Must register before logging attendance • Must log attendance during each 2 hour session • Documentation • http://mentor.ieee.org Matthew Gast, Trapeze Networks
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 orpatent 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 patentclaim 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 Slide #1 Matthew Gast, Trapeze Networks
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 http://standards.ieee.org/guides/bylaws/sect6-7.html#6 IEEE-SA Standards Board Operations Manual http://standards.ieee.org/guides/opman/sect6.html#6.3 Material about the patent policy is available at http://standards.ieee.org/board/pat/pat-material.html If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org or visit http://standards.ieee.org/board/pat/index.html This slide set is available at http://standards.ieee.org/board/pat/pat-slideset.ppt Slide #2 Matthew Gast, Trapeze Networks
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 Slide #3 Matthew Gast, Trapeze Networks
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 5.3.10 and “Promoting Competition and Innovation: What You Need to Know about the IEEE Standards Association's Antitrust and Competition Policy” for more details. Slide #4 Matthew Gast, Trapeze Networks
Resources – URLs • Link to IEEE Disclosure of Affiliation • http://standards.ieee.org/faqs/affiliationFAQ.html • Links to IEEE Antitrust Guidelines • http://standards.ieee.org/resources/antitrust-guidelines.pdf • Link to IEEE Code of Ethics • http://www.ieee.org/web/membership/ethics/code_ethics.html • Link to IEEE Patent Policy • http://standards.ieee.org/board/pat/pat-slideset.ppt Matthew Gast, Trapeze Networks
Meeting Etiquette • IEEE 802 is a world-wide professional technical organization • Meetings are to be conducted in an orderly and professionalmanner in accordance with the policies and procedures governed by the organization. • Individuals are to address the “Technical” content of the subject under consideration and refrain from making “personal” comments to or about the presenter. Matthew Gast, Trapeze Networks
Approval of prior meeting minutes • September 2008 (Waikoloa, Hawai‘i): 11-08/1114r1 • https://mentor.ieee.org/802.11/file/08/11-08-1114-01-000m-september-2008-interim-meeting-minutes-kona-hawai-i.doc Matthew Gast, Trapeze Networks
TGmb timeline • Call for comments on 802.11-2007 closed yesterday (November 10, 2008) • Future projected dates • March 2009: Initial letter ballot • November 2009: Initial sponsor ballot • March 2011: RevCom approval • Plan of record on next slide for reference Matthew Gast, Trapeze Networks
TGmb Plan of Record • May 2008 – Issue Call for Comment/Input • July 2008 – begin process input and old Interpretation requests Acknowledge previous Task Group referrals • Sept 2008 – PAR revision process started • Nov 2008 – close receipt of new input • Nov 2008 – WG/EC approval of PAR Revision • Dec 2008 – NesCom/SASB approval PAR Revision • Mar 2009 first WG Letter ballot • (includes All published Amendments as of Mar 2009) • July/Sept 2009 Recirc start • Sept 2009 – Form Sponsor Pool • Nov 2009 – Sponsor Ballot Start • (Include all published amendments as of Nov 2009) • Mar 2010 – Sponsor Recirc • Nov 2010 – WG/EC Final Approval • Mar 2011 – RevCom/SASB Approval Matthew Gast, Trapeze Networks
Interpretation Request #1 • Request received from Johannes Berg <johannes@sipsolutions.net> :In 802.11-2007, section 11.7.1.2 ("Setup procedure at the AP") [for DLS] notes:"[...] Send DLS Response frame to the STA that sent the DLS Request frame with a result code of Not a STA, if the destination STA [...]“Is this meant to say"[...] Send DLS Response frame to the STA that sent the DLS Request frame with a result code of Not QoS STA, if the destination STA [...]“(note "Not QoS STA") • Note: emphasis added Matthew Gast, Trapeze Networks
Data points for Interpretation Request • Text appears on page 458 of 802.11-2007 • Table 11-6 on page 458 of 802.11-2007 maps result codes for primitives into status codes • Table has codes for NOT_ALLOWED, NOT_PRESENT, and NOT_QOS_STA • Table 7-23 (status codes) on pp. 94-5 of 802.11-2007 has code 50 for “The Destination STA is not a QoS STA” but does not have a status code for “not a STA” Matthew Gast, Trapeze Networks
Issue Review & Resolution • Responses to initial call for comments are consolidated as 11-08/1127r4 • https://mentor.ieee.org/802.11/file/08/11-08-1127-04-000m-tgmb-issues-list.xls • After adding approved amendments (see timeline on next slide) to 802.11-2007, editor should incorporate resolutions to these initial issues Matthew Gast, Trapeze Networks
Amendment Ordering Amendment reordering is discussed by editors at each session and adjusted based on current timeline estimates • Data as of Sept 2008 from 802.11 web • See http://grouper.ieee.org/groups/802/11/Reports/802.11_Timelines.htm Slide 18 Matthew Gast, Trapeze Networks Terry L Cole (AMD)
Wednesday I • Approval of PAR changes (Jon Rosdahl) • Approval of interpretation response – 11-08/1366r0 (Matthew Gast) • Approval of Comment Group 1 in issues list (11-08/1127r5) • Security expert follow-up • Issue Review & Resolution Matthew Gast, Trapeze Networks
Wednesday II • Issue Review & Resolution Matthew Gast, Trapeze Networks
Thursday • Issue review & resolution • Teleconferences • Review timeline • Preparation for January 2009 interim meeting • AOB • Adjourn Matthew Gast, Trapeze Networks