PAR FORM

PAR Status: New PAR

PAR Approval Date:

PAR Signature Page on File: Yes

1. Assigned Project Number: P802.1AM

2. Sponsor Date of Request: 2005-XX-YY

3. Type of Document: Standard for

4. Title of Document:

Draft: Standard for Local and Metropolitan Area Networks: Media Independent Radio Frequency (RF) Management of Wireless 802 Networks

5. Life Cycle: Full-Use

6. Type of Project:

6a. Is this an update to an existing PAR? No

6b. The Project is a: New document

7. Working Group Information:

Name of Working Group (WG): IEEE 802.1 Working Group

Approximate Number of Expected Working Group Members: 50

8. Contact information for Working Group Chair:

Name of Working Group Chair: Tony A Jeffree

Telephone: +44-161-973-4278 FAX: +44-161-973-6534

Email:

9. Contact information for Co-Chair/Official Reporter, Project Editor or Document Custodian if different from the

Working Group Chair:

Name of Co-Chair/Official Reporter, Project Editor or Document Custodian:

Telephone: FAX:

Email:

10. Contact information for Sponsoring Society or Standards Coordinating Committee:

Name of Sponsoring Society and Committee: Computer Society Local and Metropolitan Area Networks

Name of Sponsoring Committee Chair: Paul Nikolich

Telephone: 857-205-0050 FAX: 781-334-2255

Email:

Name of Liaison Rep. (if different from the Sponsor Chair):

Telephone: FAX:

Email:

Name of Co-Sponsoring Society and Committee:

Name of Co-Sponsoring Committee Chair:

Telephone: FAX:

Email:

Name of Liaison Rep. (if different from the Sponsor Chair):

Telephone: FAX:

Email:

11. Sponsor Balloting Information: Individual Balloting

Expected Date of Submission for Initial Sponsor Ballot: 2007-03-31

12. Projected Completion Date for Submittal to RevCom: 2007-12-31

Explanation for Modified PAR that completion date is being extended past the original four-year life of the PAR:

13. Scope of Proposed Project:

This standard specifies protocols, procedures, and managed objects to support Radio Frequency (RF) management across IEEE 802 wireless Media Access Control (MAC) layers.

Is the completion of this document contingent upon the completion of another document? No

14. Purpose of Proposed Project:

There is currently no defined, common method for RF management or statistics reporting across IEEE 802 wireless MACs. Each working group has created separate definitions for receive signal quality, transmit power, channel numbers, etc. This effort provides enhancements for a consistent management service interface across all 802 wireless standards.

15. Reason for the Proposed Project:

There is a market need for RF management, given the widespread use of incompatible wireless 802 networks operating in the same frequencies. The ability to control channel selection and adjust transmit power, or view RF characteristics in a consistent way does not exist today. Common management and configuration algorithms are essential to the long term viability of a heterogeneous LAN.

16. Intellectual Property:

16a. Has the IEEE-SA policy on intellectual property been presented to those responsible for preparing/submitting this PAR prior to the PAR submittal to the IEEE-SA Standards Board? Yes

16b. Is the Sponsor aware of copyright permissions needed for this project? No

16c. Is the Sponsor aware of trademarks that apply to this project? No

16d. Is the sponsor aware of possible registration activity related to this project? No

17. Are there other documents or projects with a similar scope? No

While IEEE 802.11v intends to provide amendments to the IEEE 802.11 PHY/MAC layers to enable management of attached stations and IEEE 802.16f intends to provide enhancements to IEEE Standard 802.16-2004 to define a SMIv2 management information base (MIB) module, there is currently no document or project whose aim is to define a common set of managed objects applicable to all IEEE 802 wireless PHY/MAC layers, including IEEE 802.11, 802.15.1, 802.15.3, 802.15.4, 802.16, 802.20, and 802.22.

Similar Scope Project Information:

N/A

18. Future Adoptions - Is there potential for this document (in part or in whole) to be adopted by another national, regional or international

organization? No

If Yes, the following questions must be answered:

Technical Committee Name and Number:

Other Organization Contact Information:

Contact Name:

Telephone: FAX:

Email:

19. Will this project result in any health, safety, or environmental guidance that affects or applies to human health or

safety? No

20. Sponsor Information

20a. Is the scope of this project within the approved scope/definition of the Sponsor's Charter? Yes

20b. Have the Sponsor's procedures been accepted by the IEEE-SA Standards Board Audit Committee? Yes

21. Additional Explanatory Notes (Item Number and Explanation)