<div dir="auto"><div>I started to reply in thread but I think it is better to say that i am aware of and we are in violent agreement about emoji issues with IDNA.</div><div dir="auto"><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Mar 31, 2017 12:29, "Andrew Sullivan" <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On Fri, Mar 31, 2017 at 12:00:53PM -0700, Jothan Frakes wrote:<br>
> I see this on the agenda for the Redmond/Seattle group meetings - are we<br>
> deciding if this is in scope or not?<br>
<br>
</div>In scope for what? Emoji are just not allowed in the server-part<br>
unless you're suggesting that this group ought to be promoting names<br>
that are contrary to every IETF specification on the matter and are<br>
contrary to the ICANN IDN guidelines. If this group is in fact going<br>
to recommend sugh things, I predict that the future of acceptance is<br>
going to be even further from universal than you'd like.<br>
<br>
Perhaps you're talking about recommendations for use of emoji in<br>
local-parts, since email addresses are identifiers. Given the<br>
discussion in <a href="http://www.unicode.org/reports/tr36/" rel="noreferrer" target="_blank">http://www.unicode.org/<wbr>reports/tr36/</a> about visual<br>
spoofing, I hope the recommendation is just that emoji are interesting<br>
but poorly suited for identifiers. Since people can put literally<br>
anything they want in the local-part, they're going to do what they<br>
want anyway.<br>
<div class="quoted-text"><br>
> efforts towards solutions in UA, and on the plus side, Emoji support seems<br>
> to get attention from the developers at the moment.<br>
<br>
</div>Of course it does. Emoji are fun and cool. The problem is that<br>
they'll create an enormous security problem if people try to use them<br>
for real in identifiers, at least today.<br>
<div class="quoted-text"><br>
> Emoji domains on the left side of the dot do work in a small subset of the<br>
> existing TLDs<br>
<br>
</div>In some browsers. And what is this "the left side of the dot" of<br>
which you speak? DNS names are hierarchical. There are lots of<br>
possible dots.<br>
<br>
> - Addition of Emoji support as a primary project with an opportunity to<br>
<div class="quoted-text">> introduce UA readiness - Developer 'in the code' for Emoji support can be<br>
> more efficient for the team and address the matters that give access to the<br>
> next billion customers.<br>
<br>
</div>I am having a very hard time understanding what "in the code for emoji<br>
support" means, so I'd like to narrow that down.<br>
<div class="quoted-text"><br>
> What I mean about Emoji is that they are often used as short form and are<br>
> composed using characters like :) (colon closeparen) that would be<br>
> typically illegal in a DOMAIN, URI, URL, SMTP or other protocol - so it may<br>
> open a new set of challenges beyond the already daunting set we're hoping<br>
> to chip away at in the existing quixotic list.<br>
<br>
</div>The string ":)" is perfectly legal in the DNS but not legal in IDNA or<br>
under the LDH rules. It's extremely hard to use, however. The same<br>
is true in local-parts of email.<br>
<div class="quoted-text"><br>
> messenger applications. Try :) in skype, facebook other messenger and in<br>
> most cases it converts to the emoji smiley face.<br>
<br>
</div>Sometimes this is for display and sometimes this is on the wire.<br>
Figuring out which would be important. I can think of recommendations<br>
that would be useful to developers here, but they might be more<br>
properly developed as technical recommendations.<br>
<br>
> - There would have an issue with the interplay of IDNA and the<br>
<div class="quoted-text">> 'automagic' emoji handling / conversion apps perform.<br>
<br>
</div>Like that emoji and all punctuation are both not allowed under IDNA.<br>
<br>
Best regards,<br>
<br>
A<br>
<font color="#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
</font></blockquote></div><br></div></div></div>