<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
I have not enabled 2FA.</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
TOTP lies at the unfortunate confluence of vendor misfeatures and organizational policies that render it not durable or resilient in the face of mobile device failure (which seems to happen to me a LOT more often than normal). <span style="font-size: 12pt;">Possibly
I don't know something about our approved authenticator apps that might solve the problem, but last time I checked, it was a no-go for me.</span></div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
I've instead opted to use a long, randomly-generated password that I can store in ways that are both secure and durable/resilient.</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
<br>
</div>
<div style="color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);" dir="auto">
-Adam</div>
<div id="ms-outlook-mobile-signature" dir="auto">
<div><br>
</div>
Get <a href="https://aka.ms/AAb9ysg">Outlook for Android</a></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> ARIN-consult <arin-consult-bounces@arin.net> on behalf of Bram Abramson <bda@bazu.org><br>
<b>Sent:</b> Wednesday, May 25, 2022 9:26:59 AM<br>
<b>To:</b> ARIN-consult <arin-consult@arin.net><br>
<b>Subject:</b> [ARIN-consult] increasing 2FA take-up</font>
<div> </div>
</div>
<div>
<div style="font-family:sans-serif">
<div class="x_markdown" style="white-space:normal">
<p dir="auto">All,</p>
<p dir="auto">The current consultation is about rendering SMS a 2FA option, then making 2FA mandatory. But it also notes that TOTP 2FA has been available since 2015 with a 3.2 percent take-up.</p>
<p dir="auto">Optional 2FA is perhaps inevitably doomed to low take-up, but I it’s likely worth documenting any learnings from the implementation thus far, on the way to that 3.2 percent take-up:</p>
<ul>
<li>
<p dir="auto">Have most folks involved in this discussion already activated 2FA (are we preaching to the converted)? If not — why has it made sense for you not to?</p>
</li><li>
<p dir="auto">Do we think most of the broader community is aware of the 2FA opportunity — and are there thoughts, UX or otherwise, on why the crushing majority of folks haven’t availed themselves of it?</p>
</li></ul>
<p dir="auto">Thanks, and cheers,</p>
<hr style="border:0; height:1px; background:#333">
<p dir="auto">Bram Abramson<br>
<a href="mailto:bda@bazu.org" style="color:#3983C4">bda@bazu.org</a> / @bramabramson</p>
</div>
</div>
</div>
</body>
</html>