Scope Date: Authors: July 2005 July 2005

Slides:



Advertisements
Similar presentations
IEEE P Wireless RANs Date:
Advertisements

Coexistence Motions for LB84 Comment Resolution
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
SG CUB Tentative Timeline
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
TGu Closing Report Date: Authors: May 2006 May 2006
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
TGu Motions Date: Authors: September 2006 September 2006
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGu Timeline Date: Authors: January 2005 January 2005
TGv Redline D0.06 Insert and Deletion
IEEE WG Opening Report – July 2008
ADS Study Group Mid-week Report
TGu Timeline Date: Authors: July 2005 July 2005
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
Document Motions Date: Authors: November 2005 November 2005
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions
[ Policies and Procedure Summary]
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
Scope Date: Authors: July 2005 July 2005
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
WNG SC Closing Report Date: Authors: November 2005
TGu Timeline Date: Authors: May 2005 May 2005
TGu Timeline Date: Authors: July 2005 July 2005
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Timeline Date: Authors: July 2005 July 2005
TGr Proposed Draft Revision Notice
WNG SC Closing Report Date: Authors: July 2006 July 2006
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

802.11 Scope Date: 2005-07-15 Authors: July 2005 July 2005 doc.: IEEE 802.11-05/0668r0 July 2005 802.11 Scope Date: 2005-07-15 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>. Mike Moreton, STMicroelectronics Mike Moreton, STMicroelectronics

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

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

Extract from 802.11 Policies and Procedures July 2005 Extract from 802.11 Policies and Procedures 2.1 Function The 802.11™ 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 802.11™ WG. Mike Moreton, STMicroelectronics

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

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 802.11REV-ma-D2.0.pdf says: “IEEE 802.11 is required to appear to higher layers [logical link control (LLC)] as a current style IEEE 802 LAN. This requires that the IEEE 802.11 network handle station mobility within the MAC sublayer.” Mike Moreton, STMicroelectronics

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 802.11 context to include the DS. Arguably allows us to invent protocols that work across the DS All the scope of 802.11 is saying by MAC sub-layer is “make sure you use 802.2 LLC” Mike Moreton, STMicroelectronics

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

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

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

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

July 2005 Motion Resolved: WNG SC believes that standardisation of AP to AP protocols over the DS should be included in the scope of 802.11. Mike Moreton, STMicroelectronics