Presentation is loading. Please wait.

Presentation is loading. Please wait.

TGy September Chair’s Report

Similar presentations


Presentation on theme: "TGy September Chair’s Report"— Presentation transcript:

1 TGy September Chair’s Report
doc.: IEEE /1466r1 September 2006 TGy September Chair’s Report Date: Authors: Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including 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." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

2 September 2006 doc.: IEEE /1466r1 September 2006 Abstract This submission summarizes the TGy agenda for IEEE Melbourne (September 2006) meeting Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

3 Opening Report September 2006 September 2006
doc.: IEEE /1466r1 September 2006 Opening Report Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

4 Attendance Recording -802.11
September 2006 doc.: IEEE /1466r1 September 2006 Attendance Recording Sign-in at “newton” is a local server, not reachable via a VPN “newton” is active only during sessions First “sign in” to provide contact information Only name and affiliation may be posted publicly, as per IEEE rules No other personal information will not be publicly available Second, log attendance Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

5 Membership & Anti-Trust
September 2006 doc.: IEEE /1466r1 September 2006 Membership & Anti-Trust Individual membership In all IEEE standards meetings, membership is by individual, hence you do not represent a company or organization. Anti-Trust laws The Anti-Trust laws forbid the discussion of prices within our meetings. Peter Ecclesine, Cisco Systems 26 Peter Ecclesine, Cisco Systems

6 IEEE-SA Standards Board Bylaws on Patents in Standards
September 2006 doc.: IEEE /1466r1 September 2006 IEEE-SA Standards Board Bylaws on Patents in Standards 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. The patent holder or applicant should provide this assurance as soon as reasonably feasible in the standards development process. This assurance shall be provided no later than the approval of the standard (or reaffirmation when a patent or patent application becomes known after initial approval of the standard). This assurance shall be 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. Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006) Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

7 Inappropriate Topics for IEEE WG Meetings
September 2006 doc.: IEEE /1466r1 September 2006 Inappropriate Topics for IEEE WG Meetings Don’t discuss the validity/essentiality of patents/patent claims Don’t discuss the cost of specific patent use 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 or visit This slide set is available at Approved by IEEE-SA Standards Board – March 2003 (Revised January 2006) Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

8 September 2006 doc.: IEEE /1466r1 September 2006 Copyright Under the current US copyright law — the author of information is deemed to own the copyright from the moment of creation The IEEE Bylaws require copyright of all material to be held by the IEEE Must consult with IEEE for re-use of copyright material The IEEE Standards accomplishes transfer of copyright ownership through the Project Authorization Request (PAR) process The Copyright Act of 1976 made a dramatic change to U.S. copyright law. Copyright was now deemed to exist from the moment of creation. Thus anything that is created is deemed to be owned by its creator. Additionally, a work no longer needs to be published in order to be protected. Therefore, even your scribbles on a piece of note paper constitute copyrighted material that you own and control. The NII (National Information Infrastructure) and the GII (Global Information Infrastructure) are causing lawmakers and copyright owners to assess the ability of current copyright law to protect owners rights in a digital environment. While at this point the changes being talked about are not significant, they will make it clear that copyright protection is afforded to owners in the digital environment making it a requirement to honor the rights accorded to owners. It is a requirement under the IEEE Bylaws that copyright ownership of all material published by the IEEE resides with the IEEE. The Standards Department accomplishes the transfer of copyright ownership from the volunteer authors to the Institute via the Project Authorization Request (PAR) form. Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

9 September 2006 doc.: IEEE /1466r1 September 2006 Equipment Well-dressed criminals often enter meetings and steal laptops, PDAs, and similar devices Do not leave your devices unattended!! Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

10 TGy Goals for Melbourne
September 2006 doc.: IEEE /1466r1 September 2006 TGy Goals for Melbourne Hear proposals addressing PHY, MAC and system operation in US 3650 MHz band Create a D0.01 text for WG review Planning through November 2006 Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

11 Minutes from San Diego Meeting
September 2006 doc.: IEEE /1466r1 September 2006 Minutes from San Diego Meeting Any Modifications of the Minutes from CBP-TG San Diego Meeting 06/1120r0 Approve the minutes Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

12 September 2006 doc.: IEEE /1466r1 September 2006 Motions (1) Motion: Move to accept the minutes of the TGy San Diego meeting Moved: Second: Vote unanimous Yes: No: Abstain: Motion [Fails/Passes]: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

13 TGy Agenda Monday 16:00 September 2006 Peter Ecclesine, Cisco Systems
* CBP TG Meeting Call To Order - Chair 1 16:00 Review IEEE/802 & Policies and Rules Chair/All 8 16:01 Chair's Status Update and Review of Objectives for the Session 9 16:09 II Review and Approve All Minutes 10 16:18 DT Approve or Modify Agenda All 16:28 Review of situation 16:38 Overview presentation, PHY, MAC topics 30 16:48 PHY text 42 17:38 Recess until 8:00 Tuesday  0 18:00 Peter Ecclesine, Cisco Systems

14 TGy Agenda Tuesday September 2006 Peter Ecclesine, Cisco Systems *
CBP TG Meeting Call To Order - Chair 1 8:00 Technical presentations – PHY, MAC and Mobile topics Chair/All 119 8:01 Recess until 19:30 Tuesday 10:00 19:30 Technical presentations – MAC and Mobile topics, summation 19:31 Recess until 16:00 Tuesday 21:30 Peter Ecclesine, Cisco Systems

15 TGy Agenda Thursday 16:00 September 2006
* CBP TG Meeting Call To Order - Chair 1 16:00 Draft D0.01y topics All 90 16:01 Planning through Nov 06 and Motions for WG 29 17:31 Adjourn 18:00 Peter Ecclesine, Cisco Systems

16 September 2006 doc.: IEEE /1466r1 September 2006 Motions (3) Motion: Move to Instruct the editor to incorporate the normative text proposal in ”06/955r2”, into TGy Draft 0.01 Moved: Peter Ecclesine Second: Amer Hassan Vote ( voters present) Yes: unanimously No: Abstain: Motion [Fails/Passes]: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

17 September 2006 doc.: IEEE /1466r1 September 2006 Motions (4) Motion: Move to Instruct the editor to incorporate the normative text proposal in ”06/864r3”, into TGy Draft 0.01 Moved:Peter Ecclesine Second:Amer Hassan Vote ( voting members present) Yes: unanimous No: Abstain: Motion [Fails/Passes]: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

18 Teleconference minutes
September 2006 Teleconference minutes Teleconference minutes y-tgy-aug15th-and-aug29th-2006-conference-call-minutes.doc y-tgy-sept-12th-2006-conference-call-minutes.doc Peter Ecclesine, Cisco Systems

19 September 2006 doc.: IEEE /1466r1 September 2006 Motions (5) Motion: Move to accept the minutes of the Aug 15th, Aug 29th (06/1374r0) and Sept 12th (06/1427r0) teleconferences Moved: unanimous Second: Vote Yes: No: Abstain: Motion [Fails/Passes]: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

20 September 2006 Motion (6) Move to include normative text in document y-extended-csa into the TGy draft. Mover: Allan Thomson Second: Rich Kennedy Vote Yes: 3 No: 0 Abstain: 1 Motion Passes: Peter Ecclesine, Cisco Systems

21 Motion (7) September 2006 Annex A A.4.10 Regulatory domain extensions
doc.: IEEE /1466r1 September 2006 Motion (7) Move to Instruct the editor to incorporate the following normative text into TGy Draft 0.01, and alter the PICs accordingly. 9.8.3 Operation across regulatory classes within a regulatory domain Editor to add a fourth paragraph as shown: Where dot11RegulatoryClassesRequired is true, or where Regulatory Classes domain information is present, and the STA parsing a Country Information element finds a First Channel Number or Regulatory Class with a Reserved value, it shall ignore the remainder of the information element and shall parse any remaining management frame body for additional information elements. Annex A A.4.10 Regulatory domain extensions Insert new entries at end of table: ItemProtocol capabilityReferencesStatusSupport MD13Reserved First Channel Number9.8.3CFy:MYes □ No □ N/A □ MD14Reserved Regulatory Class9.8.3CFy:MYes □ No □ N/A □ Moved: Peter E Seconded:Allan T Yes: 5 No: 0 Abstain: 1 Motion Passes: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

22 Straw Polls Yes: No: September 2006 September 2006
doc.: IEEE /1466r1 September 2006 Straw Polls Yes: No: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

23 September 2006 Work completed The following normative text has been accepted and will be integrated into the TGy draft Peter Ecclesine, Cisco Systems

24 Attendance Monday PM2: 35 Tuesday AM1: 11 Tuesday Evening: not used
September 2006 doc.: IEEE /1466r1 September 2006 Attendance Monday PM2: 35 Tuesday AM1: 11 Tuesday Evening: not used Thursday PM2: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

25 Output documents September chairs report – this document
D0.01 TGy Draft Specification 11-06/xxxx – TGy Melbourne 2006 meeting minutes Peter Ecclesine, Cisco Systems

26 Goals for November Respond to internal review comments
September 2006 Goals for November Respond to internal review comments TGy normative text submissions Peter Ecclesine, Cisco Systems

27 Adjourn Meeting adjourned at xx:xx on Sept 21, 2006 September 2006
Peter Ecclesine, Cisco Systems


Download ppt "TGy September Chair’s Report"

Similar presentations


Ads by Google