<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Vrinda;
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#002060;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>William,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>There are many problems that having a standard would resolve. Simply stating an incomplete idea and then expecting Unicode Consortium or any other standards body to implement it is an arrogant and unreasonable proposition.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>To become a standard the idea has to have support from many communities, and it has to be a fit for the organization’s responsibilities.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>It isn’t clear the grid idea meets the needs of password entry, and isn’t specified in detail.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>It isn’t clear emoji are needed or optimal for this purpose, compared to just using shapes (triangle up, triangle down, etc.) or for that matter that any images are needed, since it could be select row3 column 4.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>Ultimately, the password this generates does not need Unicode since the output reduces to a series of row and column pairs. (Which is why this is just an interface.)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>So if you think this should be a standard, establish the requirements for password entry, show that the proposal satisfies the requirements, find communities that agree and support the idea, and find a standards body that will make it a standard.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>You might try NIST for example as a standards body that might support a solution.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>You have not acknowledged the requirements for password entry (see the NIST document).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>Hth<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'>Tex<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#002060'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Unicode [mailto:unicode-bounces@corp.unicode.org] <b>On Behalf Of </b>William_J_G Overington via Unicode<br><b>Sent:</b> Saturday, April 9, 2022 12:48 PM<br><b>To:</b> unicode@corp.unicode.org<br><b>Subject:</b> Re: global password strategies<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Mark E. Shoulson via Unicode wrote:<o:p></o:p></p><div><p class=MsoNormal>> That's not a format, it's a user interface ("the user is presented...") <o:p></o:p></p></div><div><p>Fine, it can be described as a user interface. Better still, as a script-independent and language-independent user interface.<o:p></o:p></p><p>> Unicode doesn't standardize user interfaces.<o:p></o:p></p><p>I don't know, as I am no expert on categorizing all of the standardization content that Unicode Inc. has published, nor am I am aware of any policies that may exist that would prevent Unicode Inc. choosing sixty-four emoji to populate an 8 by 8 grid of emoji and Unicode Inc. publishing it is some form.<o:p></o:p></p><p>> Restricting the permissible alphabet to emoji is just about as bad/annoying (for many users) as restricting it to ASCII or Cyrillic or whatever, except that it's more evenly hard on everyone.<o:p></o:p></p><p>Quite possibly it would be, yet that is not what I am suggesting.<o:p></o:p></p><p>I am suggesting an additional facility that could be a very useful facility to have available for use in some circumstances. There is absolutely nothing in my suggestion that would restrict other user interface systems for passwords from being used. Indeed, on a tablet computer end users could be presented with a choice of how to enter a password, with two or more choices presented each in its own tile, with the tiles presented side by side so that the end user can choose which one to use to set up and use a password.<o:p></o:p></p><p>Certainly any individual or organization could choose to select sixty-four emoji to populate an 8 by 8 grid of emoji and publish it, make it open source in a document, or even produce it as a pop art style poster. The poster might end up as an exhibit at MoMA in New York as an example of emoji being applied for a practical purpose.<o:p></o:p></p><p>However, for the particular layout to become used in practice by lots of independent app producers, the particular layout needs to have the provenance of being published by a widely-respected standardization body.<o:p></o:p></p><p>So I am hoping that Unicode Inc. will take up this idea and publish a particular layout of emoji and some notes about how to use it, doing that either within one of the existing projects or as a stand-alone project as Unicode Inc. decides.<o:p></o:p></p><p>William Overington<o:p></o:p></p><p>Saturday 9 April 2022<o:p></o:p></p><p><o:p> </o:p></p></div></div></div></body></html>