{"draft":"draft-ietf-dkim-rfc4871bis-15","doc_id":"RFC6376","title":"DomainKeys Identified Mail (DKIM) Signatures","authors":["D. Crocker, Ed.","T. Hansen, Ed.","M. Kucherawy, Ed."],"format":["ASCII","HTML"],"page_count":"76","pub_status":"DRAFT STANDARD","status":"INTERNET STANDARD","source":"Domain Keys Identified Mail SEC","abstract":"DomainKeys Identified Mail (DKIM) permits a person, role, or\r\norganization that owns the signing domain to claim some\r\nresponsibility for a message by associating the domain with the\r\nmessage.  This can be an author's organization, an operational relay,\r\nor one of their agents.  DKIM separates the question of the identity\r\nof the Signer of the message from the purported author of the\r\nmessage.  Assertion of responsibility is validated through a\r\ncryptographic signature and by querying the Signer's domain directly\r\nto retrieve the appropriate public key.  Message transit from author\r\nto recipient is through relays that typically make no substantive\r\nchange to the message content and thus preserve the DKIM signature.\r\n\r\nThis memo obsoletes RFC 4871 and RFC 5672.  [STANDARDS-TRACK]","pub_date":"September 2011","keywords":["[--------]","email","architecture","abuse","verification","anti-abuse","identity","integrity","responsible","author","sender","originator","email filtering","anti-phishing","mail signature"],"obsoletes":["RFC4871","RFC5672"],"obsoleted_by":[],"updates":[],"updated_by":["RFC8301","RFC8463","RFC8553","RFC8616"],"see_also":["STD0076"],"doi":"10.17487\/RFC6376","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc6376"}