[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: ietf-provreg@cafax.se
From: Patrick <patrick@gandi.net>
Date: Tue, 6 Aug 2002 12:47:56 +0200
Content-Disposition: inline
In-Reply-To: <20020806072719.GA10100@nic.fr>
Sender: owner-ietf-provreg@cafax.se
User-Agent: Mutt/1.3.24i
Subject: Re: Sending the original (Unicode) domain name as well as the ACE?

On Tue, Aug 06, 2002 at 09:27:19AM +0200, Stephane Bortzmeyer took time to write:
> > since epp's char set is utf8 i see no reason why a native utf name
> > cound't be enclosed in <domain:name> insted of the ace name.

I totally agree with Rick's comments.

> It is a matter of registrar-registry policy. I assume that a IDN
> registry will require its registrars to create domain with
> <domain:name> set to the original form OR the ACE form. And that this
> choice will be uniform among all the registrars.

My opinion is that Registry should accept the UTF-8 version and do
the ACE things by themselves. Of course this is a matter of policy.

> For instance, if the registry decides it will accept the original
> form, it will have to perform nameprep before deciding if the domain
> is already registered.

This is not a problem, I think.

> But, if the registry decides to let the registrars encode the IDN in
> ACE, it could be useful to accept the original name as well (remember

See http://www.verisign-grs.com/idn/techpaper.pdf for an example.
The Registry takes the ACE version, translates it to ISO10646,
do again the nameprep+ACE stuff on it, and compare its result with
what was given by the Registrar.

Patrick.

Home | Date list | Subject list