Doc.: IEEE 802.11-05/0796r1
IEEE P802.11
Wireless LANs
|TGV Work List |
|Date: 2005-097-192 |
|Author(s): |
|Name |Company |Address |Phone |email |
|Pat Calhoun |Cisco Systems |170 West Tasman Dr. |+1 408 853-5269 |pcalhoun@ |
| | |San Jose, CA 94588 | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
Introduction
This document contains a list of work list that have been identified as candidate work list for TGv. It is important to note that not all items listed in this document are official work list.
For every requirement listed, there may be an owner assigned to it. When an owner appears, it means that the individual in question has agreed to present his or her ideas in regards to this topic. After a presentation has been made, a decision can be made by the task group on whether the item is a requirement that is to be officially considered.
Assumptions/Design Goals
The task group has identified the following assumptions and design goals:
• The station must be controlled from an RF configuration perspective
• Understand what the algorithms are, but not define them
• Setting MIB variables over the air has security implications. There are two categories of “client configuration” that exist in this document. The first are things such as load balancing and “rf related” items (e.g., transmit power). The second is more drastic, such as downloading firmware or changing the SSID of the station. We should categorize all of the “configuration items” into buckets, in terms of those that could be managed by any network, and those that are “policy configuration” on the laptop that should not be exposed except to the “home network”.
• The work created by TGv cannot create new denial of service attacks in open systems, such as in a hot spot. Even RF configuration items may require authentication. TGv will rely on the security services provided by TGw.
• Authentication and authorization is required. The former is provided by TGw, while the latter may be a manually configured policy decision.
o Security Requirements need to be defined
• Owner: Emily Qi (11-05-0369-01-000v-secure-wnm-requirements)
Open Items
The following open items should be resolved
• Are there any additional work list in 11-05/0076r0 that need to be included in this document?
• Do we need to define what an SME is in a terminal?
o How does this relate to the APF work
o Is this within scope of 802.11?
o TGH did specify some behaviour required in the SME, but not algorithms.
Owner: Pat Calhoun
• Interdependencies of 802.11v and other TGs
o 802.11s may also need some management help (e.g., end-to-end throughput)
o 802.11u is interested in Virtual APs
Owner: Pat Calhoun
Accepted Work list
1. RF Management
a. Dynamic channel selection
Switch of channel and/or AP – due to interference, AP may want to change channel
Provided by 802.11h, but it’s only used for 802.11a
Owner: Marian Rudolf
Document:11-05-0497-00-000v-dcs-kwak-rudolf.ppt
TG Decision: Possibly in scope
b. Adjusting Tx Power on Station
Works closely with EDT control
Transmit Power Control – configuring the station’s power level
Rate control
Using disassociation is too drastic – some less performance impacting method is needed
Owners: Marian Rudolf and Joe Epstein
Document: 11-05-0506-00-000v-tx-power-requirements.ppt
11-05-0498-01-000v-tpc-edt-kwak-rudolf.ppt
TG Decision: Possibly in scope
1. Access Point Coordination
a. Intra-ESS
Time coordination between APs for resource management. Could be useful for 802.11e
to perform time slicing. Site Survey mode to perform tuning of the Aps. Could be
an initial install or on-going process.
Power coordination.
Neighbour learning process
Antenna control could also be useful in this case – AP to AP, as opposed to AP to STA
Owner: Marian Rudolf, John Klein, Joe Epstein
Document: 11-05/0505r0
TG Decision: Possibly in scope
b. Spectrum etiquette (inter-ESS)
What issues exist to STA and AP in environments that have multiple 802.11 networks
Overlapping BSS (from an RF management perspective) (e.g., dynamic channel
allocation)
Good Neighbor policy vs. rogue AP
Owner: Roger Durand
c. Coexistence
Classify RF signals from other systems (e.g., Bluetooth)
Signal classification, priorities and expected behaviour
Owner: Simon Black will present ‘k’ paper
Timeframe: September meeting
TG Decision: This is a work item for 802.19 and should not be a work item for TGv. Invite .19 representative to present their work in this area.
3. Load Balancing
Network Controlled handoffs
Should the client control, participate, or should it be controlled by the infrastructure?
Owners: Emily Qi, Necati Canpolat and Joe Epstein
Documents: 11-05/0370r2, 11-05/0501r0,
TG Decision: Possibly in scope
6. Antenna and beam forming
Management of advanced (e.g., 802.11n) antenna options
What can be done to improve the devices already in the market
Radio measurements in diversity antennas can lead to inconsistent RF measurement
802.11k is not antenna aware – 802.11v should be antenna aware and manage them
802.11v should also include advertising antenna characteristics as well
Owner: Joe Kwak
Documents: 11-05/0280r1, 11-04/1102r1
Timeframe: September
**Pat to go through the minutes and move it to the right section
8. Updating firmware
Owner: Richard Paine, John Klein
Document: 11-05-0507-00-000v-firmware-updates.ppt
TG Decision: AP Firmware Upgrade in scope, client firmware upgrade out of scope
9. Diagnostics and Troubleshooting
802.11k measurements could be used as a base
Packet generation
Place client into a diagnostic mode
How deep do we go on this topic?
Troubleshooting 802.1x and other security protocols
Owner: Necati Canpolat, Joe Epstein
Timeframe: September meeting
11. Power Saving
Does Wake On Wireless apply to 802.11v?
Stand-by and Power Management extensions could be desirable
Should 802.11v define a “deep sleep” mode
Is it already in 2003?
Could the network control, or be more aware of, station power saving algorithms?
Since power save is very HW/implementation specific, can this be done?
Owner: Jarkko and Marian Rudolf
Document: 11-05-0499-00-000v-power-saving-kwak-rudolf.ppt
TG Decision: Long term power saving issues possibly in scope
12. Virtual APs
Multiple SSIDs – not all broadcast, send it out as a single list
Multiple SSID
How does this affect RF management – could physical AP be communicated?
Also being discussed in Tgu
Owner: Pat Calhoun
Document: 11-05-0270r1-virtual-ap-requirements.ppt
TG Decision: Possibly in scope
13. MIB Interface
TGv will define an action frame that allows for MIB Variable GET/SET over the air to the STA. We could build on top of 802.11k messages?
Owner: Tim Olson
Document: 11-05-732r0-client-management-protocol.ppt
TG Decision: Possibly in scope
15. To SNMP or not to SNMP
There has been a question as to whether SNMP is appropriate (and efficient) for 802.11 management. The TG will investigate whether alternatives to SNMP (e.g., XML) would be better. There was an early study group paper for reference: 04/1104r0
Owner: Tim Olson, Simon Black
Timeframe: September meeting
Document:
TG Decision:
17. Security
Dependency on 802.11w
If we are addressing client configuration, then we cannot avoid security
Owner: Emily Qi
Document: 11-05-0369-01-000v-secure-wnm-requirements
TG Decision: The TGv components of this document are listed in 05/0642-r0
23. Operator Requirements
Network Selection – could the infrastructure provide more information to help the STA
select the right network?
Fake SSID – How does a STA know whether an SSID is valid or not
Some authentication or validation would help
Owner: Lars Falk
Document: 11-05/0169r0
TG Decision: Pat to go through the minutes
25. E911
E911 for WLANs have certain implications in terms of access control and location.
Owners: Marian Rudolf
Joe Kwak
Documents: 11-05/0014r0, 11-05/0014r1
Timeline: November
TG Decision: Discuss in September. Decide in November in joint TGu meeting
Pending Work list
The following work list have been identified as being of interest, but have not been officially accepted as of yet, and an owner and presentation is required to move forward:
4. Location based management
Pushing location based policies to the station (e.g., special Qos policies in RF problematic areas,
security)
What about privacy issues?
What can TGv add that doesn’t already exist
Owners: Veera Anantha, Necati Canpolat
Timeframe: September meeting
6. Antenna and beam forming
Management of advanced (e.g., 802.11n) antenna options
What can be done to improve the devices already in the market
Radio measurements in diversity antennas can lead to inconsistent RF measurement
802.11k is not antenna aware – 802.11v should be antenna aware and manage them
802.11v should also include advertising antenna characteristics as well
Owner: Joe Kwak
Documents: 11-05/0280r1, 11-04/1102r1
Timeframe: September
**Pat to go through the minutes and move it to the right section
9. Diagnostics and Troubleshooting
802.11k measurements could be used as a base
Packet generation
Place client into a diagnostic mode
How deep do we go on this topic?
Troubleshooting 802.1x and other security protocols
Owner: Necati Canpolat, Joe Epstein
Timeframe: September meeting
15. To SNMP or not to SNMP
There has been a question as to whether SNMP is appropriate (and efficient) for 802.11 management. The TG will investigate whether alternatives to SNMP (e.g., XML) would be better. There was an early study group paper for reference: 04/1104r0
Owner: Tim Olson, Simon Black
Timeframe: September meeting
Document:
TG Decision:
20. Fault Tolerance/Management
It was noted that fault tolerance was never addressed in 802.11k, and should be in 802.11v.
This could include coverage survey
Owners: Tatsuji Munaka
Documents:, 11-05/0048r0
Timeline: July
TG Decision: Pat to go through the minutes
24. AP MIB
TGv PAR states that we will develop a MIB that covers an Access Point’s function
Owners:
Documents:
Timeline: July
TG Decision: Pat to send email request to exploder (Paul Gray may be interested and has been volunteered)
Non-Work list (‘B’ category)
During the discussions at various meetings, several items have been discussed that have been identified as work items that the task group should not pursue. In order to reduce the possibility or rehashing old issues, these are listed here.
5. Home Area
Ease of Use
Initial Configuration – auto-provisioning of station
Owner: Necati Canpolat
TG Decision: This topic is already covered by WFA and does not need TGv’s attention
7. Client control & cooperation
IDS collaboration
Non-802.11 based interference – is there anything else required
Owner: Necati Canpolat
Timeframe: May meeting
10. Active Management Technologies (AMT)
It is being defined for Ethernet LAN
How will it work on 802.11 – they have started looking at 802.11
Are there any implications or relevance to 802.11v
Owner:
Timeframe: July meeting
14. SME Interface
Many of the interesting operations occur in the SME, not the PHY. Should 802.11v bring some parts of the SME into the standard, while leaving the controversial parts out. For instance, the SSID that the STA is associated to. However, leave roaming algorithms out. Now that we have many interoperable implementations, perhaps there is enough operational experience to start this work.
Owner:
Timeline: July
19. What does 802.11v do with IBSS?
TGv will have no choice but to deal with this requirement. Does the introduction of 802.11s introduce IBSS management requirements?
Owner: None
TG Decision: Send request to TGs on whether they require TGv’s attention
21. Advertising Service Capabilities
Does advertising service really belong at the IEEE layer, or is this an IETF problem (e.g., EAP)
Will the service classifications listed in the presentation still be relevant in a couple of years?
If the IEEE 802.11TM WG is interested, then TGu would be a better place
The concept of a “management” SSID was discussed (it would only provide service level information)
Owner: Pat Calhoun/Rohan Mahy (11-05/1595r0)
TG Decision: Already a TGu work item
16. Control framework for 802.11v
Owner: Marian Rudolf
Timeframe: Sept meeting
Document: 11-05-0500-01-000v-11v-control-kwak-rudolf.ppt
TG Decision: Discuss and develop ideas in future meetings
-----------------------
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 , 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at .
Abstract
This document includes the requirements discussed at the 802.11v meeting at the July September 2005 meeting in San FranciscoGarden Grove. This document is intended to be a live document.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- 0.05 significance level
- 0.05 significance level calculator
- 0 05 significance level calculator
- 2.05 apy
- interpreting 0.05 significance level
- 0 05 significance level
- interpreting 0 05 significance level
- ieee journal suggester
- p value 0 05 means
- p 0 05 is significant
- is 0 05 significant
- statistical significance 0 05 meaning