Extend Management Frame Subtype

Slides:



Advertisements
Similar presentations
LB84 General AdHoc Group Sept. Closing TGn Motions
Advertisements

[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
Motions Date: Authors: January 2006
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
Emergency Call Motion Date: Authors: January 2006
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
WNG SC Closing Report Date: Authors: November 2005
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGu Closing Report Date: Authors: September 2005
ADS Study Group Mid-week Report
Selection Procedure Recommendation
TGu-changes-from-d0-01-to-d0-02
September Opening Report
LB73 Noise and Location Categories
IEEE White Space Radio Intended timeline
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
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
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
[ Policies and Procedure Summary]
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
Motion to go to Letter Ballot
TGu-changes-from-d0-04-to-d0-05
Transition Nowhere Date: Authors: Sept 2005 Sept 2005
Motion for request of assigned numbers
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
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Timeline Date: Authors: July 2005 July 2005
TGr Proposed Draft Revision Notice
Selection Procedure Recommendation
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Extend Management Frame Subtype January 2005 doc.: IEEE 802.11-05/1624r0 January 2005 Extend Management Frame Subtype Date: 2005-01-14 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>. Haixiang He, Nortel Networks Haixiang He, Nortel Networks

January 2005 doc.: IEEE 802.11-05/1624r0 January 2005 Abstract This presentation discusses an issue of the shortage of management subtypes. A straw-man solution is also proposed. The goal of this presentation is to encourage the working group members to think about this issue and to solicit feedback on how to move forward with this work. Haixiang He, Nortel Networks Haixiang He, Nortel Networks

Shortage of Management Subtypes January 2005 Shortage of Management Subtypes The Subtype field is 4 bits long. (according to 2003 edition) It means that only 16 subtypes are allowed. 11 of 16 Management subtypes have been used. Only 5 subtypes are reserved for future usage. New management frames are being proposed For example, in 11k (RRM) and 11r (Fast BSS Transition). Haixiang He, Nortel Networks

January 2005 Possible Mitigation Piggyback new management frames into existing management subtypes. This is possible, but less than optimal. First, it does not make semantic sense to reuse existing management subtypes such as Authentication, Association. Second, the existing management frames are inflexible for extension. Many existing and/or required payloads are not needed for the new management frames. Haixiang He, Nortel Networks

Straw-man Proposal Allocate subtype “1111” as an extended subtype. January 2005 Straw-man Proposal Allocate subtype “1111” as an extended subtype. No change to existing management frames. The first 2 bytes of the Frame Body of type “1111” is the Extended Management Subtype field. 2 bytes are used for identifying future management frames. Extended MF subtypes will be assigned by the 802.11 following the existing allocation process (i.e. new entries are marked as TBD until the draft is finalized). Haixiang He, Nortel Networks

January 2005 Open Issue How to allocate the space? Should we also suggest/recommend/dictate a method of assigning new MF type codes? Thought One: reserve "1xxxx" for vendor specific MF subtypes. Haixiang He, Nortel Networks

Feedback This issue affects the whole 802.11 WG. January 2005 Feedback This issue affects the whole 802.11 WG. Where is the appropriate place to discuss this issue? WG, WNG, TGma ? Suggestions for moving forward strategy. Haixiang He, Nortel Networks

January 2005 References Haixiang He, Nortel Networks