zilongwang/ReadingBank huggingface dataset:
using RAW Start Time and RAW Duration. 373 80 The objective of "otherwise" is not Change this to two sentences, explain exactly what the "otherwise" is. Revised The new resolution is provided in the document IEEE 802.11-13/1096r2 under the heading of CID 471. 465 80 23 The Slot Assignment subfield is redundent since Noffset is the two least significant bytes of the FCS field of the Beacon frame that contains the RPS element. Delete the following sentence "The Slot Assignment indicates the assignment of slots to STAs based on their location in the TIM element. Noffset is indicated in the Slot Assignment and the two least significant bytes of the FCS field of the Beacon frame is used for the Noffset. The procedure of slot assignment is discussed in 9.19.4a.3 (Slot assignment procedure in RAW)." Revised The new resolution is provided in the document IEEE 802.11-13/1096r2 the heading of CID 471. 466 79 33 The Slot Assignment subfield is redundent since Noffset is the two least significant bytes of the FCS field of the Beacon frame that contains the RPS element. Delete the Slot Assignment subfield from Figure 8-401cq - RAW Slot Definition subfield. Revised The new resolution is provided in the document IEEE 802.11-13/1096r2 under the heading of CID 471. 467 80 16 The Slot Assignment subfield is redundent since Noffset is the two least significant bytes of the FCS field of the Beacon frame that contains the RPS element. Change the following sentence "The RAW Slot Definition subfield contains Slot Duration, Slot Assignments, and Cross Slot Boundary subsubfields." to "The RAW Slot Definition subfield contains Slot Duration and Cross Slot Boundary subsubfields." Revised The new resolution is provided in the document IEEE 802.11-13/1096r2 the heading of CID 471.
545 171.2 10.2.1.4 In the second sentence, "do11ShortBeaconInterval" shall be Replace "do11ShortBeaconInterval" by Revised – Agree with the commenter. However, this issue has already been addressed by comment resolutions in doc 820r1. 550 170.42 10.2.1.2 The last sentence of 10.2.1.2 says that a non-TIM support field is included in Extended Capabilities element. Though, subclause 8.4.2.170k specifies that a non-TIM support field is included in S1G Capabilities element. Replace "Extended Capabilities element" by "S1G Capabilities element". Accepted – TGah editor to make the changes proposed by the commenter. 846 160.8 9.32n.3 in order benefit fully from relays there should be a mechanism (in addition to the TXOP sharing decribed in 9.32n.3) to allow AP to enable multiple Relay STA to communicate with associated STAs at the same time define a mechiansim to allow AP to enable multiple relay STAs to operate at the same time (excluding TXOP sharing operation described in the 9.32n.3) Rejected – The commenter does not identify an to be solved and the proposed resolution does not provide enough details to evaluate its feasibility. 858 164.14 9.32r Due to the potentially high number of channels and channel widths (which means a narrow band channel may overlap with wider band channel) in 11ah there should be a mechanism for AP to indicate the preferred channel(s) where it moves when current channel becomes available. Channel switching announcement may not reach the long sleepers Specify a mechanism to indicate APs preferred operating channels and channel widhts to ensure robust BSS operation in case AP may have change channel fast due to OBSS or other unexpected interference- Rejected – in principle with the commenter. However, comment resolution for CIDs 863 and 866 (in doc 779r0) include the S1G Operation element which indicates such information (Channel Width, Primary Channel Number, etc). Discussion: None.
packet to report the selected sector to AP when sectorized operation. It may be better if we can protect those packets in a RAW (report RAW). Refer to Doc. 13/1120r0. 878 Yongho Seok 158 3 "A station may optionally use a VHT action frame (see 8.5.23.4a) for (solicited and unsolicited) Sector ID feedback." Is there any reason to use a VHT action frame for the Sector ID feedback? Sectorized beam operation is not related with the VHT. Don't use a VHT action frame. Instead, please use a S1G action frame. Sector ID feedback frame should use a S1G Action frame. ACCEPT. Refer to Doc. 13/1120r0. <Discussion> It may be better to have short packet such as NDP type for fast sectory discovery. NDP PS-POLL canbe easily re-used using the currently defined format with Preferred Sector ID (3 bits) in the Preferred MCS (4bits). TGah editor: modify the D0.2 text from P175L01, as follows 9.32m.4.3 Sector ID feedback A station may optionally use action frame (see 8.5.23) for (solicited and unsolicited) Sector ID feedback. 9.32m.4.4 Fast Sector Discovery When multiple STAs report their Sector ID feedback frames to AP, Sector ID feedback frames may be protected by Sector Report RAW indicated in the beacon to avoid contentions with others. The Sector Report RAW may be assigned after the Sounding RAW for fast sector discovery of multiple STAs. TGah editor: modify the D0.2 text from P226L32, as follows
CID Name P.L SC Comment Proposed Change Resolution 521 Mitsuru Iwaoka 4.42 4.11c Throughout the document, "Target Wake Time" and its acronym "TWT" are used inconsistently. It is better to use "TWT" instead of "Target Wake Time". Replace "Target Wake Time" by "TWT" if appropriate. Accept – Tgah editor to make the change as suggested by the commenter. enter
IEEE P802.11 Wireless LANs Active-Scanning-Resolution-Text Date: 2013-11-11 Author(s): Name Affiliation Address Phone email Jarkko Kneckt Nokia Corporation Otaniementie 19 B, 02150 Espoo Finland 6. Layer Management 6.3 MLME SAP interface 6.3.3 Scan 6.3.3.2 MLME-SCAN.request 6.3.3.2.2Semantics of the service primitive Instructions to the editor: Change the primitives table as shown: Name Type Valid range Description [CID2254] FILS Request Parameter element As defined in 8.4.2.177 (FILS Request Parameters element) The parameters used in determining whether to transmit a Probe Response frame. This parameter is optionally present when dot11FILSActivated is true. Enumeration IMMEDIATE, AT_END Indicates the result reporting mode. When immediate reporting is requested, every STA that is discovered during the scanning process shall be immediatly returned via MLME-SCAN.confirm using INTERMEDIATE_SCAN_RESULT as the ResultCode. [CID2921]This parameter is optionally present when dot11FILSActivated is true. AP Configuration Change Count element As defined in 8.4.2.184 (AP Configuration Change Count element) When a specific BSSID is indicated in the MLMESCAN.request and dot11FILSActivated is true, the AP ConfigurationChangeCount associated with the stored configuration of the AP is optionally present, when dot11FILSActivated is true. [CID3094] 6.3.3.3 MLME-SCAN.confirm 6.3.3.3.1 Function This primitive returns the descriptions of the set of BSSs detected by the scan process. Multiple primitives may be issued when the MLME-SCAN.request has ReportingOption parameter set to CHANNEL_SPECIFIC or to AT_END. [CID 2356] 6.3.3.3.2 Semantics of the service primitive MLME-
Fc: SC chip rate 880MHz = ⅔ Fs Ts: OFDM Sample Time 0.76ns=1/Fs Tc: SC Chip Time 1.14ns=1/Fc TDFT: IDFT/DFT period 0.388 us TGI: Guard Interval duration 97 ns= TDFT/4 Tseq 14.6 ns=128×Tc TSTF: Detection sequence duration 3054.5 ns=21× Tseq TCE: Channel Estimation sequence duration 1309.1 ns=9×Tseq TSYM: Symbol Interval 0.485µs= TDFT+TGI THEADER: Header Duration 0.485 µs=TSYM (OFDM) 1.75 µs =3×512×Tc (SC)
IEEE P802.11 Wireless LANs P802.11ah LB200 some proposed resolutions for Clause 4 and ToD accuracy Date: 2014-5-14 Author(s): Name Affiliation Address Phone email Mitsuru Iwaoka Yokogawa Electric Co. 2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750 Japan +81 422 52 5519 Proposed resolutons for Time of Departure accuracy CID Clause Comment Proposed Change Resolution 2543 24.3.17 A base document IEEE P802.11ac D5.0 defines 22.3.18.5 Time of Departure accuracy which is important for the Timing measurement specified in 10.24.5. The timing measurement is the base function for ranging (location) and time synchronization (IEEE Std 1588 and IEEE Std 802.1AS) and is important for Sensor STAs. It is necessary to specify the Time of Departure accuracy in 24.3.17. Insert subclause 24.3.17.5 Time of Departure accuracy based on 22.3.18.5 of IEEE P802.11ac D5.0. Detailed proposed changes are provided in 11/13-1316. Reject. Withdrawn by commenter. 2544 24.3.17 Annex T.2 needs to be modified to support S1G STA. Add following new modification to the subclause T.2 of the IEEE P802.11ac D5.0. ---- Change bullet l) in the 5th paragraph as follows: l) The Time Difference of Departure accuracy test is passed if both of the following conditions are met: 1) The RMS value of e is less than aTxPHYTxStartRMS when transmitting a VHT PPDU, a TVHT PPDU and an S1G PPDU, or aTxPmdTxStartRMS otherwise. 2) aTxPHYTxStartRMS when transmitting a VHT PPDU, a TVHT PPDU and an S1G PPDU or aTxPmdTxStartRMS otherwise is less than where the units of e, aTxPHYTxStartRMS when transmitting a Revise. Changes from 802.11ac are not implemented in the Annex T.2 of the IEEE P802.11mc D2.5, because they are related to the now-removed PMD/PLCP. So, no modification is necessary.
IEEE 802.11 Wireless LANs Normative Text for CIDs Related to ANQP Sequence Number feature and AP-List Query-Section 8 Date: 2013-11-11 Author(s): Name Affiliation Address Phone George Calcev Huawei Technologies Co. Ltd. George.Calcev@huawei.com Stephen McCan BlackBerry smccann@blackberry.com Lin Cai Huawei Technologies Co. Ltd. Lin.Cai@huawei.com
Element Element ID Length of indicated element (in octets) Extensible Number ( 8.4.2.175 (element)) [13/0725r1 <ANA> 4 Reduced Neighbor Report (see 8.4.2.176 (Reduced Neighbor Report element)) <ANA> 6 o 257 FILS Request Parameters (see 8.4.2.177 (FILS Request Parameters element)) <ANA> 3 to 11 Response Reception Time (see 8.4.2.178 (Probe Response Reception Time element)) <ANA> 3 FILS Identity [CID #1293, 1347(see 8.4.2.179 (FILS Identity element)) <ANA> 3 to 257 FILS Key Confirmation (see 8.4.2.180 (FILS Key Confirmation element)) <ANA> Variable FILS KDE Container (see 8.4.2.181 (FILS KDE container element)) <ANA> Variable FILS Session (see 8.4.2.182 (FILS Session element)) <ANA> 10 FILS Public Key (see 8 8.4.2.183 (FILS Public Key element)) <ANA> Variable Insert the new subclause for GASNumber element: Number
CID 2410 2410 2745.02 C.3 dot11HRCCAModeImplemented only appears in C.3 I can find no reference to it outside of Annex C.3. Suggest it is deleted. Delete dot11HRCCAModeImplemented at P2745L2, P2753L57, P2754L8-27, P2819L37 Discussion: The cited MIB variable is below (at P2754L8-27): Assigned to Mark Hamilton Proposed resolution: TBD CID 2483 2483 dot11BeaconInterval' is referred In 10.2.3.3 (Initialization of power management within an IBSS), but it is not defined C.3. Define the dot11BeaconInterval in MIB. Discussion: The cited MIB variable name is incorrect – change. Proposed resolution: Revised Change from “dot11BeaconInterval” to “dot11BeaconPeriod” CID 2065 2065 1200.14 9.22.7.2.2 The insertion (9.22.7.2.2) is possibly in the place. It is talking about Block Ack, not HT-Immediate block ack. Further, adding it necessitated turning the orginal contents of 9.22.7.2 into an introduction, when in fact it is the main meat of this subclause. Find a better home for this subclause. Or if it in the right place, rename 9.22.7.2.1 to "General". Discussion:
IEEE P802.11 Wireless LANs Some LB 199 Proposed Comment Resolutions Date: 2014-01-21 Author(s): Name Affiliation Address Phone email Dorothy Stanley Aruba Networks 1322 Crossman ave, Sunnyvale, CA +1 408 227 4500 CID 2449 (GEN) 2449 PICS for SA (PC36) should have a reference to subclause 10.14. Change the reference to 10.3, to instead be to "10.14 (SA Query procedures)" Discussion: The text is below: Proposed Resolution: Accepted CID 2442 (GEN) 360.22 6.3.68 isn't quite consistent in being clear that GCR is included, and not all GATS Request/Response exchanges are doing DMS. Change "DMS stream" to "DMS or GCR stream" at the end of the Description for the DMSRequest parameter. Discussion: The cited text is below: At line 23, the commenter proposes to change from “Specifies group addressed frames and parameters for the requested DMS stream.” To “Specifies group addressed frames and parameters for the requested DMS or GCR stream.” Proposed resolution: Accepted. CIDs 2440, 2441, 2439 (GEN)
CID 2414, 2005 2414 29.56 3.2 CID 1674 from LB193 was marked as ACCEPTED but the change was not implemented in D2.0 Delete the definiteion for frame or add an appropriate definition 2005 29.44 3.2 The "See EAPOL-Key frame" is bogus, because the two terms are no longer synonyms. Add a definition, or delete cited entry Discussion: CID 1674 is 1674 27.55 3.2 A EAPOL-Key and are not the same. See 802.1X-2010 clause 11.3.2 Delete Syn: EAPOL-Start frame. And its resolution is: ACCEPTED (GEN: 17:25:33Z) EDITOR 201307 approved Resolved I EDITOR: 2013-07-25 14:53:56Z The relevant text is below: Proposed resolution: Revised Change the definition to: frame: A Data MPDU that carries an 802.1X EAPOL-Start PDU. CID 2405 2405 1543.32 10.24.6 The sentence "The STA does not support the fine timing measurement procedure." does not seem to have any meaning and can be removed. Discussion: The cited text and context is below: Similar text is
Make similar changes to ""expressed in""." 1147 123.31 8.4.2.170u """ and the minimum continuous time the STA must stayin Doze in between Awake periods"" ""must"" is another of those special words that give all kind of grief. Is this itself a normative requirement, or a restatement of a rule or regulation from outside the draft?" Review all not in the frontmatter and replace with the appropriate normative verb or turn into a declarative statement. Note that the cited occurrence is in Clause 8, and should therefore either be moved to clause 9, or reworded as a declarative statement. with the commenter. Revised – TGah editor to make changes shown in under the heading for CIDs 1137, 1138, 1147, 1148 and 2942. 1148 123.45 8.4.2.170u "in units of <mu>s" -- this is wrong according to style. <mu>s is used only after a value. """in units of microseconds"" Ditto at 123.49." with the commenter Revised – TGah editor to make changes shown in under the heading for CIDs 1137, 1138, 1147, 1148 and 2942. 2942 123.00 8.4.2.170u Inappropriate use of 'us' Change 'us' to 'microsecond'. Agree with the commenter. Revised – TGah editor to make changes in under the heading for CIDs 1137, 1138, 1147, 1148 and 2942. Discussion: Agree with the commenter. Found 34 occurrences of “expressed in units of TUs” throughout REVmc 1.4. Propose to use this expression for the resolution of 1138. Short Beacon Compatibility element Instruction to Editor: Modify the subclause as follows:
IEEE P802.11 Wireless LANs Minutes for TG REVmc Teleconferences Dec 2013, Jan 2014 Date: 2013-12-06 Author(s): Name Affiliation Address Phone email Dorothy Stanley Aruba Networks 1322 Crossman Ave Sunnyvale, CA 94089 +1-630-363-1389 Jon Rosdahl CSR 10871 N 5750 W Highland, UT 84003 +1-801-492-4023 Minutes for the TG REVmc Telecon for December 6, 2013 Proposed Agenda – December 6, 2013: Call to order, Patent Policy, Attendance Editor Report Comment Resolution and available presentations AOB Adjourn Called to order by Dorothy Stanley, Chair of TG REVmc at 10:04 am; no agenda changes. Call for Patents - Review Patent Policy and Meeting Policy identified Attendance: Dorothy STANLEY, Aruba; Adrian STEPHENS, Intel; Mark HAMILTON, SpectraLink, Menzo WENTINK, Qualcomm. Jon ROSDAHL, CSR. Editor Report – Adrian Stephens D2.2 is posted on the IEEE 802.11 website and includes resolution of editorial comments approved at the November meeting. is review by reviewer volunteers and includes the remaining (largely technical) changes approved in November. D2.3 will be posted before the January meeting. noted that there is interest in draft D2.3; she has received an inquiry about availability of D2.3. Discussion of presentations: Available draft comment resolutions for review are here: . Review of 11-13-1314r9, since updated to . 2189 – Review of proposed changes to 3.1 and 3.2, moving 802.11 specific items from clause 3.1. What is the impact on the IEEE document that collects and publishes 3.1 terms? IEEE has an online database now, not a document. Adrian is working with IEEE staff to make sure that changes we make are reflected in their database. Observation that many of the defintions are 802.11 specific, and will be moved – resulting clause much shorter. Consider status of BSS definition and related definitions, portal. Adrian to revise. 2099 – Adrian and Guido Hiertz are discussing the resolution, no proposal at this time. 2258 – Agree to revised resolution as in 1314r10. 2436 – Assigned to Dan Harkins. 2468 – Assigned to Brian Hart. 2473 – Assigned to Matt Fischer.
IEEE P802.11 Wireless LANs Location Related Comments Date: 2013-12-09 Author(s): Name Affiliation Address Phone email Brian Hart Cisco Systems 170 W Tasman Dr, San Jose, CA 95134, USA Baseline is 11mc D2.1. Changes indicated by a mixture of Word track-changes and instructions. For equation changes, Tex notation is sometimes used. E.g. a_{xyz}^b denotes axyzb . 2403 692.00 8.4.2.21.10 LCI report assumes that when the feature is supported, location is known. A valid scenario is when the STA supports the feature, but does not know its location. add a sentence saying "The value of FFFF for longitude, latitude and altitude fields is reserved, a STA sets these fields to FFFF when it does not know its location." Same change to 8.4.4.12. Revised, see changes in 13/xxxxr0 that correct the parsing of the LCI When a field is unknown, it is indicated by massive tiny resolutions 2404 701.00 8.4.2.21.13 Location civic report assumes the STA is configured with its civic location. A valid use case is when the feature is supported but the STA does not know its civic location. Add a sentence which describes how the STA indicates in the Location Civic Report that it does add a sentence to this extent: "when the country code in the civic location field (figure 8-194) is set to an invalid value (see ISO3166 for valid country codes), it indicates that the reporting STA does not know its civic location." same change for 8.4.4.13 AP Civic Location subclause. Revised. Accepted element
IEEE P802.11 Wireless LANs Location Related Comments Date: 2014-01-22 Author(s): Name Affiliation Address email Brian Hart Systems 170 W Tasman Dr, San Jose, CA 95134, USA Ganesh Venkatesan Intel Corporation Baseline is 11mc D2.1. Changes indicated by a mixture of Word track-changes and instructions. For equation changes, Tex notation is sometimes used. E.g. a_{xyz}^b denotes axyzb . 2404 701.00 8.4.2.21.13 Location civic report assumes the STA is configured with its civic location. A valid use case is when the feature is supported but the STA does not know its civic location. Add a sentence which describes how the STA indicates in the Location Civic Report that it does not know its civic location. add a sentence to this extent: "when the country code in the civic location field (figure is set to an invalid value (see ISO3166 for valid country codes), it indicates that the reporting STA does not know its civic location." same change for 8.4.4.13 AP Civic Location subclause. Revised, see changes in 14/1509r<motionjedRev> that correct the parsing of the Civic field. When the Civic location is unknown, it is indicated by an empty subelement 2403 692.00 8.4.2.21.10 LCI report assumes that when the feature is supported, location is known. A valid scenario is add a sentence saying "The value of FFFF for longitude, latitude and altitude fields is reserved, a Revised, see changes in 14/1509r<motionjedRev> that correct the parsing of the LCI field. When a field is unknown, it is indicated by an empty subelement element
B.4.19 WNM extensions Item Protocol capability References Status Support WNM23 (#46) WNM23.1 Fine Timing Measurement Fine Timing Measurement Request Fine Timing Measurement ) 10.24.6 (Fine timing measurement procedure(#46 )) 8.6.8.25 (Fine Timing Measurement Request frame format(#46)) CF19:O WNM23:M Yes □ No □ N/A □ Yes □ No □ N/A □
IEEE P802.11 Wireless LANs Location Related Comments Date: 2014-03-15 Author(s): Name Affiliation Address Email Brian Hart Cisco Systems 170 W Tasman Dr, San Jose, CA 95134, USA Ganesh Venkatesan Intel Corporation Naveen Kakani CSR Bajko Mediatek Carlos Aldana Qualcomm Baseline is 11mc D2.1. Changes indicated by a mixture of Word track-changes and instructions. For equation changes, Tex notation is sometimes used. E.g. a_{xyz}^b denotes axyzb . Yellow highlighting means “look at the highlighted text more closely”. Changes in R3: Implemented issues discussed at Jan F2F Conditioned sending AP location also on dot11RMLCIMeasurementActivated Maximum Age in LCI request Unsolicited neighbor reports / FTM responses if AP position changes AP LCI/Civic request in FTM allowed only if schedule FTM parameters element is present also FQDN to Public URI Relative error to LCI report AP/STA usage-rules to LCI report AP location expected to change into LCI report
Table 8-99—IDs for Location Configuration Information Report 11mc editor: Insert new rows and renumber reserved rows Subelement ID Name Extensible 0 –220 Reserved Figure 8-187— Note movement of text (not shown via Word track changes) The definition of within the LCI are as in Section 2.2 of IETF RFC 6225(#1692) (July 2011) or as defined herein. This structure and information fields are little-endian, per conventions defined in 8.2.2 (Conventions), and are based on the LCI format described in IETF RFC 6225(#1692). NOTE—An example of fixed/fractional notation, using the longitude of the Sears Tower from p. 28of IETF RFC6225(#1692) (July 2011): Longitude West (or –87.63602°(#1491)), Using (#273)2s complement, 34bit fixed point, 25bit fraction, Longitude = 0xf50ba5b97, Longitude = 1101010000101110100101101110010111 (big-endian) DSE registered location expression for a Longitude resolution of 34-bits: Bits 56–61 Longitude resolution = (bit 56) 0 1 0 0 0 1 (bit 61) Bits 62–86 Longitude fraction = (bit 62) 1 1 1 0 1 0 0 1 1 1 0 1 1 0 1 0 0 1 0 1 1 1 0 1 0 (bit 86) Bits 87–95 Longitude integer = (bit 87) 0 0 0 1 0 1 0 1 1 (bit 95) The octets in transmission order = E2 E5 96 2E D4. The RegLoc Agreement field is set to 1 to report that the STA is operating within a national policy area or an international agreement area near a national border (see 10.12.3 (Registered STA operation)); otherwise, it is 0.(#1692) The RegLoc DSE field is set to 1 to report that the enabling STA is enabling the operation of STAs with DSE; otherwise, it is 0.(#1692) The Dependent STA field is set to 1 to report that the STA is operating with the enablement of the enabling STA whose LCI is being reported; otherwise, it is 0.(#1692)
B.4.19 WNM extensions Item Protocol capability References Status Support WNM23 (#46) WNM23.1 WNM23.2 Fine Timing Measurement Fine Timing Measurement Request Fine Timing Measurement ) 10.24.6 (Fine timing measurement procedure(#46 )) 8.6.8.25 (Fine Timing Measurement Request frame format(#46)) 8.6.8.26 (Fine Timing Measurement frame format(#46)) CF19:O WNM23:M WNM23:M Yes □ No □ N/A □ Yes □ No □ N/A □ Yes □ No □ N/A □ C.3 MIB Detail 11mc editor: Insert new MIB variable at the end of this sequence dot11WirelessMgmtOptionsEntry ::= dot11WirelessMgmtOptionsEntry ::= SEQUENCE { dot11(#1676)LocationActivated TruthValue, dot11(#1676)FMSImplemented TruthValue, dot11(#1676)FMSActivated TruthValue, dot11(#1676)EventsActivated TruthValue, dot11(#1676)DiagnosticsActivated TruthValue, dot11(#1676)MultiBSSIDImplemented TruthValue,
B.4.19 WNM extensions Item Protocol capability References Status Support WNM23 (#46) WNM23.1 WNM23.2 Fine Timing Measurement Fine Timing Measurement Request Fine Timing Measurement ) 10.24.6 (Fine timing measurement procedure(#46 )) 8.6.8.25 (Fine Timing Measurement Request frame format(#46)) 8.6.8.26 (Fine Timing Measurement format(#46)) CF19:O WNM23:M WNM23:M Yes □ No □ N/A □ Yes □ No □ N/A □ Yes □ No □ N/A □ C.3 MIB Detail 11mc editor: Insert new MIB variable at the end of this sequence dot11WirelessMgmtOptionsEntry ::= dot11WirelessMgmtOptionsEntry ::= SEQUENCE { dot11(#1676)LocationActivated TruthValue, dot11(#1676)FMSImplemented TruthValue, TruthValue, dot11(#1676)EventsActivated TruthValue, dot11(#1676)DiagnosticsActivated TruthValue, TruthValue,
IEEE P802.11 Wireless LANs Location Related Comments Date: 2014-03-18 Author(s): Name Affiliation Address Phone Email Brian Hart Cisco Systems 170 W Tasman Dr, San Jose, CA USA Ganesh Venkatesan Intel Corporation Naveen Kakani CSR Bajko Mediatek Carlos Aldana Qualcomm caldana@ qca.qualcomm.com Baseline is 11mc D2.1. Changes indicated by a mixture of Word track-changes and instructions. For equation changes, Tex notation is sometimes used. E.g. a_{xyz}^b denotes axyzb . Yellow highlighting means “look at the highlighted text more closely”. Changes in R3: Implemented issues discussed at Jan F2F Conditioned sending AP location also on dot11RMLCIMeasurementActivated Maximum Age in LCI request Unsolicited neighbor reports / FTM responses if AP position changes AP LCI/Civic request in FTM allowed only if schedule FTM parameters element is present also FQDN to Public URI Relative to LCI report AP/STA usage-rules to LCI report AP location expected to change into LCI report
B.4.19 WNM extensions Item Protocol capability References Status Support WNM23 (#46) WNM23.1 Fine Timing Measurement Fine Timing Measurement Request Fine Timing Measurement ) 10.24.6 (Fine timing measurement procedure(#46 )) 8.6.8.25 (Fine Timing Measurement Request frame format(#46)) 8.6.8.26 (Fine Timing Measurement frame format(#46)) CF19:O WNM23:M WNM23:M Yes □ No □ N/A □ Yes □ No □ N/A □ Yes □ No □ N/A □ C.3 MIB Detail 11mc editor: Insert new MIB variable at the end of this sequence dot11WirelessMgmtOptionsEntry ::= dot11WirelessMgmtOptionsEntry ::= SEQUENCE { dot11(#1676)LocationActivated TruthValue, dot11(#1676)FMSImplemented TruthValue, TruthValue, dot11(#1676)EventsActivated TruthValue, dot11(#1676)DiagnosticsActivated TruthValue, dot11(#1676)MultiBSSIDImplemented TruthValue,
duplication). Add an arrow to show the "A-MSDU subframe header" as in the baseline 2443 148.04 8.7.6 "2034" "2304" Agree in principle with the commenter. Revised – TGah editor to make changes shown in 14/1513r0 under the heading for CIDs from 1461 to 2445. 2444 148.16 8.7.6 I can't see "Long version" and "Short version" actually being used anywhere else Delete (or if actually used somewhere, isn't "Medium version" also needed?) Agree with the commenter. Revised – TGah editor to make changes shown in 14/1513r0 under the heading for CIDs from 1461 to 2445. 2445 147.47 8.7.6 This new subclause on Dynamic conflicts with the baseline subclause 8.3.2.2 which says things like "Two A-MSDU subframe formats are defined: the Basic subframe described in 8.3.2.2.2 (Basic AMSDU subframe format) and the Short A-MSDU subframe described in 8.3.2.2.3 (Short subframe format)." Merge 8.7.6 into 8.3.2.2 (with appropriate caveats about not using Dynamic A-MSDUs in non-S1G STAs) Agree with the commenter. Revised – TGah editor to make changes in 14/1513r0 under the heading for CIDs from 1461 to 2445. Discussion: None. Proposed Changes: Aggregate MSDU(11ad) (A-MSDU) format General(11ad) Instructions to TGah Editor: Change this subclause as follows (@802.11REVmc D2.0): An AMSDU is a sequence of AMSDU subframes as shown in Figure 8-45 (A-MSDU structure). Each AMSDU subframe consists of an AMSDU subframe header followed by an MSDU and 0 to 3 octets of padding as shown in
1883 9.41.5 207 45 "If the Action subfield of the NDP Paging Response is 0: If the NDP Paging Requester STA is a non- AP STA, it shall send a (NDP) PS-Poll or uplink trigger frame addressed to the NDP Paging Responder. If the NDP Paging Requester STA is an AP, it shall send an NDP CTS to self with the duration field set to zero." Wrong use of colon and capitals etc. If using bullets then stick to them. Add indented bullets at "If the NDP Paging Requestor is a non-AP STA" and " If the NDP Paging Requestor is a n AP" with the commenter Revised: TGah editor to make changes shown in 2145 9.41.5 NDP Paging Setup 184 51 change "the TWT Command Reply field of NDP Paging Response TWT element" to " the TWT Command Reply field in TWT element of NDP Paging Response " change "the TWT Command Reply field of NDP Paging Response TWT element" to " the TWT Command Reply field in TWT element of NDP Paging Response " Agree with the commenter Revised: TGah editor to make changes shown in 2146 9.41.5 NDP Paging 101 30 There's no Minimum Sleep Duration field Change to "Min Sleep Duration field" Agree with the commenter Revised: TGah editor to make changes shown in 2221 9.41.5 184 22 Have some questions to the text in line 22 page 184, including: there is no indication info in the NDP Paging field as defined in Figure 8-401de. Then, how to indicate a NDP request or a NDP response? Does it use the TWT Request indicator? If so, then can a STA request a TWT and NDP paging at the same time? Please clarify the text in line 22 page 184 to address the questions asked by the comment. Reject: Comment fails to identify an issue. In response to the commenter: NDP Paging field is in TWT element (Figure Yes, it should use TWT element as described in the paragraph
in a virtual bitmap that are equal to 1. 1099 74.08 "AP shall set EWL to 7" -- Clause 8 is for structure, not behavior. If it is necessary to describe an algorithm for encoding in terms of the behavior of the encoder, do so in Clause 9. Otherwise describe the interpretation of the fields here using declarative verbs. Also make similar changes to the 5 "shall" statements in this subclause. Agreed in principle. Revised – Change as suggested. TGah editor to make changes shown in 13/1519r0 under the heading for CID 1099. 1100 74.27 "For nAID differential values, totally WL +∙ nbits are required." -- that's totally cool, dude ".. values, a total of WL .." Revised – Change as suggested. TGah editor to make changes shown in 13/1519r0 under the heading for CID 1100. 1635 72.61 OLB is not in the list of acronyms in Section 3.3 Add OLB to list of acronyms in Section 3.3 Agreed with the commenter. Revised – Change as suggested. TGah editor to make changes shown in 13/1519r0 under the heading for CID 1635. 1636 73.24 ADE is not in the list of acronyms in Section 3.3 Add ADE to list of acronyms in Section 3.3 Agreed with the commenter. Revised – Change as suggested. TGah editor to make changes shown in 13/1519r0 under the heading for CID 1636. 2245 73.44 There are multiple problems to use padding bits to indicate the end of the ADE block, including" 1). what value the padding bits are set to? 2). Considering the EWL can be any value between 1 to 8, then the number of padding bits in the last byte could be 1 to 7, then there will be an ambiguity regarding Change the paragraph in line 44 to the following: The padding subfield contains 0-7 padding bits. The padding bits are set to 0 and they also indicate the end of the current ADE Block. Agreed with the commenter. Revised. TGah editor to make changes shown in 13/1519r0 under the heading for CID 2245. 3
IEEE P802.11 Wireless LANs LB 200 Resolution to Comments on Traffic Indication Map (TIM) Element Date: 2013-xx-xx Author(s): Name Affiliation Address Phone email Haiguang Wang I2R Zander Lei I2R Interpretation of a Motion to Adopt A motion to approve this submission means that the editing instructions and any changed or added material are actioned in the TGah Draft. This introduction is not part of the adopted material. Editing instructions formatted like this are intended to be copied into the TGah Draft (i.e. they are instructions to the 802.11 editor on how to merge the text with the baseline documents). TGah Editor: Editing instructions preceded by “TGah Editor” are instructions to the TGah editor to modify existing material in the TGah draft. As a result of adopting the changes, the TGah editor will execute the instructions rather than copy them to the TGah Draft. CID Page Clause Comment Proposed Change Resolution 1097 73.44 "The padding subfield contains 0-7 padding bits. The padding bits also indicate the end of the current ADE Block." -- how do the padding bits indicate the end of the current block? This is a particularly clever trick when there are 0 of them. Delete "The padding bits also indicate the end of the current ADE Block." Revised. Modified the sentence that causing confusion. For clarification, the description on adding padding bits is in the later part of the subclause. TGah editor to make changes shown in 13/1519r0 under the heading for CID 1097. 1098 74.04 "If all AIDs in the ADE blocks are paged," -- this language is cellular, not 802.11. No definition exists for an AID being paged. In 802.11 we have bits corresponing to an AID Replace "If all the bits in the virtual bitmap corresponding to the AIDs in the ADE block are equal to 1" Make similar changes to remove all "are paged" language in this subclause. Rejected Paged AID has been newly defined in 11ah (clause 3.2)
1577 27.40 the reference is in this table change the reference to "24.3.18.5.4 (CCA sensitivity for signals occupying the primary 2MHz channel and/or primary 1MHz channel" Revised- TGah editor to make changes shown in under the heading for CID 1033, 1412, 1577, 1578, 1579, 1773, 1787, 1788, 1789, 1790, 1791 1578 27.53 the reference is wrong in this table change "...according to the rules specified in 24.3.18.5.3 (CCA sensitivity for signals occupying the primary 2MHz channel)." to"according to the rules specified in 24.3.18.5.5 (CCA sensitivity for signals not occupying the primary 2MHz channel)." in row "secondary"; change" 24.3.18.5.4" to "24.3.18.5.5" in this table. Revised- TGah editor to make changes shown in under the heading for CID 1033, 1412, 1577, 1578, 1579, 1773, 1787, 1788, 1789, 1790, 1791 1579 28.10 the reference is wrong in this table Modify the reference to "24.3.18.5.5" to all added text. Revised- TGah editor to make changes shown in under the heading for CID 1033, 1412, 1577, 1578, 1579, 1773, 1787, 1788, 1789, 1790, 1791 1773 27.24 No technical reason why names of channel elements must be shared with those of 11n/11ac. For example, it makes it more confusing when secondary20 actually corresponds to secondary 2MHz channel. Additionally, "primary" element needs to be split to distinguish Primary 1MHz and Primary 2MHz. Current naming and definitions of channel list parameters don't match those defined in CCA section, 24.3.18.5 Create separate table to define elements specific for 11ah, rather than share terminology with 11n/11ac. Separate definitions for Primary2 and Primary1, since EDCA for 1 and >=2MHz transmissions are separate procedures. Revised- TGah editor to make changes in under the heading for CID 1033, 1412, 1577, 1578, 1579, 1773, 1787, 1788, 1789, 1790, 1791
Introduction This topic contains information on the reelection of VA benefits or military retired pay, including reelecting Section 306 Pension or Old Law Pension requesting evidence to prove continuous entitlement to Section 306 Pension or Old Law Pension determining the proper effective date when a Veteran reelects VA benefits or military retired pay special consideration of Veterans hospitalized for a service-connected (SC) disability, and awarding benefits when VA Form 21-651, Election of Compensation in Lieu of Retired Pay or Waiver of Retired Pay to Secure Compensation From Department of Veterans Affairs (38 U.S.C. 5304(a)-5305), is timely received from a Veteran in a VA or service hospital. Change Date November 13, 2015 a. Reelecting Section 306 Pension or Old Law Pension A Veteran receiving Section 306 Pension or Old Law Pension may elect to receive military retired pay. Election of retired pay does not bar subsequent election of other benefits administered by VA. Note: The effective date of reelection of VA benefits is governed by . Reference: For more information about a Veteran’s right to elect retired pay and reelect VA benefits, see . b. Requesting Evidence to Prove Continuous Entitlement to Section 306 Pension or Old Law Pension Entitlement to Section 306 Pension or Old Law Pension is not protected under if the disability or annual income did not continuously meet protected pension eligibility criteria from the date pension was waived through the date of receipt of the reelection. Before paying Section 306 Pension or Old Law Pension to a Veteran who waived his or her pension to receive military retired pay, request evidence to determine if the Veteran would have been continuously entitled to Section 306 Pension or Old Law Pension for the entire period that the pension payments were waived. Absent evidence of continuous entitlement, the Veteran can no longer receive Section 306 Pension or Old Law Pension. If entitlement to current-law pension exists, VA may pay this benefit to the Veteran.
Minute of Faculty Senate meeting held at 12:30 pm on 13th November 2017 Update from Ron Matson Ron needs the name of chairs for all Review committees (P&T) by April not by the fall. Otherwise, the lack of names will delay the P&T process. KSU is working to replace DM with Explorance Blue (student feedback) and Interfolio (faculty activity). The new set up will be easier to use and support. DM is not supporting course feedback. KSU will ensure to migrate data to Interfolio from DM. There are three Senators on the committee. Faculty Liaison Reports Faculty Liaisons are to put send Reports to FS Secretary or upload in OneDrive folder. Previous Minutes The Senate approved the previous meeting’s minute from October. Elimination of e-tuition Ken Harmon talked about undergraduate e-tuition halving in Fall 18 and going away in Fall 19. This could cost KSU $5m each year in lost income. However, there could be no decisions on any cuts until KSU got their 18/19 budget and ordinary tuition levels from USG in April or May. KSU then would look at its entire budget not just academics. He was not optimistic about keeping online tuition surcharges for graduate course in the long run, which brings in another $5m a year in income. Equity Issues Ken Harmon stated that there has been an external review of external equity of faculty, which said previous study was questionable. Also, there did not appear to be any sources to pay for external equity. So, KSU decided to look at only internal equity (inversion or compression) for staff and faculty. This study would be finished soon, hopefully by January 18. There could be no backdating of equity payments. The Deans, directors, and chairs would examine study and recommend
2. New Transmitters If retuning is not possible or if the cost of retuning exceeds the cost of replacement, a new transmitter may be required. The price of a new transmitter would include installation, mask filter, and proof of performance testing. Range of Estimated Costs UHF –IOT Transmitter Single IOT system (30 kW) 450,000 – 525,000 Two IOT system (60 kW) 815,000 – 855,000 Three IOT system (90 kW) 1,205,000 UHF – Air Cooled State Transmitter 1 – 2.5 kW 35,000 – 90,000 4 - 6 kW 157,000 – 180,000 10 – 12 kW 245,000 – 320,000 15 kW 335,000 – 450,000 20 kW 530,000 - 580,000 UHF – Liquid Cooled State Transmitter 6.3 – 9.25 kW 250,000 – 315,000 10.5 – 12.3 kW 345,000 – 465,000 15 kW 460,000 – 550,000 18 - 20 kW 530,000 – 600,000 23.8 – 29.3 kW 685,000 – 835,000 40 - 50 kW 940,000 – 1,075,000 High VHF – Air Cooled Solid State Transmitter 1 kW 82,000 2.4 kW 135,000 3.3 kW 175,000 5 kW 260,000 10 – 12 kW 315,000 15 kW 450,000
3” air dielectric 53 4” air dielectric 66 5” air dielectric 91 Rigid Transmission Line – copper Line Diameter: 3 1/8” 75 – 96 4 1/16” 95 – 130 6 1/8” 150 – 185 7 3/16” 263 8 3/16” 270 – 327 Note: Broadband rigid transmission line sections are generally 15% more expensive than other rigid line sections. TOWER EQUIPMENT AND RIGGING If replacement or addition of antennas is required, it may be necessary to modify the existing tower or construct a new tower. In addition to these expenses, a broadcaster replacing or adding an antenna would incur rigging costs. Range of Estimated Costs Existing Towers – Towers without sufficient documentation of the specifications may need to be mapped prior to completion of a tower load study. Tower mapping for an undocumented/poorly documented tower and preparation of documentation necessary for tower load study 12,000 – 16,000 Structural engineering tower load study for documented tower 5,000 – 7,000 Structural engineering tower load study for a documented tower with candelabra 10,000 Minor tower reinforcement/modifications (see Fig. 2 for sample minor modifications) 100,000 – 150,000 Major tower reinforcement/modifications (see Fig. 2 for sample major modifications) 300,000 – 400,000 Serious reinforcement/modifications (see Fig. 2 for sample serious modifications) 500,000 – 1,000,000
Return of SecurID® Tokens The SecurID® tokens distributed to qualified bidders are tailored to this auction and will not work for future auctions. The Commission will send each bidder, along with a copy of this Public Notice, a pre-addressed, stamped envelope to return its SecurID® tokens. Each bidder should return its SecurID® tokens to the Commission for recycling by June 4, 2014. Contact Information For further information, contact: News Media Wireless Telecommunications Bureau Cecilia Sulhoff at (202) 418-0587 Media Bureau Janice Wise at (202) 418-8165 Licensing Information Service Policies, Regulations Licensing Issues, Engineering Issues Due Diligence, Incumbency Issues, FCC Form 301 questions Media Bureau, Audio Division Lisa Scanlan (Attorney) or Tom Nessinger (Attorney), at (202) 418-2700 Auction Payment Information Wire Transfers Refunds FCC Auctions Accounting Branch Gail Glasser at (202) 418-0578, or Theresa Meeks at (202) 418-2945, or (202) 418-2843 (fax) Auction 84 Information General Auction Information, Process, and Procedures Auction Rules, Policies, and Regulations Auctions and Spectrum Access Division Linda Sanderson, Project Manager, or , Auction Analyst, at (202) 418-0660 Lynne Milne, Attorney, at (202) 418-0660 Accessible Formats Braille, large print, electronic files, or audio format for people with disabilities Consumer and Governmental Affairs Bureau (202) 418-0530, or (202) 418-0432 (TTY) FCC Internet Sites - FCC -
Before the DC 20554 In the Matter of Towerstream Corporation Middletown, Rhode Island ) ) ) ) ) ) ) ) File No.: EB-FIELDSCR-12-00004486 File No.: EB-FIELDNER-12-00004796 NAL/Acct. No.: 201332600006 FRN: 0015467749 CONSENT DECREE The Enforcement Bureau of the Federal Communications Commission and Towerstream Corporation (Towerstream), by their authorized representatives, hereby enter into this Consent Decree for the purpose of terminating the Enforcement Bureau’s investigation into whether Towerstream violated Sections 301 and 333 of the Communications Act of 1934, as amended, by operating radio transmitters, including Unlicensed National Information Infrastructure (U-NII) transmission systems, without a license and causing harmful interference to Federal Aviation Administration’s (FAA) Terminal Doppler Weather Radar (TDWR) systems, which the FAA uses to detect wind shear and other weather conditions near airports. DEFINITIONS For the purposes of this Consent Decree, the following definitions shall apply: “Act” means the Communications Act of 1934, as amended. “Adopting Order” means an order of the Bureau adopting the terms of this Consent Decree without change, addition, deletion, or modification. “Bureau” means the Enforcement Bureau of the Federal Communications Commission. “Part 15 Rules” means Part 15 of the Rules; and other provisions of the Act, the Rules, and Commission orders related to the operation of unlicensed devices, including U-NII transmission systems. “Commission” and “FCC” mean the Federal Communications Commission and all of its bureaus and offices. “Communications Laws” collectively, the Act, the Rules, and the published and promulgated orders and decisions of the Commission to which Towerstream is subject by virtue of its business activities, including but not limited to the Part 15 Rules. “Compliance Plan” means the compliance obligations, program, and procedures described in this Consent Decree at paragraph 11. “Covered Employees” means all employees and agents of Towerstream who perform, or supervise, oversee, or manage the performance of, duties that relate to Towerstream’s responsibilities under the Communications Laws, including the Part 15 Rules. “Effective Date” means the date by which both the Bureau and Towerstream have signed the Consent Decree. “Investigation” means the investigation commenced by the Bureau in File Nos.
_______________________________________________ Date: _________________________
of Estimated Costs (in dollars) Existing Towers – Towers without sufficient documentation of specifications may need to be mapped prior to completion of a tower load study. Tower mapping for an undocumented/poorly documented tower and preparation of documentation necessary for tower load study 16,000 - 25,000 Structural engineering load study for documented tower 5,000 - 12,000 Structural engineering tower load study for a documented tower with candelabra 15,000 - 19,000 Minor tower reinforcement/modifications (see Fig. 2 for sample minor modifications) 100,000 – 150,000 Major tower reinforcement/modifications (see Fig. 2 for sample major modifications) 300,000 – 400,000 Serious tower reinforcement/modifications (see Fig. 2 for sample serious modifications) 500,000 – 1,000,000 New Towers – Cost includes constructing a new tower, priced per foot. New tower between 1000’ and 1500’ without elevator, presumptive soil conditions 2,500 New tower between 1500’ and 2000’ without elevator, presumptive soil conditions 3,000 Note: Costs may be higher for tower sites with difficult soil or other site conditions and for towers with an elevator. Costs may be lower for towers under 1,000 feet Tower Rigging – Costs include fees paid to expert tower crews for equipment removal and installation, such as removing an existing antenna and installing a replacement antenna, and removing an existing transmission line and installing a replacement transmission line. Tall Tower (greater than 500’) 100,000 – 200,000 Short Tower (less than 500’) 60,000 – 80,000 Complex Tower (includes, e.g., towers with candelabras and/or stacked antennas) 100,000 – 400,000 Helicopter Lift (e.g., for a rooftop tower, complex tower, tall structure, or terrain constrained location requiring helicopter lift) variable INTERIM FACILITIES Stations may need to use interim facilities in order to avoid prolonged off-air periods during the repacking or to enable stations to meet their construction deadlines. Some stations currently either have a licensed auxiliary facility or own backup equipment that they can repurpose for this use post-auction, while others may need to purchase or rent equipment or facilities. Range of Estimated Costs (in dollars)