%% You should probably cite rfc5863 instead of this I-D.
@techreport{ietf-dkim-deployment-11,
    number =    {draft-ietf-dkim-deployment-11},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-dkim-deployment/11/},
    author =    {Ellen Siegel and Dave Crocker and Phillip Hallam-Baker and Tony Hansen},
    title =     {{DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations}},
    pagetotal = 51,
    year =      2010,
    month =     jan,
    day =       27,
    abstract =  {DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures, from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public key cryptography and using the domain name service as its key server technology. This permits verification of a responsible organization, as well as the integrity of the message content. DKIM will also provide a mechanism that permits potential email signers to publish information about their email signing practices; this will permit email receivers to make additional assessments about messages. DKIM's authentication of email identity can assist in the global control of "spam" and "phishing". This document provides implementation, deployment, operational, and migration considerations for DKIM. This document is not an Internet Standards Track specification; it is published for informational purposes.},
}