Re: [DNSOP] moving forward on special use names

"John Levine" <johnl@taugh.com> Fri, 16 September 2016 18:47 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A3112B293 for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 Fboz4GZbeAov for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:47:04 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5B6912B28B for <dnsop@ietf.org>; Fri, 16 Sep 2016 11:47:03 -0700 (PDT)
Received: (qmail 27175 invoked from network); 16 Sep 2016 18:47:00 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 16 Sep 2016 18:47:00 -0000
Date: 16 Sep 2016 18:46:40 -0000
Message-ID: <20160916184640.70688.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <CAPt1N1m1MbYhhnH6kp7saw8tFBoJ21=wO6dsVW8s-b-OSu+cNw@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_t8V3A-w4MCV223TU59WJIowrbQ>
Cc: mellon@fugue.com
Subject: Re: [DNSOP] moving forward on special use names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Sep 2016 18:47:05 -0000

In article <CAPt1N1m1MbYhhnH6kp7saw8tFBoJ21=wO6dsVW8s-b-OSu+cNw@mail.gmail.com> you write:
>Don't forget names resolved locally with the DNS Protocol, like
>1.1.168.192.in-addr.arpa.   A lot of the names you describe as "toxic
>waste" are likely resolved this way.

I suppose split horizon fits in there somewhere, but the toxic waste I was
thinking about is stuff like .corp and .belkin which leak out of random
old bits of hardware and software.

R's,
John



>
>On Fri, Sep 16, 2016 at 2:13 PM, John Levine <johnl@taugh.com> wrote:
>
>> >The drafts are:
>> >       https://datatracker.ietf.org/doc/draft-tldr-sutld-ps/
>> >       https://datatracker.ietf.org/doc/draft-adpkja-dnsop-
>> special-names-problem/
>>
>> Having read them both, neither one thrills me but I'd give the nod to
>> adpkja.  The "Internet Names" in tldr seems to me a bad idea, since
>> there are a lot of other names on the Internet such as URIs and handle
>> system names, and this is about domain names.
>>
>> It seems to me there are four kinds of names we have to worry about, and
>> neither draft calls them all out clearly:
>>
>> * Names resolved globally with the DNS protocol, i.e.
>>   ordinary DNS names
>>
>> * Names resolved globally with an agreed non-DNS protocol, e.g.
>>   .onion via ToR
>>
>> * Names resolved locally with an agreed non-DNS protocol, e.g,
>>   .local via mDNS
>>
>> * Names resolved locally with unknown protocols, e.g. .corp and
>>   .home, the toxic waste names
>>
>> R's,
>> John
>>
>>
>>
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>>
>
>-=-=-=-=-=-
>[Alternative: text/html]
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop
>
>-=-=-=-=-=-