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

Tom Herbert <tom@herbertland.com> Thu, 05 September 2019 14:18 UTC

Return-Path: <tom@herbertland.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 7EA8C1200E0 for <spring@ietfa.amsl.com>; Thu, 5 Sep 2019 07:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 3nSigxPgRC_1 for <spring@ietfa.amsl.com>; Thu, 5 Sep 2019 07:18:05 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 DE0BB1200F9 for <spring@ietf.org>; Thu, 5 Sep 2019 07:18:04 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id f19so2790148eds.12 for <spring@ietf.org>; Thu, 05 Sep 2019 07:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=E78aIfC4q3V/TdwltmQq1BCXnyZfyv7V3CwLeOS4BAU=; b=U8W73/oX7S0wififq8TJYUbrX7N9x3mkVgcMyzjYBQm1yHRQ4IZ+lJW4gW+nPgTqxp aQh7NEsg5Gqv58JPRCQ/cUyJVgSAj233sRvOnNWrqdSzRfuIfb63vJfuDuIFKuWxasx7 Rsjhya8PwDIu9x/Yg+u5hGi0HPdLf47nNzTb+HII7PTE6+nl/0juJn8bwTy4MI4XT6eu dizzLlIMJNN2EzQpxLk0ZdZv9w+cPYV8ZHub8jfVF4m23uxtNJiIxSac0OHa3siRsjys rTZ6FVOlObgZeb8g0iDePkihdVDnJVfAGIHid/p3FpgaSzdrHFRe1TNZefhb4DbjGq+a 6BPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=E78aIfC4q3V/TdwltmQq1BCXnyZfyv7V3CwLeOS4BAU=; b=hT06FpoYska6hXnnlf9sS6cZ1p9N7+go5pyrkLbY+TAOkr/EBbYMDDqsn5EojJYuCk sAUnUl9ZdgB47FYt299w0+9JU6as0pt1A0njiyL7McFv1nc+4/50KRneHCj2Kj9f5GC+ +NoCqRRenfrG8bKVKslYIqMuioPZG2dQTyhQtXNeNKTMxiReaaN0RZWgb3zlWgNN9wXz 9gvF+Ru81HqWt0OPSwzORevj0F51ZoyWVVMnPBw579bHpWBFAFz3Vy7OAxTj9ExzY9LL 6ZFcEeAdPvGNEJPEiVPoyhdVVLBIqgMjRKGWrh4UmRjYJUWEzcQvDCkDSrRHe4py/4iF o+rA==
X-Gm-Message-State: APjAAAWctxIngM/WJV8WSA2oXnXv+jrwQ3vP3ZtDM1vjua1CmTjVp1ZM Hxecd9sF3vVKaQxfaJpXILpDcLX8sdUstXxiQvIA+gZOdck=
X-Google-Smtp-Source: APXvYqzktKHBDH18JAK9YMgCEAjbpUN9r1x+fXyHSO0emXvARa11DvCadWjq+3UQgu6DAS32yD7WwGGStnizHg0mgkw=
X-Received: by 2002:a17:906:30d1:: with SMTP id b17mr3104431ejb.9.1567693083076; Thu, 05 Sep 2019 07:18:03 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR05MB54637FEAE1518F83977D274FAEB80@BYAPR05MB5463.namprd05.prod.outlook.com> <538732E2-915B-4952-A439-F4678FCC21B2@employees.org> <4c6b2456-db05-0771-5b98-bfd9f07b220b@si6networks.com> <34AB9F0F-614B-45C2-BD84-7DD53A1D5188@employees.org> <ea9557e5-9025-db78-8862-18454dd549c3@joelhalpern.com> <5200FFA0-E2F1-4491-8D06-0DC6BF87F77A@employees.org>
In-Reply-To: <5200FFA0-E2F1-4491-8D06-0DC6BF87F77A@employees.org>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 05 Sep 2019 07:17:51 -0700
Message-ID: <CALx6S35YHkKX1+_uKyJJOM18qL7a8kEMy+wmF3G2E_MAUt8jFQ@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Fernando Gont <fgont@si6networks.com>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/f38F5_d38LdknHPOb0OWp7OG9iQ>
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 14:18:08 -0000

On Thu, Sep 5, 2019 at 6:35 AM Ole Troan <otroan@employees.org> wrote:
>
> Joel,
>
> > Part of the reason we write restrictions and requirements into RFCs is so that we do not have to repeat the arguments.
> >
> > If the proponents of the insertion have arguments for why it is now okay, they need to make those arguments.  And they need to make sure that the discussion is taken to the relevant working groups.  The burden should not be on those who are asking that attention be paid to existing RFCs.
>
> As far as I know, but I'm trying to stay away from the actual proposals and argue this generally, no-one is proposing to update the RFC8200 header insertion text.
> What people are proposing are for specific domains. And given that, I believe people need to argue the technical merits of those specific proposals.

Ole,

I don't believe the requirements of RFC8200 were ever intended to be
conditional based on the runtime environment. Either it's IPv6 or it's
not. I would be opposed to bifurcating standard protocols so that they
work differently in the open Internet versus a limited domain.

> As opposed to throwing the "law book" around.

This is isn't just throwing the law book around. Consider that
extension header insertion was proposed in
draft-voyer-6man-extension-header-insertion and there was much
discussion on the list. There were a number of very specific arguments
articulated why this is not robust and how this can break other
protocols. I don't see that the proponents of haven't provided counter
arguments. So I believe that the current consensus is that EH
insertion is not allowed, but that 's not just because RFC8200 says so
but also because there are material reasons why it's a bad idea. This
doesn't preclude the possibility of the EH insertion could be accepted
some day, but I don't see how that can happen unless the arguments
against it are addressed.

Tom


>

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