Protocol Greasing
Deliberately sending random, meaningless values in the extension points of a protocol, so that implementations that mishandle unknown values fail early and get fixed.
Also known as: GREASE, Greasing, Generate Random Extensions And Sustain Extensibility, Use It or Lose It
Category: Software Development
Tags: networking, protocols, internet, security, compatibility, evolution, best-practices
Explanation
Protocols reserve room for the future: extension numbers, version fields, reserved bits. The rule is always the same: ignore what you don't understand. In practice, an extension point that is never used is never tested. Some implementations get the rule wrong, nobody notices, and years later the first real extension breaks connections. Then it's too late to fix the installed base (see Protocol Ossification).
Greasing is the countermeasure. Clients constantly send random reserved values that mean nothing. A correct peer ignores them. A broken peer fails immediately, during its own development or early deployment, when the bug is still cheap to fix.
The name comes from GREASE: Generate Random Extensions And Sustain Extensibility. David Benjamin at Google introduced it for TLS in Chrome, and it became RFC 8701. The image is a mechanical joint: keep it moving, or it rusts shut.
**Where it's used**:
- **TLS**: Random reserved cipher suites, extensions, named groups and versions in the handshake
- **QUIC and HTTP/3**: Reserved versions, transport parameters, frame types and settings
- **Browser client hints**: Chrome adds a deliberately odd fake brand such as "Not A Brand" to its brand list, so websites can't rely on an exact list
**Why it works**:
- It turns a rule on paper into a rule that the ecosystem enforces every day
- Intolerant implementations hurt their own vendor right away, not the whole ecosystem later
- It's cheap: a few extra bytes
**The broader idea**:
Anything you want to keep flexible has to be exercised. This is the "use it or lose it" principle for extension mechanisms. The same thinking shows up elsewhere:
- Chaos engineering injects failures so that recovery paths stay working
- Some hash map implementations randomize iteration order so nobody can depend on it. It's a direct defense against Hyrum's Law
- Regular restore drills keep backups real
**Limits**:
Greasing only protects the specific extension points that get greased, and only against the kinds of intolerance that the random values trigger.
Related Concepts
← Back to all concepts