IETF Logo Mail Archive

Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 04 February 2014 08:52 UTC

Return-Path: <bortzmeyer@nic.fr>
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 7E9CD1A03BF for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535] 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 eXwzySYnqLRP for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:52:05 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id F07281A039E for <dnsop@ietf.org>; Tue, 4 Feb 2014 00:52:04 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 72F5E280547; Tue, 4 Feb 2014 09:52:04 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 6E77E28052C; Tue, 4 Feb 2014 09:52:04 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 6BBA3960002; Tue, 4 Feb 2014 09:51:34 +0100 (CET)
Date: Tue, 04 Feb 2014 09:51:34 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: jonne.soininen@broadcom.com
Message-ID: <20140204085134.GC17756@nic.fr>
References: <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info> <CF160FB8.1983E7%jonne.soininen@renesasmobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CF160FB8.1983E7%jonne.soininen@renesasmobile.com>
X-Operating-System: Debian GNU/Linux 7.3
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-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: Tue, 04 Feb 2014 08:52:06 -0000

On Tue, Feb 04, 2014 at 01:45:11AM +0000,
 jonne.soininen@broadcom.com <jonne.soininen@broadcom.com> wrote 
 a message of 88 lines which said:

> They are not DNS and not even specified in the IETF. They have taken
> a design choice where they look like DNS

No, that's not a correct description. These proposals use domain names
(not things that "look like" domain names). Domain names are *older*
than the DNS (see RFC 810 and many others). They can be resolved by
several protocols (DNS, Bonjour, /etc/hosts, LDAP, whatever). It is
perfectly sensible to use domain names for new protocols.

> you want a TLD you go to ICANN.  Regardless of what people think of
> that process, this is the process we have created already a long
> time ago

If "we" is the US governement, the sentence is true. Otherwise, no, I
had no part in the ICANN creation. I remember a discussion with Stuart
Cheshire where he explained that IETF, not ICANN, created the entire
name space, since it created the rules, and therefore has rights above
those of ICANN.

v2.23.0 | Report a Bug | By Email