1. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 1 802 ExCom should reject the proposed 802.1AM PAR and 5 criteria 2005-05-17 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, 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 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.http:// ieee802.org/guides/bylaws/sb-bylaws.pdfstuart.kerry@philips.compatcom@ieee.org

2. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 2 ExCom should reject the 802.1AM proposal, instead promoting manageability of all wireless standards 802.1 are proposing a PAR for common RF management 802.1 are proposing that 802.1AM develop media independent RF management protocols The 802.1AM proposal was inspired by a Backes & Montemurro tutorial in San Antonio in Nov 04 All 802 WG’s have an opportunity to comment on the 802.1AM PAR & 5 criteria before ExCom in JulyPAR 5 criteria What should 802 ExCom do? 802.11 should ask 802 ExCom to reject the 802.1AM PAR & 5 criteriaPAR 5 criteria 802 should encourage the wireless WG’s to ensure wireless networks are manageable

3. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 3 802.1 are proposing that 802.1AM develop media independent RF management protocols The PAR proposes a purposePAR 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 The PAR proposes a reasonPAR 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

4. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 4 The 802.1AM proposal was inspired by the Backes & Montemurro tutorial in San Antonio in Nov 04 The claimed problem The tutorial claims interoperable wireless network management is currently impossibletutorial A quote from tutorial states, “The lack of a standard RF management interface for different implementations of a given MAC as well as different wireless MACs prohibits multi vendor, interoperable wireless network management” The claimed solution The tutorial claims common management and common configuration algorithms are necessarytutorial A quote from tutorial states, “Common management and common configuration algorithms are essential to the long term viability of heterogeneous LAN”

5. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 5 All 802 WG’s have an opportunity to comment on the 802.1AM PAR & 5 criteria before ExCom in July Tutorial presented by: –Floyd Backes (Propagate) –Michael Montemurro (Chantry) Nov 04 802.1 developed and approved: –PARPAR –5 criteria5 criteria Jan - Mar 05 Other 802 WGs have an opportunity to comment May 05 Other 802 WGs have an opportunity to comment PAR & 5 criteria submitted to ExCom for approvalPAR5 criteria July 05 San AntonioMonterey - AtlantaCairnsSan Francisco We are here!

6. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 6 802.11 should ask 802 ExCom to reject the 802.1AM PAR & 5 criteria A common management interface is not necessary for interoperable wireless management A common management interface is likely to lack useful functionality or constrain other standards The claim that there is wide interest in the 802.1AM approach is misleading 802.19 often provides a better approach to heterogeneous WLAN management than 802.1AM 802.1 does not have the appropriate expertise to execute this proposal successfully

7. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 7 A common management interface is not necessary for interoperable wireless management The PAR & tutorial claim The tutorial claims the lack of a standard (& common) RF management interface prohibits multi vendor, interoperable wireless network management The rebuttal An interoperable management system could easily be constructed using a system that understood and leverages the unique management interfaces to each of 802.11, 802.15, etc

8. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 8 A common management interface is not necessary for interoperable wireless management 802.11802.15802.16802.20 802.1AM agent 802.1AM agent 802.1AM agent 802.1AM agent Simple but less functional manager 802.11 agent 802.15 agent 802.16 agent 802.20 agent Complex but more functional manager Common management interfaces Dedicated management interfaces.1AM.11.15.16.20 802.1AM approach Alternate approach

9. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 9 A common management interface is likely to lack useful functionality or constrain other standards The PAR claim The PAR claims that a standard (& common) RF management interface is a “good thing” The rebuttal Many people at the tutorial believed this work would likely result in relatively useless a “lowest common denominator” system that does not account for the unique properties of each of the wireless standards A more useful system (probably a superset of existing management mechanisms) would require changes to current standards and thus impose unacceptable constraints on the development of these standards

10. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 10 The claim that there is wide interest in the 802.1AM approach is misleading The 5 criteria claim The 5 criteria claims, “Many vendors and users that participate in wireless 802 working groups have expressed interest in having a consistent management service interface applicable to all 802 wireless standards” The rebuttal It is probably true that vendors and users have expressed interest in a common interface because it an “nice ideal” However, given a “lowest common denominator” system or a system requiring changes to multiple standards, the proposal is far less attractive It is also worth noting that the audience at the tutorial in San Antonio voted against this concept in a straw poll

11. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 11 802.19 often provides a better approach to heterogeneous WLAN management than 802.1AM The PAR claim The PAR claims common management & configuration algorithms are essential to the long term viability of a heterogeneous LAN The rebuttal The most interesting problems will often occur in unlicensed spectrum In this environment a system will often not have the administrative control required to manage heterogeneous WLANs in the way envisaged by 802.1AM A better approach might to rely on 802.19 to encourage coexistence, which can often be achieved without the need for explicit management messages

12. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 12 802.1 does not have the appropriate expertise to execute this proposal successfully The tutorial claim The tutorial claims 802.1 is the logical place to work on management applications because it has the most: –protocol expertise –management expertise The rebuttal It is arguable whether or not 802.1 has the most protocol expertise However, while 802.1 does have significant management expertise, it has virtually no wireless expertise Very detailed knowledge of 802.11, 802.15, 802.16, etc will be required to execute this project, and it is unlikely to be available to 802.1 from other WG’s

13. doc.: IEEE 802.11-05/0453r0 Submission May 2005 Andrew Myles, CiscoSlide 13 802 should encourage the wireless WG’s to ensure wireless networks are manageable The 802.1AM proposal is not useful, except as a low functionality “lowest common denominator” solution However, it is important to ensure wireless networks are manageable when appropriate and possible 802 ExCom should continue to encourage the 802 wireless WG’s to ensure their systems are manageable 802.11 is already taking the first steps down this road with: –802.11d (Regulatory management) –802.11h (Spectrum management –802.11k (Radio measurement) –802.11v (Wireless management) –… After 802.11 and the other wireless WG’s have “learnt to walk” they should (eventually) refine the interfaces for the use of external managers