Hello Edward,
Here are your allocations:
|
TransactionID
|
Type
|
Status
|
User
|
Group
|
Resource
|
Ref Doc
|
Ref Subclause
|
Ref Location
|
Name
|
Req Value
|
Description
|
Allocated Value
|
Requested
|
|
1110
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
dot11Groups
|
IEEE Std 802.11-2016
|
C.3
|
|
dot11SMTbase15
|
|
Some MIB values are depreciated in the previous group dot11SMTbase13.
|
115
|
2019-06-06
|
|
1111
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
dot11Groups
|
IEEE Std 802.11-2016
|
C.3
|
|
dot11HTMACAdditions4
|
|
Some MIB values are depreciated in the previous group dot11HTMACAdditions3.
|
116
|
2019-06-06
|
|
1112
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
dot11Groups
|
IEEE Std 802.11-2016
|
C.3
|
|
dot11SMTRMConfig3
|
|
Some MIB values are depreciated in the previous group dot11SMTRMConfig2.
|
117
|
2019-06-06
|
|
1113
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
ElementIDs
|
IEEE Std 802.11-2016
|
9.4.2.1
|
Table 9-77
|
RSN Extension
|
|
A legacy element ID (Table 9-94 in D2.2) for an RSN Extension element introduced by CIDs #2715 and #2716 and per the
working group motion in the closing plenary of the 2019 May interim.
|
244
|
2019-06-06
|
|
1116
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
Element ID Extension 1
|
IEEE Std 802.11-2016
|
9.4.2.1
|
Table 9-77
|
Mirrored SCS
|
|
A new Extended Capabilities element (Table 9-151 in D2.2) for Mirrored SCS introduced by CID #2693.
|
88
|
2019-06-06
|
|
1117
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
dot11StationConfigEntry
|
IEEE Std 802.11-2016
|
C.3
|
|
dot11MSCSActivated
|
|
A new MIB for Dot11StationConfigEntry
|
197
|
2019-06-06
|
|
1118
|
Allocate
|
Pending
|
Edward Au
|
TGmd
|
Element ID Extension 1
|
IEEE Std 802.11-2016
|
9.4.2.1
|
Table 9-77
|
TCLAS Mask element
|
|
A new extended element ID (Table 9-94 in D2.2) for TCLAS Mask element introduced by CID #2693.
|
89
|
2019-06-06
|
I have not made (new) allocation for Beacon protection. I had previously done this for Emily:
|
1094
|
Allocate
|
Pending
|
Emily Qi
|
TGmd
|
ExtendedCapabilities
|
IEEE Std 802.11-2016
|
9.4.2.27
|
Table 9-135
|
Beacon Protection Enabled
|
|
The AP sets the Beacon Protection Enabled field to 1 when dot11BeaconProtectionEnabled is true. Otherwise, it is set
to 0.
|
84
|
2019-05-01
|
No
|
|
|
1095
|
Allocate
|
Pending
|
Emily Qi
|
TGmd
|
dot11StationConfigEntry
|
IEEE Std 802.11-2016
|
C.3
|
|
dot11BeaconProtectionEnabled
|
|
This is a control variable. It is written by an external management entity. This variable indicates whether beacon
protection is enabled.
|
195
|
2019-05-01
|
No
|
|
|
1096
|
Allocate
|
Pending
|
Emily Qi
|
TGmd
|
WNM-Notification types
|
IEEE Std 802.11-2016
|
9.6.14.29
|
Table 9-360
|
Beacon Protection Failure
|
|
|
2
|
2019-05-01
|
No
|
|
-Robert
-----Original Message-----
From: Edward Au [mailto:edward.ks.au@xxxxxxxxx]
Sent: Tuesday, June 04, 2019 12:09 PM
To: Stacey, Robert <robert.stacey@xxxxxxxxx>
Cc: STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-EDITORS] ANA request for REVmd
Hello Robert,
My bad - thanks for sharing with me the correct version of the ANA request spreadsheet. Now, I can choose the correct numbering space (the previous spreadsheet I use shows only dot11Groups
or Capabilities
- sorry!)
Actually, all I am asking for are "Allocate", and there is no
"Release" request. Please see if the instructions filled therein are
clear enough.
Regards,
Edward
On Fri, May 31, 2019 at 3:00 PM Stacey, Robert <robert.stacey@xxxxxxxxx>
wrote:
>
> Hello Edward,
>
> I am having some issues parsing your spreadsheet.
>
> The first issue has to do with "Type of Request". If you are releasing a number you should use "Release". Currently all your entries are "Allocate", but some look like they should be
release.
>
> The second issue is with the "Resource Name", i.e. the numbering space from which the allocation is made. Your requests are all either dot11Groups or Capabilities, which doesn't seem
right.
>
> You might need use the request form in the attached since the dropdown for the "Resource Name" in your sheet doesn't have all the entries.
>
> -Robert
>
> -----Original Message-----
> From: *** IEEE stds-802-11-editors List ***
> [mailto:STDS-802-11-EDITORS@xxxxxxxx] On Behalf Of Edward
Au
> Sent: Friday, May 31, 2019 6:55 AM
> To:
STDS-802-11-EDITORS@xxxxxxxxxxxxxxxxx
> Subject: [STDS-802-11-EDITORS] ANA request for REVmd
>
> --- This message came from the IEEE 802.11 Editors' Reflector ---
>
> Hi Robert,
>
> Enclosed please find a few requests from TGmd on ANA. We hope we
> would get these ANA assignments for the publication of Draft 2.3.
>
> Thanks and Regards,
> Edward
>
> ______________________________________________________________________
> _________
>
> IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.
>
> SELF SERVICE OPTION:
> Point your Browser to -
>
http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-EDITORS
> and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.
>
> Further information can be found at:
>
http://www.ieee802.org/11/Email_Subscribe.html
> ______________________________________________________________________
> _________
--