1. 802.11 Scope Date: 2005-07-15 Authors: July 2005 July 2005
doc.: IEEE /0668r0
July 2005
Scope
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Mike Moreton, STMicroelectronics
Mike Moreton, STMicroelectronics

2. Abstract This submission discusses the scope of 802.11. July 2005
doc.: IEEE /0668r0
July 2005
Abstract
This submission discusses the scope of
Mike Moreton, STMicroelectronics
Mike Moreton, STMicroelectronics

3. Extract from 802 LMSC P&P 2. LMSC Scope
July 2005
Extract from 802 LMSC P&P
2. LMSC Scope
The scope of the IEEE Project 802 (IEEE P802) LAN MAN Standards Committee (LMSC) is to develop and maintain networking standards and recommended practices for local, metropolitan, and other area networks, using an open and accredited process, and to enable and advocate them on a global basis.
Mike Moreton, STMicroelectronics

4. Extract from 802.11 Policies and Procedures
July 2005
Extract from Policies and Procedures
2.1 Function
The ™ WG's charter is to develop Physical layer and MAC sub-layer specifications for wireless Local Area Networks (LANs) carried out under Project Authorization Requests (PAR) approved by the IEEE Standards Board and assigned to ™ WG.
Mike Moreton, STMicroelectronics

5. Scope of 802 and 802.11 The scope of 802 is almost unlimited
July 2005
Scope of 802 and
The scope of 802 is almost unlimited
It’s clear that the scope of was intended to be much more limited
How limited depends on how you interpret “MAC sub-layer”.
Mike Moreton, STMicroelectronics

6. Use of term “MAC Sublayer”
July 2005
Use of term “MAC Sublayer”
IEEE 802 (2001) says:
“the Data Link layer is structured as two sublayers, with the LLC sublayer operating over a MAC sublayer.”
“The MAC sublayer performs the functions necessary to provide packet-based, connectionless-mode (datagram style) data transfer between stations in support of the LLC sublayer”
IEEE REV-ma-D2.0.pdf says:
“IEEE is required to appear to higher layers [logical link control (LLC)] as a current style IEEE 802 LAN. This requires that the IEEE network handle station mobility within the MAC sublayer.”
Mike Moreton, STMicroelectronics

7. Meaning of “MAC Sub-Layer”
July 2005
Meaning of “MAC Sub-Layer”
Seems to be anything that isn’t the PHY, and anything that isn’t the LLC.
Has been used in an context to include the DS.
Arguably allows us to invent protocols that work across the DS
All the scope of is saying by MAC sub-layer is “make sure you use LLC”
Mike Moreton, STMicroelectronics

8. Protocol Stacks July 2005 July 2005 doc.: IEEE 802.11-05/0668r0
From 3GPP
Mike Moreton, STMicroelectronics
Mike Moreton, STMicroelectronics

9. The 7 Layer Model Is just a model, it’s not always reality…
July 2005
The 7 Layer Model
Is just a model, it’s not always reality…
You can’t determine which layer a protocol fits into solely by what it’s encapsulated in
What really matters is the function of a protocol, not how it’s transported
A well designed protocol should be independent of the protocol it’s encapsulated in – all that matters is the service provided by that protocol.
What determines the function is the level of the entities connected by a protocol
If they are MAC sub-layer entities, then any protocol that connects them is a MAC sub-layer protocol, even if it is transported in IP…
Mike Moreton, STMicroelectronics

10. Enough of the Legal Word Picking…
July 2005
Enough of the Legal Word Picking…
What is the pragmatic scope of ?
Suggested scope:
We do the things that no-one else will do in order to get networks to work.
We do this in a way that allows LLC to run over the top of us, and so allows us to fit into the 802 family of LANS.
Mike Moreton, STMicroelectronics

11. AP to AP Protocols 802.11 defines an 802.11 AP
July 2005
AP to AP Protocols
defines an AP
If we need a protocol between two AP entities then we can’t expect anyone else to do it
The DS gives us a transport independent mechanism for delivering frames between APs
Times have changed since TGF
We shouldn’t be scared of standardising AP to AP protocols.
Mike Moreton, STMicroelectronics

12. July 2005
Motion
Resolved: This group believes that standardisation of AP to AP protocols should not be excluded from the scope of
Mike Moreton, STMicroelectronics