IETF Logo Mail Archive

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

David Conrad <drc@virtualized.org> Fri, 06 December 2013 15:33 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 9FA6B1ADEB7 for <dnsop@ietfa.amsl.com>; Fri, 6 Dec 2013 07:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 N8y7wlWmn52G for <dnsop@ietfa.amsl.com>; Fri, 6 Dec 2013 07:33:25 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 016481AC863 for <dnsop@ietf.org>; Fri, 6 Dec 2013 07:33:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id AF27284CEF; Fri, 6 Dec 2013 10:33:20 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 25345-02; Fri, 6 Dec 2013 10:33:20 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 91D0A848F1; Fri, 6 Dec 2013 10:33:19 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_B420D2F6-1487-44B5-8A51-F79CD410C9E4"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20131206094140.GB8309@nic.fr>
Date: Fri, 06 Dec 2013 07:33:14 -0800
Message-Id: <34A02CD2-F620-447F-954E-7F7CA6E18BCC@virtualized.org>
References: <6DBBC8339C394DBDAE4FE1F764E02A8D@hopcount.ca> <20131203170825.GA17211@nic.fr> <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> <alpine.LSU.2.00.1312041229560.8824@hermes-2.csi.cam.ac.uk> <6A3B7F5A-238C-45BC-AFF9-38F3213A7322@virtualized.org> <20131205084044.GB5215@nic.fr> <98F4DF09-2C6C-4FE2-A020-D6CDD2741739@virtualized.org> <20131206094140.GB8309@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1822)
Cc: dnsop WG <dnsop@ietf.org>
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: Fri, 06 Dec 2013 15:33:26 -0000

Stephane,

On Dec 6, 2013, at 1:41 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>> With the proliferation of new TLDs, how is anyone supposed to know
>> if a TLD is a real TLD and not some pseudo-domain that looks like a
>> TLD but isn't really 
> I disagree with the use of depreciative words like "pseudo-TLD".

I intentionally used the word from RFC 6761, section 4:

"  The specification MUST state how implementations determine that the
   special handling is required for any given name.  This is typically
   done by stating that any fully qualified domain name ending in a
   certain suffix (i.e., falling within a specified parent *pseudo-
   domain*) will receive the special behaviour. [...]"

(emphasis added)

I'll observe that changing what we call it does not address the concern.

Regards,
-drc

v2.23.0 | Report a Bug | By Email