I-D Action:draft-ietf-idnabis-mappings-00.txt

[Mark Davis]

Re: http://tools.ietf.org/html/draft-ietf-idnabis-mappings

I agree with other comments in this thread; and with all due respect to the
effort put into writing the draft, I don't think it accomplishes much. The
core is:

   The general algorithm that an application (or the input method
   provided by an operating system) should use is relatively
   straightforward and generally follows section 5
<http://tools.ietf.org/html/draft-ietf-idnabis-mappings-00#section-5>
of
   [I-D.ietf-idnabis-protocol
<http://tools.ietf.org/html/draft-ietf-idnabis-mappings-00#ref-I-D.ietf-idnabis-protocol>]:

...

   These are the minimal mappings that an application SHOULD do.

The user of SHOULD rather than must means that, for example, one still
wouldn't know what a IDNAbis-conformant browser would do with href="
http://Übersetzung.de <http://xn--bersetzung-8db.de>". Would it interpret it
as übersetzung.de <http://xn--bersetzung-8db.de> or just fail? By having no
firm requirements, it leaves the issue open, and we are no better off than
if this document weren't there.

Mark


On Wed, May 27, 2009 at 12:57, Paul Hoffman <phoffman at imc.org> wrote:

> I'm glad that we have a document to work from, but this document seems
> upside-down. The long, stuffy "architectural principles" should be an
> appendix, and it should be clearly labelled as "non-normative" and/or
> "informational". There is no way that this WG will agree on such
> architectural principles except by attrition (which we are getting good at,
> unfortunately).
>
> Similarly, putting the actual algorithm as an appendix just seems wrong.
>
> On a technical level, the algorithm is wrong in that there are characters
> that are legal in IDNAbis that will not make it through the algorithm. We
> *need* to come to agreement on the mapping of those, and we need to do so
> sooner rather than later.
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20090527/abcedc58/attachment.htm