Skip to content

Commit cffaa94

Browse files
authored
Merge pull request #41 from dthaler/transition
Add reference to the IAB RFC on protocol transitions
2 parents e2e99ff + cc38100 commit cffaa94

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

draft-edm-protocol-greasing.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -223,7 +223,8 @@ might end up special-casing grease values.
223223
The patterns for sending grease values can be made more effective by
224224
coordinating between devices sending the values. One example of coordination
225225
is having a "flag day" where implementations start sending grease values
226-
broadly, and measure to see where errors occur.
226+
broadly, and measure to see where errors occur. See {{Section 3 of ?TRANSITION=RFC8170}}
227+
for more considerations concerning the use of a flag day.
227228

228229
## Don't Handle Grease Values as a Special Case
229230

@@ -371,9 +372,13 @@ connections, or phases within a connection.
371372

372373
# Considerations for Protocol Versions {#versions}
373374

374-
There are intrinsic and well-documented issues related to testing version
375+
{{TRANSITION}} discusses considerations around planning for transitioning
376+
from an existing protocol, or protocol version, to a new one.
377+
There are also intrinsic and well-documented issues related to testing version
375378
negotiation of protocols; see {{?EXTENSIBILITY=RFC6709}} and {{Sections 2.1 and
376-
3.2 of VIABILITY}}. This section will be expanded with advice for protocol
379+
3.2 of VIABILITY}}.
380+
381+
This section will be expanded with advice for protocol
377382
designers and implementers about how to approach these problems.
378383

379384
# Security Considerations

0 commit comments

Comments
 (0)