On Wed, 8 Jan 2014, Paul Hoffman wrote:
In the real world, there are few users who have LHS user names that are more than 30 (or
maybe even 20) characters long. What you are proposing is "base32 but not really
base32" and that could introduce errors in libraries looking up the names.
It's not _that_ hard:
paul@thinkpad:~$ python
Python 2.7.5 (default, Nov 12 2013, 16:45:54)
[GCC 4.8.2 20131017 (Red Hat 4.8.2-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
import base64
x =
bas64.b32encode("PaulReallyIHaveNoMiddleNameAndThatOtherGuyIsNotMeAndIdontBowlEitherNorRunaNudeBeachInRotterdamWouters")
[ x[i:i+60] for i in range(0, chunks, 60) ]
".".join([ x[i:i+60] for i in range(0, chunks, 60) ]).lower()
'kbqxk3csmvqwy3dzjfegc5tfjzxu22lemrwgkttbnvsuc3tekrugc5cporug.k4shov4us42on52e2zkbnzseszdpnz2ee33xnrcws5dimvze433skj2w4yko.ovsgkqtfmfrwqslokjxxi5dfojsgc3kxn52xizlsom======'
Similarly, it's easy to add a .strip("=")
Also, with say "6" octets of input, e.g. "viktor", we have 48 bits
OZUWW5DPOI======
This seems rather wasteful.
Relative to, say, the size of a PKIX certificate? :-)
In some sense, I'm more interested in skipping the '=' symbols because
some GUI's won't allow "=" in DNS names. Size does not really matter
to me.
Allowing for significantly longer local parts (ultimately limited
by the total length of a DNS fqdn when combined with the relevant
suffix derived from the domain part).
I think this is vast overkill for a rarely-needed use case, but I'm open to
hear where people think LHS names longer than 35 characters are used in places
where S/MIME or PGP are also used.
That I agree with. I'd rather not do it if it is not a "real thing".
Paul
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
