From 773b2cbd988b36b200bd0f1b1f44698e67642b79 Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Mon, 7 Jul 2025 11:00:06 -0700 Subject: [PATCH 1/3] Add reference to the IAB RFC on protocol transitions Since section 6 is supposed to cover discussion like this. That RFC also mentions grease in A.4.1. Signed-off-by: Dave Thaler --- draft-edm-protocol-greasing.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/draft-edm-protocol-greasing.md b/draft-edm-protocol-greasing.md index 63ee568..52e67f2 100644 --- a/draft-edm-protocol-greasing.md +++ b/draft-edm-protocol-greasing.md @@ -355,9 +355,13 @@ connections, or phases within a connection. # Considerations for Protocol Versions {#versions} -There are intrinsic and well-documented issues related to testing version +{{?TRANSITION=RFC8710}} discusses considerations around planning for transitioning +from an existing protocol, or protocol version, to a new one. +There are also intrinsic and well-documented issues related to testing version negotiation of protocols; see {{?EXTENSIBILITY=RFC6709}} and {{Sections 2.1 and -3.2 of VIABILITY}}. This section will be expanded with advice for protocol +3.2 of VIABILITY}}. + +This section will be expanded with advice for protocol designers and implementers about how to approach these problems. # Security Considerations From e2c1884fe03c1312165b520d25eeaedf0cefe12f Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Mon, 7 Jul 2025 11:22:21 -0700 Subject: [PATCH 2/3] Add another section reference Signed-off-by: Dave Thaler --- draft-edm-protocol-greasing.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/draft-edm-protocol-greasing.md b/draft-edm-protocol-greasing.md index 52e67f2..2ec8024 100644 --- a/draft-edm-protocol-greasing.md +++ b/draft-edm-protocol-greasing.md @@ -222,7 +222,8 @@ might end up special-casing grease values. The patterns for sending grease values can be made more effective by coordinating between devices sending the values. One example of coordination is having a "flag day" where implementations start sending grease values -broadly, and measure to see where errors occur. +broadly, and measure to see where errors occur. See {{Section 3 of ?TRANSITION=RFC8710}} +for more considerations concerning the use of a flag day. ## Don't Handle Grease Values as a Special Case @@ -355,7 +356,7 @@ connections, or phases within a connection. # Considerations for Protocol Versions {#versions} -{{?TRANSITION=RFC8710}} discusses considerations around planning for transitioning +{{TRANSITION}} discusses considerations around planning for transitioning from an existing protocol, or protocol version, to a new one. There are also intrinsic and well-documented issues related to testing version negotiation of protocols; see {{?EXTENSIBILITY=RFC6709}} and {{Sections 2.1 and From cc3810073a19445e609678370651ab43fa37127c Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Mon, 21 Jul 2025 13:03:50 -0700 Subject: [PATCH 3/3] Apply PR feedback Signed-off-by: Dave Thaler --- draft-edm-protocol-greasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-edm-protocol-greasing.md b/draft-edm-protocol-greasing.md index 2ec8024..e969e1f 100644 --- a/draft-edm-protocol-greasing.md +++ b/draft-edm-protocol-greasing.md @@ -222,7 +222,7 @@ might end up special-casing grease values. The patterns for sending grease values can be made more effective by coordinating between devices sending the values. One example of coordination is having a "flag day" where implementations start sending grease values -broadly, and measure to see where errors occur. See {{Section 3 of ?TRANSITION=RFC8710}} +broadly, and measure to see where errors occur. See {{Section 3 of ?TRANSITION=RFC8170}} for more considerations concerning the use of a flag day. ## Don't Handle Grease Values as a Special Case