CID 186, 206 and 211 resolution Date: Authors: January 2007

Slides:



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

LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Motions Date: Authors: January 2006
IEEE White Space Radio Contribution Title
London TGu Motions Authors: January 2007 Date: Month Year
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
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
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
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
TGn Frame Format Ad Hoc Status and Motions
CID 186, 206 and 211 resolution Date: Authors: January 2007
On Coexistence Mechanisms
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
TGu-changes-from-d0-01-to-d0-02
Number of Encoder as a function of MCS
LB73 Noise and Location Categories
PHY CID 3242 Date: Authors: September 2007 September 2007
Extended Channel Switch Announcements
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
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:
TGp Closing Report Date: Authors: March 2007 Month Year
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions
[ Policies and Procedure Summary]
PHY CID 3242 Date: Authors: September 2007 September 2007
Draft P802.11s D1.03 WordConversion
TGv Redline D0.13 Insert and Deletion
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
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
PSMP Adhoc Oct TGn Adhoc
Beamforming and Link Adaptation Motions for LB 84 Comment Resolutions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

CID 186, 206 and 211 resolution Date: 2007-01-15 Authors: January 2007 doc.: IEEE 802.11-07/0065r1 January 2007 CID 186, 206 and 211 resolution Date: 2007-01-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@ok-brit.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>. Jari Jokela, Nokia Jari Jokela, Nokia

January 2007 doc.: IEEE 802.11-07/0065r1 January 2007 Abstract This presentation includes proposed resolution to CID186, CID206 and CID211 Jari Jokela, Nokia Jari Jokela, Nokia

January 2007 CID186 Section: 7.3.2.45 CID 186: "Optional TCLAS Processing" IE is undefined. Proposed resolution: Change "Optional TCLAS Processing" to "TCLAS Processing" . Add "optional" operation in clause 9. Jari Jokela, Nokia

January 2007 Motion Move to include normative text (Part 1) in document 11-07-0066-00-000v-cid-186-211-normative-text.doc into the TGv draft. Mover: Seconder: Results: Jari Jokela, Nokia

January 2007 doc.: IEEE 802.11-07/0065r1 January 2007 CID206 Section: 7.3.2.46 CID 206: Why Multicast MAC Address is needed? Proposed resolution: Clarify FBMS Status Element Jari Jokela, Nokia Jari Jokela, Nokia

Multicast MAC address in FBMS Status element January 2007 Multicast MAC address in FBMS Status element It is not clear why it is needed as broadcast/multicast service is identified/specified by TCLAS element sent in the FBMS Request With TCLAS elements it is possible to define multiple services that are using the same MAC address => service cannot be identified by MAC address FBMSID is unique identifier for the service Proposal is to remove Multicast MAC address from the FBMS Status Element Jari Jokela, Nokia

Move to remove Multicast Address field from FBMS Status element January 2007 Motion Move to remove Multicast Address field from FBMS Status element Mover: Seconder: Results: Jari Jokela, Nokia

January 2007 CID211 Section: 9.2.7.1 CID 211: FBMS operation in case of non-transmitted BSSIDs (11.15.5) is not defined Proposed resolution: Need to define FBMS operation in case non-transmitted BSSID procedures are used. Problem is that usage of AID 0 Descriptor element is not specified in case of non-transmitted BSSID procedures are used Jari Jokela, Nokia

January 2007 Motion Move to include normative text (Part 2) in document 11-07-0066-01-000v-cid-186-211-normative-text.doc into the TGv draft. Mover: Seconder: Results: Jari Jokela, Nokia