Q3: What characters should be allowed in a revised IDNA2008 specification?
mark at macchiato.com
Wed Apr 1 02:23:27 CEST 2009
I believe that the consensus from the meeting is the optimal solution; to
suggest in the document a transitional strategy for handling non-M-Labels,
with such a strategy being much like what you list. As opposed to the
mapping, this is an area where after some (probably extensive) period of
time, people could retire the transitional strategy. That is, the two
different kinds of characters would be handled differently.
For example, a capital U-umlaut or a half-width katakana character would be
mapped, and not subject to a transitional strategy, while a Heart symbol
would be handled by the transitional strategy.
On Tue, Mar 31, 2009 at 09:14, Vint Cerf <vint at google.com> wrote:
> IDNA2008 currently allows a more restricted set of characters to be
> used in domain name labels than IDNA2003 does.
> Does the working group agree that the more restricted set of the
> current IDNA2008 Tables document should apply once IDNA2008 is
> adopted? What should be done about registrations that use characters
> that would not be allowed under IDNA2008? Should there be a
> transitional period of finite duration after which these registrations
> will become invalid? Should they be grandfathered somehow? If we
> believe all future registrations should be restricted, how would such
> grandfathered registrations be found if the IDNA2008 rules would
> reject lookups of the disallowed characters?
> A two-lookup scheme might solve this problem:
> 1. lookup according to IDNA2008 rules (if disallowed characters are
> present, go to step 2); if domain name record is found, return the
> information. If not, go to step 2
> 2. lookup according to IDNA2003 rules (permitting a broader range of
> characters in the lookup process). If domain record is found, return
> it, if not return "no such domain name"
> Vint Cerf
> 1818 Library Street, Suite 400
> Reston, VA 20190
> vint at google.com
> Idna-update mailing list
> Idna-update at alvestrand.no
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update