Updates to Exceptions and BackwardCompatible Sets

[Vint Cerf]

nominally I think we hope that we will not have to deal with going  
from disallowed to contextO.

I think the current view is that such changes should require IETF- 
level intervention in the near
term although a lighter-weight process might be considered based on  
experience.

Does anyone see this differently?

vint


On Jul 15, 2009, at 5:26 PM, Wil Tan wrote:

> What are the WG's expectations on possible updates to the list of  
> exceptions?
>
> I'm not suggesting that we would update it often (or at all) but
> *should* the need arise, e.g. to change a character currently
> classified as DISALLOWED to CONTEXTO and define a contextual rule for
> it, what would the process look like?
>
> The set of code points in Exceptions (2.6 of idna-tables-05) is
> immutable, so I presume the only way to update it would be to have a
> new document that updates this one.
>
> It seems that the BackwardCompatible set can be used as a more
> lightweight method to address this use case, though it appears to be
> designed only for incompatible changes to Unicode version after 5.1,
> and not for errata in version 5.1 itself.
>
> I don't pretend to have completely read all the relevant drafts, so I
> may have completely missed the point. If so, please point me in the
> right materials.
>
> =wil
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update