[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Extension header order in draft-leddy-6man-truncate-04
From:       "C. M. Heard" <heard () pobox ! com>
Date:       2018-06-30 20:08:18
Message-ID: CACL_3VEWyZ5=peCfFG0swEN5gDktFEEwwSycOHTAc9x6QG4WzA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hello Ron,

It occurs to me that the proper order of headers when the "Truncation
Eligible" or "Truncated Packet" options appear should be:

      IPv6 header
      Hop-by-Hop Options header
      Destination Options header ("Truncation Eligible", "Truncated
Packet" , or note 1)

      Routing header
      Authentication header (note 2)
      Encapsulating Security Payload header (note 2)
      Destination Options header (note 3)
      Upper-Layer header



      note 1: for options to be processed by the first destination that
              appears in the IPv6 Destination Address field plus
              subsequent destinations listed in the Routing header.

      note 2: additional recommendations regarding the relative order of
              the Authentication and Encapsulating Security Payload
              headers are given in [RFC4303
<https://tools.ietf.org/html/rfc4303>].

      note 3: for options other than "Truncated Packet" that are to be

              processed only by the final destination of the packet.


My reasoning is that (a) we want "Truncation Eligible" to be processed by
the first destination if in the IPv6 header and subsequent destinations
listed in the routing header and (b) we want Truncated Packet" to be
processed before the Authentication Header (if one is present) at the final
destination. Note that case (b) is necessary since the truncated packet
will fail the AH integrity check. If AH were processed first, the
destination node would not send the desired PTB message,

Do you agree?

Mike Heard

[Attachment #5 (text/html)]

<div dir="ltr">Hello Ron,<div><br></div><div>It occurs to me that the proper order of \
headers when the &quot;<span style="color:rgb(0,0,0);font-size:13.3333px">Truncation \
Eligible&quot; or &quot;</span><span \
style="color:rgb(0,0,0);font-size:13.3333px">Truncated Packet&quot; options appear \
should be:</span><br></div><div><span \
style="color:rgb(0,0,0);font-size:13.3333px"><br></span></div><div><pre \
class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;page-break-before:always;color:rgb(0,0,0)"> \
IPv6 header  Hop-by-Hop Options header
      Destination Options header (&quot;Truncation Eligible&quot;, <span \
style="font-family:arial,sans-serif;font-size:13.3333px">&quot;</span><span \
style="font-family:arial,sans-serif;font-size:13.3333px">Truncated Packet&quot;  , or \
note 1</span><span style="font-size:13.3333px;font-family:arial,sans-serif">)</span></pre><pre \
class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;page-break-before:always;color:rgb(0,0,0)"> \
Routing header  Authentication header (note 2)
      Encapsulating Security Payload header (note 2)
      Destination Options header (note 3)
      Upper-Layer header
</pre></div><div><pre class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;page-break-before:always;color:rgb(0,0,0)"><br \
class="gmail-Apple-interchange-newline">  note 1: for options to be processed by the \
first destination that  appears in the IPv6 Destination Address field plus
              subsequent destinations listed in the Routing header.

      note 2: additional recommendations regarding the relative order of
              the Authentication and Encapsulating Security Payload
              headers are given in [<a href="https://tools.ietf.org/html/rfc4303" \
title="&quot;IP Encapsulating Security Payload (ESP)&quot;">RFC4303</a>].

      note 3: for options other than &quot;Truncated Packet&quot; that are to \
be</pre><pre class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;page-break-before:always;color:rgb(0,0,0)"> \
processed only by the final destination of the packet.</pre><pre \
class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;page-break-before:always;color:rgb(0,0,0)"><br></pre>My \
reasoning is that (a) we want &quot;Truncation Eligible&quot; to be processed by the \
first destination if in the IPv6 header and subsequent destinations listed in the \
routing header and (b) we want  <span \
style="color:rgb(0,0,0);font-size:13.3333px">Truncated Packet&quot; to be processed \
before the Authentication Header (if one is present) at the final destination. Note \
that case (b) is necessary since the truncated packet will fail the AH integrity \
check. If AH were processed first, the destination node would not send the desired \
PTB message,</span></div><div><br></div><div>Do you \
agree?</div><div><br></div><div>Mike Heard</div></div>



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]