Changing the xn-- prefix

[Mark Davis]

+1

On Mon, Mar 24, 2008 at 11:29 PM, YAO Jiankang <yaojk at cnnic.cn> wrote:

>
> ----- Original Message -----
> From: "Patrik Fältström" <patrik at frobbit.se>
> To: "Shawn Steele" <Shawn.Steele at microsoft.com>
> Cc: <idna-update at alvestrand.no>; "John C Klensin" <klensin at jck.com>; "Mark
> Davis" <mark.davis at icu-project.org>
> Sent: Tuesday, March 25, 2008 10:23 AM
> Subject: Re: Changing the xn-- prefix
>
>
> > On 25 mar 2008, at 00.13, Shawn Steele wrote:
> >
> >> I reread your original mail, and in particular I don't want to get
> >> bogged down in the debate of details while trying to set the
> >> guidelines, but I'd like to try for "A prefix change MUST be
> >> avoided" (removing the condition).  If that's going to cause too
> >> much randomization, then I'd back down, but the repercussions of
> >> changing the prefix are huge.
> >
> > I am personally in favor of text in the charter that say "The prefix
> > xn-- MUST NOT be changed." where MUST NOT is defined according to the
> > IETF definition in RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt).
>
> +1
>
>
> > This put a constrain on the changes the wg is allowed to do to
> > IDNA200X (not large so that the prefix has to change) -- at least not
> > without rechartering.
> >
> >    Patrik
> >
> > _______________________________________________
> > Idna-update mailing list
> > Idna-update at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/idna-update
> >
>



-- 
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20080325/627658a2/attachment.html