←back to thread

Hyrum’s Law in Golang

(abenezer.org)
317 points thunderbong | 1 comments | 21 Nov 24 07:12 UTC | HN request time: 0.204s | source
Show context
lovasoa ◴[21 Nov 24 09:40 UTC] No.42202586[source]▶
An interesting topic is how to fight Hyrum's law. A possibility is to add randomness in things you don't want people to rely on. If I remember well, this is what the QUIC protocol does. Some fields are unused in the current version, but required by the specification to be set to random values, not null bytes, so that routers don't start relying on them to identify the packets.

EDIT.

I think I found the source: https://www.rfc-editor.org/rfc/rfc9000#section-17.2.1

> The value in the Unused field is set to an arbitrary value by the server. Clients MUST ignore the value of this field. [...] Note that other versions of QUIC might not make a similar recommendation.

I think they call it "greasing", to prevent "ossification".

replies(3): >>42202840 #>>42203994 #>>42204140 #
1. vitus ◴[21 Nov 24 13:12 UTC] No.42203994[source]▶
> I think they call it "greasing"

This is a reference to RFC 8701, which coined the acronym GREASE ("Generate Random Extensions And Sustain Extensibility"), first in the context of TLS.

https://www.rfc-editor.org/rfc/rfc8701.html

(The earliest draft of the RFC dates back to mid-2016, which is likely the first public mention of the term: https://datatracker.ietf.org/doc/html/draft-davidben-tls-gre...)