Re: 2606bis

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Thu, 20 October 2005 00:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESOPD-0001IC-Oq; Wed, 19 Oct 2005 20:35:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESOPA-0001Cn-3i for ietf@megatron.ietf.org; Wed, 19 Oct 2005 20:35:36 -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 UAA28833 for <ietf@ietf.org>; Wed, 19 Oct 2005 20:35:26 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESOax-0001Oj-2P for ietf@ietf.org; Wed, 19 Oct 2005 20:47:50 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1ESOP2-00088c-HC; Wed, 19 Oct 2005 17:35:29 -0700
Message-Id: <6.2.3.4.2.20051020020904.04e1a040@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Thu, 20 Oct 2005 02:17:27 +0200
To: John C Klensin <john-ietf@jck.com>, Bill Fenner <fenner@gmail.com>, Frank Ellermann <nobody@xyzzy.claranet.de>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <D9DD64A87AE4FD60479C62F3@scan.jck.com>
References: <Pine.LNX.4.61.0509191647510.23762@internaut.com> <p0620074fbf5509dd070a@192.168.2.2> <Pine.LNX.4.61.0509192043550.28535@internaut.com> <4333DDFF.8020909@zurich.ibm.com> <4333F545.7619@xyzzy.claranet.de> <4355E8A4.7634@xyzzy.claranet.de> <C56AABD8019A5267529A992C@scan.jck.com> <435697F6.3014@xyzzy.claranet.de> <ed6d469d0510191440u45a70950ve074ee12ab637cb3@mail.gmail.com> <D9DD64A87AE4FD60479C62F3@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ietf@ietf.org
Subject: Re: 2606bis
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

At 01:17 20/10/2005, John C Klensin wrote:
>1591 norms and definitions, and a large fraction of top-level
>domains and others have declined to accept the ICANN version,
>1591 probably still does represent a best practice consensus in
>most respects.

The ccTLD community has a BCP under "preparation" for a while and 
globally abides by the version we completed in Dec. 2000. It is 
mainly based on RFC 1591.

There is certainly a need for a liaison between the IETF and the 
ccTLD. However the response of Brian to my proposition to introduce 
the hows at the Luxembourg meeting, shown a confusion between 
Registry Manager's role and community trustee. This is the same 
confusion which mares the relations with ICANN. The comming Tunis 
resolution may help solving this situation. This is why most of the 
proposed additions to RFC 2606bis seem an unwelcome and inappropriate 
debate right now (unless IETF wants to get involved in the 
international network operations).

jfc


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