I have updated draft-ietf-dane-openpgpkey
Latest version: http://tools.ietf.org/html/draft-ietf-dane-openpgpkey-03 Diff: http://www.ietf.org/rfcdiff?url1=draft-ietf-dane-openpgpkey-02&url2=draft-ietf-dane-openpgpkey-03 Items changed: - SHA-224 changed to SHA-256 truncated at 28 octets. It was indicated that SHA224 is the black sheep of the SHA2 (FIPS) family and is also not part of the Microsoft CryptoAPI. [various people including Stephen Farrell and Sean Leonard] - Clarify the local part should be in UTF-8/ASCII encoding [Wil Tan] - Lowercase before hash - as there seems to be consensus that all email servers in real life deployments do not have different mailboxes for different case ([email protected] vs [email protected]). This avoids the most common problem of webforms and phone virtual keyboards automatically capitalizing the first letter of a recognised name. [based on John Levine's input] - Forbid any other kind of attempt at guessing or rewriting the local-part [based on the many people present at the Dallas DANE meeting] - Added a section more clearly documenting the usage of OPENPGPKEY and updating the Introduction section [result of discussion with Paul Hoffman] - Do not allow replacing/adding local key stores without user confirmation [Pieter Lexis] - Do not cache the record beyond its TTL [Pieter Lexis] - Point to the OpenPGP key ring section within the RFC, instead of just the RFC [based on feedback from Petr Spacek] _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
