jefsey at jefsey.com
Thu Jul 17 20:53:21 CEST 2008
we obviously have different priorities you as an academic designer
and I as a pragmatic operator. However, I am sure you realise that if
a character is replaced by another because Unicode decides it, the
registered Trade Mark will follows the replacement if it is adopted
by ISO. Courts and TLD Managers will see it as a technical typo
correction having nothing to do with creating new IPRs (missing
clarifications about this kind of points is for them a worry). If we
are not sure of that, the best is then that we ask the WIPO?
May be you misread my mail which was only to suggest a domain name
update to operators. This has nothing to do with the way the DNS
works nor any transitional effects which belongs to the Registry
Manager authority and competence. It was only that a reminder in the
single IDNA document that they should use would encourage them to use
and respect it; or it could be a mention in the security section?
The only thing is that as a Registry Manager I am not interested in
supporting deprecated chararcter domain names without them to be
duplicated through a PNAME. (Since I am prevented to document it
otherwise I call a PNAME a polynym [strict synonym in another
At 20:21 17/07/2008, John C Klensin wrote:
>--On Thursday, 17 July, 2008 19:32 +0200 JFC Morfin
><jefsey at jefsey.com> wrote:
> > At 18:03 17/07/2008, John C Klensin wrote:
> >> But it does seem to me that there is a more general
> >> question here at least for the future and especially if the
> >> reason for deprecating a character is to replace it with a
> >> different preferred (or normalized) form.
> > This seems to indicate that the proposed unique text should
> > not only be clear to developpers but also to operators. If a
> > character is replaced, should it not be suggested that the
> > domain names using be automatically updated ?
>"Automatically" would be very bad news, for reasons that should
>be clear to anyone who has read the specs and considered the way
>that IDNA is necessarily implemented, the way the DNS works, and
>the associated transitional effects. In that sense, I think it
>is obvious that Mark is correct -- since deprecation does not
>remove code points, we are safe in ignoring any deprecation of
>characters and just continuing whatever we are doing.
>My question was about whether best practices might tend in the
>direction of discouraging further registrations with deprecated
>characters and whether changes made outside the IDNA
>environment might make such characters harder to access, enter,
>display, etc., in the long term.. and, if so, whether we need to
>make any provisions for those possible trends.
More information about the Idna-update