Return-Path: <brian.e.carpenter@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 4DB2D3A11AA;
 Sat, 29 Feb 2020 11:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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,
 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 F5eazEPF5byG; Sat, 29 Feb 2020 11:25:36 -0800 (PST)
Received: from mail-pg1-x541.google.com (mail-pg1-x541.google.com
 [IPv6:2607:f8b0:4864:20::541])
 (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 2A6F03A11AE;
 Sat, 29 Feb 2020 11:25:36 -0800 (PST)
Received: by mail-pg1-x541.google.com with SMTP id y30so3268945pga.13;
 Sat, 29 Feb 2020 11:25:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=subject:to:cc:references:from:message-id:date:user-agent
 :mime-version:in-reply-to:content-language:content-transfer-encoding;
 bh=AbwBKerLdEd5jgJo+xL28xroUbJ1dTh6LvMPFcHygkw=;
 b=jAo6WNTyRZBHmfHqWWGL/d8MEoUeA+EKin1hGSeQuUzWbSHJnqX3De6syojLxcEeBh
 lDIdtfTKkdkBtrPkbWUwflBKk2YA6CeBzVXDwMXvx/Fpk5SbF+/10ND3VKJvIT1zC9/Q
 FrP3UvMgnvluPcNfRPpL3vKTEVPRzVNLP7cPE0sJIOE15vUYh7y4dNgcNefk5whlmwXr
 lpj6KZgXiVAW/CaUKReVpjHAqleqlPAMIMyv/S8yJHuXYeWiIx5peSarGm8cI/aEokbK
 XaArPB0Mx7MJAJJ2C4UF+7dxS8k9SPrKJe+hR6fywYAqB9JhDVvjZlwkE5+GZ4HdXrxC
 K2BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:subject:to:cc:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-language
 :content-transfer-encoding;
 bh=AbwBKerLdEd5jgJo+xL28xroUbJ1dTh6LvMPFcHygkw=;
 b=FCuvtA2K+u7hSGSbc5fcSH2XnA/y+YD8Bkmxoa8DTBV9tHInYnEK/BL/oX8KoJjBTb
 N4mG5ZJtuDUuhpBZKicD0F4pgs6ZATuunrgx+Kr2iQ96ORpTYKQHG3sdNwZ9ouyV7V9p
 hnvpVK1OORvjmeRtoXN5WGDh7mcnryZR4yMwZnIPTbZ79wi5NBpgz+jreyIVqCI5ws5+
 xcl5eGNxhtd8pAIVbbqvXUG9fsFBzjuLjAdXYPmV2v6yb9ED/n7WO7/qzQFRmgyKIpG4
 f/BmQY6dMb6h8r4ugMrI7ZtU1/305pzrKAvprL+eDA6b+FT9WK1+oyanYIAhLo8mgUXU
 EJKQ==
X-Gm-Message-State: APjAAAVz91cItoLuAKKtHT3n263aHavmoePbKnGjl93J2g/XTdUC4NoA
 al9tqyTpXrg0bcgrDHm+pC8=
X-Google-Smtp-Source: 
 APXvYqxG4V0tVjO8e6tl8LdBnGRohIW8GAalVLZZZBoqIdMUvXce2dnTm/8xpvoAR3P2YQXxvWdbQg==
X-Received: by 2002:a63:36cd:: with SMTP id
 d196mr11282682pga.280.1583004335490;
 Sat, 29 Feb 2020 11:25:35 -0800 (PST)
Received: from [192.168.178.30] ([165.84.25.143])
 by smtp.gmail.com with ESMTPSA id t2sm1619532pfb.140.2020.02.29.11.25.32
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 29 Feb 2020 11:25:34 -0800 (PST)
To: Robert Raszuk <robert@raszuk.net>, John Scudder <jgs@juniper.net>
Cc: "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>,
 =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3c07fa08-cd93-d0ae-fc76-ac8c8ae5baa7@gmail.com>
Date: Sun, 1 Mar 2020 08:25:30 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: 
 <CAOj+MMGzjP4C4CXi+6i+o_TMO5Un8HdGF+MMGLVa-KPUH+pXZw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/spring/PzAdB43yO2AxZz6VQGqdvEnSaKw>
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 19:25:41 -0000

On 01-Mar-20 07:25, Robert Raszuk wrote:
> Hi John,
>=20
> I respectfully will disagree with your assessment.=C2=A0
>=20
> Reason #1 - IPv6 can be encapsulated in IPv6 - RFC2473. This is base of=
 SRv6 operation. If this would be deprecated, moved to historic or made i=
llegal - games over. But if this is still legal then ultimate destination=
 for a packet is what it listed in outer IPv6 header DA. That's pretty ba=
sic. Now what the destination in the header will do with the packet is co=
mpletely different story.=C2=A0
>=20
> Reason #2 - "a node can=E2=80=99t be both the penultimate, and the ulti=
mate, node." Of course it can. You are looking flat ..=20

But I've been told by several people that this is not the use case. I bel=
ieve
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 segm=
ents-left =3D=3D 0
but the destination address is not yet set to the final one:

https://mailarchive.ietf.org/arch/msg/spring/n46VuroVGvRurIgGNLZxFbAHvIo/=


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. Th=
en 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 mult=
iple roles - I can easily count 3 but with TI-LFA it could be=C2=A0 even =
more.=C2=A0
>=20
> The same node is ultimate destination for the outer header=C2=A0
> in the same time=C2=A0
> The same node is penultimate destination for SR path
> in the same time=C2=A0
> The same node is just regular IPv6 transit from the perspective of the =
original non encapsulated packet=C2=A0
>=20
> Kind regards,
> R.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> On Sat, Feb 29, 2020 at 6:46 PM John Scudder <jgs@juniper.net <mailto:j=
gs@juniper.net>> wrote:
>=20
>     Robert,
>=20
>     I think your comment (emphasis added):
>=20
>>     we are dealing here with an *encapsulated* packet which _has as it=
s ultimate destination_ SR node X. That SR node X is to perform or not PS=
P.
>=20
>     Is wrong. It contradicts everything else that=E2=80=99s been said i=
n the hundreds of messages that have gone before, not to mention the plai=
n language of=C2=A0draft-ietf-spring-srv6-network-programming-10. The wor=
d =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=
=2E It=E2=80=99s a contradiction in terms, like saying 0 equals 1.=C2=A0
>=20
>     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 r=
emoves the RH and then sends the encapsulated packet on to Y which perfor=
ms the decapsulation. (This point was made in one of the other threads re=
cently, 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.
>=20
>     =E2=80=94John
>=20
>>     On Feb 29, 2020, at 6:06 AM, Robert Raszuk <robert@raszuk.net <mai=
lto:robert@raszuk.net>> wrote:
>>
>>     Dear Jinmei,
>>
>>     Even if RFC8200 section 4 text would say:=C2=A0
>>
>>     =C2=A0"Extension headers cannot be added to a packet after it has =
left its source node and extension headers cannot be removed from a packe=
t until it has arrived at its ultimate destination".
>>
>>     PSP would be still not be violating anything said in this sentence=
=2E Reason being is that we are dealing here with an *encapsulated* packe=
t which has as its ultimate destination SR node X. That SR node X is to p=
erform or not PSP. So it is still fully compliant=C2=A0with the specifica=
tion.=C2=A0
>>
>>     IMHO 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 pa=
cket or it is equally legal to look at that value after local processing =
occurs. Definition says:=C2=A0
>>
>>
>>           Segments Left       8-bit unsigned integer.  Number of route=

>>                               segments remaining, i.e., number of expl=
icitly
>>                               listed intermediate nodes still to be vi=
sited
>>                               before reaching the final destination.
>>
>>     which to me really means that as long as you recognize given routi=
ng header type you can decrement this value and if zero remove it.=C2=A0
>>
>>     Besides that is a minor detail - as NPG draft could be updated to =
say:=C2=A0
>>
>>      S14.1.   If (Segments Left Before Local Decrement =3D=3D 1) {
>>      S14.2.      Update the Next Header field in the preceding header =
to the
>>                     Next Header value of the SRH
>>      S14.3.      Decrease the IPv6 header Payload Length by the Hdr Ex=
t Len
>>                     value of the SRH
>>      S14.4.      Remove the SRH from the IPv6 extension header chain
>>      S14.5.   }
>>
>>     Many thx,
>>     R.=C2=A0
>>
>>     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:xieji=
ngrong@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 R=
FC8200 text may be
>>         > modified in the future, the PSP may also need to change acco=
rdingly.
>>
>>         No, it violates Section 4 of RFC8200.=C2=A0 It's a pity that w=
e 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 dr=
aft),
>>         but anyone who involved the discussion should know the intent =
of this
>>         text intended to say (borrowing from Ron's text) "Extension he=
aders
>>         cannot be added to a packet after it has left the its source n=
ode and
>>         extension headers cannot be removed from a packet until it has=
 arrived
>>         at its ultimate destination".=C2=A0 It might look "an attempt =
of blocking
>>         an innovation by a small group of vocal fundamentalists", but =
if you
>>         see the responses without a bias, you'd notice that even some =
of those
>>         who seem neutral about the underlying SRv6 matter interpret th=
e text
>>         that way.
>>
>>         I'd also note that simply because PSP violates RFC8200 doesn't=

>>         immediately mean it (PSP) "needs to change".=C2=A0 It can upda=
te RFC8200 with
>>         explaining why it's necessary and justified.=C2=A0 That's what=
 I
>>         requested as you summarized:
>>
>>         > Jinmei: it should say it updates this part of RFC8200 and ex=
plain why it's justified.
>>
>>         And, since PSP at least wouldn't break PMTUD, I guess the upda=
te
>>         proposal will have much more chance to be accepted than a prop=
osal
>>         including EH insertion.=C2=A0 On the other hand, pretending th=
ere's no
>>         violation will certainly trigger many appeals and objections a=
t the
>>         IETF last call (I'll certainly object to it).=C2=A0 In the end=
, it can
>>         easily take much longer, or even fail, than formally claiming =
an
>>         update to RFC8200.
>>
>>         --
>>         JINMEI, Tatuya
>>
>>         _______________________________________________
>>         spring mailing list
>>         spring@ietf.org <mailto:spring@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/spring <https://urldefen=
se.com/v3/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!=
Qj4iGvIKXE0YABWYjk5PNMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3UdazBorQ$>
>>
>>     ------------------------------------------------------------------=
--
>>     IETF IPv6 working group mailing list
>>     ipv6@ietf.org <mailto:ipv6@ietf.org>
>>     Administrative Requests: https://urldefense.com/v3/__https://www.i=
etf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5PNMfr1ed=
PfPjJBED6VMnC3MxTiIYCqCc0y3X18TtwYw$ <https://urldefense.com/v3/__https:/=
/www..ietf.org/mailman/listinfo/ipv6__;!!NEt6yMaO-gk!Qj4iGvIKXE0YABWYjk5P=
NMfr1edPfPjJBED6VMnC3MxTiIYCqCc0y3X18TtwYw$>
>>     ------------------------------------------------------------------=
--
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

