<chair-hat on> The drafts will be advanced with the same lookup mechanism. The process is defined in OPENPGP draft, the SMIME draft will follow OPENPGP lead in email address “transformation”.
Olafur > On Apr 2, 2015, at 9:40 AM, Christian Rößner > <[email protected]> wrote: > > Hi, > >> 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] > > Is this also an option for SMIMEA draft? > >> - 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] > > And is this also an option for the SMIMEA draft? > > Christian > -- > Bachelor of Science Informatik > Erlenwiese 14, 36304 Alsfeld > T: +49 6631 78823400, F: +49 6631 78823409, M: +49 171 9905345 > USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com > > _______________________________________________ > dane mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dane _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
