1 / 19

TGmb Agenda, January 2010

TGmb Agenda, January 2010. Authors:. Date: 2010-03-15. Abstract. Agenda for the TGmb meeting in Orlando, Florida, USA from March 15-18, 2010. Monday PM1 15 March 2010, 13:30 – 15:30. Call meeting to order. Participants, Patents, and Duty to Inform.

upton-hanson
Download Presentation

TGmb Agenda, January 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TGmb Agenda, January 2010 Authors: Date: 2010-03-15 Matthew Gast, Trapeze Networks

  2. Abstract Agenda for the TGmb meeting in Orlando, Florida, USA from March 15-18, 2010. Matthew Gast, Trapeze Networks

  3. Monday PM115 March 2010, 13:30 – 15:30 • Call meeting to order Matthew Gast, Trapeze Networks

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

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

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

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

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

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

  10. Monday PM1 (continued)15 March 2010, 13:30 – 15:30 • Attendance recording procedures • See 11-09/0246r0 • https://murphy.events.ieee.org/imat • Must register before logging attendance • Must log attendance during each 2 hour session • Documentation • http://mentor.ieee.org • Use “TGm” for documents relating to the Revision PAR Matthew Gast, Trapeze Networks

  11. Monday PM1 (continued)15 March 2010, 13:30 – 15:30 • Results from LB160 (REVmb-D2.0) • 166 affirmative (89%), 20 negative (11%), with 25 abstentions • Change from LB 149: +11 affirmative, -3 negative, -4 abstensions • This was a recirculation ballot; all comments must be against changed text • 246 comments received (195 technical), stored in 11-09/0706r7 • Plan of record on next slide Matthew Gast, Trapeze Networks

  12. Current 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 • May 2009 – First WG Letter ballot • (includes All published Amendments as of May 2009) • Nov 2009 – Recirc start • May 2010 – Form Sponsor Pool (45 days) • July 2010 – Sponsor Ballot Start • (Include all published amendments as of July 2010) • November 2010 – Sponsor Recirc • March 2011 – WG/EC Final Approval • June 2011 – RevCom/SASB Approval Matthew Gast, Trapeze Networks

  13. Monday PM1 (continued)15 March 2010, 13:30 – 15:30 • Approval of minutes of prior meetings • January 2010 minutes: 11-10/0075r0 – https://mentor.ieee.org/802.11/dcn/10/11-10-0075-00-000m-minutes-of-tgmb-jan-2010-la-interim.doc • Teleconference minutes: 11-10/0214r3 -- https://mentor.ieee.org/802.11/dcn/10/11-10-0214-03-000m-january-february-march-2010-tgmb-teleconference-minutes.doc • Draft Update & Editor’s Report (Adrian Stephens) Matthew Gast, Trapeze Networks

  14. Monday PM1 (continued)15 March 2010, 13:30 – 15:30 • Comment Resolution • Three ad hoc databases: GEN, MAC, and SECURITY • Comments are in 11-09/790r9 (filter on letter ballot column) • CID 2092 submission – 11-10/0308r0 (Adrian Stephens) • CID 2115 submission – 11-10/0300r0 (Bill Marshall) • Comment Resolution • Recycled comment discussion Matthew Gast, Trapeze Networks

  15. Tuesday PM116 March 2010, 13:30 – 15:30 • 13:30–14:15: Security Comment Resolution • OKC Clarification: 11-10/0209r0 (Dan Harkins) • 14:15–15:30: Admission Control Comment Resolution (Dave Stephenson) • CIDs 2227, 2228, 2232, 2234, 2238, and 2241 Matthew Gast, Trapeze Networks

  16. Tuesday PM216 March 2010, 16:00 – 18:00 • Approval motions for teleconference recommendations • Editorial comments • CIDs 2214 & 2039 • Clause 11.3 • Security • MAC • Comment Resolution • Remaining clause 11.3 comments (Jon Rosdahl) Matthew Gast, Trapeze Networks

  17. Wednesday PM117 March 2010, 13:30 – 15:30 • Joint Regulatory Session • Discussion of LB 160 CID 2113 • Presentation: 11-10/0210r6 (Peter Ecclesine) • Motion to approve 11-10/0210r6 • Additional Comment Resolution • CID 2219 presentation: 11-10/0313r0 (Robert Stacey) Matthew Gast, Trapeze Networks

  18. Wednesday PM217 March 2010, 16:00 – 18:00 • Comment Resolution Matthew Gast, Trapeze Networks

  19. Thursday PM218 March 2010, 16:00 – 18:00 • Comment Resolution • Letter Ballot Authorization Motion • Preparation for May 2010 meeting • Teleconferences/ad hocs • Review Timeline (slide 13) • AOB • Adjourn Matthew Gast, Trapeze Networks

More Related