Re: homograph attacks

Hi John,

It's been a while!

In fact, it's been so long since I've really taken part in any RFC or 
Internet Draft related discussion that I'd like to apologize in advance 
if the following questions are, um, stupid...

John C Klensin wrote:
> While I think that an "International coordination list" would be
> helpful, my assumption is that ICANN's idn-discuss list (see
> http://www.icann.org/topics/idn.html for subscription
> information and some other information that might be useful) is
> intended to serve that purpose.  It is pretty clearly not this,
> or any other, IETF list: the IETF made a series of fairly
> explicit decisions to not get into the business of deciding what
> things could or could not be registered within the very broad
> coding mechanisms specified as part of IDNA.

I had a look at the welcome message of the idn-discuss list at ICANN, 
and it seems to be aimed more at the registry operators. I was hoping to 
find a forum where a broader group of interested parties could discuss 
the issue of IDN spoofing. I'm thinking of IDN applications, domain 
registries, ICANN and even IETF.

The reason I include IETF in this list is because I believe the IDN RFCs 
are a product of the IETF, and (1) those RFCs are not at the Standard 
Maturity Level yet, and (2) any discussion of IDN spoofing should 
probably include a discussion of the nameprep spec, since that may be 
something we could tweak, to help solve the problem.

If, as you say, the IETF has decided not to get into the business of 
deciding what can and what cannot be registered, then I suppose a forum 
centered on the registries (probably ICANN?) would be best.

But then I still wonder what forum is going to be discussing the IDN 
RFCs when they attempt to climb to the Draft Standard Maturity Level. I 
note that the IETF IDN WG has concluded.

Also, I saw that you published a new version of your IDN guidelines:

http://www.ietf.org/internet-drafts/draft-klensin-reg-guidelines-06.txt

Where is this I-D to be discussed?

Thanks,

Erik