[DNSOP] special names process & context Re: More complete review of draft-grothoff-iesg-special-use-p2p-names-01

Suzanne Woolf <suzworldwide@gmail.com> Sun, 05 January 2014 16:39 UTC

Return-Path: <suzworldwide@gmail.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 699951AEED6 for <dnsop@ietfa.amsl.com>; Sun, 5 Jan 2014 08:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 X7y0yMwNc8Jb for <dnsop@ietfa.amsl.com>; Sun, 5 Jan 2014 08:39:56 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 984881AEED7 for <dnsop@ietf.org>; Sun, 5 Jan 2014 08:39:56 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id ii20so2180685qab.1 for <dnsop@ietf.org>; Sun, 05 Jan 2014 08:39:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Lv/ZY8D9YmcevEC9wWVVmTxi1jeDfcX1CFS8zLDMS5M=; b=eXJ3H814QzmkT0b6L8TjNOGyepvVLpSPp24QJQV0DCeXlgBe9aoJBVZi5U6QiDzPXU 2IrrEb+d/szgHbBL8aK6QKryfxp1yaetO2M7UYqDZLcZPMUUUE7jPNQ3UZTlatlWpOzs +uyJ+r/9EHZ/wLFMetSjJ2YaxFilQvp7epADlg7hXr9fQlELopBcCFXFI7tTOhWvBT9Z C6fiEy3K1Txjc2iJTkvK9cC73hbKiH0Q4qk3K9D0ihenKSYhpRho8+54NuaHuOLLy4Kf EswZxJAfkH89Um0FTRQgbu6BXT0dRb//qtCCY+8Q9UbIFBOuJcIt4LAbf2Davhb9Yigk poqQ==
X-Received: by 10.224.16.80 with SMTP id n16mr171538757qaa.42.1388939988368; Sun, 05 Jan 2014 08:39:48 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id g10sm95425787qaf.9.2014.01.05.08.39.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 Jan 2014 08:39:47 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20131231000412.GV4291@mx1.yitter.info>
Date: Sun, 5 Jan 2014 11:39:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <27E859E9-0E94-4694-B931-B0C4D885D667@gmail.com>
References: <20131231000412.GV4291@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
Cc: christian@grothoff.org, hellekin@gnu.org, dnsop@ietf.org, wachs@net.in.tum.de, jacob@appelbaum.net
Subject: [DNSOP] special names process & context Re: More complete review of draft-grothoff-iesg-special-use-p2p-names-01
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: Sun, 05 Jan 2014 16:39:59 -0000

Hi,

(chair hat on, not sure it fits right quite yet….)

Thanks Andrew for the thorough review on this draft, and everyone for substantive followups.

To put the topic of this draft, and "special names" generally, into some context: 

The "special names" registry is established in RFC 6761, which specifies "standards action or IESG approval" as the threshold for adding names. It also specifies in some detail what an RFC justifying such registrations needs to cover. (Section 4, 'If it is determined that special handling of a name is required in order to implement some desired new functionality, then an IETF "Standards Action" or "IESG Approval" specification [RFC5226] MUST be published describing the new functionality.' See also the registry at http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml).

Accordingly, the outcome of a discussion of this draft, or any special names request, in DNSOP should be any advice or insight we have as DNS experts for the IESG. 
The WG has no specific role in the process except as we can help the IESG decide whether to approve this set of additions to the registry.

Ted Lemon has participated here in earlier discussion of this draft, and I hope other IESG members will also feel free to step in and speak for themselves on their concerns. But earlier discussion, here and elsewhere, suggests that the most helpful input would be along a couple of lines:

1. The primary concern is on the specifics of whether this draft complies with RFC 6761 adequately to allow DNS implementors and operators to treat the proposed names consistently and interoperably, without unacceptable side effects. 

2. It may also be useful to consider any concerns on the scalability or architectural implications of special names: Andrew's comments in his review on the "deep and extremely confusing path of mixing the domain name system and other namespaces," the possibility that such requests will not remain rare events, etc. This goes to the question of how high the barrier to approval for new special names should be, as the p2p draft is the first invocation of RFC 6761 since its publication and seems likely to be taken as precedent.


best,
Suzanne

Re:
On Dec 30, 2013, at 7:04 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> Dear colleagues,
> 
> I made some remarks in the earlier discussion of
> draft-grothoff-iesg-special-use-p2p-names-00.  In this message, I
> attempt to review draft-grothoff-iesg-special-use-p2p-names-01
> completely.  I hope these remarks are useful.
> 
> Overall
> =======
> 
> I remain extremely concerned that this effort represents another step
> along a deep and extremely confusing path of mixing the domain name
> system and other name spaces.  I think the IETF needs to figure out
> whether we're going to accept that, historically, we had multiple name
> spaces but that now we're going to have one big one; or whether we're
> going to continue pretending that every other name space doesn't end
> up wandering into the DNS anyway.  (If there are additional
> alternatives, I am unable to think of them.)  I think a pragmatic
> answer is to accept that, given the number of places we expose domain
> name slots, anything that uses a name is going to end up having to be
> somehow compatible with domain name slots.  But I think that is a
> wide-ranging discussion that almost certainly needs to be tackled
> #separately from the consideration of this particular draft.
>