Re: [arch-d] [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)

John C Klensin <john-ietf@jck.com> Fri, 28 February 2020 22:12 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C7B3A1EE3 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2020 14:12:10 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_NONE=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 Pcz8PKNYT0KL for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2020 14:12:09 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F733A0C6C for <ietf@ietf.org>; Fri, 28 Feb 2020 14:12:08 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1j7nrY-0002yR-MA; Fri, 28 Feb 2020 17:12:04 -0500
Date: Fri, 28 Feb 2020 17:11:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Keith Moore <moore@network-heretics.com>
cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: [arch-d] [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
Message-ID: <5C60C807CE70E1ECC1BAB1D1@PSB>
In-Reply-To: <CAMm+LwjpOd5AB0_HYSYA7Ma-WeBhAv_XL9KLP6jiMSGqv9a5eQ@mail.gmail.com>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <CALx6S36wN7VEi_rxLC1ETcTvkGaPhs20KhQrGWAGGTrCL5OT+g@mail.gmail.com> <CAMm+Lwg+4xMv=EKLfvmZMCgrQz31+38Fv0bYKeJ0fTB5vbXiaw@mail.gmail.c om> <8d3e7b714666db00e0c05a2e06959da6@strayalpha.com> <CAMm+LwjYeSTro_TJujtRPDfVKtVMg7JbDL6A5V3Tj447c2E7nA@mail.gmail.com> <74763844-FA56-43DC-981E-E366E2C24758@strayalpha.com> <CAMm+LwjeWXUmOEzvbUhrG1H8OMqG9EhcF3TzdZBA61LnySSPqw@mail.gmail.com> <CALx6S35ko4zfCWwtR+LTKR6NdH86pVx7E-JoF0Cf4RVZOSJtkA@mail.gmail.c om> <CAMm+LwjxxTQmJMPxydMGC5GByHu2qkbd_+W1and=xOMhq2RV6g@mail.gmail.com> <CALx6S34ikDKdKeEfCJQF+ZGdNorsXZHRL=8u8bXdZ1NRpaLmvA@mail.gmail.c om> <ce5ac3bd-c5e3-28a5-e4ec-b7c2432783f0@network-heretics.com> <CAMm+LwjpOd5AB0_HYSYA7Ma-WeBhAv_XL9KLP6jiMSGqv9a5eQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_PTTUP1ZhzJ_4GWTZcSydG-mHH4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 22:12:11 -0000

I've been trying to stay out of this, but...

--On Friday, February 28, 2020 13:58 -0500 Phillip Hallam-Baker
<phill@hallambaker.com> wrote:

>...
> I have given the application layer view of the transport layer
> and below. I really don't care if you think we are doing it
> wrong, that is how we is going to continue to do it.

You are entitled to your opinion and what you have given is
certainly an "application layer view", but some of us who have
been doing applications and application-layer design and
development for a very long time have a different view both of
the transport layer and about the important characteristics of
the Internet design.  Now you may feel that we are wrong,
hopelessly out of date, or both, but that still does not turn
your opinion into _the_ application layer view.

Similar comments apply to several of the other statements you've
made in the last few days.  Correctly or incorrectly, many of us
see some of the issues for which you apparently have "everyone
who disagrees is wrong" positions as involving complex tradeoffs
for which the issue is finding the right balance (either
generally or to match a particular situation) rather than one of
absolutes.  Keith's comment about practices that might have many
advantages but that also result in single points of failure may
be a particularly relevant example.

>...

best,
   john