On Wed, Jun 7, 2017 at 10:01 AM, Nico Williams <nico@xxxxxxxxxxxxxxxx> wrote:
On Wed, Jun 07, 2017 at 09:23:13AM +0200, Christian Huitema wrote:
> On 6/6/2017 5:36 PM, Randy Bush wrote:
> > the ietf is far from the only event with this problem. but it is kind
> > of in our purview to automate it. the noc is not the place to work on
> > protocols and databases; the noc is just the customer/user. a bof or
> > some existing wg might be.
>
> Another argument for MAC Address randomization...
+1
Though that's likely to lead geoloc providers to use other methods over
which we'd have even less control. But still, MAC address randomization
is a good thing all around.
How would Client MAC address randomization help this situation? I not aware of APs implementing MAC address (BSSID) randomization.
===============================================
David Farmer Email:farmer@xxxxxxx
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================
David Farmer Email:farmer@xxxxxxx
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE Phone: 612-626-0815
Minneapolis, MN 55414-3029 Cell: 612-812-9952
===============================================