if this is to be a separate document, this document still needs to be considered a part of the specifications because that is what we agreed to do in the last face/face working group meeting: ie. to map on lookup while not mapping on registration.<br>
<br>In other words this mapping function is not distinct from the IDNA2008 spec at least that is how I read our conclusion at the meeting.<br><br>vint<br><br><div><span class="gmail_quote">On 4/13/09, <b class="gmail_sendername">Andrew Sullivan</b> <<a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, Apr 12, 2009 at 02:34:24PM -0500, Pete Resnick wrote:<br> > If we're going to deal with mappings, I want it to be a separate<br> > document.<br> <br> <br>I like that suggestion. It seems to me to enforce the separation of<br>
"here's the definition of IDNA2008" and "here are some things to make<br> IDNA2008 work well with other stuff".<br> <br> A<br> <br><br> --<br> Andrew Sullivan<br> <a href="mailto:ajs@shinkuro.com">ajs@shinkuro.com</a><br>
Shinkuro, Inc.<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">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</blockquote></div><br>