IETF Logo Mail Archive

Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 05 December 2013 15:13 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 6FD951AE044 for <dnsop@ietfa.amsl.com>; Thu, 5 Dec 2013 07:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 F-2pbFjwCN1e for <dnsop@ietfa.amsl.com>; Thu, 5 Dec 2013 07:13:23 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9061AE032 for <dnsop@ietf.org>; Thu, 5 Dec 2013 07:13:23 -0800 (PST)
Received: from mx1.yitter.info (unknown [62.49.66.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id EBA0C8A031 for <dnsop@ietf.org>; Thu, 5 Dec 2013 15:13:18 +0000 (UTC)
Date: Thu, 05 Dec 2013 10:13:14 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20131205151313.GF28898@mx1.yitter.info>
References: <21D03162-81D1-494A-89A9-41BE89D28A0E@nominum.com> <BB7627E9-8D50-48E5-B809-64AE4D574271@virtualized.org> <20131203221006.GB5689@sources.org> <D3E446D0-F9ED-4671-A1C2-29A15D3DE010@virtualized.org> <20131204094449.GA5492@nic.fr> <9650BF6D-727B-4EF3-B357-7E4E2FDDE0AF@virtualized.org> <2614C613-1399-429D-856B-5E2C18DCA7A6@kumari.net> <20131205083609.GA5215@nic.fr> <52A07388.8060105@teamaol.com> <6BD0AE0A-C789-4F78-BF02-E0DDB5EC1B73@kumari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6BD0AE0A-C789-4F78-BF02-E0DDB5EC1B73@kumari.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]
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: Thu, 05 Dec 2013 15:13:24 -0000

On Thu, Dec 05, 2013 at 10:02:18AM -0500, Warren Kumari wrote:
> 
> Sure -- I don't think that the string itself is important, but rather, in the words of Connor MacLeod: There can be only one!
> 

The difficulty is in the claim that these names are already "out
there".  If that is in fact true -- that these are names that are
being handed around and potentially will get into protocol slots --
then as a matter of prudence we should put all the strings in the
special-use registry, and treat them all as .invalid is.

Best,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email