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

Fernando Gont <fernando@gont.com.ar> Thu, 05 September 2019 12:13 UTC

Return-Path: <fernando@gont.com.ar>
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 EC22E12011D; Thu, 5 Sep 2019 05:13:15 -0700 (PDT)
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=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 F0EXI7s89tLc; Thu, 5 Sep 2019 05:13:14 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C6A120288; Thu, 5 Sep 2019 05:13:13 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (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 793AA861CC; Thu, 5 Sep 2019 14:13:06 +0200 (CEST)
To: Ole Troan <otroan@employees.org>, Ron Bonica <rbonica@juniper.net>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
References: <BYAPR05MB54637FEAE1518F83977D274FAEB80@BYAPR05MB5463.namprd05.prod.outlook.com> <538732E2-915B-4952-A439-F4678FCC21B2@employees.org>
From: Fernando Gont <fernando@gont.com.ar>
Openpgp: preference=signencrypt
Message-ID: <8731b9ff-6224-eb86-6bf0-6251e6e30658@gont.com.ar>
Date: Thu, 05 Sep 2019 15:12:59 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <538732E2-915B-4952-A439-F4678FCC21B2@employees.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/lMvCp-X49HUwlPdLYG-6gYgmWd4>
Subject: Re: [spring] 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: Thu, 05 Sep 2019 12:13:22 -0000

On 5/9/19 11:18, Ole Troan wrote:
[...]
> 
> Let me quote Tony Li's response to Fernando's escalation email to the architecture list:
> 
> "The fact of the matter is that the IETF is completely helpless to prevent such things. 
> True, it can block standardization, but if the market wants it, the market will drive it
> and all that the IETF does is to make itself irrelevant to the process."

Even doing SRv6 does not need to imply doing EH insertion.

For instance, I just re-read
draft-voyer-6man-extension-header-insertion, and there's no comment
whatsoever why they don't address the same issues with encapsulation.




> My suggestion to Fernando was to argue the issues on technical merit.

The ietf consensus on this topic resulted from technical merit.

I don't think it's productive or even fair to simply ignore such
discussions and consensus, and ignore standards at will.

If you don't like the standard, make your case why you think it should
be updated, and work on it. The onus is on you to change the standard,
not on the standard to remain "as is".


> Can you please explain why you don't do that?
> 
> - Does it break end to end transparency?

Is IPv6 an end-to-end protocol if you allow EH-insertion in the middle
of a network?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1