Return-Path: <gregimirsky@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 94C853A1313;
 Sat, 29 Feb 2020 12:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id iUmCTEsALeLO; Sat, 29 Feb 2020 12:46:41 -0800 (PST)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com
 [IPv6:2a00:1450:4864:20::142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 84A133A1310;
 Sat, 29 Feb 2020 12:46:40 -0800 (PST)
Received: by mail-lf1-x142.google.com with SMTP id 7so4689274lfz.11;
 Sat, 29 Feb 2020 12:46:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc;
 bh=6Lysyq9UGuaFWmQCgjWw9LBFdmWmFI3vx6kTtUA4dlo=;
 b=g5XBDkuEUTSncdrrl8eGxomtRu60Tv0ceJEfNFxM5OBBkaWjtGuEHWHeK2wSx0asof
 OeoPsEbdVOOC0VneNwN6nc4jmxieCTxlk3DTZxNUlA1sTiWVfFUSqqZlgb90Y7CpmCi3
 oPY0omJoUTbsCHe3RihYnT4wi6jV+maCaMWYgLVbp46UjHg1N3tFFgALh0bN3BooXkXZ
 kZF/g/VaZQ0N1b7IgbLEW9HkmW8Z7G4NPqyj45OvuoRkLL4i7Ygk74nYm/QllzU7rSog
 Zca1uxx5TmYQWekK882LKUSl9m4dXEfzSwOIVk/8tO5KXnDW4d0wCGRSBsELUgnZXcO5 r88Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=6Lysyq9UGuaFWmQCgjWw9LBFdmWmFI3vx6kTtUA4dlo=;
 b=S5BlhUk4qjDLDdDsQ77wH7dYqCi+NL5Oz/QhKhDyzZggNHtibE4Wt162sR4hN+1Snd
 pcVtSBEakaweBHhQGTwqt8sTfrf6di1UkNDrTd4bjoBqm7je5nooj1WvoAAVtfI4i2WI
 3q2ZxdNnD9pXzojNf0VaePrBiGsbqtxIcRUaNKScONPqj4aiTrs237moQ4wRFvUSt67c
 9R+U12ycpiJc4rZr3wYZnbY5tMIZaYFcbwZgx5N0oJ/9em5P2njGEd/8GzzxQJR2KEUi
 UANYczO9ufb0qSzEqXl3U2lDvV+ddCjy5INWXjQ6O6S2lEvQkn+bsTsL4SDjJlJQVJgX
 XX5Q==
X-Gm-Message-State: ANhLgQ1LwjMHTwT89NzOCCc0aCwlmCZfX9vYyYuuNPtLobjjB8CxZEug
 m0PXSs/xJQLcgiyvIU4jaGHZjbJWuKUtL8KE2Uw=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vsYE8Wpr724aGkHeUXkGGCYyGFwKWGNU0aaj7Dg?=
 =?utf-8?q?MYzzmvkYXbDYPjtKq2oD+zcFwqxl5mAHJ5KfA0sHc6fB2OY=3D?=
X-Received: by 2002:a19:97:: with SMTP id 145mr5778060lfa.98.1583009198696;
 Sat, 29 Feb 2020 12:46:38 -0800 (PST)
MIME-Version: 1.0
References: <965ff6bbf1cb4c2f8d48b7b535a0cf5b@huawei.com>
 <CAJE_bqcTNWt==mtYKeNVXOBAzBNLG=+_mXQQ9xMHYOCDRqCb_Q@mail.gmail.com>
 <CAOj+MMEzbyzy98iFyfe6Z=dQiWHo=triX6bHKx9fNEUCaSuy3Q@mail.gmail.com>
 <085238CD-14F6-43AE-8D58-49A20DDCBB24@juniper.net>
 <CAOj+MMGzjP4C4CXi+6i+o_TMO5Un8HdGF+MMGLVa-KPUH+pXZw@mail.gmail.com>
 <3c07fa08-cd93-d0ae-fc76-ac8c8ae5baa7@gmail.com>
 <CA+RyBmX0EQydgvgUoPJB+6z6hcAiesVr43MnK_HNua0v8BieVA@mail.gmail.com>
 <CAOj+MMHBdU=urwhJV6QTn8RZZKZ0kyefHF9TDRbv5cH5CAQ5qg@mail.gmail.com>
In-Reply-To:
 <CAOj+MMHBdU=urwhJV6QTn8RZZKZ0kyefHF9TDRbv5cH5CAQ5qg@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 29 Feb 2020 12:46:27 -0800
Message-ID:
 <CA+RyBmV_AwDJAxrGwp8T7tBim9zfT2s6xqtwXKXQa8A+r_FXEQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>,
 John Scudder <jgs@juniper.net>, 
 "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>,
 =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary="000000000000f6f2ed059fbd0c1f"
Archived-At:
 <https://mailarchive.ietf.org/arch/msg/spring/aSbbp-SLhn037pSn0RejlNS0GBg>
Subject: Re: [spring] Suggest some text //RE: Request to close the LC and
 move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>,
 <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>,
 <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Feb 2020 20:46:44 -0000

--000000000000f6f2ed059fbd0c1f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Robert,
s/OEM/OAM/ ;)
True, active OAM should not generate excessive number of test packets and
that might make selective non-use of PSP on these packets acceptable. But
some have made a use case for PSP by describing environment where the
ultimate tunnel endpoint is not capable to process SRH. If that is the
practical case, then how SRv6 OAM will work at all?

Regards,
Greg

On Sat, Feb 29, 2020 at 12:36 PM Robert Raszuk <robert@raszuk.net> wrote:

> Greg,
>
> You are thinking of PSP like MPLS PHP to apply to all packets towards the
> guy who advertised implicit-null label.
>
> That is not the case here at all.
>
> You apply PSP when you like on a per segment endpoint basis. OEM as we
> have all agreed will not be subject to PSP. Is there a value to keep
> repeating that every day :) ?
>
> Cheers,
> R.
>
>
>
> On Sat, Feb 29, 2020 at 8:57 PM Greg Mirsky <gregimirsky@gmail.com> wrote=
:
>
>> Hi Brian,
>> you've said
>>
>>  Also, answering
>> your question "what harm does it do?" I think the answer objectively is
>> "none, unless
>> you want to use AH".
>>
>> On the other thread Ron and I have pointed that PSP does have decrementa=
l
>> effect on the ability to perform OAM, particularly performance monitorin=
g,
>> and the use of the O-bit proposed in draft-ietf-6man-spring-srv6-oam
>> <https://tools.ietf.org/html/draft-ietf-6man-spring-srv6-oam-03>is
>> questionable. Though these may not be veied as harmful consequences of P=
SP
>> but they clearly, in my opinion, are benefitial either.
>>
>> Regards,
>> Greg
>>
>> On Sat, Feb 29, 2020 at 11:25 AM Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>
>>> On 01-Mar-20 07:25, Robert Raszuk wrote:
>>> > Hi John,
>>> >
>>> > I respectfully will disagree with your assessment.
>>> >
>>> > Reason #1 - IPv6 can be encapsulated in IPv6 - RFC2473. This is base
>>> of SRv6 operation. If this would be deprecated, moved to historic or ma=
de
>>> illegal - games over. But if this is still legal then ultimate destinat=
ion
>>> for a packet is what it listed in outer IPv6 header DA. That's pretty
>>> basic. Now what the destination in the header will do with the packet i=
s
>>> completely different story.
>>> >
>>> > Reason #2 - "a node can=E2=80=99t be both the penultimate, and the ul=
timate,
>>> node." Of course it can. You are looking flat ..
>>>
>>> But I've been told by several people that this is not the use case. I
>>> believe
>>> the little diagram I sent yesterday is the use case. And the trick in
>>> the description
>>> of PSP is what I pointed out yesterday too: deleting the header when
>>> segments-left =3D=3D 0
>>> but the destination address is not yet set to the final one:
>>>
>>> https://mailarchive.ietf.org/arch/msg/spring/n46VuroVGvRurIgGNLZxFbAHvI=
o/
>>>
>>> The thing is, it can be coded and I fully believe there is running code=
.
>>> Also, answering
>>> your question "what harm does it do?" I think the answer objectively is
>>> "none, unless
>>> you want to use AH". Making a packet smaller on the last hop cannot
>>> break PMTUD.
>>>
>>> So I think the text needs to admit the trick it's playing on RFC 8200.
>>> Then the IETF
>>> can choose whether to let that trick pass.
>>>
>>>    Brian
>>>
>>>
>>> > If you look at different layers the same node is in fact acting in
>>> multiple roles - I can easily count 3 but with TI-LFA it could be  even
>>> more.
>>> >
>>> > The same node is ultimate destination for the outer header
>>> > in the same time
>>> > The same node is penultimate destination for SR path
>>> > in the same time
>>> > The same node is just regular IPv6 transit from the perspective of th=
e
>>> original non encapsulated packet
>>> >
>>> > Kind regards,
>>> > R.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Sat, Feb 29, 2020 at 6:46 PM John Scudder <jgs@juniper.net <mailto=
:
>>> jgs@juniper.net>> wrote:
>>> >
>>> >     Robert,
>>> >
>>> >     I think your comment (emphasis added):
>>> >
>>> >>     we are dealing here with an *encapsulated* packet which _has as
>>> its ultimate destination_ SR node X. That SR node X is to perform or no=
t
>>> PSP.
>>> >
>>> >     Is wrong. It contradicts everything else that=E2=80=99s been said=
 in the
>>> hundreds of messages that have gone before, not to mention the plain
>>> language of draft-ietf-spring-srv6-network-programming-10. The word
>>> =E2=80=9Cpenultimate=E2=80=9D itself is enough to prove this: by defini=
tion a node can=E2=80=99t be
>>> both the penultimate, and the ultimate, node. It=E2=80=99s a contradict=
ion in
>>> terms, like saying 0 equals 1.
>>> >
>>> >     Now, if node X were to remove the RH /and perform the
>>> decapsulation/ that would be a different story, but the whole point of =
PSP
>>> is that X removes the RH and then sends the encapsulated packet on to Y
>>> which performs the decapsulation. (This point was made in one of the ot=
her
>>> threads recently, but I=E2=80=99ve lost track of by whom and which thre=
ad.) As far
>>> as I can tell, this non-controversial behavior is described in 4.16.3 o=
f
>>> the draft and referred to as =E2=80=9CUSD=E2=80=9D.
>>> >
>>> >     =E2=80=94John
>>> >
>>> >>     On Feb 29, 2020, at 6:06 AM, Robert Raszuk <robert@raszuk.net
>>> <mailto:robert@raszuk.net>> wrote:
>>> >>
>>> >>     Dear Jinmei,
>>> >>
>>> >>     Even if RFC8200 section 4 text would say:
>>> >>
>>> >>      "Extension headers cannot be added to a packet after it has lef=
t
>>> its source node and extension headers cannot be removed from a packet u=
ntil
>>> it has arrived at its ultimate destination".
>>> >>
>>> >>     PSP would be still not be violating anything said in this
>>> sentence. Reason being is that we are dealing here with an *encapsulate=
d*
>>> packet which has as its ultimate destination SR node X. That SR node X =
is
>>> to perform or not PSP. So it is still fully compliant with the
>>> specification.
>>> >>
>>> >>     IMHO the only grey area as pointed by Brian is if RFC8200 sectio=
n
>>> 4.4 really mandates you to look at segments_left before processing the
>>> packet or it is equally legal to look at that value after local process=
ing
>>> occurs. Definition says:
>>> >>
>>> >>
>>> >>           Segments Left       8-bit unsigned integer.  Number of rou=
te
>>> >>                               segments remaining, i.e., number of
>>> explicitly
>>> >>                               listed intermediate nodes still to be
>>> visited
>>> >>                               before reaching the final destination.
>>> >>
>>> >>     which to me really means that as long as you recognize given
>>> routing header type you can decrement this value and if zero remove it.
>>> >>
>>> >>     Besides that is a minor detail - as NPG draft could be updated t=
o
>>> say:
>>> >>
>>> >>      S14.1.   If (Segments Left Before Local Decrement =3D=3D 1) {
>>> >>      S14.2.      Update the Next Header field in the preceding heade=
r
>>> to the
>>> >>                     Next Header value of the SRH
>>> >>      S14.3.      Decrease the IPv6 header Payload Length by the Hdr
>>> Ext Len
>>> >>                     value of the SRH
>>> >>      S14.4.      Remove the SRH from the IPv6 extension header chain
>>> >>      S14.5.   }
>>> >>
>>> >>     Many thx,
>>> >>     R.
>>> >>
>>> >>     On Sat, Feb 29, 2020 at 2:28 AM =E7=A5=9E=E6=98=8E=E9=81=94=E5=
=93=89 <jinmei@wide.ad.jp <mailto:
>>> jinmei@wide.ad.jp>> wrote:
>>> >>
>>> >>         At Fri, 28 Feb 2020 07:54:28 +0000,
>>> >>         "Xiejingrong (Jingrong)" <xiejingrong@huawei.com <mailto:
>>> xiejingrong@huawei...com>> wrote:
>>> >>
>>> >>         > The design of PSP for the benefits of deployment is based
>>> on the understanding
>>> >>         > that it does not violate section 4 of RFC8200. In case the
>>> RFC8200 text may be
>>> >>         > modified in the future, the PSP may also need to change
>>> accordingly.
>>> >>
>>> >>         No, it violates Section 4 of RFC8200.  It's a pity that we
>>> have to
>>> >>         discuss it at this level due to the poor editorial work then
>>> (I was
>>> >>         also responsible for that as one of those reviewing the bis
>>> draft),
>>> >>         but anyone who involved the discussion should know the inten=
t
>>> of this
>>> >>         text intended to say (borrowing from Ron's text) "Extension
>>> headers
>>> >>         cannot be added to a packet after it has left the its source
>>> node and
>>> >>         extension headers cannot be removed from a packet until it
>>> has arrived
>>> >>         at its ultimate destination".  It might look "an attempt of
>>> blocking
>>> >>         an innovation by a small group of vocal fundamentalists", bu=
t
>>> if you
>>> >>         see the responses without a bias, you'd notice that even som=
e
>>> of those
>>> >>         who seem neutral about the underlying SRv6 matter interpret
>>> the text
>>> >>         that way.
>>> >>
>>> >>         I'd also note that simply because PSP violates RFC8200 doesn=
't
>>> >>         immediately mean it (PSP) "needs to change".  It can update
>>> RFC8200 with
>>> >>         explaining why it's necessary and justified.  That's what I
>>> >>         requested as you summarized:
>>> >>
>>> >>         > Jinmei: it should say it updates this part of RFC8200 and
>>> explain why it's justified.
>>> >>
>>> >>         And, since PSP at least wouldn't break PMTUD, I guess the
>>> update
>>> >>         proposal will have much more chance to be accepted than a
>>> proposal
>>> >>         including EH insertion.  On the other hand, pretending
>>> there's no
>>> >>         violation will certainly trigger many appeals and objections
>>> at the
>>> >>         IETF last call (I'll certainly object to it).  In the end, i=
t
>>> can
>>> >>         easily take much longer, or even fail, than formally claimin=
g
>>> an
>>> >>         update to RFC8200.
>>> >>
>>> >>         --
>>> >>         JINMEI, Tatuya
>>> >>
>>> >>         _______________________________________________
>>> >>         spring mailing list
>>> >>         spring@ietf.org <mailto:spring@ietf.org>
>>> >>         https://www.ietf.org/mailman/listinfo/spring <
>>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/sprin=
g__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3Uda=
zBorQ$
>>> >
>>> >>
>>> >>
>>>  --------------------------------------------------------------------
>>> >>     IETF IPv6 working group mailing list
>>> >>     ipv6@ietf.org <mailto:ipv6@ietf.org>
>>> >>     Administrative Requests:
>>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6_=
_;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3X18Tt=
wYw$
>>> <
>>> https://urldefense.com/v3/__https://www..ietf.org/mailman/listinfo/ipv6=
__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3X18T=
twYw$
>>> >
>>> >>
>>>  --------------------------------------------------------------------
>>> >
>>> >
>>> > --------------------------------------------------------------------
>>> > IETF IPv6 working group mailing list
>>> > ipv6@ietf.org
>>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> > --------------------------------------------------------------------
>>> >
>>>
>>> _______________________________________________
>>> spring mailing list
>>> spring@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spring
>>>
>>

--000000000000f6f2ed059fbd0c1f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Robert,<div>s/OEM/OAM/ ;)</div><div>True, active OAM sh=
ould not generate excessive number of test packets and that might make sele=
ctive non-use of PSP on these packets acceptable. But some have made a use =
case for PSP by describing environment where the ultimate tunnel endpoint i=
s not capable to process SRH. If that is the practical case, then how SRv6 =
OAM will work at all?</div><div><br></div><div>Regards,</div><div>Greg</div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Sat, Feb 29, 2020 at 12:36 PM Robert Raszuk &lt;<a href=3D"mailto:rober=
t@raszuk.net">robert@raszuk.net</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Greg,<div><br></div><div>=
You are thinking of PSP like MPLS PHP to apply to all packets towards the g=
uy who advertised=C2=A0implicit-null label.=C2=A0</div><div><br></div><div>=
That is not the case here at all.=C2=A0</div><div><br></div><div>You apply =
PSP when you=C2=A0like on a per segment endpoint basis. OEM as we have all =
agreed will not be subject to PSP. Is there a value to keep repeating that =
every day=C2=A0:) ?=C2=A0</div><div><br></div><div>Cheers,</div><div>R.</di=
v><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 29, 2020 at 8:57 PM Greg Mirsky=
 &lt;<a href=3D"mailto:gregimirsky@gmail.com" target=3D"_blank">gregimirsky=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr">Hi Brian,<div>you&#39;ve said</div><blockquote =
style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div>=C2=A0Also, =
answering</div><div>your question &quot;what harm does it do?&quot; I think=
 the answer objectively is &quot;none, unless</div><div>you want to use AH&=
quot;.=C2=A0</div></blockquote>On the other thread Ron and I have pointed t=
hat PSP does have decremental effect on the ability to perform OAM, particu=
larly performance monitoring, and the use of the O-bit proposed in <a href=
=3D"https://tools.ietf.org/html/draft-ietf-6man-spring-srv6-oam-03" target=
=3D"_blank">draft-ietf-6man-spring-srv6-oam=C2=A0</a>is questionable. Thoug=
h these may not be veied as harmful consequences=C2=A0of PSP but they clear=
ly, in my opinion, are benefitial either.<div><br></div><div>Regards,</div>=
<div>Greg</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Sat, Feb 29, 2020 at 11:25 AM Brian E Carpenter &lt;<a h=
ref=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpen=
ter@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">On 01-Mar-20 07:25, Robert Raszuk wrote:<br>
&gt; Hi John,<br>
&gt; <br>
&gt; I respectfully will disagree with your assessment.=C2=A0<br>
&gt; <br>
&gt; Reason #1 - IPv6 can be encapsulated in IPv6 - RFC2473. This is base o=
f SRv6 operation. If this would be deprecated, moved to historic or made il=
legal - games over. But if this is still legal then ultimate destination fo=
r a packet is what it listed in outer IPv6 header DA. That&#39;s pretty bas=
ic. Now what the destination in the header will do with the packet is compl=
etely different story.=C2=A0<br>
&gt; <br>
&gt; Reason #2 - &quot;a node can=E2=80=99t be both the penultimate, and th=
e ultimate, node.&quot; Of course it can. You are looking flat .. <br>
<br>
But I&#39;ve been told by several people that this is not the use case. I b=
elieve<br>
the little diagram I sent yesterday is the use case. And the trick in the d=
escription<br>
of PSP is what I pointed out yesterday too: deleting the header when segmen=
ts-left =3D=3D 0<br>
but the destination address is not yet set to the final one:<br>
<br>
<a href=3D"https://mailarchive.ietf.org/arch/msg/spring/n46VuroVGvRurIgGNLZ=
xFbAHvIo/" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.or=
g/arch/msg/spring/n46VuroVGvRurIgGNLZxFbAHvIo/</a><br>
<br>
The thing is, it can be coded and I fully believe there is running code. Al=
so, answering<br>
your question &quot;what harm does it do?&quot; I think the answer objectiv=
ely is &quot;none, unless<br>
you want to use AH&quot;. Making a packet smaller on the last hop cannot br=
eak PMTUD.<br>
<br>
So I think the text needs to admit the trick it&#39;s playing on RFC 8200. =
Then the IETF<br>
can choose whether to let that trick pass.<br>
<br>
=C2=A0 =C2=A0Brian<br>
<br>
<br>
&gt; If you look at different layers the same node is in fact acting in mul=
tiple roles - I can easily count 3 but with TI-LFA it could be=C2=A0 even m=
ore.=C2=A0<br>
&gt; <br>
&gt; The same node is ultimate destination for the outer header=C2=A0<br>
&gt; in the same time=C2=A0<br>
&gt; The same node is penultimate destination for SR path<br>
&gt; in the same time=C2=A0<br>
&gt; The same node is just regular IPv6 transit from the perspective of the=
 original non encapsulated packet=C2=A0<br>
&gt; <br>
&gt; Kind regards,<br>
&gt; R.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On Sat, Feb 29, 2020 at 6:46 PM John Scudder &lt;<a href=3D"mailto:jgs=
@juniper.net" target=3D"_blank">jgs@juniper.net</a> &lt;mailto:<a href=3D"m=
ailto:jgs@juniper.net" target=3D"_blank">jgs@juniper.net</a>&gt;&gt; wrote:=
<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Robert,<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I think your comment (emphasis added):<br>
&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0we are dealing here with an *encapsulated* pack=
et which _has as its ultimate destination_ SR node X. That SR node X is to =
perform or not PSP.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Is wrong. It contradicts everything else that=E2=80=
=99s been said in the hundreds of messages that have gone before, not to me=
ntion the plain language of=C2=A0draft-ietf-spring-srv6-network-programming=
-10. The word =E2=80=9Cpenultimate=E2=80=9D itself is enough to prove this:=
 by definition a node can=E2=80=99t be both the penultimate, and the ultima=
te, node. It=E2=80=99s a contradiction in terms, like saying 0 equals 1.=C2=
=A0<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Now, if node X were to remove the RH /and perform t=
he decapsulation/ that would be a different story, but the whole point of P=
SP is that X removes the RH and then sends the encapsulated packet on to Y =
which performs the decapsulation. (This point was made in one of the other =
threads recently, but I=E2=80=99ve lost track of by whom and which thread.)=
 As far as I can tell, this non-controversial behavior is described in 4.16=
.3 of the draft and referred to as =E2=80=9CUSD=E2=80=9D.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0=E2=80=94John<br>
&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0On Feb 29, 2020, at 6:06 AM, Robert Raszuk &lt;=
<a href=3D"mailto:robert@raszuk.net" target=3D"_blank">robert@raszuk.net</a=
> &lt;mailto:<a href=3D"mailto:robert@raszuk.net" target=3D"_blank">robert@=
raszuk.net</a>&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Dear Jinmei,<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Even if RFC8200 section 4 text would say:=C2=A0=
<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0=C2=A0&quot;Extension headers cannot be added t=
o a packet after it has left its source node and extension headers cannot b=
e removed from a packet until it has arrived at its ultimate destination&qu=
ot;.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0PSP would be still not be violating anything sa=
id in this sentence. Reason being is that we are dealing here with an *enca=
psulated* packet which has as its ultimate destination SR node X. That SR n=
ode X is to perform or not PSP. So it is still fully compliant=C2=A0with th=
e specification.=C2=A0<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0IMHO the only grey area as pointed by Brian is =
if RFC8200 section 4.4 really mandates you to look at segments_left before =
processing the packet or it is equally legal to look at that value after lo=
cal processing occurs. Definition says:=C2=A0<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Segments Left=C2=A0 =C2=A0=
 =C2=A0 =C2=A08-bit unsigned integer.=C2=A0 Number of route<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0segments remaining, i.e., numb=
er of explicitly<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0listed intermediate nodes stil=
l to be visited<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0before reaching the final dest=
ination.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0which to me really means that as long as you re=
cognize given routing header type you can decrement this value and if zero =
remove it.=C2=A0<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Besides that is a minor detail - as NPG draft c=
ould be updated to say:=C2=A0<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 S14.1.=C2=A0 =C2=A0If (Segments Left Before Lo=
cal Decrement =3D=3D 1) {<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 S14.2.=C2=A0 =C2=A0 =C2=A0 Update the Next Hea=
der field in the preceding header to the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Next Header value of the SRH<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 S14.3.=C2=A0 =C2=A0 =C2=A0 Decrease the IPv6 h=
eader Payload Length by the Hdr Ext Len<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0value of the SRH<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 S14.4.=C2=A0 =C2=A0 =C2=A0 Remove the SRH from=
 the IPv6 extension header chain<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 S14.5.=C2=A0 =C2=A0}<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Many thx,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0R.=C2=A0<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0On Sat, Feb 29, 2020 at 2:28 AM =E7=A5=9E=E6=98=
=8E=E9=81=94=E5=93=89 &lt;<a href=3D"mailto:jinmei@wide.ad.jp" target=3D"_b=
lank">jinmei@wide.ad.jp</a> &lt;mailto:<a href=3D"mailto:jinmei@wide.ad.jp"=
 target=3D"_blank">jinmei@wide.ad.jp</a>&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0At Fri, 28 Feb 2020 07:54:28 +000=
0,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;Xiejingrong (Jingrong)&quot=
; &lt;<a href=3D"mailto:xiejingrong@huawei.com" target=3D"_blank">xiejingro=
ng@huawei.com</a> &lt;mailto:<a href=3D"mailto:xiejingrong@huawei." target=
=3D"_blank">xiejingrong@huawei.</a>..com&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; The design of PSP for the be=
nefits of deployment is based on the understanding<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; that it does not violate sec=
tion 4 of RFC8200. In case the RFC8200 text may be<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; modified in the future, the =
PSP may also need to change accordingly.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0No, it violates Section 4 of RFC8=
200.=C2=A0 It&#39;s a pity that we have to<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0discuss it at this level due to t=
he poor editorial work then (I was<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0also responsible for that as one =
of those reviewing the bis draft),<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0but anyone who involved the discu=
ssion should know the intent of this<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0text intended to say (borrowing f=
rom Ron&#39;s text) &quot;Extension headers<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cannot be added to a packet after=
 it has left the its source node and<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0extension headers cannot be remov=
ed from a packet until it has arrived<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0at its ultimate destination&quot;=
.=C2=A0 It might look &quot;an attempt of blocking<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0an innovation by a small group of=
 vocal fundamentalists&quot;, but if you<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0see the responses without a bias,=
 you&#39;d notice that even some of those<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0who seem neutral about the underl=
ying SRv6 matter interpret the text<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0that way.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I&#39;d also note that simply bec=
ause PSP violates RFC8200 doesn&#39;t<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0immediately mean it (PSP) &quot;n=
eeds to change&quot;.=C2=A0 It can update RFC8200 with<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0explaining why it&#39;s necessary=
 and justified.=C2=A0 That&#39;s what I<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0requested as you summarized:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; Jinmei: it should say it upd=
ates this part of RFC8200 and explain why it&#39;s justified.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0And, since PSP at least wouldn&#3=
9;t break PMTUD, I guess the update<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0proposal will have much more chan=
ce to be accepted than a proposal<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0including EH insertion.=C2=A0 On =
the other hand, pretending there&#39;s no<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0violation will certainly trigger =
many appeals and objections at the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IETF last call (I&#39;ll certainl=
y object to it).=C2=A0 In the end, it can<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0easily take much longer, or even =
fail, than formally claiming an<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0update to RFC8200.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0JINMEI, Tatuya<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_________________________________=
______________<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0spring mailing list<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:spring@ietf.org=
" target=3D"_blank">spring@ietf.org</a> &lt;mailto:<a href=3D"mailto:spring=
@ietf.org" target=3D"_blank">spring@ietf.org</a>&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/m=
ailman/listinfo/spring" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/mailman/listinfo/spring</a> &lt;<a href=3D"https://urldefense.com/v3=
/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!Qj4iGvIKXE0=
YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3UdazBorQ$" rel=3D"noreferrer" ta=
rget=3D"_blank">https://urldefense.com/v3/__https://www.ietf.org/mailman/li=
stinfo/spring__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTi=
IYCqCc0y3UdazBorQ$</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0-----------------------------------------------=
---------------------<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0IETF IPv6 working group mailing list<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:ipv6@ietf.org" target=3D"_bla=
nk">ipv6@ietf.org</a> &lt;mailto:<a href=3D"mailto:ipv6@ietf.org" target=3D=
"_blank">ipv6@ietf.org</a>&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Administrative Requests: <a href=3D"https://url=
defense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk=
!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3X18TtwYw$" rel=3D"no=
referrer" target=3D"_blank">https://urldefense.com/v3/__https://www.ietf.or=
g/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED=
6VMnC3MxTiIYCqCc0y3X18TtwYw$</a> &lt;<a href=3D"https://urldefense.com/v3/_=
_https://www..ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!Qj4iGvIKXE0YAB=
WYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3X18TtwYw$" rel=3D"noreferrer" targe=
t=3D"_blank">https://urldefense.com/v3/__https://www..ietf.org/mailman/list=
info/ipv6__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCq=
Cc0y3X18TtwYw$</a>&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0-----------------------------------------------=
---------------------<br>
&gt; <br>
&gt; <br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.org</a><b=
r>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; <br>
<br>
_______________________________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/spring</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000f6f2ed059fbd0c1f--

