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

Keith Moore <moore@network-heretics.com> Fri, 28 February 2020 17:40 UTC

Return-Path: <moore@network-heretics.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 3076A3A0CA3 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2020 09:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 Lr3GFFf4pVlw for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2020 09:40:11 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DCED3A0B4E for <ietf@ietf.org>; Fri, 28 Feb 2020 09:40:11 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 1DF4C10C5; Fri, 28 Feb 2020 12:40:10 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 28 Feb 2020 12:40:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=vc4BTX 9FNiIxgf5K4I0MTaZfy4vd6Qz6dSWivNcx318=; b=gZ+bFEJml7ZLoyDPB8JEb6 HXC4/9+5SNmUSHvNtOCqdk+YmaApl8bID/RpJnbkzjJE69j5oCchuyMNuaNzp50Q 7v2jlMCgKDKFITkzI/X4vWmEI2JBkRf1WAjr2O0FM2DgcGzwEVSdvf4AcQozJtS/ 6MuEU5uS1xD9fFllCntN01sKBtZdhfPADBdDoTCbR6sC5fVXWnedM6RmTk2aLhM0 c7FA5g7nCkQxjfBBXETV2EA40qZ8umKjGxzI13cqptGKFm2VC/h0JL49+6morvaV 6SmTIoIGFtu+KYHTlo8QblsLZ4Xli4H+t4XFm9PhdLcPF+FsTha6sR/Q3ZoTKTIg ==
X-ME-Sender: <xms:eVBZXq4tHmIscT8LcRpOEK_9SfajWLW5WP8407XWCgkedvHVPX8fFA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleekgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecukfhppedutdekrddvvddurddukedtrdduhe enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohho rhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:eVBZXqcHlIoGFCCpNImOibQCFxCPja6lbzIPxZTUkfZKHDeS96FY3A> <xmx:eVBZXmp4ZFGOcpUUJ0QE6tNTEtX-S8r7j2mnYX9r_oRhEI4nSBcqCQ> <xmx:eVBZXpNi4-ZVPPBR6MlxDInkzc31g-vDcaqimuLQPphRQfUMcfoX8g> <xmx:eVBZXmRRL2W7uA-dDwkaZxqTXGIB3yPO56ObMTJFa2RzH0B0fJazmw>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id D99753060F09; Fri, 28 Feb 2020 12:40:08 -0500 (EST)
Subject: Re: [arch-d] [Int-area] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
To: ietf@ietf.org
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.com> <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.com> <CAMm+LwjxxTQmJMPxydMGC5GByHu2qkbd_+W1and=xOMhq2RV6g@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <72c048ee-db66-6281-f326-a5d2660c95fa@network-heretics.com>
Date: Fri, 28 Feb 2020 12:40:08 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjxxTQmJMPxydMGC5GByHu2qkbd_+W1and=xOMhq2RV6g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1B3FD89579C8652E45C3D626"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9nW6unU-WD0oOGo6rN_orGtQPAo>
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 17:40:19 -0000

On 2/28/20 12:19 PM, Phillip Hallam-Baker wrote:

> That is a TCP connection. Applications don't deal in TCP connections, 
> they deal in sockets.
>
> Its called abstraction. All that complexity belongs in a box that the 
> application programmer doesn't need to open.
>
> Now current practice is that people use the gethostbyname() call to do 
> DNS resolution and so they end up being unable to make use of DNS 
> properly. But that is a problem with the 40 year old legacy API which 
> can be changed or circumvented entirely
>
> RFC6763 is what the application layer should use.

Uh, no.  It's hopelessly fragile and completely inadequate.

Keith