Re: [DNSOP] moving forward on special use names

Ted Lemon <mellon@fugue.com> Fri, 16 September 2016 18:42 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 59ECB12B293 for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:42:16 -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 K8vj_yoTYVub for <dnsop@ietfa.amsl.com>; Fri, 16 Sep 2016 11:42:14 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 F256B12B286 for <dnsop@ietf.org>; Fri, 16 Sep 2016 11:42:11 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id l131so67699368lfl.2 for <dnsop@ietf.org>; Fri, 16 Sep 2016 11:42:11 -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=BKjK7OynzjzjZtkESd+j2DjP07MfZh0LJzGRx517Rjc=; b=CKhFmYfbmu/YzBNi6VZWQbZqEtRgqy01KeytjGMwTrFht4VUrBGrLggzLeujUQUBmf Qg7F3KLjX3jbzXcaZzgAELom8hxT4qmIzz35l+HzC9SKz7iE3LcMUcsYzflELI0FGlX6 MByBdSjUXDPvguN/gvQDnGJN+eJNM8NjMdiW1GmtobFAl0/jL3O2GvkvIyxLG5bzwbno k5irdNfvdTB4BVB6tJqsB7KPrsQE1K2MDzY/A0pu2Mh3lnjzTLlhREEuhNvkvm/dtvnQ kl1ZMzwnrkZqCp+Vghsi4SA6Td+JxPGJpaDc6JITNbhX3M+7g/N8F+qMrm7fpK30Ivnd jPmw==
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=BKjK7OynzjzjZtkESd+j2DjP07MfZh0LJzGRx517Rjc=; b=ZK++Fz/PabKpuwhl5uvdxnPOm5URghn6l/EwINY9QOWX/qAM+3/Htv2mlxVpQxwvM0 WHwWlyd6BfQINQRP/VASdaFUp0S7wWnE+o3POlgYFHOM7xYmmYEGAfzq11+Q9l1xvN+M YtMozbDNINEB+33THh/3BSvNHG4Cxfp/51/Y0qu2XoQGPZUJOD5c5K3no657FzH0KzAH hBYiKyhW2o/xvEszQRSkUKr90eae/jPBd9kpQO3OXm9AIgbf1ZoQc5Wu+GQ5iUWwenRF 3JkJPJ17eETREMeAtTvE2l1n7ZuaARoRpBvk/vYzcG90OsIVB+u3NrP+0r1842Nr7y83 eELg==
X-Gm-Message-State: AE9vXwM7nuNpzkTEtlRjDcSu9tWJhsAQ/HwGfgEFO3IiBaD8cNRShvIiiT/bNnBqabjcSeJy87PK3o7C61BkdQ==
X-Received: by 10.46.5.202 with SMTP id 193mr6533778ljf.13.1474051330058; Fri, 16 Sep 2016 11:42:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.93 with HTTP; Fri, 16 Sep 2016 11:41:29 -0700 (PDT)
In-Reply-To: <20160916181356.70566.qmail@ary.lan>
References: <D60BBDEF-3C13-44CB-A0D9-DEA98F5297F5@gmail.com> <20160916181356.70566.qmail@ary.lan>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 16 Sep 2016 14:41:29 -0400
Message-ID: <CAPt1N1m1MbYhhnH6kp7saw8tFBoJ21=wO6dsVW8s-b-OSu+cNw@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a114a7370e8bcae053ca45171
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ql0FdQNlk8FnEy0Hc66D2R-bjxo>
Cc: dnsop WG <dnsop@ietf.org>, Suzanne Woolf <suzworldwide@gmail.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:42:16 -0000

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.

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
>