Re: [idn] Newbie's questions implementing the [IDNA]

["William Blackwood" <wblackwo@tampabay.rr.com>]

Adam,
Do you have any estimate when the RFC is going to be published?  How far
behind, in terms of calendar months/years is this working group's output
according to the original schedule?

Thank you,

William



----- Original Message -----
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: <idn@ops.ietf.org>
Sent: Monday, December 09, 2002 6:18 PM
Subject: Re: [idn] Newbie's questions implementing the [IDNA]


> Soobok Lee <lsb@postel.co.kr> wrote:
>
> > Only LDH and PREFIX--** ones are allowed as valid inputs to ToUnicode
> > according to IDNA.
>
> According to the first paragraph of the ToUnicode section, any sequence
> of Unicode code points can be the input of ToUnicode.
>
> > the output of ToUnicode must not contains
> > unnameprepped/prohibited/(unassigned) codepoints.
>
> The output of ToUnicode can contain unnameprepped, prohibited, and
> unassigned code points.  Simply feed such a string as input to
> ToUnicode, and the string will be output unaltered by ToUnicode.
>
> > ToUnicode is for display and verification purpose for the punycode
> > encoded labels later.
>
> IDNA uses ToUnicode for exactly two purposes: to force labels to
> human-friendly form before displaying them to users, and to define the
> concept of ACE label (which is any label that ToUnicode would alter).
>
> IDNA uses ToASCII for exactly two purposes: to define the concept of
> internationalized label (which is anything that ToASCII can be applied
> to without failing), and to force labels to ASCII form before putting
> them into slots (protocol fields, function arguments, etc).
>
> AMC
>