Re: [DNSOP] moving forward on special use names

"John R Levine" <johnl@taugh.com> Fri, 16 September 2016 19:14 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 2141D12B2B9 for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 12:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=xdyzOvWr; dkim=pass (1536-bit key) header.d=taugh.com header.b=d2ZKimCi
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 los8x8_VJEvb for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 12:14:28 -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 30EB112B253 for <dnsop@ietf.org>; Fri, 16 Sep 2016 12:14:28 -0700 (PDT)
Received: (qmail 36467 invoked from network); 16 Sep 2016 19:14:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=8e72.57dc4490.k1609; bh=8yN/OmpIwA9XtOfjxw++supK/3sDJGVMD7HbGTzgj2U=; b=xdyzOvWrmY0y5zWjPgL+jq5pEFF9+28yQU7gyfEMY1Us8LFGcMNUiz7tb6SvHGmOg+p4tobasgBvYBh96LMV094DyfBmfLdOos0Fp6i8cUBuvQDaA0ldQYzMcXm6zI6ZY+V/kkWSG1n8zzYYZiAwoUb+EzhsJvIplHOnbP4iNoWWmVbcZZLicU4xKgWR0iD0ZxR4wWQ+zOJ2IiHHXioOeXjBos4TyDELFeh1jc8abqj2r/AmJxY/ty0BPCK4/Og9
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=8e72.57dc4490.k1609; bh=8yN/OmpIwA9XtOfjxw++supK/3sDJGVMD7HbGTzgj2U=; b=d2ZKimCiWFPsELh81AauO5vCnR/qzSYo42cNDZmTYdQuAAjMTQYX5JOZLysMP625c19Fe370LJU99MJp7eW7wd17ErR+MXKARAPtEv7+edz5yDxrjZgKAV7xsQZaPpWBM2uP0n4p7UtKlcyP1xPkLfA9FYI8BLl4306QN3RaailxVd+nSTIRyfUYYTyJ/r0ecfgvyBOX8fd3r/iV2r3hCa6Fxgi2FkY0i/1YKwhEcSUkie25esFjbZNwns0MhBiG
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 16 Sep 2016 19:14:24 -0000
Date: 16 Sep 2016 15:14:25 -0400
Message-ID: <alpine.OSX.2.11.1609161500500.90741@ary.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ted Lemon" <mellon@fugue.com>
In-Reply-To: <CAPt1N1krYizxBOjRjNQ8159ppp+LM5ZV9_QQn3cLX3T-okcndA@mail.gmail.com>
References: <CAPt1N1m1MbYhhnH6kp7saw8tFBoJ21=wO6dsVW8s-b-OSu+cNw@mail.gmail.com> <20160916184640.70688.qmail@ary.lan> <CAPt1N1krYizxBOjRjNQ8159ppp+LM5ZV9_QQn3cLX3T-okcndA@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/erZQQ4Akbhv00csiq_RCmjIYIl4>
Cc: dnsop WG <dnsop@ietf.org>
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 19:14:30 -0000

> Split horizon is another thing.   I'm talking about locally resolved zones
> (RFC 6303).

I see that as a kind of split horizon.  One of the problems with the toxic 
waste is that we don't know how much of it is from names that are supposed 
to be resolved locally but escaped (much of .corp I would guess) and how 
much is just mistakes (.belkin.)

R's,
John

>
> On Fri, Sep 16, 2016 at 2:46 PM, John Levine <johnl@taugh.com> wrote:
>
>> 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
>>>
>>> -=-=-=-=-=-
>>
>>
>>
>

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly