Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGM] Scope of RCM TIG



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Dear all,

We discussed this extensively in the meetings yesterday, and as far as I
was aware we were able to reach a common understanding at that time
around the purpose, reflected here by both Mark and Jerome.

That said, many participants in the RCM TIG may not be regularly
following TGM reflector or expect discussions on RCM TIG to appear
there. If there is now an assertion that we no longer have a common
understanding of the scope of RCM TIG, perhaps it is better that we
allocate 10 minutes to discussing in which sense our shared
understanding from yesterday is being violated in the beginning of next
meeting?

Thank you for your kind attention,

best regards,

Amelia

On 2019-11-14 03:39, Jerome Henry wrote:
> --- This message came from the IEEE 802.11 Task Group M Technical
> Reflector ---
> Thank you Mark.
> I have the same reading. It does not seem that the scope includes
> promoting anything, or describing use cases where using random MACs
> would be a great idea. Rather, starting from a Standard where most
> provisions were built on the assumption of MAC address unicity, what
> does MAC address randomization potentially break, and what could be do
> to alleviate the impact.
>
> Jerome 
>
>
> ---- On Wed, 13 Nov 2019 21:11:35 -0500
> *<mark.hamilton2152@xxxxxxxxx>* wrote ----
>
>     --- This message came from the IEEE 802.11 Task Group M Technical
>     Reflector ---
>
>     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-TGM list, click the following
>     link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&A=1
>
>
>
> ------------------------------------------------------------------------
>
> To unsubscribe from the STDS-802-11-TGM list, click the following
> link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM&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, 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-TGM 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
_______________________________________________________________________________