Skip to content

Commit 3a608ce

Browse files
committed
Expand frequency discussion
1 parent 671945b commit 3a608ce

File tree

1 file changed

+17
-2
lines changed

1 file changed

+17
-2
lines changed

draft-edm-protocol-greasing.md

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -205,8 +205,23 @@ can be made unpredictable. Implementations can vary their behavior by including
205205
no grease values, one grease value, or multiple grease values for a given protocol
206206
extension point.
207207

208-
TODO: Discuss the implications of how often grease values are used; using very
209-
infrequently and very frequently can both be ossifying
208+
How consistently an frequently to use grease values is a choice that implementations
209+
and deployments need to consider and weigh against several factors.
210+
211+
Deployments of greasing should consider how they expect errors exposed by
212+
using grease values to be noticed and measured.
213+
214+
If grease values are sent too infrequently, so that errors due to sending
215+
grease values blend in with the noise of other errors, it is likely that
216+
no one will notice failures, thus defeating the purpose of greasing.
217+
When grease values are sent more frequently, they will be noticed more.
218+
However, if grease values are sent too consistently, receiver implementations
219+
might end up special-casing grease values.
220+
221+
The patterns for sending grease values can be made more effective by
222+
coordinating between devices sending the values. One example of coordination
223+
is having a "flag day" where implementations start sending grease values
224+
broadly, and measure to see where errors occur.
210225

211226
## Don't Handle Grease Values as a Special Case
212227

0 commit comments

Comments
 (0)