RE: What is necessity for SRH, and other EH, insertion/removal?

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 07 December 2019 17:44 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDF5120807 for <ipv6@ietfa.amsl.com>; Sat, 7 Dec 2019 09:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 JNWY5gcEMceb for <ipv6@ietfa.amsl.com>; Sat, 7 Dec 2019 09:44:16 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59E1D120019 for <ipv6@ietf.org>; Sat, 7 Dec 2019 09:44:16 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id xB7HiEXG009315; Sat, 7 Dec 2019 17:44:14 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F12A72203A; Sat, 7 Dec 2019 17:44:13 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id DC36F22032; Sat, 7 Dec 2019 17:44:13 +0000 (GMT)
Received: from LAPTOPK7AS653V ([84.93.96.25]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id xB7HiDCo022833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 7 Dec 2019 17:44:13 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Tom Herbert' <tom@herbertland.com>, '6man' <ipv6@ietf.org>
References: <CALx6S34vG=L_5nw_FzxHBUy+7tbWH4dhOh8xodOfKf2oOdrarg@mail.gmail.com>
In-Reply-To: <CALx6S34vG=L_5nw_FzxHBUy+7tbWH4dhOh8xodOfKf2oOdrarg@mail.gmail.com>
Subject: RE: What is necessity for SRH, and other EH, insertion/removal?
Date: Sat, 07 Dec 2019 17:44:12 -0000
Organization: Old Dog Consulting
Message-ID: <04a501d5ad25$f0745a50$d15d0ef0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH6zk13jtmljzkCEJAzoFRws84P66dkrTUw
Content-Language: en-gb
X-Originating-IP: 84.93.96.25
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25090.001
X-TM-AS-Result: No--14.633-10.0-31-10
X-imss-scan-details: No--14.633-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25090.001
X-TMASE-Result: 10--14.633100-10.000000
X-TMASE-MatchedRID: oHOSwQSJZWg/j7VQtPldN3FPUrVDm6jtekMgTOQbVFtS4PwzM2cbygtq ZTGYNzread24pGsl3BqStbBktZGB8HTKTfMe0dCwIDrhNaNLPjric2JqBZEdqk8iLpubparm1Is 5GvhmGbzMnknh3Dve7BqxrT3szZT84OhwfKpL0fCHgJ7XaDMQWofQ3g3I7jVbabJxhiIFjJmhKc 8m2YMAUkv/YMn3fcUlIg6GCquy+lJj+8xSbQZgNC8s/ULwMh46GDp0A8FqdMQutoY2UtFqGL1lS 8OHT6mh5qduK012SP43R90AqkJ55NOw7n5gNTiExVtvemNbkyepvQ5ST6UgvQpCjqVELlwVf9YO 7YQzxxn1Ge7KOjoe/vV+zHR8UQf+2qjKAYV8LUbyxz2hgoG97UwmfzNxJlttWtcoU8Jtc7l4KXI IjHoLjiITAT8ebbYpzzU2+MLrDVSPl8suWHSuVJ4CIKY/Hg3AtOt1ofVlaoKKLuVdohwX9bDszp 3K5gqDjoczmuoPCq2x3hzBFxE+puZeOcfRYJ0Lgy0vNa1Ai1ukrSiwvmf7Uz3GzDKPGKpV
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pZ4cnNyP1Ww1b7TQ9kplDSxOqwo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2019 17:44:19 -0000

Hi Tom,

Thanks for breaking the thread and focussing us back on technical questions.

I can see some small value in PSP just as there is in MPLS PHP. This arises
in the combination of two circumstances:
- The destination node is not SRH-capable
- The source node and/or the node that determines the SR path is not aware
that the destination is not SRH-capable
In that case, the penultimate segment end point can know that its segment
neighbour end point is not SRH-capable and can perform PSP.

Whether this is ever the case with a central controller is unclear.

I'm not sure that this is a big use case, although MPLS PHP has proven to
have use cases as a form of "pop and go" especially when the next hop needs
to process the payload as "native".

There may be other use cases, and I'd be keen to learn about them.

The principle of keep things simple yet extensible would suggest that if
there are no substantial reasons to include a function it should be shelved
until there is a use case, but that this should be done in a way that allows
additions if necessary.

Cheers,
Adrian

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Tom Herbert
Sent: 07 December 2019 17:17
To: 6man <ipv6@ietf.org>
Subject: What is necessity for SRH, and other EH, insertion/removal?

Pulling this out into a separate thread. Pertinent questions are:

Why is extension header insertion and removal at necessary?

Why isn't the proposed alternative of IPIP encapsulation sufficient?
(where the encapsulating headers contain the extension headers that
would otherwise be inserted)

Please note, I'm asking for the technical justification of the
protocol design, saying that it's necessary because it's already being
deployed isn't useful in this regard.

Tom

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