Keith Moore <moore@xxxxxxxxxxxxxxxxxxxx> wrote:
> This is where the biggest disconnect between 2026 and reality is. If the
> reality is that industry is going to deploy implementations at Proposed
> Standard or sooner (and as far as I can tell, that's been reality for as long
> as there's been an Internet "industry"), it makes sense for IETF to recognize
> that and react accordingly.
You are saying this as if it's a bug.
It's not! It's by design.
We deploy at PS in order to find out if there is interoperability.
> If we want there to be a prototype "just for testing" status, it should
> probably be called something other than Proposed - the name has come to mean
> something else in IETF context. And we should deliberately change one or
> more protocol elements to make the standard incompatible with
We do "just for testing" regularly at the internet-draft stage.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
