<html>
<body>
At 23:21 17/07/2008, John C Klensin wrote:<br>
<blockquote type=cite class=cite cite="">--On Thursday, 17 July, 2008
20:53 +0200 JFC Morfin<br>
<jefsey@jefsey.com> wrote:<br><br>
> Dear John,<br>
> we obviously have different priorities you as an academic<br>
> designer and I as a pragmatic operator.<br><br>
Gee, I haven't been accused of that in circa sixteen years
years.</blockquote><br>
Dear John,<br>
"accused"? I do not see any accusation of anything here. I just
note that you are not (to my knowledge) a field operator or a TLD
Registry Manager, have no terms and conditions coined by a lawyer,
discussed with the WIPO and are used to address legal complains of
registrants of yours. Your last paragraph, seems to confirm that. Or am I
wrong ?<br><br>
<blockquote type=cite class=cite cite="">> However, I am sure<br>
> you realise that if a character is replaced by another<br>
> because Unicode decides it, the registered Trade Mark
will<br>
> follows the replacement if it is adopted by ISO. Courts
and<br>
> TLD Managers will see it as a technical typo correction<br>
> having nothing to do with creating new IPRs (missing <br>
> clarifications about this kind of points is for them a worry).<br>
> If we are not sure of that, the best is then that we ask
the<br>
> WIPO?<br><br>
But here I have almost no idea what you are talking about. The<br>
characters that are proposed for deprecation are not, if I<br>
understand any of Mark's comments, Ken's note, or the review<br>
question as presented on the web site, "being replaced by other<br>
characters". </blockquote><br>
I discuss this of yours:<br>
> > At 18:03 17/07/2008, John C Klensin wrote:<br>
> >> But it does seem to me that there is a more general<br>
> >> question here at least for the future and especially if
the<br>
> >> <b>reason for deprecating a character is to replace it</b>
with a<br>
> >> different preferred (or normalized) form.<br><br>
<blockquote type=cite class=cite cite="">Their use is simply being
discouraged because they<br>
should not have been assigned code points in the first place or<br>
because there are better ways to do that same thing. And, as<br>
Ken's note points out, very few of them are allowed in IDNs<br>
anyway (they are DISALLOWED, not PVALID, and hence irrelevant to<br>
anything that could appear in a domain name).</blockquote><br>
John, the point is not if there only are a very few, but if there any.
<br>
What is discussed is a standard.<br><br>
<blockquote type=cite class=cite cite="">ISO doesn't have anything to do
with actions that affect<br>
registered Trade Marks, and things that they "adopt" (in
ISO/IEC<br>
JTC1/SC2 or elsewhere) don't automatically change
anything.</blockquote><br>
This is your vision of the WIPO's position, it is not ours. <br>
The best is we ask the WIPO and copy this WG of the WIPO position when we
have obtained it. <br><br>
<blockquote type=cite class=cite cite="">More generally, let's assume
that there were a character that<br>
Unicode and ISO 10646 decided declare obsolete, obsolete,<br>
withdraw, and replace by something else -- that case is<br>
theoretically possible but let me save Ken the time by saying<br>
that it doesn't happen in practice and certainly is not what is<br>
being discussed as "deprecation". If I had a Trademark
that<br>
involved that code point and had reflected that Trademark in a<br>
domain name, I would certainly rush out an register the name<br>
name with the new spelling. </blockquote><br>
Dear John, what you would do, either in registering names in here, or in
cancelling a nth level domain name whose nth+1 level does not fullfil
your obligation (a previous thread) is wise. But as above, what has it to
do whith the Charter of a standard? And Best Operational Practices
?<br><br>
<blockquote type=cite class=cite cite="">I would probably also retain
the<br>
old spelling forever, just to prevent various sorts of mischief.<br>
And I would use the trademark laws against anyone who tried to<br>
get ahead of me in registering the new form on the grounds that<br>
the two forms were a lot closer together than what would<br>
normally be considered similar enough to cause confusion. And
I<br>
would do that regardless of whether the trademark itself somehow<br>
magically migrated from one form to another.</blockquote><br>
This is well said. And exactly what the IETF standard, the national law,
and the Registry rules are to organise, so the registrant is protected
from the impact of issues out of his control, but under the control of
the IETF/Unicode Reviewer. <br><br>
<blockquote type=cite class=cite cite="">And, because that whole issue
affects decisions made by<br>
trademark holders and registries, it has nothing to do with the<br>
task list for this WG, so you are confusing policy issues for<br>
which responsibility lies elsewhere with WG tasks.
Again.</blockquote><br>
Then I have not understood what IETF is about, and I apologise for
confusing the issues.<br>
May I take this text of yours as expressing a WG-IDNABIS rough
consensus?<br>
jfc<br><br>
<br><br>
<br>
</body>
</html>