[newprep] wg/newprep project: clarification asked

[JFC Morfin <[e-mail]>]

Mark's review is clear and enlightening.

As you know, as Internet Users, we believe IDNA2008 represents 
several major achievements. One is to uncouple the Internet and 
Unicode while succeeding in using ISO 10646 Unicode generated tables. 
This is a double big step ahead:

-          giving the Internet its own independent charset.
-          advancing towards a better transtechnology/usage 
operational scripting methods unification.

However, IDNA still has to document three major issues that affect 
stringprep and definitely disqualify any further involvement of 
Unicode in the network support of strings:

-          lack of support of orthotypograhy (i.e. language script syntax)
-          the multitude of "stringpreps" functions (at least one per 
ISO 639-6 linguistic entity) that are now to be specified on the users' side.
-          how they will be administered together (what will then 
also concern "newprep")

This is why what you call "IDNA" (just what is IDNA DNS layer 
related, not what will be User layer related) also cannot qualify at 
this stage. Everything is to be discussed together; the different 
stringpreps are equivalents to additional languages with their own 
orthotypographies.

Now, as users, we have a different, more pragmatic approach that goes 
further and does not call on this endless kind of discussion. This is 
because as Internet lead users we are more interested in forward 
compatibility (i.e. with our needs, innovation, and simplification) 
than in backward compatibility (installed basis).

In a technological evolution, those who were in advance knew that 
their solution might not be final. Cf. RFC 1958: the fundamental 
Internet architectural principle of constant change. The second main 
architectural Internet principle (RFC 1958 and 3439) is the principle 
of simplicity. We are not interested in several stringprep solutions 
due to historical or partial technical analysis. We are interested in 
a stable, unique, comprehensive manner to format strings in the world 
digital ecosystem, which is currently mainly under Internet 
technology that prevents phishing and sustains a single sorting and 
indexing order.

This is our architectural target. Our implementation strategy is to 
help and use every effort that can help reaching that target, and 
oppose (IETF and real world operations) every attempt that would 
confuse or delay it.

This is because our main interest is not so much to "influence those 
who design, use, and manage the Internet for it to work better", 
(without a definition of what "better" may means RFC 3935is 
meaningless anyway); our main interest is for us and our partners to 
best use the Internet to better suit our common and present-day 
needs. This SHOULD be the same. However, experience has shown that it 
MIGHT not always be the same.

This is why the best is to clarify this issue from the onset. I was 
not responded to when we started the WG/LTRU on langtags and I had to 
force the consensus the way we know. I was very clearly responded to 
in the case of IDNA and we were able to fully support the consensus.

---

My question is therefore:

-          "a need is identified by our Internet user contributing 
party. This need is for a stable, unique, comprehensive manner to 
orthotypographically format prepared strings whatever the script and 
language. Such a format must prevent phishing and support a single 
registry indexing and sorting order of every possible 
orthotypographic string, throughout the Internet protocols, related 
applications, and interoperated technologies.
-          Is this or is this not also an immediate or ultimate goal 
for the AD, WG Chair, and WG/newprep possible participants?"

Depending on the response given, we will participate and try to help 
this wg/newprep effort, or we will pursue our own project, with the 
ambition to address our needs while keeping things as interoperable 
with newprep-like endeavors as is possible.

I thank you for your time, attention, and response.

jfc

At 17:56 19/05/2010, Mark Lentczner wrote:
>It should be noted that *all* approaches induce standards coupling 
>with Unicode itself, though that is, I think, a clear aim of this 
>group. Unicode as a whole has many different stability guarantees, 
>of various levels, and I believe it is quite reasonable to choose 
>which parts of Unicode to couple to in order to achieve the aims 
>needed by IETF protocols and human nomenclature.
>
>While I think the above discussion reveals I lean toward the UAX #31 
>approach, I'm eager to learn what others think of these approaches, 
>and ideas for other ways to proceed.
>
>- Mark