Re: [DNSOP] *.DNS metaTLD [ref: additional special names]

Warren Kumari <warren@kumari.net> Wed, 05 March 2014 15:22 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7431A014F for <dnsop@ietfa.amsl.com>; Wed, 5 Mar 2014 07:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 U70JrSWRvMZY for <dnsop@ietfa.amsl.com>; Wed, 5 Mar 2014 07:22:22 -0800 (PST)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id ED6C41A00DF for <dnsop@ietf.org>; Wed, 5 Mar 2014 07:22:21 -0800 (PST)
Received: by mail-wg0-f50.google.com with SMTP id x13so1420774wgg.9 for <dnsop@ietf.org>; Wed, 05 Mar 2014 07:22:17 -0800 (PST)
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:date :message-id:subject:from:to:cc:content-type; bh=WQCqvyucVP2jUWb0+YtTLJFz72cZl9yECFM7qnGTSJk=; b=c702qpJLvpIicFb06Lj4LNQ7zuNLpET/GYD+nhdeXl84pFH30CA4PAlwHeHPCg+g+5 GjO1HwnI/gITWsXG9YrrjiJsF4rA31und7xkeJZzN44JrtBFLCxGwSfTjItsuK5TCCsX VjMoJ5XK4j+r0lY6NdCRyslEK6joFYVwM5KfLkQZWw9FInBd/pr3cXI8cYEzVWaJ0MQl 6dqeVab8JHoIS07CA3+jpasJGoCh11X542OLJAT08go1yoAqvj4UchWXZX9FJ1R/mlaw IbyPmj3hD1TOFFrgXmC3o4Y4t3/yIUHZZhxDgeNQkP4o5JHeU5oCPzDsTAvLMENTEFrm AG2w==
X-Gm-Message-State: ALoCoQkSs05ty0WdZZKn9T2KRQKz1OmfNolyqyJm/JQfkUQIxTQlCxuoyCKLPS3SVbzgepa4RTJ3
MIME-Version: 1.0
X-Received: by 10.195.13.103 with SMTP id ex7mr1815936wjd.3.1394032937569; Wed, 05 Mar 2014 07:22:17 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Wed, 5 Mar 2014 07:22:17 -0800 (PST)
X-Originating-IP: [2001:67c:370:0:d51f:111c:ee4e:cc9c]
In-Reply-To: <2CA4A531-5CBB-4AEC-B382-712352FD1CF5@hopcount.ca>
References: <F88E53A6-A9CC-4F44-A986-AEB8F02EEFA1@okturtles.com> <7923940A-298A-49A2-8153-4777C95DDA77@hopcount.ca> <20140302230243.GA17774@laperouse.bortzmeyer.org> <FDBDECCE-35BE-48A8-B3ED-79ED5E89D633@hopcount.ca> <A73B4140-2E17-4081-B232-B2FA5174E134@nominum.com> <2CA4A531-5CBB-4AEC-B382-712352FD1CF5@hopcount.ca>
Date: Wed, 5 Mar 2014 15:22:17 +0000
Message-ID: <CAHw9_iK1ygCESpyY82Fa77kjmegX5S=i-CP0yUm6EZwct17ZYQ@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Joe Abley <jabley@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/eqLX2TkNcx6_BDY0R1XnpoQIQfU
Cc: dnsop <dnsop@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, okTurtles <hi@okturtles.com>
Subject: Re: [DNSOP] *.DNS metaTLD [ref: additional special names]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 05 Mar 2014 15:22:24 -0000

On Mon, Mar 3, 2014 at 1:20 PM, Joe Abley <jabley@hopcount.ca> wrote:
>
> On 3 Mar 2014, at 13:12, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>
>> On Mar 3, 2014, at 1:09 PM, Joe Abley <jabley@hopcount.ca> wrote:
>>> I suggest that it's entirely plausible for someone to choose a DNS-namespace anchor for their non-DNS namespace that is as stable as they want, depending on their needs.
>>
>> This is clearly not the case for an open protocol spec, though, since there is no one entity that could be responsible for maintaining the registration.
>
> Certainly there could be cases where that is true. I can't think of an example from the candidates we've identified in this (and other threads) to date, though.
>
> (e.g. tor -> eff.org; dns -> okturtles.com).
>

because I don't want my leaked query for www.nakedfurries.foo to hit
the wimble.example.com nameservers? Even if I currently trust them not
to be logging that.

Putting .foo under .alt and making it a locally served zone (return
NXDOMAIN for all queries) means that my leaked queries only hit my
local resursive. And not everyone's leaked queries get aggregated
somewhere. The ALT doc also suggests that stubs could drop queries,
and then they wouldn't even hit the recursive ( I suspect that this is
not likely, but...)

W



> There's inevitably *someone* who needs to take a lead on coordinating any codebase, if the codebase is to produce anything useful. I'm suggesting that that person could easily register a domain.
>
>
> Joe
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop