Re: [802SEC] Path to resolution of 802.11 VHT60 PAR
As part of the VHT60 group resolving comments from 802.15 WG, we were unsure
whether a specific standard (especially one that hasn't yet been approved)
could be mentioned in the scope of another standard. This was mentioned as
something NESCOM would object to having in the scope. We asked Paul and
requested clarification, but did not get anything contrary to that opinion.
For that reason, the committee elected to use "Addresses coexistence with
other systems in the band." This statement implies that the proposed
standard has addressED coexistence and I would think that lack of anything
in the proposed standard that handles coexistence would be grounds for
sending it back to the WG for changes. "Supports mechanisms to enable
coexistence with other systems in the band." would be a good replacement.
Having just IEEE 802.15.3c in this sentence could offend others in the
industry who may be working on other systems in the same band.
Secondly, the VHT60 committee included the following in the Additional Notes
section:
"It is in the best interest of users and the industry to strive for a level
of coexistence between wireless systems. VHT will investigate coexistence
with other systems in the 60 GHz band.
* One approach will be to investigate a common PHY between VHT and
802.15.3c, and adopt if feasible.
* Another approach is a common coexistence mechanism that may be used by
other 60 GHz systems"
This clearly addresses the issues raised by the 802.15 WG, but that group
was unwilling to read the whole document and insisted on just considering
the scope statement. It would have helped to have guidance from IEEE 802
leadership to explain some of the rules for forming scope statements and
explain that the "whole" PAR should be considered and not just the scope
statement.
Also, it may not be possible to adopt mechanisms that are being used in
802.15.3c to establish a coexistence mechanism suitable to protect either
system from the other system. Coexistence must work both ways. The result of
addressing coexistence may be a mechanism that would need to be included in
IEEE 802.15.3c as well. Will the IEEE 802 EC recommend that 802.15.3c be
held up until that common coexistence mechanism has been defined?
Regards, John
On 8/5/08 5:52 PM, "Shellhammer, Steve" <sshellha@qualcomm.com> wrote:
> EC Members,
>
> It has been brought up by several people that the term "ensure" is
> almost a synonym for "guarantee" which was not the intention. So I wanted to
> float some alternative wording, and solicit feedback.
>
> Instead of the sentence "Ensure coexistence with IEEE 802.15.3c." I
> would like to suggest the sentence "Supports mechanisms to enable coexistence
> with IEEE 802.15.3c."
>
> I would like to hear feedback in particular from Bruce Kraemer and Bob
> Heile, but comments from other EC members is also welcome.
>
> Regards,
> Steve
>
>
> -----Original Message-----
> From: ***** IEEE 802 Executive Committee List *****
> [mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of Shellhammer, Steve
> Sent: Saturday, July 26, 2008 8:23 AM
> To: STDS-802-SEC@LISTSERV.IEEE.ORG
> Subject: [802SEC] Path to resolution of 802.11 VHT60 PAR
>
> EC Members,
>
> Bruce Kraemer, Bob Heile, Paul Nikolich and I held a conference
> call on Thursday to discuss a path forward for the 802.11 VHT60 PAR. Paul had
> asked us to see if we could define a path to resolution. Here is what we came
> up with.
>
> Path to resolution of 802.11 VHT60 PAR
>
> The following is a brief description of the path for resolution of the 802.11
> VHT60 PAR, which is recommended by the chairs of 802.11/15/19.
>
> The following modifications would be made to the PAR
>
> 1. A stronger declaration of coexistence with 802.15.3c in the Scope of the
> PAR. Possible wording that could be used is the wording used in the motion to
> amend during the closing EC meeting,
> Replace the text "Addresses coexistence with other wireless systems" with the
> text "Ensure coexistence with IEEE 802.15.3c."
>
> 1. Adding a definition of coexistence in the Additional Notes section. One
> possible definition is the definition in 802.15.2, which was approved by both
> the 802.11 and 802.15 working groups.
> 2. Adding 802.15.3c and ECMA TC48 to section 7.1 (Projects will similar
> scope) of the PAR
>
> Regards,
> Steve
>
>
> ----------
> 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.
--
John R. Barr (John.Barr@Motorola.com)
Director, Standards Realization - <http://www.motorola.com>
Vice Chairman of the Board, Bluetooth SIG - <http://www.bluetooth.org>
(847) 576-8706 (office) +1-847-962-5407 (mobile) (847) 576-6758 (FAX)
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.