Message-Id: <6.2.1.2.2.20050723001644.04ac0c70@mail.jefsey.com>
Date: Sat, 23 Jul 2005 01:13:49 +0200
To: Brian E Carpenter <brc@zurich.ibm.com>,
	Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <42E15D0C.5090103@zurich.ibm.com>
References: <Pine.LNX.4.62.0507220718250.2773@localhost>
	<20050722114950.GA24287@nic.fr>
	<Pine.LNX.4.62.0507221003130.620@localhost>
	<20050722141658.GA4984@nic.fr> <42E15D0C.5090103@zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
Subject: Re: Multiple roots & E2E PKI trust discovery,	chain management
 & capabilities exchange
Precedence: list
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

At 22:54 22/07/2005, Brian E Carpenter wrote:
I wouldn't change a word in RFC 2826.

The problem with RFC 2826 is that it links (for information) a unique 
domain name resolution (what we want) with a unique authoritative root file 
(we do not care it is "unique", we want the one we use to be pertinent). 
Confusing the description with the described space was a way to protect the 
name space, but it unfortunately lead to open roots confusion and to 
alt-root suspicion (I only know one: ICANN with .biz) and to the lack of 
preparation in front to PAD (private roots).

Now, I agree with Stephane and ICANN that a lot is/can to be done. We just 
have to remember IMHO the namespace is the same as geographical space: the 
map does not build the geography and no one thinks that geography depends 
on the map he uses.

Except may be politics.

But there may and is to be a lot of innovative thinking. ICP-3 is 
excellent, starting with a good review of RFC 2826, rooting into RFC 920 
which is the true basis of the DNS as we live it, and calling on 
experimentation and proposing avenues for the research and development with 
classes (the way to the externets).

jfc



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf