| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Title: Objection to Resolution of TGn Draft 4.0 Comment 6069 --- This message came from the IEEE 802.11 Working Group Reflector --- Eldad,
- To: <STDS-802-11@xxxxxxxxxxxxxxxxx>
- Subject: [STDS-802-11] Objection to Resolution of TGn Draft 4.0 Comment 6069
- From: John Barr<John.Barr@xxxxxxxxxxxx>
- Date: Tue, 13 May 2008 17:01:01 -0500
- List-Help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-11>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-802-11>
- List-Owner: <mailto:STDS-802-11-request@LISTSERV.IEEE.ORG>
- List-Subscribe: <mailto:STDS-802-11-subscribe-request@LISTSERV.IEEE.ORG>
- List-Unsubscribe: <mailto:STDS-802-11-unsubscribe-request@LISTSERV.IEEE.ORG>
- Reply-To: John Barr <john.barr@xxxxxxxxxxxx>
- Sender: ***** IEEE stds-802-11 List ***** <STDS-802-11@xxxxxxxxxxxxxxxxx>
- Thread-Index: Aci1RNSkE2PHyiE4Ed2BFAANkzJBMA==
- Thread-Topic: Objection to Resolution of TGn Draft 4.0 Comment 6069
- User-Agent: Microsoft-Entourage/11.3.6.070618
I was surprised to see the resolution of my comment 6069 in 11/0517. It was my understanding that Coexistence comments were going to be handled at a later session or I would have been in the session to voice my concerns. Your proposed resolution references an informative appendix (T.3.2) as a reason for rejecting comment 6069. However, there is no normative link between the paragraph that includes “An additional constraint on establishing a 20/40 MHz BSS includes the allowance for any 802.11 device to explicitly prohibit the operation of the 20/40 BSS mode due to other considerations. For example, if an 802.15.1 WPAN device is operating in the area, ...” to what is included in 11.4.5 and the statement “Before starting a 20/40 MHz BSS, an FC HT AP is required by the rules defined in 11.14.5 to examine the
channels of the current regulatory domain to determine whether the operation of a 20/40 MHz BSS might unfairly
interfere with the operation of existing 20 MHz BSSs.” at the beginning of T.3.2.
From the way this text is included (informative) and the rules for setting dot11FortyMHzIntolerant, it is obvious that no coexistence requirements for IEEE 802.15.1 devices are included in TGn Draft 4.0.
Since it is probably unreasonable to require all 802.11n devices to detect presence of IEEE 802.15.1 devices and set dot11FortyMHzIntolerant when those devices are found, and due to the broad based use of IEEE 802.15.1 devices world wide (over 2 billion have been delivered and at least 15 million more are delivered every week) the best solution would be to assume that IEEE 802.15.1 devices will always be present and just prevent use of 40 MHz channels by STA 19 devices.
My proposed resolution should be accepted: In 20.3.15 change "When using 40 MHz channels, it can operate in the channels defined in 20.3.15.1 and 20.3.15.2." to "When using 40 MHz channels, it can only operate in the channels defined in 20.3.15.2."
As an example of the scope of the problem consider the number of IEEE 802.11 devices in a room at an IEEE 802 meeting compared to the number of IEEE 802.15.1 devices in the same room. Most likely there are nearly twice as many IEEE 802.15.3 devices (40% of laptops contain IEEE 802.15.1 (Bluetooth)), most everyone carries a mobile phone (75% of mobile phones include Bluetooth), most mobile phone users have a Bluetooth headset (say 50% of mobile phones), and some percentage of laptop users (especially Mac users) have a Bluetooth mouse (5%). 0.4 + 0.75 + 0.5 + 0.05 = 1.7
All IEEE 802;15.1 devices implement Advanced Frequency Hopping to detect and avoid IEEE 802.11 signals. IEEE 802.15.1 has implemented good coexistence rules. It is time for IEEE 802.11n to do the same.
Regards, John
--
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)
_______________________________________________________________________________IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11 and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________
--- This message came from the IEEE 802.11 Working Group Reflector ---
- To: <STDS-802-11@xxxxxxxxxxxxxxxxx>
- Subject: [STDS-802-11] IEEE 802.11 Recirculation Letter Ballot #129 for Task Group-n Draft 5.0 Starts Today
- From: "Stephens, Adrian P"<Adrian.P.Stephens@xxxxxxxxx>
- Date: Fri, 23 May 2008 15:50:45 +0100
- List-Help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-11>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-802-11>
- List-Owner: <mailto:STDS-802-11-request@LISTSERV.IEEE.ORG>
- List-Subscribe: <mailto:STDS-802-11-subscribe-request@LISTSERV.IEEE.ORG>
- List-Unsubscribe: <mailto:STDS-802-11-unsubscribe-request@LISTSERV.IEEE.ORG>
- Reply-To: "Stephens, Adrian P" <Adrian.P.Stephens@xxxxxxxxx>
- Sender: ***** IEEE stds-802-11 List ***** <STDS-802-11@xxxxxxxxxxxxxxxxx>
- Thread-Index: Aci85GFAACY1EbhTSeaw0pl/556oYA==
- Thread-Topic: IEEE 802.11 Recirculation Letter Ballot #129 for Task Group-n Draft 5.0 Starts Today
IEEE 802.11(TM) Letter Ballot #129
To: IEEE 802.11 Voters,With this email, the 802.11 Working Group is officially beginning WG Recirculation Letter Ballot 129 (LB129), which is a vote to submit the contents of Task Group-n Draft P802.11n_D5.0.pdf to Sponsor Ballot.
This Ballot opens Fri May 23, 2008 at 23:59 Eastern Time USA (11:59PM) and will close 20 days later on Thu Jun 12, 2008 at 23:59 Eastern Time USA (11:59pm). All necessary documents are available in the instructions that can be found on the main page of the IEEE 802.11 web site at http://ieee802.org/11/index.html.Important:
1. This is a recirculation letter ballot and the voters pool for this ballot is the same as for the original ballot that passed the 75% threshold for 802.11n, i.e., Letter Ballot 97. If you have voted on any of LB97, 115, and 124, you are not required to vote on this ballot. Your most recent ballot will be carried forward. If you wish to change your vote from your most recent ballot, you must respond to this ballot.
2. You must follow the instructions on the 802.11 web site to vote. Do not send an email to vote.
Attached, for your convenience, is a reminder set to fire a few days before completion of the ballot. (You can open this to set a reminder in your calendar).
Thank you for participating in the Letter Ballot #129.Bruce Kraemer, IEEE 802.11 Working Group Chair
Bruce Kraemer, IEEE 802.11 Task Group-n Chair
E-mail: bkraemer@marvell.comAdrian Stephens, IEEE 802.11 Working Group Vice Chair / Balloting Coordinator_______________________________________________________________________________
E-mail: Adrian.P.Stephens@intel.comIF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11 and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________