Wireless Architectural Thoughts May 2005 doc.: IEEE 802.11-05/0481r0 May 2005 Wireless Architectural Thoughts Date: 2005-05-17 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

May 2005 doc.: IEEE 802.11-05/0481r0 May 2005 Abstract Some general thoughts about wireless architectural issues and 802 architectural issues. Darwin Engwer, Nortel Darwin Engwer, Nortel

May 2005 Scope of 802 802 originally deemed many architectural aspects to be out-of-scope from 802.11 WG now those seem to be in-scope, hence the proliferation of new 802.11 task groups Observation: 802 architectural issues are decided by WG and TG formation Are there any real architectural issues that have not essentially already been decided by TG formation? Darwin Engwer, Nortel

Potential 802 wireless architectural issues May 2005 Potential 802 wireless architectural issues AP functionality bridging access control - mobile STA authentication, authorization and admission (i.e. gating ala 802.1X) data frame processing encryption compression mobility network integrity (infrastructure device authorization) management? environmental issues coexistence (RF spectrum sharing)/ interference mitigation [link signal quality measurement] ... Darwin Engwer, Nortel

May 2005 Wired and Wireless The difficulty is that in a wired network many core issues are easily handled in an architectural fashion. But, in a wireless network there becomes a strong MAC-level (or lower) effect that varies from MAC-to-MAC. For example, you can't architect away mobility at the 802 level. Certainly there is an aspect of mobility that must be considered that is above the MAC. But, each individual MAC implementation must also be directly involved in addressing a level of mobility that is below the 802 level. The same comment applies to the other architectural aspects enumerated above. Darwin Engwer, Nortel

802 WGs and TGs The result is the failure of groups like 802.10. May 2005 802 WGs and TGs The result is the failure of groups like 802.10. Hence we see a security group in 802.11i, a mesh group in 802.11s, a mesh group in 802.15.5, a mobility group in 802.11r, a mobility group in 802.15, and a mobility group (next hierarchical level up) in 802 (i.e. 802.21). There is also a complexity issue here. All other things being equal, wireless issues tend to be more complex than wired issues. Darwin Engwer, Nortel

May 2005 Improving the Process Given those observations, what can we do to improve 802's architecture process so that these work efforts are better and more uniformly partitioned? One area that is not addressed well today (that is within scope of 802) relates to network discovery by [wired or] wireless mobile STAs. IETF DNA dabbles in this area, but not effectively to date, because they can't modify the [wireless] LAN infrastructure to provide the information that the [wireless] mobile STAs need. We (as 802) can provide that information. [Steve McCann notes that TGu is doing this and will propose changes to 802 to make this work] Darwin Engwer, Nortel

May 2005 References none Darwin Engwer, Nortel