Script updating gh-pages from 236355a. [ci skip]

lamps-wg · Nov 27, 2023 · 97583eb · 97583eb
1 parent 7f643b4
commit 97583eb
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 1 deletion.
diff --git a/draft-ietf-lamps-rfc4210bis.html b/draft-ietf-lamps-rfc4210bis.html
@@ -3577,6 +3577,9 @@ <h5 id="name-multiple-protection">
   NestedMessageContent ::= PKIMessages
 </pre><a href="#section-5.1.3.5-4" class="pilcrow">¶</a>
 </div>
+<p id="section-5.1.3.5-5">In case an RA needs to modify a request message, it <span class="bcp14">MAY</span> include the original
+PKIMessage in the generalInfo field of the modified message as described in
+<a href="#sect-5.1.1.3" class="auto internal xref">Section 5.1.1.3</a>.<a href="#section-5.1.3.5-5" class="pilcrow">¶</a></p>
 </section>
 </div>
 </section>
@@ -7820,7 +7823,10 @@ <h2 id="name-history-of-changes">
           <p id="appendix-G-3.3.1">Some editorial changes to Section 5.1.3.4 and Appendix E after discussion with David resolving #30 and discussing at IETF 117<a href="#appendix-G-3.3.1" class="pilcrow">¶</a></p>
 </li>
         <li class="normal" id="appendix-G-3.4">
-          <p id="appendix-G-3.4.1">Fixed some references in Section 5.2.8.3 which broke from RFC2510 to RFC4210<a href="#appendix-G-3.4.1" class="pilcrow">¶</a></p>
+          <p id="appendix-G-3.4.1">Added a cross-reference to Section 5.1.1.3 regarding use of OrigPKIMessage to Section 5.1.3.5<a href="#appendix-G-3.4.1" class="pilcrow">¶</a></p>
+</li>
+        <li class="normal" id="appendix-G-3.5">
+          <p id="appendix-G-3.5.1">Fixed some references in Section 5.2.8.3 which broke from RFC2510 to RFC4210<a href="#appendix-G-3.5.1" class="pilcrow">¶</a></p>
 </li>
       </ul>
 <p id="appendix-G-4">From version 06 -&gt; 07:<a href="#appendix-G-4" class="pilcrow">¶</a></p>

diff --git a/draft-ietf-lamps-rfc4210bis.txt b/draft-ietf-lamps-rfc4210bis.txt
@@ -1959,6 +1959,10 @@ Table of Contents
 
      NestedMessageContent ::= PKIMessages
 
+   In case an RA needs to modify a request message, it MAY include the
+   original PKIMessage in the generalInfo field of the modified message
+   as described in Section 5.1.1.3.
+
 5.2.  Common Data Structures
 
    Before specifying the specific types that may be placed in a PKIBody,
@@ -5759,6 +5763,9 @@ Appendix G.  History of Changes
    *  Some editorial changes to Section 5.1.3.4 and Appendix E after
       discussion with David resolving #30 and discussing at IETF 117
 
+   *  Added a cross-reference to Section 5.1.1.3 regarding use of
+      OrigPKIMessage to Section 5.1.3.5
+
    *  Fixed some references in Section 5.2.8.3 which broke from RFC2510
       to RFC4210