Thoughts on the 802.1AM PAR Date: 2005-09-19 Authors: Sept 2005 doc.: IEEE 802.11-05/0940r1 Sept 2005 Thoughts on the 802.1AM PAR Date: 2005-09-19 Authors: 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>. Darwin Engwer, Nortel Darwin Engwer, Nortel

Sept 2005 doc.: IEEE 802.11-05/0940r1 Sept 2005 Abstract “I've flown from one side of the network to the other. I've seen a lot of strange stuff, but I've never seen anything to make me believe there's one all-powerful force that can control everything.” Darwin Engwer, Nortel Darwin Engwer, Nortel

The management field is very broad Sept 2005 The management field is very broad A: not clear whether 802.1AM will address over-the-air mgmt or over-the-backhaul network mgmt, or both poor scope definition in in the 802.1AM PAR B: Technical feasibility is greatly in question Darwin Engwer, Nortel

Quotes from the 802.1AM PAR, part 1 Sept 2005 Quotes from the 802.1AM PAR, part 1 13. Scope of Proposed Project: “This standard specifies managed objects to support Radio Frequency (RF) management across IEEE 802 wireless Media Access Control (MAC) layers.” 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.” Darwin Engwer, Nortel

Quotes from the 802.1AM PAR, part 2 Sept 2005 Quotes from the 802.1AM PAR, part 2 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 is essential to the long term viability of a heterogeneous LAN.” Darwin Engwer, Nortel

Quotes from the 802.1AM PAR, part 3 Sept 2005 Quotes from the 802.1AM PAR, part 3 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.” Darwin Engwer, Nortel

802.1AM Technical Feasibility Sept 2005 802.1AM Technical Feasibility over-the-air management over-the-backhaul network management Darwin Engwer, Nortel

over-the-air "management” Sept 2005 over-the-air "management” there is no common framework for over-the-air "management" between different RF technologies (within 802.11 let alone within 802) it is not viable bcus the devices operate in difference frequency bands using different modulation types and no single radio can (simultaneously) operate across all those bands/ modulation types. perhaps a SDR could perhaps do something in this regard by altering it's operational mode over time. But doing so on the fly is [today] impossible. needs to be real-time to address temporal aspects of management Darwin Engwer, Nortel

over-the-air "management” (cont’d) Sept 2005 over-the-air "management” (cont’d) well, unless you have a universal wideband transceiver. maybe this is a "subspace" communication [vs. today’s "ether" space communications], which we don't know how to do today subspace communication would need to occur outside space and time; currently that is only science fiction hence my updated position is not that over-the-air "management” is impossible, but that the fundamental support technologies required to make it work don't yet exist. Darwin Engwer, Nortel

over-the-backhaul network management Sept 2005 over-the-backhaul network management there is no common framework for over-the-backhaul network management between different types of RF networks the backhaul networks are different types, and are not interconnected even if they were interconnected they are likely in different administrative domains e.g. the hotel network is isolated from the 802 meeting net even if not isolated; which network has higher authority? e.g. hotel net does what our network tells it to do or vice versa? Darwin Engwer, Nortel

over-the-backhaul network management (cont’d) Sept 2005 over-the-backhaul network management (cont’d) further, some RF network types have no backhaul component at all (e.g. 802.15 and 802.11 IBSS/ ad hoc networks) Darwin Engwer, Nortel

Summary 802.1AM feasibility remains in question Sept 2005 doc.: IEEE 802.11-05/0940r1 Sept 2005 Summary 802.1AM feasibility remains in question this is not addressed by the 802.1AM PAR not yet responded to by 802.1 therefore the question remains open could be addressed by a supporting document if space in the PAR document is unduly constrained Value proposition is also unclear i.e. what is the value or benefit vs. the required effort? Darwin Engwer, Nortel Darwin Engwer, Nortel

Sept 2005 Darwin Engwer, Nortel

Sept 2005 Darwin Engwer, Nortel

Q & A Q: Is there a useful partial solution? Sept 2005 Q & A Q: Is there a useful partial solution? ans: solving part of the problem essentially doesn't solve the problem, since RF is a shared medium a partial solution would be like arranging things so you can be partially not pregnant I'm an optimist so I won't say that's impossible but any partial proposal should indicate how it will avoid the "9 month surprise" Q: Couldn’t we start with center frequency, power and bandwidth? not likely - even those basic concepts have completely different meanings, even across the subset of devices operating in the same spectrum, see [2] plus, other than being “cool”, what’s the benefit? Darwin Engwer, Nortel

References [1] am-wireless-management-draft-par-0705.doc (802.1) Sept 2005 References [1] am-wireless-management-draft-par-0705.doc (802.1) [2] 11-05-0892-01-0wng-dot1am-work-sizing.xls [3] 11-05-0907-00-0wng-dot1am-management-plane.ppt [4] 11-05-0908-00-0wng-dot1am-management-par-5c.doc Darwin Engwer, Nortel