Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

David Conrad <drc@virtualized.org> Fri, 08 May 2015 21:17 UTC

Return-Path: <drc@virtualized.org>
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 D7C2A1A0115 for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 14:17:13 -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, 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 0i1k0uyB3ikd for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 14:17:11 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) (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 659571A0102 for <dnsop@ietf.org>; Fri, 8 May 2015 14:17:11 -0700 (PDT)
Received: by pdbnk13 with SMTP id nk13so97391046pdb.0 for <dnsop@ietf.org>; Fri, 08 May 2015 14:17:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=vy/isuvHgYaTablZQd9gpcwbfMDU30niSUMAoeW8TZg=; b=h7q/nxgSwrmCbzu8ZeoMZJdPKp9vNbupKGbuWZEO5HUyV38jSh9iTPPreU4SF/kuo6 Hl8rJg85h1UhIc1NVFGknkJkufFb/3ZIrelVjp6ktgY6jdm4aq8K5uZDHUuGUHwnWd4f bQHgJFuEBVfLQXpga08hXitAuOWAbeRCIMAfdtMpOpvO6WLKin6jcswe2kYAdJwv+KLg 9w27Fb1UoKtnxvrQmuCZXKDaImkov/ehECD8moLmgCmtwJXZ/Qai9/wm0PtbbKvmhJpI q5Z9k4pvctg6ybKPL4wT463Xj5sl9SCKZulShAS2VErJdA1Z6m2785vdzVqYc7pcJJxY SBkQ==
X-Gm-Message-State: ALoCoQmX69rqIww0Xc6QRpYMtaGU9PynLhXz97NnPO2UEHOc8dcLZ672zkhBrxlSp23FyZemoT5y
X-Received: by 10.66.165.67 with SMTP id yw3mr1552146pab.95.1431119831089; Fri, 08 May 2015 14:17:11 -0700 (PDT)
Received: from [10.0.0.5] (c-50-184-24-209.hsd1.ca.comcast.net. [50.184.24.209]) by mx.google.com with ESMTPSA id by13sm6097684pdb.37.2015.05.08.14.17.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 May 2015 14:17:09 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5CB7BB83-1380-470A-AA64-243B45C08D4A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5b6
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20150508194223.55320.qmail@ary.lan>
Date: Fri, 08 May 2015 14:17:07 -0700
Message-Id: <7A92128C-F44C-45CE-B29E-83B699E50A04@virtualized.org>
References: <20150508194223.55320.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/nOTYlqKYUS7_5uErouF0j1W6HVc>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
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: Fri, 08 May 2015 21:17:14 -0000

John,

> On May 8, 2015, at 12:42 PM, John Levine <johnl@taugh.com> wrote:
>> The justification for removing home/corp/mail primarily appears to be "because they showed up
>> 'a lot' at the root servers". Without characterizing this a bit better, it seems to me it would
>> be trivial to set up situations to move pretty much any undelegated name to the "Special Names"
>> registry -- just fire up a few thousand zombies to query names in the TLD you want removed
>> using random source addresses.
> 
> Hmmn.  Is this a serious accusation,

Accusation?

> or is this just channelling the
> usual domainers whinging about their business plans?

Neither. It is an honest question as to how to objectively identify which non-delegated TLDs are receiving sufficient traffic as to justify never delegating them.  You know, sort of like how one would be able to justify a statement like:

>>> I'd probably put "lan" into the same group, no doubt to the dismay of the South American airline group.


But thanks for debasing the conversation.

> Does anyone seriously argue that those domains aren't widely used in
> private networks, and that nominally private DNS names leak all the time?


Depends on the name.  Why do you call out home/corp/mail? Should LAN be reserved or not?  What's your criteria?

Regards,
-drc