Re: Feedback: Proposed IESG Statement on Restricting Access

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Oct 11, 2022, at 1:11 PM, Stephen Farrell <stephen.farrell@xxxxxxxxx> wrote:
> 
> Can I be assured the ability to restrict some person will
> not require changes (such as tracking) that affect other
> persons? IOW, I'd like reassurance that this won't cause
> vast swathes of the IETF web sites to require authentication
> or to attempt user identification via other means.

And also, what are the implications for future access to the network at IETF meetings?

Right now, the only possible way to deny someone access to the network at an IETF meeting is by MAC address (which, for many systems, can easily be changed/randomized anyway).  In the future, might we end up being required to log in (e.g., with our meeting registration number) at a 'captive portal’, whenever we want to access an IETF meeting’s network?

	Ross.





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux