Re: Single DNS root

John C Klensin <john-ietf@jck.com> Thu, 01 September 2005 19:10 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAuSO-0008Bq-Mn; Thu, 01 Sep 2005 15:10:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAuSM-0008AP-Od for ietf@megatron.ietf.org; Thu, 01 Sep 2005 15:10:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24076 for <ietf@ietf.org>; Thu, 1 Sep 2005 15:10:35 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAuUN-0001Rm-64 for ietf@ietf.org; Thu, 01 Sep 2005 15:12:43 -0400
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1EAuS8-000DN9-Qz; Thu, 01 Sep 2005 15:10:24 -0400
Date: Thu, 01 Sep 2005 15:10:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>, Harald Tveit Alvestrand <harald@alvestrand.no>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <F2D9A9939B5D0CD4B290F851@scan.jck.com>
In-Reply-To: <6.2.3.4.2.20050901012427.04c6e6a0@mail.jefsey.com>
References: <p0620071abf3a39e7c365@[172.17.33.112]> <87k6i3rnwc.fsf@windlord.stanford.edu> <431577A3.5080902@peter-dambier.de> <086e5646420e7121920d06ad4ac4287a@karoshi.com> <C2D94E2C-6180-4AB7-B44F-CEFF8646F25B@let.de> <C9F748BE2C84DBBDC3C48190@B50854F0A9192E8EC6CDA126> <6.2.3.4.2.20050901012427.04c6e6a0@mail.jefsey.com>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: Single DNS root
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


--On Thursday, 01 September, 2005 02:49 +0200 "JFC (Jefsey)
Morfin" <jefsey@jefsey.com> wrote:

> Dear Harald and Paul,
> May be time to stop 3683ing this issue. Major moves in the
> naming area are probable in the year to come (PADs - shared
> root under UN - National TLDs, CENTR move.); while an ICANN
> request of update of RFC 2826 stays unanswered or opposed for
> four years.

Jefsey,

Just to understand the relationship between your reality and
mine, what "ICANN request for an update of RFC 2826" are you
talking about?  Certainly there was some discussion within ICANN
circles about whether 2826 meant what it said.  But, of course,
anyone can say just about anything in an ICANN meeting or on an
ICANN mailing list as long as it is consistent with the
organization's norms for appropriate behavior (just as with
Internet Drafts and IETF mailing lists).  Such a comment is not
equivalent to an "ICANN request".  

I am aware of one informal inquiry from an ICANN staff member as
to whether the IAB was likely to have more to say on the
subject.  The informal response (from one of the editors of 2826
but with general sympathy from the IAB) was, if I recall,
approximately "which part of 'unique' are you having trouble
understanding?".

At least in my memory and reality, there has been no "ICANN
request" for an update, much less one that has been "unanswered
or opposed".

Could you explain what you are talking about and identify the
request to which you are referring? 

Or stop this, lest the claim about such a request become part of
Harald's 3683 case?

   john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf