September 2005
doc.: IEEE 802.11-05/0908r0
IEEE P802.11
Wireless LANs
dot1AM management PAR 5C
Date: 2005-09-16
Author(s):
Name
Peter
Ecclesine
Company
Cisco Systems
Address
170 W. Tasman Dr., MS SJ-105, San Jose, CA 95134-1706
Phone
+1-408-527-0815
email
petere@ieee.org
Abstract
As radio operation and regulation are expressed in terms of time, space,
frequency, code and power, it is useful to look at those dimensions in the
approved standards and the ones under development.
Related to 11-05-0892-01-0wng-dot1AM-task-sizing.xls
11-05-0907-00-0wng-dot1AM-management-plane.ppt
Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the
contributing individual(s) or organization(s). The material in this document is subject to change in form and content after
further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution,
and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE
Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit
others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and
accepts that this contribution may be made public by IEEE 802.11.
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http://
ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s),
including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents
essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of
patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development
process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair
<stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under
patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you
have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>.
Submission
page 1
Peter Ecclesine, Cisco Systems
September 2005
doc.: IEEE 802.11-05/0908r0
Change RF to PMD and ‘wireless’ to ‘wired and wireless’:
http://www.ieee802.org/1/files/public/docs2005/am-wireless-management-draft-par-0705.doc
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 (PMD)
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: tony@jeffree.co.uk
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: paul.nikolich@att.net
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-12-31
12. Projected Completion Date for Submittal to RevCom: 2008-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 managed objects to support Radio Frequency (PMD) management across IEEE 802 wired
and 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 PMD management or statistics reporting across IEEE 802 wired
Submission
page 2
Peter Ecclesine, Cisco Systems
September 2005
doc.: IEEE 802.11-05/0908r0
and 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 wired and wireless standards.
15. Reason for the Proposed Project:
There is a market need for PMD management, given the widespread use of incompatible wired and wireless 802
networks operating in the same frequencies. The ability to control channel selection and adjust transmit power, or
view PMD characteristics in a consistent way does not exist today. Common management is 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 wired and 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)
http://www.ieee802.org/1/files/public/docs2005/amwireless-management-5c-0705.doc
CRITERIA FOR STANDARDS DEVELOPMENT
(FIVE CRITERIA)
for
Standard for Local and Metropolitan Area Networks: Media Independent Radio Frequency (PMD) Management of
Wired and Wireless 802 Networks (P802.1AM)
6.1 Broad Market Potential
A standards project authorized by IEEE 802 shall have a broad market potential. Specifically, it shall have the
potential for:
a) Broad sets of applicability.
Submission
page 3
Peter Ecclesine, Cisco Systems
September 2005
doc.: IEEE 802.11-05/0908r0
Media independent Radio Frequency (PMD) management would apply to all wired and
wireless 802 networks ensuring broad applicability.
b) Multiple vendors and numerous users.
Many vendors and users that participate in wired and wireless 802 working groups have
expressed interest in having a consistent management service interface applicable to all 802
wired and wireless standards.
c) Balanced costs.
Existing 802 wired and wireless devices provide an interface for PMD management, but the
semantics for these interfaces are inconsistent across vendors. This project would not increase
the cost of these devices to adhere to a consistent management service interface. Rather, there
is the potential for reducing costs in management applications.
6.2 Compatibility
IEEE 802 defines a family of standards. All standards shall be in conformance with the IEEE 802.1 Architecture,
Management and Internetworking documents as follows: 802. Overview and Architecture, 802.1D, 802.1Q and
parts of 802.1f. If any variances in conformance emerge, they shall be thoroughly disclosed and reviewed with 802.
Each standard in the IEEE 802 family of standards shall include a definition of managed objects which are
compatible with systems management standards.
The proposed standard will conform to the aforementioned documents.
6.3 Distinct Identity
Each IEEE 802 standard shall have a distinct identity. To achieve this, each authorized project shall be:
a) Substantially different from other IEEE 802 standards.
There is no IEEE 802 standard that addresses a consistent PMD management interface across
all 802 wired and wireless MACs.
b) One unique solution per problem (not two solutions to a problem).
While there are management task groups in several of the 802 wired and wireless working
groups, there is no activity in IEEE 802 to provide a consistent interface.
c) Easy for the document reader to select the relevant specification.
The proposed standard will be a new specification and clearly identifiable. A SMIv2
Management Information Base (MIB) module will be made available in text format for use by
network management applications.
6.4 Technical Feasibility
For a project to be authorized, it shall be able to show its technical feasibility. At a minimum, the proposed project
shall show:
a) Demonstrated system feasibility.
Existing 802 wired and wireless devices already provide an PMD management interface
indicating system feasibility.
Submission
page 4
Peter Ecclesine, Cisco Systems
September 2005
doc.: IEEE 802.11-05/0908r0
b) Proven technology, reasonable testing.
Examples of PMD management interfaces exist today.
c) Confidence in reliability.
A consistent management service interface is expected to be more reliable than current
inconsistent solutions.
d) Coexistence of 802 wireless standards specifying devices for unlicensed operation
The working group proposing a wireless project is required to demonstrate Coexistence through the
preparation of a Coexistence Assurance (CA) document unless it is not applicable.
Task Group will not create a CA document
Reason it is not applicable: ____________________________________
This task group is not creating a new wired and wireless MAC/PHY. This consistent PMD
management interface facilitates cognizance and by that virtue, enables coexistence.
6.5 Economic Feasibility
For a project to be authorized, it shall be able to show economic feasibility (so far as can reasonably be estimated),
for its intended applications. At a minimum, the proposed project shall show:
a) Known cost factors, reliable data.
There are several commercially viable PMD management solutions available in the market
today.
b) Reasonable cost for performance.
It is not anticipated that adherence to this proposed specification would add cost to
implementations.
c) Consideration of installation costs.
A consistent PMD management interface across all wired and wireless 802 MACs would reduce
installation costs.
Submission
page 5
Peter Ecclesine, Cisco Systems
September 2005
Submission
doc.: IEEE 802.11-05/0908r0
page 6
Peter Ecclesine, Cisco Systems