January 2005doc.: IEEE802.11-05/0017-00
IEEE P802.11
Wireless LANs
Conference Call Minutes Task Group K Nov-Jan. 2005
Date:
January 17, 2005
Author:
Paul Gray
AirWave Wireless, Inc.
1700 El Camino Real Suite 500
San Mateo, CA94025
Phone: 650-286-6107
Fax: 650-286-6101
e-Mail:
Abstract
CumulativeTGk conference call Minutes forNovember 2004r throughJanuary 2005.
Detailed minutes follow:
Wednesday, November 24, 2004 – 8:30 AM Pacific
- Chair calls the conference call to order at 8:30 AM
- Attendance Paine, Gray, Kwak
- Editorial Comment Resolution 11-0964r26
- Comments
Comment #6 – Clause 10.3.11 - Johnson
Problem - P38, L13 Replace "management protocol model" with "protocol layer model"
Remedy - Specify P38, L13 Replace "management protocol model" with "protocol layer model"
Resolution – Accept – instruct editor to make change as described above.
Comment #7 – Clause 10.3.11 – Johnson
Problem - P39, L1 Replace "diagrams" with "figures"
Remedy - P39, L1 Replace "diagrams" with "figures"
Resolution – decline
Comment #9 – Clause 10.3.12.1.2 – Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Comment – It is abstract, but you need to know
Resolution – decline
Comment #10 – Clause 10.3.12.3.2 - Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Resolution - decline
Comment #11 – Clause 10.3.14.1.2 – Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Resolution – decline – see Comment #9
Comment #12 – Clause 10.3.14.3.2 – Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Resolution – decline – see Comment #9
Comment #14 – 10.3.16.1.2 - Cole
Problem - The font for tables in this sub-clause and those subsequent don't match the prior sub-clause tables.
Remedy - Please change to match
Resolution – accept – instruct editor to make change as described above.
Comment #16 – Clause 10.3.16.1.2 - Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Resolution – decline
Comment #17 – Clause 10.3.16.2.2 – Cole
Problem - Indentation inconsistency in the TPC element of the table.
Remedy - Please change to match.
Resolution – accept – instruct editor to make change as described above.
Comment #18 – Clause 10.3.16.2.2 - Johnson
Problem - If the Measurement Category is only present if dot11Radio MeasurementEnabled is true does SPECTRUM MANAGEMENT need to be an enumeration type since by default if not RADIO MEASUREMENT it must be SPECTRUM MANAGEMENT.
Remedy - Delete SPECTRUM MANAGEMENT enumeration type.
Resolution – decline – See Comment #9
Comment #20 – Clause 10.3.16.2.2 – Zuniga
Problem - Pg 43, table - Description of TPC Report Element has extra indentation
Remedy - Remove indentation to be consistent with the presentation format in other rows
Resolution – accept – See comment #17
Comment #23 – 10.3.2.2 – Ecclesine
Problem – p38 lin2 editing instructions
Remedy - add "and renumber accordingly" to the editing instructions as a new table is added
Resolution – decline – MLME primitive tables do not have table numbers in the base standard.
Comment #29 – Clause 11.1.3 – Johnson
Problem – P44, L4 Remove extra space between "set" and "to"
Remedy - P44, L4 Remove extra space between "set" and "to"
Comment – we removed this text in 1095 document
Resolution – accept – text was removed by document 1095
Comment #30 – Clause 11.1.3 – Johnson
Problem – P44, L9 Delete "that element of" since adds no meaning
Remedy – P44, L9 Delete "that element of"
Resolution – accept – text was removed by document 1095
Comment #32 – Clause 11.1.3 – Kwak
Problem - P44L3: Missing space in RCPIMeasurement.
Remedy – none
Resolution – decline – this is the official name of the field
Comment #36 – Clause 11.3.2.21.4-11.3.2.21.10 – Johnson
Problem - P11, L7 - Should indicate how randomization interval is used for all delimited clauses.
Remedy - Resolution - Simply add "See 11.7.3." after sentence describing the Randomization Interval much like Measurement Duration or use the sentence from P19, L6 in all other clauses.
Resolution – decline -
Comment #38 – Clause 11.5 – Thrasher
Problem - First sentence in second paragraph (line 39, 40).. Need to remove the reference of "future regulatory requirements in Europe" I'd assume the TPC procedures could be used to satisfy future regulatory requirements in other places besides Europe…:)
Remedy - should read ….This clause describes TPC procedures that may be used to satisfy this particular European regulatory requirement. The procedures may also satisfy comparable needs …..
Comment – This is changing text form 11h.
Resolution – defer – address at the ad-hoc meeting or in SA (TPC issues)
Comment #39 – Clause 11.5 – Ecclesin
Problem - As only one sentence is being modified, only one sentence needs to be present.
Remedy - Remove the other sentences from what of 11.5 is present
Comment – Change the 3rd paragraph
Comment – P45 there is additional text in 11h.
Resolution – defer – need to review the document closer to ensure there are no other changes to 11h (TPC)
Comment #42 – Clause 11.5 – Johnson
Problem - P45, L37 Delete blank line
Remedy - P45, L37 Delete blank line
Problem – accept – instruct editor to make change described above.
Comment #43 – Clause 11.5.2 – Wright
Problem - Line 41, "Beaon" -> "Beacon"
Remedy - Correct spelling
Resolution – accept – instruct editor to make change described above.
Comment #44 – Clause 11.5.2 – Audeh
Problem - Line 41 - beacon is misspelled as beaon
Remedy - Put correct spelling
Resolution – accept – see comment #43
Comment #45 – Clause 11.5.2 – Johnson
Problem - P45, L42 Delete blank line
Remedy - P45, L42 Delete blank line
Resolution – accept – instruct editor to make change described above.
Comment #46 – Clause 11.5.2 - Johnson
Problem – P45, L40 Delete "resource" to make consistent with TGk draft
Remedy – P45, L40 Delete "resource"
Resolution – accept – instruct editor to make change as described above
Comment #47 – Clause 11.5.2 – Johnson
Problem - P45, L40 Change "Where" to "When"
Remedy – P45, L40 Change "Where" to "When"
Resolution – accept – instruct editor to make change as described above
Comment #48 – Clause 11.5.2 – Zuniga
Problem - pg 45 line 41 - misspelling "Beaon"
Remedy - change to "Beacon"
Resolution – accept – see Comment #44
Comment #50 – Clause 11.7 – Johnson
Problem – P45, L45 Change 11.7 - should be replaced with either a TBD or at least 11.11 since TGe define 11.1, 11.2, 11.4, 11.5, 11.6, 11.7, TGh define 11.5, 11.6, and TGi define 11.3, 11.4. So there is much confusion here. Ask base standard editor
Remedy - Update appropriately.
Comment – all of these standards have been adopted where should 11k standard.
Comment – The rollups are not the official standards – the “base” is the standard
Resolution – defer – Simon can work this out with Terry Cole
Comment #61 – Clause 11.7.3 – Edney
Problem - Last line: insert the word "pseudo" in front of "random number". The problem described does not occur with truly random numbers
Remedy - See comment
Resolution – accept – instruct editor to make change described above
Comment #67 – Clause 11.7.4 – Kwak
Problem – P46L32: delete "not" at end of line.
Remedy – none
Resolution – accept - instruct editor to make change described above
Comment #69 – Clause 11.7.4 – Olson
Problem - Page 46 line 33 Extra "not" in sentence.
Remedy - Remove.
Resolution – accept – See Comment #67
Comment #79 – Clause 11.7.5 – Johnson
Problem - P46, L37 Replace "Measurement-capable" with "Measurement enabled" for draft consistency.
Remedy - P46, L37 Replace "Measurement-capable" with "Measurement enabled"
Resolution – accept - instruct editor to make change described above
Comment #81 – Clause 11.7.6 – Lefkowitz
Problem – Be explicit about who is sending the request in infrastructure. If STA's can not send requests to each other in infrastructure then stat that the AP sends a request to the STA in infrastructure and that STA's can send requests to each other in Ad-Hoc. If there can not be two AP's in infrastructure mode then the wording in the beginning of the clause is not clear about a STA sending to other STA's since the table states that a STA can send a request to an AP.
Remedy – Clarify.
Comment – This should be a technical comment
Comment – Table k13 addresses this issue. (… source and destination …)
Resolution – defer – get clarification from Marty
Comment #87 – Clause 11.7.6 – Thrasher
Problem – line 2,3 of page 48…"shall be returned without undue delay" and the definition of undue delay is…….
Remedy – should read "should be returned without undue delay"
Comment – This is technical because you changing a “shall” to “may”
Resolution – reclassify to technical
Comment #88 – Clause 11.7.6 – Thrasher
Problem - line 2,3 of page 48…"shall be returned without undue delay" and the definition of undue delay is…….
Remedy - should read "should be returned without undue delay"
Resolution – accept - instruct editor to make change described above
Comment #91 – Clause 11.7.6 – Wright
Problem - pg 48, line 22 - Need to look up the definition of "solicited" and "autonomous" meas. Reports
Remedy – none
Resolution – defer - change this to a technical comment. We need a complete or withdraw comment
Comment #97 – Clause 11.7.6 – Kandala
Problem - Please format table k13 in a more presentable from (eliminate redundant rows/columns - use merge/straddle feature of the word processing tool)
Remedy – As suggested.
Resolution – accept – see resolution on Comment #99
Comment #99 – Clause 11.7.6 - Johnson
Problem - Table k13 - Change table so it is clearer that the Infrastructure BSS applies to the 1st three line of the table. Combine 3 cells into a single cell for Service Set column indicating Infrastructure BSS.
Remedy - See comment.
Resolution – accept - instruct editor to make change described above
Comment #100 – Clause 11.7.6
Problem - P48, L4 Shouldn't this be plural - "element is" should be "elements are"
Remedy - P48, L4 Shouldn't this be plural - "element is" should be "elements are"
Resolution – decline – sentence is correct
Comment #105 – Clause 11.7.6 – Levy
Problem - In Table k13 - it is unclear due to the lines in the table that the first three lines all are Infrastructure BSS, Service Set.
Remedy - Correct the lines in the table so that there are no lines between the cells in the Service Set column for the first three cells.
Resolution – accept – see Comment #99
Comment #788 – Clause 7.4.2
Problem - Value '6' is missing in Table k12
Remedy - add missing value '6'
Resolution – accept – instruct editor to make change as described above.
Comment #789 – Clause 7.4.2 - Ecclesine
Problem - Editing instructions add new subsections after 7.4.1
Remedy - add "and renumber accordingly" to the editing instructions as new figures and tables are added
Resolution – accept –See comment #228
Comment #790 – Clause 7.4.2 – Audeh
Problem - Table k12 is missing a value for 6.
Remedy - Define value for action value field = 6.
Resolution – accept - #788
Comment #791 – Clause 7.4.2 – Johnson
Problem - Clause 7.4.2 should be minimally 7.4.5 since clause 7.4.2, 7.4.3, 7.4.4 have been used by TGe. So TGk value should reference subclause 7.4.5 not 7.4.2
Remedy - Change subclause of Radio Measurement action frame to 7.4.5 from 7.4.2.
Resolution – accept - Same #789
Comment #792 – Clause 7.4.2 – Johnson
Problem - Change the category field definition to reference the clause in which Table 19a is. Replace the existing Category field definition with the Category field definition from 7.4.2.3.
Remedy - Change the category field definition to reference the clause in which Table 19a is. Replace the existing Category field definition with the Category field definition from 7.4.2.3.
Resolution – accept – change to reference table in k24
Comment #793 – Clause 7.4.2.1-7.4.2.6 – Johnson
Problem - Reorder subclauses so they are in the same order as Table k12. Basically move TPC Request/Report before Neighbor
Remedy - none
Resolution – accept – see comment #788
Comment #797 - Clause 7.4.2.3 - Ecclesine
Problem - p36 line 8 "shall be shall be one octets"
Remedy - change to "each shall be one octet"
Resolution – accept – instruct editor to make change as described above.
Comment #798 – Clause 7.4.2.3 – Black
Problem - P36, l8 octets should be octet
Remedy - Correct editorial.
Resolution – accept - see as #797
Comment #802 – Clause 7.4.2.3 – Johnson
Problem - P36, L4 - Incorrect reference. Change "Table 20f" to "Table k12"
Remedy - P36, L4 - Incorrect reference. Change "Table 20f" to "Table k12"
Resolution – accept – instruct editor to make change as described above.
Comment #803 – Clause 7.4.2.3 – Johnson
Problem - P36, L7 - Change "report" to "request"
Remedy - P36, L7 - Change "report" to "request"
Resolution – Decline – the sentence is correct
Comment #804 – Clause 7.4.2.3 – Johnson
Problem - P36, L8 - "octets" should be singular "octet"
Remedy - P36, L8 - "octets" should be singular "octet"
Resolution – accept – see comment #797
Comment #807 – Clause 7.4.2.3 – Kwak
Problem - P36L8: one octets change to one octet.
Remedy – none
Resolution – accept – see comment #797
Comment #815 – Clause 7.4.2.4 – Black
Problem - p37, l2 incorrect reference - should be k12 in 7.4.2.
Remedy - Correct reference
Resolution – accept – instruct editor to make change as described above
Comment #816 – Clause 7.4.2.4 – Black
Problem - p37, l8 use shall in place of will
Remedy - Correct
Resolution – accept – instruct the editor to make change as described above.
Comment #818 – Clause 7.4.2.4 – Johnson
Problem - P36, L4 - Incorrect reference. Change "Table 5 in 7.4.1" to "Table k12 in 7.4.2"
Remedy - P36, L4 - Incorrect reference. Change "Table 5 in 7.4.1" to "Table k12 in 7.4.2"
Resolution – accept with amendment to clause 7.4.2.3
Comment #819 – Clause 7.4.2.4 - Johnson
Problem - P37, L6 - Incorrect reference. Change "7.3.2.22" to "7.3.2.26"
Remedy - P37, L6 - Incorrect reference. Change "7.3.2.22" to "7.3.2.26"
Resolution – accept – instruct editor to make change as described above.
Comment #823 – Clause 7.4.2.5 – Johnson
Problem - P37, L14 - Incorrect Reference. Change "Table 1 in 7.3.11" to Table 19a in 7.3.1.11"
Remedy - P37, L14 - Incorrect Reference. Change "Table 1 in 7.3.11" to Table 19a in 7.3.1.11"
Resolution – accept – Table 19a is an 11h table number
Comment #824 – Clause 7.4.2.5 – Johnson
Problem - Get rid of bullet by replacing the text in the clause with the following "The TPC Request frame format for radio measurement shall be as described in 7.4.1.3 with one exception. The Category field shall be set equal to the value indicating the Radio Measurement Category, as specified in Table 19a in 7.3.1.11."
Remedy - Get rid of bullet by replacing the text in the clause with the following "The TPC Request frame format for radio measurement shall be as described in 7.4.1.3 with one exception. The Category field shall be set equal to the value indicating the Radio Measurement Category, as specified in Table 19a in 7.3.1.11."
Resolution – accept – instruct editor to make change as described above.
Comment #827 – Clause 7.4.2.6 – Johnson
Problem - P37, L19 - Incorrect Reference. Change "Table 1 in 7.3.11" to Table 19a in 7.3.1.11"
Remedy - P37, L19 - Incorrect Reference. Change "Table 1 in 7.3.11" to Table 19a in 7.3.1.11"
Resolution – accept – instruct editor to make change as described above
Comment #828 – Clause 7.4.2.6 – Johnson
Problem - Get rid of bullet by replacing the text in the clause with the following "The TPC Report frame format for radio measurement shall be as described in 7.4.1.3 with one exception. The Category field shall be set equal to the value indicating the Radio Measurement Category, as specified in Table 19a in 7.3.1.11."
Remedy - Get rid of bullet by replacing the text in the clause with the following "The TPC Report frame format for radio measurement shall be as described in 7.4.1.3 with one exception. The Category field shall be set equal to the value indicating the Radio Measurement Category, as specified in Table 19a in 7.3.1.11."
Resolution - accept – instruct the editor to make change as described above.
Comment #833 – Clause A.4.1.3 – Faccin
Problem - What happened to RRM19-22? The table jumps from RRM18 to RRM23?
Remedy - Correct numbering
Accept – Change RRM23 to RRM19
Comment #845 – Clause A.4.1.3 – Black
Problem - What happened to RRM19-22? The table jumps from RRM18 to RRM23?
Remedy - Correct numbering
Accept – see Comment #833
Comment #852 – Clause Annex A – Johnson
Problem - Annex D is labeled Annex D. Shouldn't Annex A be listed as Annex A. P64, L1
Remedy - Delete "Annex A - PICS" and replace with "Annex A"
Resolution – accept – instruct editor to make change as described above.
Comment #854 – Clause Annex A – Johnson
Problem - Change "Radio Resource Measuremetn" to "Radio Measurement" in Annex A. Located in two locations *CF10 and RRM1
Remedy - Change "Radio Resource Measuremetn" to "Radio Measurement" in Annex A
Resolution – Accept – instruct editor to make as described above.
Comment #879 – Clause Annex D – Malinen
Problem -Complex description of what is included in dot11BeaconRprtReceivedElements.
Remedy - Change "All fields, except Timestamp, Beacon interval and Capability Information" with "All information elements". Similar change was already done in text portion of beacon report.
Defer – Paul Gray will reconcile with draft
Comment #905 – Clause 7.2.3.4 – He
Problem - Line13 uses "order 5", but line14 uses "order 6". Is the intent to change the order number also or just modify "order 5"?
Remedy - none
Resolution - Accept – Change order 5 to order 6
Comment #906 – Clause 7.2.3.6 – He
Problem - similar comment as in clause 7.2.3.4
Remedy - none
Accept – Change order 6 to order 7
Comment #908 – Clause 7.3.2.21 – He
Problem – none
Remedy - Delete "4" under the "Reserved" field.
Resolution – Accept – instruct editor to make change as described above.
Comment #913 – Clause 7.4.2.3 – He
Problem – none
Remedy - Delete one "shall be".
Resolution – Accept – instruct the editor to make change as described above.
Comment #915 – Clause Annex D – Cole
Problem - In the first 4 sections of the MIB changes, the changes are shown without context.
Remedy - Please consider showing the smallest but whole changed item with underscores. This is clearer.
Resolution - Accept – done in 1073r1
Comment #917 – Clause Annex D – Cole
Problem - in Dot11OperationEntry sequence list, the changes are shown without context.
Remedy - Please consider showing the smallest but whole changed item with underscores. This is clearer.
Resolution - accept – done in 1073r1
Comment #918 – Clause General – Lefkowitz
Problem - Change the wording the document to say Sender of a request and receiver of a report.
Remedy – see comment
Decline – cannot determine commenter intent
Comment #924 – Clause General – Kim
Problem - Line 28: Please use my full name
Remedy - Change "J" Kim to Byoung-Jo "J" Kim
Resolution - accept – instruct editor to make change as described above.
Comment #927 – Clause General – Black
Problem - Need to be consistent with bit field diagrams - compare figure k5 and k19.
Remedy - Make consistent.
Resolution - accept – make consistent with K19 format.
Comment #935 – Clause General – Pratik
Problem - Need to clarify that received power is measured at the current receiving antenna connector.
Remedy - Change "as seen at the antenna connector" to "as seen at the current receiving antenna connector."