Since I have never been in the camp of believing that the email matching problem has been solved, I have not really looked very hard at these drafts. However, in the process of getting updates to S/MIME ready I got an item pinged into my mind that they probably need to address. How are the capabilities of an S/MIME client for encryption to be obtained as part of this query? Today getting a signed message will provide those capabilities, it is possible to put them into a certificate (RFC 4262) but this has problems when they change (you need to get a new certificate) and LDAP has the userSMIMECertificate field which contains both the certificates and the capabilities.
Since knowing what content encryption algorithm is supported can be considered critical, this should be covered in the draft. Jim > -----Original Message----- > From: dane [mailto:[email protected]] On Behalf Of Paul Hoffman > Sent: Friday, July 08, 2016 8:36 AM > To: [email protected] > Subject: [dane] draft-ietf-dane-smime-11.txt > > Greetings. Jakob and I have made a large number of changes to draft-ietf-dane- > smime to incorporate the related WG changes that were made to draft-ietf- > dane-openpgpkey during its last calls. We think > draft-ietf-dane-smime-11 is ready for WG Last Call and progression. > > --Jakob Schlyter and Paul Hoffman > > _______________________________________________ > dane mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dane _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
