Section 3.1 has lots of factually incorrect rationals for encoding using base32. The DNS is capable of encoding binary data in labels up to 63 octets. I've got no problem with encoding, but if one intends to include rationalisations please make them factually correct.
There is no mention of how to encode LHS which exceed 63 octets when encoded using base32. Pack the left most labels or the right most labels? There is no mention of how to normalise LHS prior to base32 encoding. Are "Hugh" and "hugh" the same? Should "hugh" and "hugh+xxx" be treated the same? It should be possible to specify normalisation rules and store them at _openpgpkey. Is the input UTF-8 or some other character set. If UTF-8 what normalisations need to be applied? It might be useful to suppress the padding at the end of base32 encoded strings. We already do similar suppression with NSEC3 records. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
