deploy: 553e899

Author: klassert

draft-ietf-ipsecme-eesp-latest.html

@@ -1223,11 +1223,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">EESP</td>
-<td class="right">June 2025</td>
+<td class="right">July 2025</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">Klassert, et al.</td>
-<td class="center">Expires 29 December 2025</td>
+<td class="center">Expires 4 January 2026</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1238,12 +1238,12 @@
 <dd class="workgroup">IPSECME Working Group</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2025-06-27" class="published">27 June 2025</time>
+<time datetime="2025-07-03" class="published">3 July 2025</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-12-29">29 December 2025</time></dd>
+<dd class="expires"><time datetime="2026-01-04">4 January 2026</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1295,7 +1295,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 29 December 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 4 January 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1772,7 +1772,6 @@ <h4 id="name-fixed-base-header">
               <p id="section-2.2.1-3.12.1">32 bits: The SPI is an arbitrary
 32-bit value that is used by a receiver to identify the SA to which
 an incoming packet is bound.<a href="#section-2.2.1-3.12.1" class="pilcrow">¶</a></p>
-<p id="section-2.2.1-3.12.2">#This combined with the 16-bit Session ID is the Enhanced SPI.<a href="#section-2.2.1-3.12.2" class="pilcrow">¶</a></p>
 </dd>
           <dd class="break"></dd>
 </dl>
@@ -1866,7 +1865,8 @@ <h3 id="name-peer-header">
 |                    Sequence Number (optional)                 |
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-|                          IV (optional)                        |
+|                                                               |
+~                          IV (optional)                        ~
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 </pre>
@@ -1941,7 +1941,8 @@ <h4 id="name-initialization-vector">
 <p id="section-2.3.2-2">Counter mode algorithms MAY use the 64-bit counter as the
 Initialization Vector (IV) in the Sequence number Field, as specified
 <span>[<a href="#RFC8750" class="cite xref">RFC8750</a>]</span>. This option, Implicit Initialization Vector (IIV)
-saves 8 header bytes on each packet. Whether or not this option is
+saves the size of IV on each packet.
+Whether or not this option is
 selected is determined as part of Security Association (SA)
 establishment.<a href="#section-2.3.2-2" class="pilcrow">¶</a></p>
 </section>
@@ -2110,7 +2111,8 @@ <h3 id="name-full-and-optimized-packet-f">
 |                   Sequence Number (optional)                  |
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-|                          IV* (optional)                       |
+|                                                               |
+~                          IV* (optional)                       ~
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  0x0  |        Reserved       | Next Header   | Pad Length    |
@@ -2149,7 +2151,8 @@ <h3 id="name-full-and-optimized-packet-f">
 |                   Sequence Number (optional)                  |
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
-|                          IV* (optional)                       |
+|                                                               |
+~                          IV* (optional)                       ~
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                                                               |
@@ -2520,14 +2523,14 @@ <h4 id="name-eesp-flow-identifier-option">
           </h4>
 <p id="section-3.1.2-1">Flow Identifier (FID) Options are used to carry characteristic
 information of the inner flow and SHOULD NOT change on per packet
-basis inside any inner flow. # to avoid packet reordering.
-The Flow Identifier SHOULD be negotiated by IKEv2 or another
+basis inside any inner flow.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p>
+<p id="section-3.1.2-2">The Flow Identifier SHOULD be negotiated by IKEv2 or another
 suitable protocol. The detailed specification of FIDs MAY be provided
 in subsequent documents. The precise meaning of a FID is opaque to
-intermediate devices.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p>
+intermediate devices.<a href="#section-3.1.2-2" class="pilcrow">¶</a></p>
 <span id="name-flow-identifier-option"></span><div id="fid-option">
 <figure id="figure-11">
-            <div class="sourcecode" id="section-3.1.2-2.1">
+            <div class="sourcecode" id="section-3.1.2-3.1">
 <pre>
  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
@@ -2544,21 +2547,21 @@ <h4 id="name-eesp-flow-identifier-option">
 <a href="#name-flow-identifier-option" class="selfRef">Flow Identifier Option</a>
             </figcaption></figure>
 </div>
-<span class="break"></span><dl class="dlParallel" id="section-3.1.2-3">
-            <dt id="section-3.1.2-3.1">Option Type</dt>
-            <dd style="margin-left: 1.5em" id="section-3.1.2-3.2">
-              <p id="section-3.1.2-3.2.1">8 bits: See <a href="#sec-eesp-header-options" class="auto internal xref">Section 3</a><a href="#section-3.1.2-3.2.1" class="pilcrow">¶</a></p>
+<span class="break"></span><dl class="dlParallel" id="section-3.1.2-4">
+            <dt id="section-3.1.2-4.1">Option Type</dt>
+            <dd style="margin-left: 1.5em" id="section-3.1.2-4.2">
+              <p id="section-3.1.2-4.2.1">8 bits: See <a href="#sec-eesp-header-options" class="auto internal xref">Section 3</a><a href="#section-3.1.2-4.2.1" class="pilcrow">¶</a></p>
 </dd>
             <dd class="break"></dd>
-<dt id="section-3.1.2-3.3">Option Length</dt>
-            <dd style="margin-left: 1.5em" id="section-3.1.2-3.4">
-              <p id="section-3.1.2-3.4.1">8 bits: See <a href="#sec-eesp-header-options" class="auto internal xref">Section 3</a><a href="#section-3.1.2-3.4.1" class="pilcrow">¶</a></p>
+<dt id="section-3.1.2-4.3">Option Length</dt>
+            <dd style="margin-left: 1.5em" id="section-3.1.2-4.4">
+              <p id="section-3.1.2-4.4.1">8 bits: See <a href="#sec-eesp-header-options" class="auto internal xref">Section 3</a><a href="#section-3.1.2-4.4.1" class="pilcrow">¶</a></p>
 </dd>
             <dd class="break"></dd>
-<dt id="section-3.1.2-3.5">FID</dt>
-            <dd style="margin-left: 1.5em" id="section-3.1.2-3.6">
-              <p id="section-3.1.2-3.6.1">Variable length, carries characteristic information of a
-inner flow and MUST NOT change for a given inner flow within a SA.<a href="#section-3.1.2-3.6.1" class="pilcrow">¶</a></p>
+<dt id="section-3.1.2-4.5">FID</dt>
+            <dd style="margin-left: 1.5em" id="section-3.1.2-4.6">
+              <p id="section-3.1.2-4.6.1">Variable length, carries characteristic information of a
+inner flow and MUST NOT change for a given inner flow within a SA.<a href="#section-3.1.2-4.6.1" class="pilcrow">¶</a></p>
 </dd>
           <dd class="break"></dd>
 </dl>
@@ -2568,12 +2571,12 @@ <h4 id="name-eesp-flow-identifier-option">
           <h4 id="name-eesp-crypt-offset-option">
 <a href="#section-3.1.3" class="section-number selfRef">3.1.3. </a><a href="#name-eesp-crypt-offset-option" class="section-name selfRef">EESP Crypt Offset Option</a>
           </h4>
-<p id="section-3.1.3-1">This option is typically used for within one Datacenter use case
+<p id="section-3.1.3-1">This option is typically used within one Datacenter use case
 such as <span>[<a href="#PSP" class="cite xref">PSP</a>]</span>. When enabled, full packet format with Payload Info
 Header MUST be used; for the intermediate router to have Next Header.<a href="#section-3.1.3-1" class="pilcrow">¶</a></p>
 <p id="section-3.1.3-2">The Crypt Offset can vary on a per packet basis. The maximum
 allowed Crypt Offset MUST be negotiated by IKEv2 or any other
-appropriate protocol. Packets with a Crypt Offset grater than
+appropriate protocol. Packets with a Crypt Offset greater than
 the negotiated maximum MUST be dropped by the receiver.
 The receiver SHOULD cryptographically process such packets anyway.
 The action in case of a correct ICV value depends on local policy.