1. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 1 IBSS TPC Issues Mike Moreton, Synad Technologies, Ltd. Mike.Moreton@Synad.com

2. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 2 The Problem One of the “fundamental concepts” of TGh is that the AP provides the client with country information. This is done because we can’t assume that a client is configured correctly. But an IBSS is started by a client. Is it any more likely to be configured correctly than any other client?

3. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 3 AP and “IBSS starter” are different An AP is normally used in the country where it was bought The station that starts an IBSS may often be used in different countries An AP is normally configured by a network administrator An IBSS is normally configured by a user, many of which may have almost no technical understanding. An infrastructure BSS is normally expected to be used for a considerable period of time. An IBSS is often an “ad-hoc” quick fix not expected to be round for very long. Only the AP sends out beacons in an infrastructure BSS. In an IBSS, other stations copy the original beacon, and may continue to send out beacons when they have moved far away from the originating station.

4. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 4 Conclusion The chance of the country information being correctly configured in an IBSS is almost negligible.

5. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 5 An Example A laptop is used to start an IBSS in a meeting in one country. The laptop is taken to another country. It beacons out a Country IE that is still for the first country. As a result, other stations may start to use channels and power levels that are illegal in the second country.

6. doc.: IEEE 802.11-02/392r0 Submission June 2002 Mike Moreton, Synad Technologies Ltd.Slide 6 Suggested Changes (1)IBSS Country and Supported Channels elements should only contain information for the channel on which the IBSS is active. (2)Stations should in general ignore Country elements and Supported Channels elements received in IBSS beacons and probe responses. (3)A station joining an IBSS that includes the Country element in the beacon must observe the power limitation indicated for the current channel in that element and in the Supported Channels element (if present). (4)Stations JOINing an IBSS should generate Country and Supported Channels elements by duplicating them from an existing beacon in the IBSS. They should not send these elements if they are not present in the beacon being copied.