Inline
On Sun, Aug 11, 2024 at 11:29:10AM -0700, Christian Huitema wrote:
> On 8/11/2024 12:51 AM, Toerless Eckert wrote:
> > 1. S: How are the original RFC8110 authors relevant when the RFC and the new
> > draft are IETF AD sponsored instead of ISE track ?
>
> This is a process question, others are best placed to respond.
Seems like those people are not listening to this last-call exchange.
I hope those concerns are not just simply ignored.
> > 2. Of course, if further progress on this technology is something the IETF
> > does not care about, it does make sense to make it as easy as possible for
> > IEEE do this work. I am not sure whether the draft achieves this because
> > of 1. I don't understand from the draft what exactly the IETF promises to
> > change in its behavior, or what legally changes - if anything. E.g.: is this
> > a promise to never ever touch anything related to rfc8110 ?? Has the IETF
> > ever made such a promise, e.g.: prior examples ?
>
> From a security point of view, it seems highly preferable that security
> enhancements to 802.11 protocols be done by the IEEE and integrated in the
> next version of these 802.11 protocols.
>
> A parallel effort would only be justified if the IETF did not trust the IEEE
> and wanted to take over such developments. I don't think there is any
> appetite for that.
My main point was merely questioning the usefulness of this draft overall,
because it does not sound to me as if we even have a process to guarantee non-work
in the future.
My secondary point is that if 802.11 was more welcoming for new work, it seems to
me as if RFC8110 would not have been necessary in the first place. But thats
a question to the origins of RFC8110 (which it does not explain), and why the
work was not directly brought to IEEE.
Cheers
Toerless
> > 3. I very much hope that the IEEE provides an equal or better opportunity
> > for those interestd to work on updates as IETF would. I am not sure this is
> > the case. Seems as if there is at least a potentially significant
> > membership fee associated with working in IEEE SA.
>
> I can think of many security experts who are participating in both the IEEE
> 802.11 work and the IETF security work.
>
> As other have mentioned, we do have a liaison process.
>
> > 4. What happens if this draft does not become RFC ?
>
> Again, I am not the best placed to respond.
>
> -- Christian Huitema
--
---
tte@xxxxxxxxx
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
