Christopher Wood <c...@heapingbits.net> wrote: > I wonder: what is the point of adopting this draft when the important work is > already done? If it’s that some folks won’t implement it until there’s an RFC > number assigned to it, well, that’s pretty silly.
It may seem silly to all folks who are directly involved here in these discussions, but many software and service providers view a "draft" as immature, not final, subject to change and may not implement until it has an RFC number. For those who are not actively tracking developments in the IETF and standards communities and who are relying on formal publications, this is an important signal. Likewise, for customers of such providers it's a lot easier to inquire "do you implement RFCXXXX" or, for interoperation, to request compliance with an RFC than with a "draft". With that, I support adoption. -Jan _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
