Hiya! On 19.05.2025 17:23, Eric Rescorla wrote:
This is equivalent to a bit diagram and in many pre-QUIC specifications, that's what it would have been. The IETF could, if it wanted, require that specifications contain this kind of formal description of PDUs. This does not preclude the existence of bit diagrams or even make them difficult to provide: one could readily write a tool to draw a bit diagram based on this input and I'm sure many people have done so for similar languages (and most likely for this one!), so that the bit diagrams were automatically produced aspart of the RFC production process.
It's probably good to consider this in the context of coding assistants like Co-pilot. I will assert that the more we standardize the format of such diagrams, the easier it is to build out implementations. Of course, tying a reference implementation to the RFC would do even more.
Eliot
OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
