Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient

Keith Moore <moore@network-heretics.com> Mon, 30 March 2015 18:37 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90ED91A6F38 for <v6ops@ietfa.amsl.com>; Mon, 30 Mar 2015 11:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level:
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 U-J6h5FEkui2 for <v6ops@ietfa.amsl.com>; Mon, 30 Mar 2015 11:37:35 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A8181A916F for <v6ops@ietf.org>; Mon, 30 Mar 2015 11:37:34 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 715CD20B7D for <v6ops@ietf.org>; Mon, 30 Mar 2015 14:37:29 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 30 Mar 2015 14:37:32 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=u6xSRQrOu2TdtRh 4sJ++tRWiqno=; b=jok7xP5lxj+rnxEh+TLsjBzWgJl4WL77aYSYMSctBFQc02E 0TG6Gnfa9TAu6Jcn2D2F56IkZfour/TBshTW/xf5q1QvMnbqhP1EEb1S3XP/QCdm WLwg9/x2p63hyocFzjvKewHFv4DwBO5hJlrhmv6RvUuRCfcv2gRzPR8TrJ0M=
X-Sasl-enc: nsWtmQvHnB0SIUIarBS+7nRtPb+ANTHGklLeQ2vz1awD 1427740652
Received: from [21.151.212.93] (unknown [66.87.152.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A530C00023; Mon, 30 Mar 2015 14:37:32 -0400 (EDT)
References: <CAD6AjGT-hG-uvRQvRosrZtfrf0Nb8ne9jy=tD9oh=5zNM42Xsg@mail.gmail.com> <alpine.DEB.2.02.1503200639340.20507@uplift.swm.pp.se> <20150320134204.32af9c67@echo.ms.redpill-linpro.com> <A0BB7AD89EA705449C486BDB5FDCBC7B28518DD8@OPE10MB06.tp.gk.corp.tepenet> <550F1F1F.3060703@cernet.edu.cn> <CAD6AjGSxk-Hrf_NBOjpV-jvraG+xSA4p1j-AO+FQFcVGzuf1Lg@mail.gmail.com> <CAKD1Yr3ywVy_00GYuw4Eq6cW_ZeL16bxpquaWWDMgSz44LagAg@mail.gmail.com> <CAD6AjGS-QMi+3oVGWDxnSMhEJH=VymwcF=PwKLdwFRxwHpp_-Q@mail.gmail.com> <CAKD1Yr3Fhnx3XaXouK57gupGOzodKGb0quhQxaf76NjWxSp3WA@mail.gmail.com> <CADhXe51MUB-czeCtpc63E0cHPpb_39Vv0o2Y57EVU2w_makP5Q@mail.gmail.com> <CAD6AjGTcKgK8W+VB1H5EQpHaYiKVYXqOz_2RS-w_CiTf9kL2CQ@mail.gmail.com> <CADhXe530+OVZrFZVaYh1-zoRDvJhUd0rf4sx6a2nO8SvKmm6zg@mail.gmail.com> <CAPi140PQ+TF0rED_bQPeS=Fj415qt0-zE2RdGnEL34PAzHyx6Q@mail.gmail.com> <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@mail.gmail.com> <CADhXe51TCqU2eMP4LS3DooZxQDAPD95OVJDXbiU7qvuvKCMq+w@mail.gmail.com> <5516C71F.3020606@network-heretics.com> <CADhXe51CRAT7t3kP=mcbKjXnZGQo7DGsaEvB25oWpvJJedYr_Q@mail.gmail.com>
In-Reply-To: <CADhXe51CRAT7t3kP=mcbKjXnZGQo7DGsaEvB25oWpvJJedYr_Q@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="Apple-Mail-E28701C9-5158-47E6-9F83-F5A26914DF6D"
Message-Id: <BE769B02-5D5D-4DCF-A267-A11047029658@network-heretics.com>
X-Mailer: iPhone Mail (12D508)
From: Keith Moore <moore@network-heretics.com>
Date: Mon, 30 Mar 2015 14:37:28 -0400
To: James Woodyatt <jhw@nestlabs.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/YheVNtFcWoABK_nPAz1mW0Zix9w>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 18:37:36 -0000

Of course, AppleTalk name/service discovery didn't have to work at Internet scale.  But maybe I should try to write an informational RFC on the myriad ways that DNS fails to be an adequate and reliable name lookup service.

Sent from my iPhone

> On Mar 30, 2015, at 2:20 PM, James Woodyatt <jhw@nestlabs.com> wrote:
> 
> Keith—​
> 
> I would have drawn that comparison to Appletalk not BITNET, except strangely enough— maybe not so strangely— I don't remember seeing a lot of Appletalk literal addresses littering source code the way you see IPv4 literals still so widely used today. Hmm, I wonder what lessons might be drawn from such a comparison.