<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">yes<div><br><div><div>On Jul 15, 2009, at 5:49 PM, Mark Davis ⌛ wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I think we need to strictly forbid, for stability's sake, any changes in the following direction:<br><ul><li>PVALID => CONTEXT* => DISALLOWED</li></ul>The whole premise for this major invalidation of existing IDNs is that it be a one-time occurrence.<br> <br>Making any change in the <i>other</i> direction should probably require IETF-level intervention in the near term, but as you say, might be made lighter-weight over time.<br><ul><li>DISALLOWED => CONTEXT* => PVALID</li> </ul>Does this match what you think, Vint?<br><br>Mark<br> <br><br><div class="gmail_quote">On Wed, Jul 15, 2009 at 14:40, Vint Cerf <span dir="ltr"><<a href="mailto:vint@google.com">vint@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> nominally I think we hope that we will not have to deal with going<br> from disallowed to contextO.<br> <br> I think the current view is that such changes should require IETF-<br> level intervention in the near<br> term although a lighter-weight process might be considered based on<br> experience.<br> <br> Does anyone see this differently?<br> <font color="#888888"><br> vint<br> </font><div><div></div><div class="h5"><br> <br> On Jul 15, 2009, at 5:26 PM, Wil Tan wrote:<br> <br> > What are the WG's expectations on possible updates to the list of<br> > exceptions?<br> ><br> > I'm not suggesting that we would update it often (or at all) but<br> > *should* the need arise, e.g. to change a character currently<br> > classified as DISALLOWED to CONTEXTO and define a contextual rule for<br> > it, what would the process look like?<br> ><br> > The set of code points in Exceptions (2.6 of idna-tables-05) is<br> > immutable, so I presume the only way to update it would be to have a<br> > new document that updates this one.<br> ><br> > It seems that the BackwardCompatible set can be used as a more<br> > lightweight method to address this use case, though it appears to be<br> > designed only for incompatible changes to Unicode version after 5.1,<br> > and not for errata in version 5.1 itself.<br> ><br> > I don't pretend to have completely read all the relevant drafts, so I<br> > may have completely missed the point. If so, please point me in the<br> > right materials.<br> ><br> > =wil<br> > _______________________________________________<br> > Idna-update mailing list<br> > <a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br> > <a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br> <br> _______________________________________________<br> Idna-update mailing list<br> <a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br> <a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br> </div></div></blockquote></div><br></blockquote></div><br></div></body></html>