Issues lists and the "preprocessing" topic

[Vint Cerf]

Frank,

your observation suggests to me that there may be some utility in  
drawing attention to 3987 for example in the rationale document.

vint


On Aug 21, 2008, at 3:51 AM, Frank Ellermann wrote:

> Lisa Dusseault wrote:
>
>> I don't really expect most of these kinds of developers
>> to participate in IDNABIS in general, so I really don't
>> know how to integrate their needs properly.
>
> From my POV 3987bis is the critical part.  The developers
> have to support the "correct" IRI to URI transformation,
> the variant based on IDNA for host names.
>
> Once they got that it is obvious to use exactly the same
> recipe (= pure IDNA) also for bare host names outside of
> IRIs.
>
> But if they pick the "wrong" transformation, where host
> names end up as percent-encoded UTF-8 non-LDH gibberish,
> we get an interoperability nightmare.
>
> 3987bis "MUST NOT" permit the wrong transformation.  But
> this mustard is IMO a job for 3987bis, not for IDNAbis.
>
>  Frank
>
>
>
>
>
>
>
>
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update