From e9edb35ef60bf13f20dcae93448e60e68afd177f Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Fri, 26 Jul 2024 14:53:48 +0100 Subject: [PATCH] Explain greasing briefly earlier Closes #25 --- draft-edm-protocol-greasing.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/draft-edm-protocol-greasing.md b/draft-edm-protocol-greasing.md index 953ccc2..29b86a8 100644 --- a/draft-edm-protocol-greasing.md +++ b/draft-edm-protocol-greasing.md @@ -57,10 +57,12 @@ replacing the protocol. Greasing, a technique initially designed for TLS {{?GREASE=RFC8701}} and later adopted by other protocols such as QUIC {{?QUIC=RFC9000}}, can help support the -long-term viability of protocol extension points. Greasing is suitable for many -protocols but not all; {{Section 3.3 of ?VIABILITY=RFC9170}} discusses the -applicability and limitations of greasing. {{grease-considerations}} provides -additional protocol maintenance considerations. +long-term viability of protocol extension points. In these protocols, extension +codepoints are reserved only for greasing and when received must be ignored. +Greasing is suitable for many protocols but not all; {{Section 3.3 of +?VIABILITY=RFC9170}} discusses the applicability and limitations of greasing. +{{grease-considerations}} provides additional protocol maintenance +considerations. Applications are built with the intent of serving user needs {{?END-USERS=RFC8890}}, which might only require support for a subset of protocol features. Adapting to changing user