|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
All, I'm not sure what traffic Geoff was referring to but there have been several conference calls regarding adjustments to the VHT 60 PAR to make it both WG & LMSC acceptable. The attached document represents progress to date and will be discussed further amongst the wireless community in the September interim. Although there have been several edits the item in blue should address the primary concerns discussed in Denver. 5.2 Scope of Proposed Standard: The scope of this project is to define an amendment that shall define standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) to enable operation in the 60 GHz frequency band (typically 57-66 GHz) capable of very high throughput. The MAC and PHY specified in this amendment: * Enables a maximum throughput of at least 1 Gbps, as measured at the MAC data service access point (SAP) * Enables fast session transfer between PHYs * Maintains the 802.11 user experience * Supports mechanisms to enable coexistence with IEEE 802.15.3c and with other systems in the band If anyone on the EC would wish to review and comment it would help us during our interim. Following the interim, a WG approved version will be circulated to the EC prior for consideration during the November Plenary. Bruce -----Original Message----- From: owner-stds-802-sec@LISTSERV.IEEE.ORG [mailto:owner-stds-802-sec@LISTSERV.IEEE.ORG] On Behalf Of Geoff Thompson Sent: Monday, August 11, 2008 3:12 PM To: STDS-802-SEC@LISTSERV.IEEE.ORG Cc: Geoff Thompson; firstname.lastname@example.org Subject: Re: [802SEC] EC telecon meeting to review 802.11 60GHz Very Hight Throughput PAR status-- 3PM ET WED 03SEP08 Colleagues- I sincerely hope that you are of like mind with me on this topic. At this point it is not clear that I will be able to attend the conference call From the traffic I have seen on this topic so far it is not clear that this issue is being taken seriously from the customer point of view. That is, the comments I have seen have been focused on the semantics of the requirement instead of the "real" requirement. From my point of view "coexistence" means the following: Traffic from a customer utilizing an implementation of the 802 standard will not interfere with another customer utilizing an implementation of the 802 standard except to contend fairly for bandwidth on shared spectrum. This the issue that I was speaking to at the July closing EC. I strongly believe we should settle for nothing less across 802. Best regards, Geoff Thompson >***** IEEE 802 Executive Committee List ***** ><STDS-802-SEC@LISTSERV.IEEE.ORG> wrote on 11/08/2008 12:50:47: > > > Dear EC members, > > > This email confirms the below teleconference.will be held 3PM ET > > WED 03SEP08. The agenda is to review the 802.11 60GHz VHT PAR > > status and potential resolution to the concerns raised during the > > closing EC meeting. > > > BruceK, SteveS and BobH have confirmed they are avaliable, all EC > > members please plan to attend if at all possible. > > > Sprint # 1-888-869-7158 or 1-763-315-6831 > > Participant Code # 802622 > > > Regards, > > > --Paul > > > > > ----- Original Message ----- > > From: "Paul Nikolich" <paul.nikolich@ATT.NET> > > To: <STDS-802-SEC@LISTSERV.IEEE.ORG> > > Sent: Wednesday, August 06, 2008 9:46 AM > > Subject: [802SEC] EC telecon meeting request to review 802.11 60GHz > > Very Hight Throughput PAR status--tentatively 3PM ET WED 03SEP08 > > > > > All, > > > One of my actions from the closing EC meeting was to convene a > > teleconference of the EC to review the 802.11 60GHz VHT PAR >status/concerns. > > > I'd like to schedule that telecon at 3PM ET WED 03 SEP 2008. > > BruceK, SteveS and BobH does this work for you? > > > Regards, > > > --Paul ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.