Re: [STDS-802-11] FW: Scope of RCM TIG
--- This message came from the IEEE 802.11 Working Group Reflector ---
Dear Mark,
As we previously discussed om TGM reflector, your points below were
raised in the Tuesday meetings and there was a common understanding.
Since you will have a further 10 minutes to elaborate on your
concerns(?) with the outcome of the Tuesday meetings, perhaps interested
readers could feel invited to our meeting tomorrow AM1.
best regards,
Amelia
On 2019-11-14 11:27, mark.hamilton2152@xxxxxxxxx wrote:
> --- This message came from the IEEE 802.11 Working Group Reflector ---
>
> Resending to the correct reflector. Apologies for the error.
>
>
>
> Mark
>
>
>
> *From:* mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
> *Sent:* Wednesday, November 13, 2019 7:12 PM
> *To:* STDS-802-11-TGM@xxxxxxxxxxxxxxxxx
> *Subject:* Scope of RCM TIG
>
>
>
> All,
>
>
>
> As an FYI, per our discussion in the RCM TIG yesterday, here is actual
> wording of the motion creating (and setting the scope) for the TIG:
>
>
>
> 1.1.1. *Approve formation of a random and changing MAC address (RCM)
> TIG to investigate the:*
>
> *• current and planned implementations of random and changing MAC
> addresses in devices, and current and planned 802.11/802 Standards
> treatment of randomized MAC addresses*
>
> *• impact on 802.11 features from random MAC addresses and/or
> changing addresses during:*
>
> *• Pre-association (stateless)*
>
> *• Preparing for (creating shared state) and
> during associations*
>
> *• potential mechanisms to address the above impacts, through:*
>
> *• Implementation options, or possible guidelines
> document*
>
> *• Modifications to the Standard, if any, and
> recommend continuing work (Study Group/PAR)*
>
> *The TIG is to complete a report on this topic at or before the
> November 2019 session.*
>
>
>
>
>
> My personal takeaway (which could be debated, of course), is that our
> scope is to identify what devices’ implementations are doing (or
> planning) w.r.t. random MAC addresses, and to identify how those
> changes will impact 802.11 features – and I read “impact” to mean in a
> negative sense, and hence why the next bullet of exploring mechanisms
> to “address” the impacts. Thus, my personal view is that we are not
> expected to also list out the positive/benefits of random and changing
> MAC addresses on 802.11 or other aspects (like privacy). That is, in
> summary, “what does this _break_, and what can we do about it?”
>
>
>
> Mark
>
> ------------------------------------------------------------------------
>
> To unsubscribe from the STDS-802-11 list, click the following link:
> https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11&A=1
>
--
Amelia Andersdotter
Technical Consultant, Digital Programme
Chair, RCM TIG, IEEE 802.11
ARTICLE19
www.article19.org
PGP: 3D5D B6CA B852 B988 055A 6A6F FEF1 C294 B4E8 0B55
_______________________________________________________________________________
If you wish to be removed from this reflector, do not send your request to this reflector - it will have no effect.
Instead, go to http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11 and then press the LEAVE button.
If there is no LEAVE button here, try http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-RO.
Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html
_______________________________________________________________________________