260 likes | 268 Views
This report provides information on the IEEE-SA Standards Board Patent Policy, including requirements for assurance of essential patents in standards. It also lists inappropriate topics for discussion in IEEE working group meetings.
E N D
TGn Opening ReportSept 200404/1030 r0 Bruce Kraemer, Chair bkraemer@conexant.com Garth Hillman, Secretary garth.hillman@amd.com Kraemer, Conexant; Hillman, AMD
Administrative Intro Kraemer, Conexant; Hillman, AMD
1. IEEE-SA Standards Board Bylaws on Patents in Standards Approved by IEEE-SA Standards Board – May 2004 • 6. Patents • IEEE standards may include the known use of essential patents and patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard. This assurance shall be provided without coercion and prior to approval of the standard (or reaffirmation when a patent becomes known after initial approval of the standard). This assurance shall be a letter that is in the form of either: • a) A general disclaimer to the effect that the patentee will not enforce any of its present or future patent(s) whose use would be required to implement the proposed IEEE standard against any person or entity using the patent(s) to comply with the standard or • b) A statement that a license will be made available without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination • This assurance shall apply, at a minimum, from the date of the standard's approval to the date of the standard's withdrawal and is irrevocable during that period. Kraemer, Conexant; Hillman, AMD
Patent Policy IEEE-SA Standards Board Bylaws 6. Patents IEEE standards may include the known use of essential patents and patent applications provided the IEEE receives assurance from the patent holder or applicant with respect to patents whose infringement is, or in the case of patent applications, potential future infringement the applicant asserts will be, unavoidable in a compliant implementation of either mandatory or optional portions of the standard [essential patents]. This assurance shall be provided without coercion and prior to approval of the standard (or reaffirmation when a patent or patent application becomes known after initial approval of the standard). This assurance shall be a letter that is in the form of either: • a) A general disclaimer to the effect that the patentee will not enforce any of its present or future patent(s) whose use would be required to implement either mandatory or optional portions of the proposed IEEE standard against any person or entity complying with the standard; or • b) A statement that a license for such implementation will be made available without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination. • This assurance shall apply, at a minimum, from the date of the standard's approval to the date of the standard's withdrawal and is irrevocable during that period. Kraemer, Conexant; Hillman, AMD
1. Inappropriate Topics for IEEE WG Meetings Approved by IEEE-SA Standards Board – March 2003 • Don’t discuss licensing terms or conditions • Don’t discuss product pricing, territorial restrictions or market share • Don’t discuss ongoing litigation or threatened litigation • Don’t be silent if inappropriate topics are discussed… do formally object. If you have questions, contact the IEEE-SA Standards Board Patent Committee Administrator at patcom@ieee.org Kraemer, Conexant; Hillman, AMD
1. Attendance & Voting Status Use 802wirelessworld to register attendance If you encounter Attendance Issues during the session send an email to Harry Worstell – • hworstell@att.com • Questions on Voting status – see Harry Worstell – • hworstell@att.com Kraemer, Conexant; Hillman, AMD
TGN – July Minutes 04-0728r0 • Cumulative minutes of the High Throughput Task Group meetings held during the IEEE 802.11 Plenary meeting in Portland from July 12 through 16, 2004. • Executive Summary (see closing report doc. 11-04-0839r0): • 14 Technical presentations were heard • Joint meetings were held with 802.19, .18 and .21 • Decision was made not to hold elections for the technical editor and vice-chair at this meeting or the September meeting • Overview of TGn timeline was given • Logistics for the September meeting in Berlin, where the proposals will be heard for the first time, were agreed upon Kraemer, Conexant; Hillman, AMD
Approve Minutes • Motion to approve minutes of the July session contained in document 04-0728 Kraemer, Conexant; Hillman, AMD
Plan for the Week Kraemer, Conexant; Hillman, AMD
1. TGn - September Meeting Hours All sessions will be held in ECC Room 1 Kraemer, Conexant; Hillman, AMD
1. TGn - Speaker Schedule All sessions will be held in ECC Room 1 Kraemer, Conexant; Hillman, AMD
Speaker Sequence- distributed Kraemer, Conexant; Hillman, AMD
Speaker Sequence - distributed Kraemer, Conexant; Hillman, AMD
Extraordinary event • Family illness requires change per WG chair Kraemer, Conexant; Hillman, AMD
Speaker Sequence Proposal –move all 1 slot Kraemer, Conexant; Hillman, AMD
Agenda Logic • September (set this morning) • Dispose of administrative affairs – set expectations & the stage • Complete first round of presentations for all submissions • Use special orders to fix time slots • Hold no selection votes • Discuss November plans in some detail before session close • Expect/encourage mergers and resubmissions between Sept & Nov • November (for guidance only) • Hear extended presentations of revised complete proposals • Perhaps 4 hours each • Hold panel • Vote? Kraemer, Conexant; Hillman, AMD
Special Order Seaking slots of 1 hour each Agenda Detail – Mon + Tues Special Order Seaking slots of 1 hour each Kraemer, Conexant; Hillman, AMD
Special Order Seaking slots of 1 hour each Special Order Seaking slots of 1 hour each Agenda Detail – Wed + Thu Kraemer, Conexant; Hillman, AMD
Speaker Logistics • Each speaker is allocated a one hour block • This includes transition time, presentation, and question and answer. • Speaker decides/announces how they will handle Q&A • Distributed: Acknowledge and answer questions as they proceed • Or • Lump: Finish presentation then to allow Q & A after completion • Alarm clock will be used to assist Kraemer, Conexant; Hillman, AMD
Speaker Logistics • TGn officers, with assistance from WG officers, (plus Tour Host and hotel staff ) will assist in keeping the process moving (microphones, projectors, lights,…) • Speakers must be ready to present at the agreed to times. E.g. if you show up 15 minutes late that time is lost. • If the speaker finishes early we will have a recess. • Make sure you can connect to the projecter • Announce to the group which documents are being presented Kraemer, Conexant; Hillman, AMD
Approve Agenda • Motion to approve agenda with speaking slots as special orders. Kraemer, Conexant; Hillman, AMD
Documents Kraemer, Conexant; Hillman, AMD
WG Vice Chair 2.3.10.2.2 Document Collection and Maintenance The objectives of this task are: • After assignment by the Chair, maintain a consistently numbered set of documents and on the meeting server using electronic wireless Wi-FI™ medium and the IEEE 802.11 WEB site. • Verify document formats before presentation and circulation of materials to membership • Update document list and assign document numbers as requested. • Keep meeting attendees informed about document status during plenary and interim sessions. Kraemer, Conexant; Hillman, AMD
802.11 Policies and Procedures04-0510 r0 • 2.5 Documentation • All 802.11™ documents are disseminated in electronic format only, other than exceptional cases. Documents are only accepted if they adhere to the rules spelled out in this subclause. • 2.5.1 Types • 2.5.2 Format • Documents with the exception of draft standards and amendments shall in the current template as specified by the WG Chair. The templates are located on the 802.11™ WG website at: http://ieee802.org/11/Documents/format-rules.html. • 2.5.3 Layout • 2.5.4 Timing of Submissions • 2.5.5 Naming Conventions Kraemer, Conexant; Hillman, AMD
Submission/ Presentations • Formatting of documents is important. • Authors: Check your work • Members: Constructive commentary is appreciated. Should you see any documents with formatting errors please bring them to the attention of the authors so they can be duly noted and fixed ASAP. • Any issues mentioned in session will be minuted • Status reviewed in the subsequent session • Lets concentrate on technical presentations and discussions • Consider the months of preparation and expense to reach this point • Avoid diverting time to administrative debates Kraemer, Conexant; Hillman, AMD
We are now ready to begin!! Kraemer, Conexant; Hillman, AMD