1 / 13

TGmb Teleconferences March 2009 through May 2009

TGmb Teleconferences March 2009 through May 2009. Date: 2009-03-31. Authors:. Abstract. Agendas for TGmb teleconferences to be held between March 2009 plenary meeting and May 2009 interim meeting. Conference Details. Web session (document sharing)

agamemnon-elena
Télécharger la présentation

TGmb Teleconferences March 2009 through May 2009

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 TeleconferencesMarch 2009 through May 2009 Date: 2009-03-31 Authors: Matthew Gast, Trapeze Networks

  2. Abstract Agendas for TGmb teleconferences to be held between March 2009 plenary meeting and May 2009 interim meeting. Matthew Gast, Trapeze Networks

  3. Conference Details • Web session (document sharing) • http://www.meetingzone.com/presenter/?schedid=5194480 • Test link (use before first session): http://ash-t1-cs1.conferenceservers.com/browser?brand=MeetingZonePresenter • Audio conference • Access code: 5194480# • USA toll free: 1-866-443-7118 • UK freephone: 0800 358 1650 and 0800 358 6785 • Finland: 0800 0111 218 • UK national: +44 (0)207 863 6156 • Canada: 1-866-889-9071 • (Other countries are available on request.) Matthew Gast, Trapeze Networks

  4. Teleconference schedule • March 27: document structure (9) • April 3: style (7) & definitions (5) • April 10: no teleconference – Good Friday holiday • April 17: power save (3) • April 24: security (2), MAC (2) & management (2) • May 1: Document structure leftovers (4) • May 8: (if required) Matthew Gast, Trapeze Networks

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

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

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

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

  9. Teleconference #1: March 27, 2009Topic: document structure • Roll call • Call for essential patent claims • Discussion of document structure CIDs • Issue #1: normative statements in clause 7 (CIDs 16, 29, 43, 53, 103; note that CID 29 has two tabs suggesting 250 changes) • Left for future call -- • Issue #2: documentation of SME (CID 18) • Issue #3: use of “if and only if” (CID 32) • Issue #4: normative nature of MIB (CID 54) • Issue #5: use of terms “mandatory” and “optional” (CID 63) Matthew Gast, Trapeze Networks

  10. Teleconference #2: April 3, 2009Topics: style & definitions • Roll call • Call for essential patent claims • Discussion of definitions • One issue: what definitions should move from the definition clause to the 802.11-specific definition clause? (CIDs 5, 11, 12, 14, & 26) • Discussion of style CIDs • Issue #1: indentations, headings, and hanging paragraphs (CIDs 27 & 28; note that both have an extra tab in the comment spreadsheet) • Issue #2: use of “if and only if” (CID 20) • Issue #3: number of ordered lists in a subclause (CID 22) • Issue #4: source of the value aDTT2UTTTime (CID 19) • Small editorial issues: CIDs 37 & 71 Matthew Gast, Trapeze Networks

  11. Teleconference #3: April 17, 2009Topic: power save • Roll call • Call for essential patent claims • Discussion of power save CIDs • Finish proposing resolutions to CIDs 61, 62, and 101 Matthew Gast, Trapeze Networks

  12. Teleconference #4: April 24, 2009Topic: security, MAC, and management • Roll call • Call for essential patent claims • Discussion of security comments • CIDs 81 & 92: discuss proposed resolution • Discussion of MAC comments • Double encapsulation (CID 68) • MA-UNITDATA.confirm (CID 56) • Discussion of management comments • CID 77: Discuss proposed resolution • CID 78: Determine if 802.11k addressed this comment Matthew Gast, Trapeze Networks

  13. Teleconference #5: May 1, 2009Topic: Document structure • Roll call • Call for essential patent claims • Discussion of document structure CIDs • Left from call #1 -- • Issue #1: documentation of SME (CID 18) • Issue #2: use of “if and only if” (CID 32) • Issue #3: normative nature of MIB (CID 54) • Issue #4: use of terms “mandatory” and “optional” (CID 63) Matthew Gast, Trapeze Networks

More Related