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

Re: New Internet Draft on registering IDNs


At 11:36 AM -0500 4/4/03, Martin Duerst wrote: 
Okay, let me try again. On a very high level, I'm suspicious of
documents with the word "framework" in the title, because this
seems to be used more for buzword compatibility than anything else.

Years ago, I created a protocol that had the word "Simple" in the title. Someone commented that every protocol should have the word "simple" or "fast" or "revised" in the title so that people could not argue against it. Maybe I should add "framework" to that list.

On a lower level, I think your document contains two things:
1) the table format and the algorithm to use it (which is
   basically a technical/protocol spec, and therefore doesn't
   seem appropriate for BCP)
2) Some general recommendations for registries (think about
   what languages you want to support, think about what
   mappings/blockings to use, document your policies,
   use the table format/algorithm where possible).
   This kind of material seems to be adequate for a BCP.

So I guess my suggestion is that the draft be split in two,
which would then get rid of "framework" automatically.

I don't think the draft can be split into two because the whole idea of allocations/blockings is tied quite tightly to the algorithm that creates the bundles.

Having said that, and since I'm slogging through creating the -01 draft, I will see what I can do to separate out the three parts (recommendations, algorithm, format) better in the words in the document.

For ASCII, as for any other script, there is the question of whether
some of these characters are part of the language or not.

Agree, but that is a concern for the person making the table.

However, there are also other questions specific to ASCII,
because all current domain names are in ASCII.

This document is only for IDNs. Non-IDN domain names are not relevant here.

 These are
not linguistic questions, but very much operational questions.

Sorry, I still don't see how.

One could imagine for example that we/somebody make/s a recommendation
that every host reachable by an IDN is also reachable by an ASCII-only
domain name. One could then imagine that in many cases, this is
done most easily by allowing ASCII in the same zone.

We aren't making that recommendation here. If someone wants to make that recommendation, they would have to show how to have IDNs map to non-IDNs. They can do that, but it isn't relevant here, just as someone who says "every host reachable by an IDN is also reachable by an all-Ethiopic IDN."

Also, there is the question of constructing tables for
zones that already allow ASCII (and maybe already have
ASCII entries).

Sorry, I'm still not seeing what you are saying. How does this relate to IDNs?

Yes, please add examples like these.

Will do.

--Paul Hoffman, Director
--Internet Mail Consortium