Proposed Changes for D0.25 Comments Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2006 Proposed Changes for D0.25 Comments Date: 2006-01-19 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>. Bryan Wells, DENSO LA Laboratories John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 January 2006 Abstract Proposed solutions for comments Wells/5, /6, /7, /8, /9, and /10 as included in 11-06-0018-00-000p-p802-11p-d0-25-comments.xls. Bryan Wells, DENSO LA Laboratories John Doe, Some Company

January 2006 Problem description TGp accepted comments Wells/5, /6, /7, /8, /9, and /10 as included in 11-06-0018-00-000p-p802-11p-d0-25-comments.xls. TGp asked me to submit more specific change recommendations than those submitted with the original comments. Bryan Wells, DENSO LA Laboratories

Wells/5 Comment: Resolution January 2006 D0.25 Clause 7.4.5.1, pg 10 It is not clear how the TSF is to be used for WAVE Announcement Frames. Clause 11.1.2 of 802.11-REVma/D4.0 clearly describes the method of setting the timestamp value of beacons and probe responses. Similar description is needed for the timestamp in WAVE Announcement Frames. Resolution Change D0.25 subclause 7.4.5.1, pg10, line 8: “Timestamp format is defined in 7.3.1.10. A WAVE station sending a WAVE announcement shall set the value of the WAVE announcement’s timestamp so that it equals the value of the station’s TSF timer at the time that the data symbol containing the first bit of the timestamp is transmitted to the PHY plus the transmitting station’s delays through its local PHY from the MAC-PHY interface to its interface with the WM. Capability information is defined in 7.3.1.4.” Still need to identify an interface and method for updating the timestamp from an upper layer. Bryan Wells, DENSO LA Laboratories

Wells/6 January 2006 Comment: Resolution D0.25 Clause 10.3.24.3.2, pg 14 BSSID is not defined in 802.11p or 802.11-REVma/D4.0 (10.3.10.1.2), as indicated. BSSID for Infrastructure and IBSS networks is defined in 802.11-REVma/4.0 (7.1.3.3.3), however these definitions do not apply to WAVE networks. Resolution Change line 19 of .11p D0.25 to: “BSSID is defined in 7.1.3.3.3. SSID,… defined at… ” Insert after the 2nd paragraph of 7.1.3.3.3: “For a WBSS, the value of the BSSID field shall be the MAC address of the initiator of the WBSS . The value of this field in an OBU-initiated WAVE BSS shall be a locally administered IEEE MAC address as defined in 5.2 of IEEE Std 802-1990. The remaining 46 bits of that MAC address shall be a 46-bit random number. This MAC address shall be a number selected in a manner that minimizes the probability of STAs generating the same number, even when those STAs are subjected to the same initial conditions. It is important that designers recognize the need for statistical independence among the random number streams among STAs.” Add to the last paragraph of 7.1.3.3.3. Insert after the last sentence: “The broadcast BSSID shall be allowed for message broadcasting in WAVE.” Bryan Wells, DENSO LA Laboratories

Wells/7 Comment: Resolution D0.25 Clause 10.3.24.3.2, pg 14 January 2006 Wells/7 Comment: D0.25 Clause 10.3.24.3.2, pg 14 Timestamp is not defined in 802.11p or 802.11-REVma/D4.0 (10.3.10.1.2), as indicated. Timestamp is defined in 802.11-REVma/D4.0 (11.1), but only with respect to the TSF for Infrastructure and IBSS networks. Resolution See Wells/5. Bryan Wells, DENSO LA Laboratories

Wells/8 Comment: Resolution January 2006 D0.25 Clause 10.3.24.3.2, pg 14 Local time is not defined in 802.11p or 802.11-REVma/D4.0 (10.3.10.1.2), as indicated. Local time is defined in 802.11-REVma/D4.0 (10.3.2.2.2), but as a parameter of the BSSDescription, and in the context of the MLME-SCAN function. Resolution Remove “Local time” from 10.3.24.3.2, pg 14, line 19. Add to 10.3.24.3.2, pg14, before table: “Local time is the value of a WAVE station’s TSF timer at the start of reception of the first octet of the timestamp field of the received WAVE announcement action frame”. Bryan Wells, DENSO LA Laboratories

Wells/9 Comment: Resolution D0.25 Clause 11, pg 15 January 2006 Wells/9 Comment: D0.25 Clause 11, pg 15 Clause 11.1.1 of 802.11-REVma/D4.0 describes the TSF for Infrastructure and IBSS networks. A WAVE BSS will use the TSF different than both of the above. Resolution See Wells/5. Bryan Wells, DENSO LA Laboratories

Wells/10 Comment: Resolution: D0.25 Clause 11.7.1, pg 15 January 2006 Wells/10 Comment: D0.25 Clause 11.7.1, pg 15 Sub-clause 11.1.3 only describes BSSID for infrastructure and IBSS networks. Resolution: Change line 21 from … (as described in 11.1.3) to (as described in 7.1.3.3.3). Bryan Wells, DENSO LA Laboratories