Re: [idn] iDNS.net

["James Seng/Personal" <James@Seng.cc>]

>   Suzanne, the upcoming IETF meeting in San Diego next week should prove
> pivotal in clarifying the technical direction of the IDN working group
> with respect to the resolution of internationalized domain names.

No, I do not think so. No one will know how the final standard will look like
and it is best not to second guess how and when it will come. Even the
resolutions you stated below itself are subjected to debate nor complete.

No offence, but just trying to set record striaght just incase anyone expect
too much of San Diego meeting. I do not want a reporter to pick this up and
wrote a report how the WG is going to set a standard next week which we know
we aint ready yet. We dont need unduely more pressure. *sigh*

-James "as co-chair" Seng

>   - What encoding to use for the names.  The two basic choices are some
> flavor of ACE or UTF-8.  I think the consensus of the wg is, at this
> point, that Unicode is the best direction to go in terms of a character
> set encoding.  I've seen other proposals, and Unicode has its own set of
> issues, but that seems to be the most reasonable, and technically mature
> choice.  An ACE likely implies no changes to the protocol, UTF-8 would.
>
>   - Where to do IDN.  There are a number of choices here, constrained
> partially on what you choose above.  In an ACE-based approach, you can do
> IDN transformation in the resolver (in my opinion the best place to do
> it), in a proxy-agent, by modifying the resolving nameserver, or perhaps
> by modifying the authoritative nameservers.
>
>   I would expect to see a substantial amount of activity on the IDN WG
> mailing list following next week's meetings.
>
>   -brian
>
>
>
>
>
>