1. Proposed Changes for LB81 Comments
Month Year
doc.: IEEE yy/xxxxr0
May 2006
Proposed Changes for LB81 Comments
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
B. Wells, J. Hunzinger, DENSO LA Laboratories
John Doe, Some Company

2. Month Year
doc.: IEEE yy/xxxxr0
May 2006
Abstract
Identify major issues and recommend procedure for addressing them.
Many comments
Common issues
Resolving each issue has the potential to resolve multiple comments
B. Wells, J. Hunzinger, DENSO LA Laboratories
John Doe, Some Company

3. Problem description Major comments from IEEE 802.11 LB #81
May 2006
Problem description
Major comments from IEEE LB #81
Multi-Channel MAC
MAC Congestion Control
MAC Message QoS
B. Wells, J. Hunzinger, DENSO LA Laboratories

4. LB #81 Multi-channel Comments
May 2006
LB #81 Multi-channel Comments
Multi-channel MAC not completely specified in P802.11p D1.0.
See CIDs 166, 167, 214, 217, 347, 380, 465, 466, 485, 925, etc.
P802.11p is coupled to a channel switching method described in P
Other drafts specify channel switching (e.g h, P802.11s D0.01, March ‘06).
B. Wells, J. Hunzinger, DENSO LA Laboratories

5. May 2006
LB #81 Multi-channel Comments Problems with defining WAVE multi-channel MAC outside of p
802.11p spec defines multiple 10 and 20MHz channels in the PHY but does not specify Medium Access Control (MAC) for the 75MHz of spectrum ( GHz).
How can MAC Prioritization & QoS services specified in (e) be applied and used outside of ?
Spec must not assume implementation of both the MAC and “the rest of the WAVE MAC” on the same silicon.
B. Wells, J. Hunzinger, DENSO LA Laboratories

6. May 2006
LB #81 Multi-channel Comments Problems with defining WAVE multi-channel MAC outside of p
If all channel coordination is removed from p, then all unnecessary timing and synchronization requirements associated with channel coordination must be removed from p as well, (no beacons, no scanning.)
Why is Timestamp information in the WAVE Announcement Frame? How is it used? (See )
Why is MLME timing synchronization required? (See )
Why is Timestamp and Local Time in the MLME.WAVEANNOUNCEMENT.indication? How are they used? (See )
Why is Timestamp and Local Time in the MLME.WAJOIN.request? How are they used? (See )
Why is synchronization necessary when initializing a WBSS? (See )
Why is it necessary for a User to adopt the Timestamp of a Provider when joining a WBSS? (See )
B. Wells, J. Hunzinger, DENSO LA Laboratories

7. LB #81 Multi-channel Comments
May 2006
LB #81 Multi-channel Comments
Recommendations
Define the complete MAC and MLME in p.
Open P802.11p TG to proposals for a globally effective channel switching method to be completely specified in .11p.
B. Wells, J. Hunzinger, DENSO LA Laboratories

8. May 2006
Motion
Move to issue a call for proposals in P802.11p TG for a complete multi-channel switching method, including managing and coordinating channel switching operations, to be completely specified within the p standard.
Motion by:
Second:
Approve:
Disapprove:
Abstain:
B. Wells, J. Hunzinger, DENSO LA Laboratories

9. LB #81 Congestion Control Comments
May 2006
LB #81 Congestion Control Comments
Congestion control process incomplete in P802.11p D1.0
See CIDs 101, 202, 390, 473, 1009, etc.
P802.11s D0.01 defines congestion monitoring and rate control methods, but defers decisions for controlling congestion to upper layers.
Recommendations
Limit p scope to defining congestion monitoring and control methods.
Defers decisions for controlling congestion to upper layers
Open P802.11p TG to proposals for globally effective methods of congestion monitoring and control.
B. Wells, J. Hunzinger, DENSO LA Laboratories

10. May 2006
Motion
Move to issue a call for proposals in P802.11p TG for a complete congestion control method, including monitoring and control operations, to be completely specified within the p standard.
Motion by:
Second:
Approve:
Disapprove:
Abstain:
B. Wells, J. Hunzinger, DENSO LA Laboratories

11. May 2006
LB #81 QoS Comments
EDCA parameters and QoS requirements are unclear in P802.11p D1.0.
See CID 46, 53, 212, 547, 720, 887, etc.
Goal: Ensure appropriate QoS for applications.
Check: Does selected QoS mechanism meet requirements?
WAVE is expected to support much larger networks than traditional (500+)
Broadcast communications anticipated for WAVE may limit detection of collisions and subsequent MAC retransmissions (if 4-way handshake not used).
Recommendations
Research and evaluate e EDCA mechanism for WAVE.
Open P802.11p TG to proposals for QoS enhancements.
B. Wells, J. Hunzinger, DENSO LA Laboratories

12. May 2006
Motion
Move to issue a call for proposals in P802.11p TG for Quality of Service enhancements, to be completely specified within the p standard.
Motion by:
Second:
Approve:
Disapprove:
Abstain:
B. Wells, J. Hunzinger, DENSO LA Laboratories