%% You should probably cite draft-ietf-dane-smime instead of this I-D.
@techreport{hoffman-dane-smime-03,
    number =    {draft-hoffman-dane-smime-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hoffman-dane-smime/03/},
    author =    {Paul E. Hoffman and Jakob Schlyter},
    title =     {{Using Secure DNS to Associate Certificates with Domain Names For S/MIME}},
    pagetotal = 6,
    year =      2012,
    month =     mar,
    day =       9,
    abstract =  {S/MIME uses certificates for authenticating and encrypting messages. Users want their mail user agents to securely associate a certificate with the sender of an encrypted and/or signed message. DNSSEC provides a mechanism for a zone operator to sign DNS information directly. This way, bindings of certificates to users within a domain are asserted not by external entities, but by the entities that operate the DNS. This document describes how to use secure DNS to associate an S/MIME user's certificate with the intended domain name. IMPORTANT NOTE: This draft is intentionally sketchy. It is meant as a possible starting point for the DANE WG if it wants to consider making a protocol similar to TLSA, as described in draft-ietf-dane-protocol, but that applies to S/MIME. The WG may or may not want to adopt such work, or if it does, may want to use a very different scheme from the one described here.},
}