<html>
<body>
<blockquote type=cite class=cite cite="">At 01:10 18/02/2009, John C
Klensin wrote:</blockquote><br>
Dear John,<br>
We are not talking here of mapping on the registration side, but in the
naming policy; to be voted by the ".fr" ccTLD BoD - or the
French Parliament, since ".fr" is legally delegated as a public
service. <br><br>
The actual way this will be implemented will then be a different
question. <br><br>
The position can either be for the Gov to publish an RFP calling for an
alternative solution to IDNA, or for users to develop it and use it with
broad support. I think the consensus will be pragmatic: "confusion
starts from the very mistyping". <br><br>
<blockquote type=cite class=cite cite=""><b>> Andrew Sullivan</b><br>
> To be clear, are you here distinguishing the narrow meaning of<br>
> "mapping" to mean "transforming one character into
another",<br><br>
yes<br><br>
> and another possible meaning, which is "expanding to match<br>
> other characters, and registering those _too_? For
instance<br>
> the example that Jefsey provided is just école.fr and<br>
> ecole.fr, which could easily be resolved by registering<br>
XÀole.fr also whenever xn--cole-9oa.fr is registered. </blockquote><br>
Unfortunately, this proposed procedural patch <br><br>
1. does not make sense since ecole.fr is already registered (actually in
this case reserved) and a decision MUST be taken. As for probably a
million of other accentuated domain names).<br>
<br>
2. is not legally acceptable: <br><br>
--- "école" means school; <br>
--- "ecole" can be a TM: ex.
<a href="http://www.defl.ca/fr/ecole.html" eudora="autourl">
http://www.defl.ca/fr/ecole.html</a>. For other terms the accentuated and
the non-accentuated terms are different words or TMs. <br>
--- "Ecole" will usually mean a national school.<br>
--- "schule", "scola", etc. are valid terms from
French languages that would not suffer the constraint. This would create
an anti-competitive commercial image imballance. <br>
--- There is "ecole.gouv.fr" which will oblige to a documented
legal terminology decision. <br><br>
3. would violates the French language and people's equality. I do not see
it being legally and technically accepted just because the IETF did not
find a solution. <br><br>
<blockquote type=cite class=cite cite=""><b>Andrew Sullivan </b><br>
This<br>
> doesn't need anything at all in the IDNA protocol -- you can<br>
> do it all with registration bundling.<br><br>
Exactly. But I read Jefsey's note as saying that it was up to<br>
the registry whether to do that or not. If it was not done,<br>
then the two strings would effectively be treated as completely<br>
different strings, as different as, say, "école" and
"school".</blockquote><br>
The question is related to case folding.<br>
Both domain names can also be typed as "Ecole.fr".<br><br>
<blockquote type=cite class=cite cite="">I agree with that, but note
that, were the protocol to<br>
do/require the mapping between "é" and "e", the
registry would<br>
be deprived of the ability to make the choice. Of course, no<br>
one has seriously suggested that mapping, </blockquote><br>
That mapping is currently de-facto imposed as "ecole" is the
only way to "école".<br>
jfc<br>
</body>
</html>