November 2006doc.: IEEE 802.11-06/1611r0
IEEE P802.11
Wireless LANs
Date: 2006-10-25
Author(s):
Name / Company / Address / Phone / email
Bill Marshall / TGr Editor / 180 Park Ave, Florham Park, NJ07932 / 973-360-8718 /
Comment #1184
Comment: The term "reservation" and "resource request" are seemingly used interchangeably in the document.
Proposed change: Suggest changing "Reservation" to "Resource Request"
Make the following changes to D3.0:
In addition to the 23 comments that identified specific places in D3.0 to change,
7.3.1.9:
Change text of status code 53 from “Expected a reservation to precede Fast BSS Transition” to “Expected a resource request to precede Fast BSS Transition”
7.3.2.45:
In Figure 112T, change “Reservation over air” to “Resource request over air”, change “Reservation over DS” to “Resource request over DS”, and change “Reserve option” to “Resource request option”
In paragraph below Figure 112T make corresponding changes. Also change “resource reservation” to “resource request”, and “reservation request” to “resource request”
7.4.7.3:
In first sentence, change “reserve resource” to “request resources”
8A.1.1:
Change “Reservation over air” to “Resource request over air”, change “Reservation over DS” to “Resource request over DS”, and change “Reserve option” to “Resource request option”
Change MIB variables “dot11FTReservationOverAirEnabled” to “dot11FTResourceRequestOverAirEnabled”, “dot11FTReservationOverDSEnabled” to “dot11FTResourceRequestOverDSEnabled”, and “dot11FTReservationRequired” to “dot11FTResourceRequestRequired”
8A.3.3:
In first paragraph, change “reservation mechanism” to “resource request protocol”
In third paragraph, change “reservation” to “resource request” twice.
8A.3.6:
In third paragraph, change “reservation” to “resource request” twice.
8A.4:
In third paragraph, change “Reservation over air” to “Resource request over air”, change “Reservation over DS” to “Resource request over DS”, and change “Reserve option” to “Resource request option”
Also in third paragraph, change “reservation request” to “resource request”. 13 changes in all.
8A.4.1:
In fourth paragraph, change “reservation” to “resource request”
In fourth paragraph, leave “PTKSA shall be reserved” unchanged.
8A.5:
In first paragraph, change “resource reservation” to “resource request”.
In second paragraph, change “reservation” to “request”.
8A.6:
In list of MLME interfaces, change “reservation over the air” to “resource request over the air”, and change “MLME_RESERVATION” to “MLME-RESOURCE-REQUEST”
8A.8.1:
In fourth paragraph, change “reservation” to “resource request” twice.
In final paragraph, change “reservation” to “resource request”
8A.8.3.1:
In seventh paragraph, change “reserved” to “accepted”
In ninth paragraph, change “reservation” to “request”.
8A.8.3.2:
Change MLME-RESERVATION_LOCAL to MLME-RESOURCE_REQUEST_LOCAL.
10.3.7.2.2:
Change “This includes an optional resource reservation response” to “This includes an optional response to a resource request”
10.3.7.4.2:
Change “This includes an optional resource reservation response” to “This includes an optional response to a resource request”
10.3.34.3.2:
Change “This includes an optional resource reservation response” to “This includes an optional response to a resource request”
10.3.34.4.2:
Change “This includes an optional resource reservation response” to “This includes an optional response to a resource request”
10.3.34.4.4:
In first paragraph, change “reservation” to “resource request” twice.
11.4.3:
In paragraph under figure, change “Reservation message” to “message”
11.4.4a:
Change “reservation” in title to “resource request”
In first paragraph, change “reservation message” to “resource request message”
In second paragraph, change “reservation” to “resource request”
D:
Change “dot11ReservationOverAirEnabled” to “dot11ResourceRequestOverAirEnabled”
Change “dot11ReservationOverDSEnabled” to “dot11ResourceRequestOverDSEnabled”
Change “dot11ReservationRequired” to “dot11ResourceRequestRequired”
Change “dot11ReservationLimit” to “dot11ResourceRequestLimit” (isn’t this obsolete?)
In description of “dot11ReservationRequired” change “Reservation mechanism” to “resource request mechanism” (twice).
Comment #1160
Comment: The term "mechanism" is not specific and should be replaced; the text alteady uses the term "services".
Counter proposal: Since “service” already has a meaning in 802.11, change "mechanism" to "method" or “protocol”. The 26 specific places identified for change established the pattern.
Make the following changes to D3.0:
In addition to the 26 comments that identified specific places in D3.0 to change,
3.95a:
Change “mechanism” to “protocol”
3.95b:
Change “mechanism” to “protocol”
7.3.2.45:
In final paragraph, change “mechanism” to “method” twice
8.4.1.1:
In second and third dash list item, change “mechanism” to “method”
8A.1.2:
In second paragraph, change “mechanism” to “protocol”
8A.4:
In thid paragraph, change “mechanism” to “method”
8A.6:
In second paragraph, change “mechanisms” to “methods”
8A.6.1.1:
In CALC-PMK-R1, change “mechanism” to “method”
8A.6.4.1:
In FT-AIR-REQUEST, change “mechanism” to “method”
In FT-DS-REQUEST, change “mechanism” to “method”
In FT-INIT, change “mechanism” to “method”
8A.8.1:
In final paragraph, change “Base Mechanism” to “protocol”
D:
In description of dot11FTReservationOverAirEnabled, change “mechanism” to “protocol”
In description of dot11FTReservationOverDSEnabled, change “mechanism” to “protocol”
In description of dot11FTReservationRequired, change “mechanism” to “protocol”
Comment #1205/1245 (also 1277/1296/1298 reference this change)
Comment: Figures 158B,C,D and E provide flows and descriptions which are more completely described in clause 8A.3.1,.2, .4 and .5. and its unnecessary to keep going back from one section to another, and verifying that the text is consistent.
Proposed change: Move the figures and associated text to the corresponding sections in clause 8A.3. This will make the text consistent with 8A.2.1 and 8A.2.2, which have the figures ans all text description in one subsection.
Comment #1245 was similar, for 8A.1.3 figures moving into 8A.4.
Make the following changes to D3.0:
8A.1.1:
Change 8A.1.1 to 8A.2 (since there is no longer a 8A.1.2)
8A.1.2 and 8A.1.3:
Delete, after moving the figures as below.
8A.3:
Insert at beginning of clause “Systems capable of Fast BSS Transition shall support the Fast BSS Transition protocol[#1199]”.
8A.3.1:
Insert at beginning of clause “The over-the-air Fast BSS Transition protocol in an RSN is shown in Figure 158b.”
Insert figure following this paragraph.
Insert after figure “The STA and AP use this Authentication Algorithm to specify the PTKSA and to provide values of SNonce and ANonce that enable a liveness proof, replay protection, and PTK key separation. This exachange enables a fresh PTK to be computed in advance of reassociation. The PTKSA is used to protect the subsequent reassociation transaction, including the optional resource request[#1219].”
8A.3.2:
Insert at beginning of clause “The over-the-DS Fast BSS Transition protocol in an RSN is shown in Figure 158c.”
Insert figure following this paragraph.
8A.3.4:
Insert at beginning of clause “The over-the-air Fast BSS Transition protocol in a non-RSN is shown in Figure 158d.”
Insert figure following this paragraph.
8A.3.5:
Insert at beginning of clause “The over-the-DS Fast BSS Transition protocol in a non-RSN is shown in Figure 158e.”
Insert figure following this paragraph.
8A.4:
Copy first two paragraph of 8A.1.3 to beginning of 8A.4.
8A.4.1:
Insert at beginning of clause “The over-the-air Fast BSS Transition resource request protocol in an RSN is shown in Figure 158f.”
Insert figure following this paragraph, removing RIC-Request and RIC-Response from the Reassociation exchange.
Insert “The over-the-air Fast BSS Transition resource request protocol in a non-RSN is shown in Figure 158h.”
Insert figure following this paragraph, removing RIC-Request and RIC-Response from the Reassociation exchange.
8A.4.2:
Insert at beginning of clause “The over-the-DS Fast BSS Transition resource request protocol in an RSN is shown in Figure 158g.”
Insert figure following this paragraph, removing RIC-Request and RIC-Response from the Reassociation exchange.
Insert “The over-the-DS Fast BSS Transition resource request protocol in a non-RSN is shown in Figure 158i.”
Insert figure following this paragraph, removing RIC-Request and RIC-Response from the Reassociation exchange.
Comment #1445
Comment: This section describes the contents of the authentication sequence. I think it should appear before the examples that use it.
Proposed change: Move this section to before the message exchanges, suggest after 8A.1.1.
Counter proposal, discussed and accepted at ad-hoc meeting: Leave 8A.5.x as contents of IEs; Move more of the content to 8A.3 and 8A.4, specifically all the text prior to the IE contents; move intro stuff from 8A.5.x to 8A.5. Reason for not including all of the content into 8A.3/8A.4 is the amount of duplication – IE contents from 8A.1/8A.2 would appear twice, and 8A.3/8A.4 would appear four times.
Make the following changes to D3.0:
8A.3.1:
Change “{Fast BSS Transition Request information elements}” to “MDIE, FTIE[R0KH-ID, SNonce], RSNIE[PMKR0Name], R1DIST”
Change “{Fast BSS Transition Response information elements}” to “MDIE, FTIE[R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR0Name], R1DIST, R1DISTV”
Following second paragraph, insert “In the Authentication Request frame, the MAC address of the STA shall be asserted in the SA field of the message header, and the BSSID of the target AP shall be asserted in the DA field of the message header.”
Following, insert “In the Authentication Response frame, the BSSID of the target AP shall be asserted in the SA field of the message header, and the MAC address of the STA shall be asserted in the DA field of the message header. The Status Code field shall be a value from those listed in 7.3.1.9.”
8A.3.2:
Change “{Fast BSS Transition Request information elements}” to “MDIE, FTIE[R0KH-ID, SNonce], RSNIE[PMKR0Name], R1DIST”
Change “{Fast BSS Transition Response information elements}” to “MDIE, FTIE[R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR0Name], R1DIST, R1DISTV”
Following second paragraph, insert “The MAC address of the STA shall be asserted in the STA address field of the FT Action frame, and the BSSID of the target AP shall be asserted in the Target AP address field of the FT Action frame. In the FT Response Action frame, the Status Code field shall be a value from those listed in 7.3.1.9.”
8A.3.3:
Change “{Fast BSS Transition Confirm information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR1Name], RIC-Request”
Change “{Fast BSS Transition Acknowledgement information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce, GTK[N]], RSNIE[PMKR1Name], RIC-Response”
Following second paragraph, insert “In the Reassociation Request frame, the MAC address of the STA shall be asserted in the SA field of the message header, and the BSSID of the target AP shall be asserted in the DA field of the message header.”
Following, insert “In the Reassociation Response frame, the BSSID of the target AP shall be asserted in the SA field of the message header, and the MAC address of the STA shall be asserted in the DA field of the message header. The Status Code field shall be a value from those listed in 7.3.1.9.”
8A.3.4:
Change “{Fast BSS Transition Request information elements}” to “MDIE”
Change “{Fast BSS Transition Response information elements}” to “MDIE”
Following second paragraph, insert “In the Authentication Request frame, the MAC address of the STA shall be asserted in the SA field of the message header, and the BSSID of the target AP shall be asserted in the DA field of the message header.”
Following, insert “In the Authentication Response frame, the BSSID of the target AP shall be asserted in the SA field of the message header, and the MAC address of the STA shall be asserted in the DA field of the message header. The Status Code field shall be a value from those listed in 7.3.1.9.”
8A.3.5:
Change “{Fast BSS Transition Request information elements}” to “MDIE”
Change “{Fast BSS Transition Response information elements}” to “MDIE”
Following second paragraph, insert “The MAC address of the STA shall be asserted in the STA address field of the FT Action frame, and the BSSID of the target AP shall be asserted in the Target AP address field of the FT Action frame. In the FT Response Action frame, the Status Code field shall be a value from those listed in 7.3.1.9.”
8A.3.6:
Change “{Fast BSS Transition Confirm information elements}” to “MDIE, RIC-Request”
Change “{Fast BSS Transition Acknowledgement information elements}” to “MDIE, RIC-Response”
Following second paragraph, insert “In the Reassociation Request frame, the MAC address of the STA shall be asserted in the SA field of the message header, and the BSSID of the target AP shall be asserted in the DA field of the message header.”
Following, insert “In the Reassociation Response frame, the BSSID of the target AP shall be asserted in the SA field of the message header, and the MAC address of the STA shall be asserted in the DA field of the message header. The Status Code field shall be a value from those listed in 7.3.1.9.”
8A.4.1:
Change “{Fast BSS Transition Confirm information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR1Name], RIC-Request”
Change “{Fast BSS Transition Acknowledgement information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR1Name], RIC-Response”
Following second paragraph, insert “In the Authentication Confirm frame, the MAC address of the STA shall be asserted in the SA field of the message header, and the BSSID of the target AP shall be asserted in the DA field of the message header. In a non-RSN, the FTIE and RSNIE shall not be present.”
Following, insert “In the Authentication Acknowledge frame, the BSSID of the target AP shall be asserted in the SA field of the message header, and the MAC address of the STA shall be asserted in the DA field of the message header. In a non-RSN, the FTIE and RSNIE shall not be present. The Status Code field shall be a value from those listed in 7.3.1.9.”
8A.4.2:
Change “{Fast BSS Transition Confirm information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR1Name], RIC-Request”
Change “{Fast BSS Transition Acknowledgement information elements}” to “MDIE, FTIE[MIC, R0KH-ID, R1KH-ID, ANonce, SNonce], RSNIE[PMKR1Name], RIC-Response”
Following second paragraph, insert “The MAC address of the STA shall be asserted in the STA address field of the FT Action frame, and the BSSID of the target AP shall be asserted in the Target AP address field of the FT Action frame. In a non-RSN, the FTIE and RSNIE shall not be present. In the FT Response Action frame, the Status Code field shall be a value from those listed in 7.3.1.9.”
8A.5:
Move first two paragraphs of 8A.5.1 (combining them into one paragraph) to follow Table 64A.
Move the first three paragraphs of 8A.5.2 (combining them into one paragraph) to follow.
Move the first two paragraphs of 8A.5.3 (combining them into one paragraph) to follow.
Move the first three paragraphs of 8A.5.4 (combining them into one paragraph) to follow.
8A.5.1:
Delete first four paragraphs.
8A.5.2:
Delete first six paragraphs
8A.5.3:
Delete first four paragraphs
8A.5.4:
Delete first six paragraphs
Submissionpage 1Bill Marshall, TGr Editor