An idea for transition principles
vint at google.com
Mon Dec 14 20:31:35 CET 2009
I think trying to schedule an Internet-wide deadline across all
registries would be very difficult. Browsers that adopt IDNA2008
before all registries have completed their sunrise actions will get
NXDOMAIN for things that used to resolve to IP addresses for those
domain names containing the new characters (sharp-s and final sigma).
This will be visible - and the visibility might help to accelerate
registry action. I think under the suggested rules, domains that have
no vulnerable registrations (e.g. new TLDs) might be able to move
ahead with immediate use of IDNA2008; taking into account the possible
need to register also matching IDNA2003-compatible entries into the
relevant zone file(s) for backward compatibility. I am not sure what
other problems might arise - but appreciate further discussion within
On Dec 14, 2009, at 2:25 PM, Gervase Markham wrote:
> On 13/12/09 20:49, Vint Cerf wrote:
>> please see:
>> Your comments will be much appreciated.
> I think this is excellent, but there is one point which might
> require further clarification.
> As Shawn has mentioned, client authors need to know how much time
> must elapse before they can/should start switching their software to
> implement IDNA2008 rules.
> Would the best approach here to be for IETF/ICANN to canvass the key
> affected registries in order for us to determine the value of a time
> "S" which represents the upper bound on how long they think it will
> take to run the "sunrise" process? After that time, clients can
> begin to switch. Other registries, while retaining full control over
> their own operations, would know that if they did not run sunrise
> processes which completed inside time S, resolution problems of
> various sorts may result.
More information about the Idna-update