<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Aside: in pursuit of helping Jake register “.onion” as a "special name” in an RFC, I am currently being beaten-up on the IETF discussion mail-list regards the potential future length of onion addresses, and that they may possibly exceed the bounds of DNS’ maximum label length of 63 characters:<div class=""><br class=""></div><div class=""><a href="https://www.ietf.org/mail-archive/web/ietf/current/msg94332.html" class="">https://www.ietf.org/mail-archive/web/ietf/current/msg94332.html</a></div><div class=""><br class=""></div><div class="">The examples in Proposal 224 are a mere 53 characters long leaving 10 to play with for padding-hyphens and possibly checksum characters.</div><div class=""><br class=""></div><div class="">Nick: Is this likely to need to change? Or might there be a need to encode > 315 bits / 63 chars total?<br class=""><div class=""><br class=""></div><div class=""> -a</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">—</div><div class="">Alec Muffett</div><div class="">Security Infrastructure</div><div class="">Facebook Engineering</div><div class="">London</div></div></div>
</div>
<br class=""></div></div></body></html>