diff --git a/draft-iab-protocol-greasing.md b/draft-iab-protocol-greasing.md
index ae0c0c4..43e9667 100644
--- a/draft-iab-protocol-greasing.md
+++ b/draft-iab-protocol-greasing.md
@@ -384,8 +384,15 @@ 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
-designers and implementers about how to approach these problems.
+One way to grease protocol versions is to have a protocol pass
+a list of supported versions or features (e.g., cipher suites), along with a grease
+value, such that the grease value will not impact the actual version
+or features chosen, since it will not be selected by the receiving entity.
+
+Another method is to have a protocol include a recovery mechanism (e.g., an extra
+round trip to try with another option) for cases when an unsupported version or feature
+is attempted.  In this case, a grease value might be attempted at some
+frequency or opportunity that would not adversely affect performance.
 
 # Security Considerations