Re: [spring] IPv6 EH-insertion (Re: Spirit and Letter of the Law (was: Question about SRv6 Insert function))

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 08 September 2019 11:54 UTC

Return-Path: <mcr@sandelman.ca>
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 2507812001E; Sun, 8 Sep 2019 04:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 J5pOi6_gnv_s; Sun, 8 Sep 2019 04:54:55 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78AB0120018; Sun, 8 Sep 2019 04:54:54 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [88.214.187.115]) by relay.sandelman.ca (Postfix) with ESMTPS id 800251F459; Sun, 8 Sep 2019 11:54:53 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 7FBFB2025; Sun, 8 Sep 2019 12:55:15 +0100 (WEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: spring <spring@ietf.org>, 6man <6man@ietf.org>, draft-ietf-spring-srv6-network-programming@ietf.org
In-reply-to: <357ceb44-5ef4-a5e6-4cb0-087792c9daf5@si6networks.com>
References: <BYAPR05MB54637FEAE1518F83977D274FAEB80@BYAPR05MB5463.namprd05.prod.outlook.com> <0d3df64e-d596-1cac-eb3d-e08a6e1151ea@si6networks.com> <HK0PR03MB3970EB9B1326CDD4609A6CB4FCBB0@HK0PR03MB3970.apcprd03.prod.outlook.com> <BL0PR05MB54580DA411A332701090B5A6AEBB0@BL0PR05MB5458.namprd05.prod.outlook.com> <66f1195d-3e71-71d8-9304-1b5e76211c5b@si6networks.com> <17262_1567694774_5D711FB6_17262_144_1_53C29892C857584299CBF5D05346208A48BFA9FB@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <C7C2E1C43D652C4E9E49FE7517C236CB026B769F@dggeml529-mbx.china.huawei.com> <357ceb44-5ef4-a5e6-4cb0-087792c9daf5@si6networks.com>
Comments: In-reply-to Fernando Gont <fgont@si6networks.com> message dated "Sat, 07 Sep 2019 05:54:36 +0300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 08 Sep 2019 12:55:15 +0100
Message-ID: <28835.1567943715@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/tXzM9wOLhaORucLo_CFCv-oSbAc>
Subject: Re: [spring] IPv6 EH-insertion (Re: Spirit and Letter of the Law (was: Question about SRv6 Insert function))
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: Sun, 08 Sep 2019 11:54:58 -0000

Fernando Gont <fgont@si6networks.com> wrote:
    >> 
    >> Why do these kind of arguments emerge right now instead of 5 years
    >> ago?  We left the “problem “ for 5 years? And suddenly we notice them?
    >> How interesting.

    > One possibility: All this kind of arguments did emerge a long time ago
    > -- NAmely, when working on rfc2460bis, which eventually became
    > RFC8200. As a results of the problems associated with EH-insertion,
    > there was IETF consensus to explicitly ban it in RFC8200. Maybe some
    > 6man'ers were not subscribed to the spring wg list, were quite
    > surprised to see documents relying on EH-insertion (one ins spring, and
    > another, indirectly, in lsr), and hence decided to comment.

I would suggest that the result was slightly different.

We decided in RFC8200 that EH-insertion by random devices for randomly
defined purposes was banned.

That if a device/operator needed to do that, that they ought to use IPIP
insertion. We failed to actually follow through with RFC8504 to make
it possible to actually use IPIP in a general case.

What I think that we wound up in RFC8200, and I think that it was
intentionally very subtly under-stated by the AD at the time, was that any
IETF Specification could in effect make any rule it wanted, and it
would be subject to IETF Last Call and IESG review.

So what we banned was EH-insertion by vendors or operators without
significant (standards-level) thought as to applicability.  We are now here,
we are supposed to be discussing if this use case, along with it's
applicability, warant a reasonable exception.

I have not followed the hundreds of messages in this thread, but I read a few.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-