Script updating gh-pages from f8ff51b. [ci skip]

draft-edm-protocol-greasing.html

@@ -1149,6 +1149,11 @@ <h2 id="name-copyright-notice">
 </li>
               <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.4">
                 <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="auto internal xref">3.4</a>.  <a href="#name-define-and-register-grease-" class="internal xref">Define and Register Grease Value Ranges</a></p>
+<ul class="compact toc ulBare ulEmpty">
+<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.4.2.1">
+                    <p id="section-toc.1-1.3.2.4.2.1.1"><a href="#section-3.4.1" class="auto internal xref">3.4.1</a>.  <a href="#name-effectively-instructing-ian" class="internal xref">Effectively Instructing IANA about grease</a></p>
+</li>
+                </ul>
 </li>
             </ul>
 </li>
@@ -1304,17 +1309,24 @@ <h3 id="name-define-and-register-grease-">
 Small contiguous blocks increase the chance that such reservations might
 unintentionally use grease values, which could lead to interoperability
 failures.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
-<p id="section-3.4-2">Protocols might ask IANA to create new registries for their extension points.
-When greasing, it is recommended that only a single entry for the entire grease
-value set is registered. When an algorithm has been used, it should be included
-in the entry; see for example
-https://www.iana.org/assignments/http3-parameters/http3-parameters.xhtml#http3-parameters-frame-types.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
-<p id="section-3.4-3">Grease values must not be used or registered for any other purpose. Registries
+<div id="iana-tips">
+<section id="section-3.4.1">
+          <h4 id="name-effectively-instructing-ian">
+<a href="#section-3.4.1" class="section-number selfRef">3.4.1. </a><a href="#name-effectively-instructing-ian" class="section-name selfRef">Effectively Instructing IANA about grease</a>
+          </h4>
+<p id="section-3.4.1-1">Protocol designers might ask IANA to create new registries for their extension
+points. When greasing, it is recommended that only a single entry for the entire
+grease value set is registered. When an algorithm has been used, it should be
+included in the entry; see for example
+https://www.iana.org/assignments/http3-parameters/http3-parameters.xhtml#http3-parameters-frame-types.<a href="#section-3.4.1-1" class="pilcrow">¶</a></p>
+<p id="section-3.4.1-2">Grease values must not be used or registered for any other purpose. Registries
 should include a label to identify the protected grease value range; a label of
 "reserved" may be confused with other ranges that are reserved for private or
 experimental extensions. An implementer that conflates these two meanings may
 cause a new class of interoperability failure. Therefore a label such as
-"reserved for greasing" may help to avoid the confusion.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
+"reserved for greasing" may help to avoid the confusion.<a href="#section-3.4.1-2" class="pilcrow">¶</a></p>
+</section>
+</div>
 </section>
 </div>
 </section>
@@ -1388,7 +1400,8 @@ <h2 id="name-security-considerations">
       <h2 id="name-iana-considerations">
 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
       </h2>
-<p id="section-7-1">This document has no IANA actions.<a href="#section-7-1" class="pilcrow">¶</a></p>
+<p id="section-7-1">This document has no IANA actions itself. Guidance on how other documents can effectively
+instruct IANA about protocol greasing is provided in <a href="#iana-tips" class="auto internal xref">Section 3.4.1</a><a href="#section-7-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="sec-combined-references">

draft-edm-protocol-greasing.txt

@@ -71,6 +71,7 @@ Table of Contents
      3.2.  Use Unpredictable Grease Values
      3.3.  Use Grease Values at Unpredictable Times
      3.4.  Define and Register Grease Value Ranges
+       3.4.1.  Effectively Instructing IANA about grease
    4.  Considerations for Increasing Protocol Variability
      4.1.  Example: QUIC frames
    5.  Considerations for Protocol Versions
@@ -186,11 +187,13 @@ Table of Contents
    might unintentionally use grease values, which could lead to
    interoperability failures.
 
-   Protocols might ask IANA to create new registries for their extension
-   points.  When greasing, it is recommended that only a single entry
-   for the entire grease value set is registered.  When an algorithm has
-   been used, it should be included in the entry; see for example
-   https://www.iana.org/assignments/http3-parameters/
+3.4.1.  Effectively Instructing IANA about grease
+
+   Protocol designers might ask IANA to create new registries for their
+   extension points.  When greasing, it is recommended that only a
+   single entry for the entire grease value set is registered.  When an
+   algorithm has been used, it should be included in the entry; see for
+   example https://www.iana.org/assignments/http3-parameters/
    http3-parameters.xhtml#http3-parameters-frame-types.
 
    Grease values must not be used or registered for any other purpose.
@@ -261,7 +264,9 @@ Table of Contents
 
 7.  IANA Considerations
 
-   This document has no IANA actions.
+   This document has no IANA actions itself.  Guidance on how other
+   documents can effectively instruct IANA about protocol greasing is
+   provided in Section 3.4.1
 
 8.  References
 

index.html

@@ -29,7 +29,7 @@ <h2>Preview for branch <a href="iana-signposting">iana-signposting</a></h2>
       <tr>
         <td><a href="iana-signposting/draft-edm-protocol-greasing.html" class="html draft-edm-protocol-greasing" title="Maintaining Protocols Using Grease and Variability (HTML)">Protocol Greasing</a></td>
         <td><a href="iana-signposting/draft-edm-protocol-greasing.txt" class="txt draft-edm-protocol-greasing" title="Maintaining Protocols Using Grease and Variability (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://intarchboard.github.io/draft-protocol-greasing/draft-edm-protocol-greasing.txt&amp;url_2=https://intarchboard.github.io/draft-protocol-greasing/iana-signposting/draft-edm-protocol-greasing.txt" class="diff draft-edm-protocol-greasing">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <h2>Preview for branch <a href="update-deps">update-deps</a></h2>