Hi, > As for hash vs. base32, if more providers are likely to support > base32, so be it. The sticking point is lower-case lookup, not > whether the result is hashed or base32 encoded.
Full ack! I must admit I personally would prefer hashing for its simplicity, chopped sha256 really is easy to implement in basically all languages including shell scripts. The need to split some localparts in two records adds complexity and I don't see the benefits. But I don't have real objections against base32, as long as the tolower() part remains. To have the full benefits base32 might have over hashing, I think the additional lookup of the original form would have to be a MUST then, so people really wanting to implement some clever lookup server side (which I currently dont really expect to happen, it simply doesn't make sense as a PGP key has a fixed set of user IDs and those should be the lookup targets, simple as that) can do so. Regarding adding dots every few bytes: if people really fear big Zonefiles that would be an option I also would not object. But again I don't really see the problem it wants to solve, really big providers will most probably do live signing on request... Greetings, Florian -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstrasse 15, 81669 Muenchen Sitz der Gesellschaft: Muenchen, Amtsgericht Muenchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
