Re: [DNSOP] moving forward on special use names

Ted Lemon <mellon@fugue.com> Fri, 16 September 2016 18:55 UTC

Return-Path: <mellon@fugue.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 CBEF912B2DC for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 k33ZZneF_-HR for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:55:29 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C0FB12B28B for <dnsop@ietf.org>; Fri, 16 Sep 2016 11:55:28 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id l131so67906422lfl.2 for <dnsop@ietf.org>; Fri, 16 Sep 2016 11:55:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WrVnko5r+qPoxGSfna9P7jucrCLvP/hdS9uMmI+MHAI=; b=wYxQAnmsLN11VUW8TmAf5Vj9pxW9RCPZZ4lonSCfMz0xJg2zoGJZ8OTvJqrSTwsn9O dwfJWojhqu5AsN9gP+DFxQfrk61dZB3AynW/lOEPzncSlhwlGDwyvR+nbhnNpveZU0M0 qVNCdIvHp1HfUbd9cK60U+hLkJaC8MYiBCmYuRbw7AH9CtFoCzncA82ratCgmdfZLC0c N4FMNel+ME6xBfQiCCHCpZvrrc3zEv3qDasFVv0/MNLF+gvqwbax1pWbWyTf4H/bxjAC WH5dg1ouCvOjrJuSsdAcqiurNBbYJzem3wle+rjahCNvc1QqWC/BE2AbxcuRPo7r5mFR L9sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WrVnko5r+qPoxGSfna9P7jucrCLvP/hdS9uMmI+MHAI=; b=SyyLPBECjCd6cnvztwOb0jpXPkRt/0mQzWkbOyJgV7s8dMI1LoTV8lg0Gi8EBojjN2 +yq2RtaZ/DOzkegVKQeLpTCi1lBW3FLS1vNLFl4thMoPKW5az3DKLHAC2mDJ3iViStYm 7q8UTrKnFmjI787KT6j1jl8a4XYj6PyjxZYOL1s+KECIWX3Qlb8HC2Fk0G9iNyn+1HHa 2jlvWgDk2JaXN5QGcXm7FKGjHywm8jQfh/r83UD8DwBvpyijlAXKA8YEmgbOt8mE0n89 sLrbwOubsgJmvRoJDoh/6+Ibm/H5HMJ61ReqSzDYVLj1Kfa3glaKh5pNXR1cJmu/DKX4 8Kvg==
X-Gm-Message-State: AE9vXwMQjyU86T7aE706e9e5P73VbJ8SqZwkdP45qybiLc7tsyQWEWAGUsZ21NdUxXUwgBTbUBWpeAeaH9EVvQ==
X-Received: by 10.25.42.2 with SMTP id q2mr6898240lfq.5.1474052126654; Fri, 16 Sep 2016 11:55:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.93 with HTTP; Fri, 16 Sep 2016 11:54:46 -0700 (PDT)
In-Reply-To: <20160916184640.70688.qmail@ary.lan>
References: <CAPt1N1m1MbYhhnH6kp7saw8tFBoJ21=wO6dsVW8s-b-OSu+cNw@mail.gmail.com> <20160916184640.70688.qmail@ary.lan>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 16 Sep 2016 14:54:46 -0400
Message-ID: <CAPt1N1krYizxBOjRjNQ8159ppp+LM5ZV9_QQn3cLX3T-okcndA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a1140245c63d9c0053ca4818c
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qixg2u-KKgaJO_66rOk1u0o55Kg>
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 18:55:31 -0000

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

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
> >
> >-=-=-=-=-=-
>
>
>