Re: [spring] PSP and a logical application of RFC8200

Fernando Gont <fgont@si6networks.com> Mon, 02 March 2020 20:46 UTC

Return-Path: <fgont@si6networks.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 0EE953A111B; Mon, 2 Mar 2020 12:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 RVbQBc0k_YsO; Mon, 2 Mar 2020 12:46:22 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0B73A1124; Mon, 2 Mar 2020 12:46:21 -0800 (PST)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 604B8808C6; Mon, 2 Mar 2020 21:46:17 +0100 (CET)
To: "Pablo Camarillo (pcamaril)" <pcamaril=40cisco.com@dmarc.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "Darren Dukes (ddukes)" <ddukes=40cisco.com@dmarc.ietf.org>, 6man WG <ipv6@ietf.org>, SPRING WG List <spring@ietf.org>
References: <39544C17-1AD0-412E-A8BD-E17376537FCF@cisco.com> <bf9d68e6-cbae-2b19-11e0-1e452f0bf654@gmail.com> <FD806998-8218-4C70-B383-332C5F934A73@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <cd7cbeef-d502-20d8-fdd6-ba8473acb6fd@si6networks.com>
Date: Mon, 02 Mar 2020 17:45:22 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <FD806998-8218-4C70-B383-332C5F934A73@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/szsqpqSHuzncmNZEZgSo375qsUw>
Subject: Re: [spring] PSP and a logical application of RFC8200
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: Mon, 02 Mar 2020 20:46:23 -0000

On 2/3/20 17:02, Pablo Camarillo (pcamaril) wrote:
> Brian,
> 
> The PSP pseudocode is presented as a modification to the End pseudocode starting at line S14 of such.
> Please go through the PSP pseudocode in conjunction with the End pseudocode (Section 4.1).
> You will see that the ingress state of the packet is (Segments Left == 1 and Destination Address == the PSP node's address).

You are also changing the semantics of routing headers: if you prcessed 
the RH when Segments Left == N, you don't get to decrement SegmentsLeft 
and process the routing header again.

So, again, you should be updating RFC8200, and probably even the 
segment-routing-header I-D.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492