Re: [idn] Internationalized PTR draft submitted

[Mark Davis <markdavis@ispchannel.com>]

Some of the reasons the plane 14 codes are discouraged is outlined in chapter 5 of
the Unicode Standard (I forget which section of that chapter). Briefly, because
they are actual characters in the text, and yet stateful, there are many
possibilities for corruption by unaware text editors. Where language tagging is
really necessary, we encourage the use of out-of-band protocols.

Mark

James Seng wrote:

> Mark Davis wrote:
> > 4.3.2.1.in-addr.arpa  IPTR  en "english commerce.com in utf8"
> >                       IPTR  de "german handel.com in utf8"
> >                       IPTR  it    "italian commercio.com in utf8"
>
> Yes, something like that.
>
> > In any event, if they are different characters and are to be used as domain
> > names, it would seem that they would need to be separately registered.
>
> Yes, unfortunately :P
>
> This is reverse, as it is possible there are 2+ names for a single IP.
>
> > 2. Perhaps you can motivate the use of this more, with a usage scenario?
>
> Not sure, honest! :-) Hongbo Shi has to answer this.
>
> Actually, this is a good section to add to the next version of the I-D.
>
> > 3. The Unicode consortium does not encourage use of the plane 14 language
> > tags. When language tagging is necessary, it should be done with a higher
> > protocol (such as xml:lang in XML, or HTTP accept-lang).
>
> As Paul told me, Plane 14 is been inserted at the request of IETF. I suppose
> there is a reason why IETF want this.
>
> May I ask why UC does not encourage it? Will Plane 14 will be drop off leaving
> 1M+ codepoints?
>
> -James Seng