On Mon, Nov 4, 2024 at 8:25 AM Sean Turner <s...@sn3rd.com> wrote: > > > On Nov 4, 2024, at 15:35, Joseph Salowey <j...@salowey.net> wrote: > > > > On Mon, Nov 4, 2024 at 10:48 AM Salz, Rich <rs...@akamai.com> wrote: > > > While there is overlap between professional behavior and the perceived > focus on browser specific use cases; I think we should try to separate out > the topic. > > > > My memory, perhaps faulty, is that "will browsers implement this" has > been a process-gating question in the past. Recognizing that not everything > the WG will do is useful or applicable to all participants is, I think, a > useful reminder for, well, all participants. > > Not faulty, I definitely asked this at the end of the TLS 1.3 development, > because we really wanted to make sure we got buy in. It may have happened > other times too, but I don’t remember it happening recently. We should be > saying "who will implement." > > > Yes. I think we can do that as a separate reminder > > I tend to agree and I would like to propose that we update the FAQ and > then send a separate reminder to list about the FAQ. More reminders, I > think, can’t hurt. >
Well, everyone kind of has to agree on scope during chartering and rechartering, right? I will write an exaggeration here, just to show there must be limits: "My implementation is a Nintendo 64 that controls a nuclear power plant, and I must have visibility into the SNI, so ECH is unacceptable. PQ proposals are too expensive for my hardware, which I can only update every 25 years." When the WG takes on new work, we must have consensus that it's worth doing. In particular, the WG is not required to accomodate our Nintendo 64 enthusiast here while doing new work (that person can use the old stuff...), even though the use case might be a real thing. Looking at it that way, it's clear that there will always be people upset that their use case is ignored if the WG is being managed well. thanks, Rob
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
