IETF Logo Mail Archive

Re: [dnsext] RFC 2142 and "organization's top level domain"

Florian Weimer <fweimer@bfk.de> Tue, 14 September 2010 14:13 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D1D23A697A; Tue, 14 Sep 2010 07:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.171
X-Spam-Level:
X-Spam-Status: No, score=-0.171 tagged_above=-999 required=5 tests=[AWL=2.078, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5QJIwRsD1nd; Tue, 14 Sep 2010 07:13:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 83F1F3A69B7; Tue, 14 Sep 2010 07:13:19 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OvWAh-000HDF-Cm for namedroppers-data0@psg.com; Tue, 14 Sep 2010 14:07:43 +0000
Received: from mx01.bfk.de ([193.227.124.2]) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <fweimer@bfk.de>) id 1OvWAe-000HCz-Oo for namedroppers@ops.ietf.org; Tue, 14 Sep 2010 14:07:40 +0000
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1OvWAa-0000yk-5E; Tue, 14 Sep 2010 14:07:36 +0000
Received: by bfk.de with local id 1OvWAZ-00024S-V5; Tue, 14 Sep 2010 14:07:35 +0000
To: dcrocker@bbiw.net
Cc: namedroppers@ops.ietf.org
Subject: Re: [dnsext] RFC 2142 and "organization's top level domain"
References: <4C8AD1C5.1050601@dcrocker.net> <AANLkTimxYjPKkZ0rWk983y=+fBDd60X+o7WtLMn292w6@mail.gmail.com> <4C8AF3BE.3020009@dcrocker.net>
From: Florian Weimer <fweimer@bfk.de>
Date: Tue, 14 Sep 2010 14:07:35 +0000
In-Reply-To: <4C8AF3BE.3020009@dcrocker.net> (Dave CROCKER's message of "Fri\, 10 Sep 2010 20\:13\:02 -0700")
Message-ID: <82vd68e7vc.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

* Dave CROCKER:

> 1. The requirement is for a term that can be widely used, and
> particularly by regular (non-geek) users.  This imposes a significant
> burden in making the term be relatively natural and friendly for
> everyday use by everyday people.

"domain" or "domain name", without further qualification.  In cases
where this leads to ambiguities, there are difficulties which could
only be resolved by formalistic approaches anyway.

> 2. The apps discussion explored "registered" and "delegated" before
> getting to "principal".  About the first two, it was decided that the
> use of a DNS term of art in a way that might not be sufficiently
> accurate or precise would be ill-advised.

It's also inappropriate because authoritaty over the name may not have
been delegated to the organization, or the name may not hot have been
registered, but assigned.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

v2.23.0 | Report a Bug | By Email