Extensions to DKIM for Failure Reporting
draft-ietf-marf-dkim-reporting-10
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (marf WG)
|
|
Author |
|
Murray Kucherawy
|
|
Last updated |
|
2011-06-10
(latest revision 2011-05-15)
|
|
Replaces |
|
draft-kucherawy-dkim-reporting
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Waiting for WG Chair Go-Ahead
Doc Shepherd Follow-up Underway
|
|
Document shepherd |
|
Barry Leiba
|
IESG |
IESG state |
|
AD is watching
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Pete Resnick
|
|
Send notices to |
|
marf-chairs@tools.ietf.org, draft-ietf-marf-dkim-reporting@tools.ietf.org
|
MARF Working Group M. Kucherawy
Internet-Draft Cloudmark
Intended status: Standards Track February 12, 2012
Expires: August 15, 2012
Extensions to DKIM for Failure Reporting
draft-ietf-marf-dkim-reporting-10
Abstract
This memo presents extensions to the DomainKeys Identified Mail
(DKIM) specification to allow for detailed reporting of message
authentication failures in an on-demand fashion.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 15, 2012.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Kucherawy Expires August 15, 2012 [Page 1]
Internet-Draft DKIM Reporting Extensions February 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Imported Definitions . . . . . . . . . . . . . . . . . . . 4
2.3. Other Definitions . . . . . . . . . . . . . . . . . . . . 4
3. Optional Reporting for DKIM . . . . . . . . . . . . . . . . . 5
3.1. Extension DKIM Signature Tag . . . . . . . . . . . . . . . 5
3.2. DKIM Reporting TXT Record . . . . . . . . . . . . . . . . 5
3.3. DKIM Reporting Algorithm . . . . . . . . . . . . . . . . . 6
4. Optional Reporting Address for DKIM-ADSP . . . . . . . . . . . 9
5. Requested Reports . . . . . . . . . . . . . . . . . . . . . . 11
5.1. Requested Reports for DKIM Failures . . . . . . . . . . . 11
5.2. Requested Reports for DKIM ADSP Failures . . . . . . . . . 11
6. Report Generation . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Report Format . . . . . . . . . . . . . . . . . . . . . . 13
6.2. Other Guidance . . . . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7.1. DKIM Signature Tag Registration . . . . . . . . . . . . . 14
7.2. DKIM ADSP Tag Registration . . . . . . . . . . . . . . . . 14
7.3. DKIM Reporting Tag Registry . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8.1. Inherited Considerations . . . . . . . . . . . . . . . . . 16
8.2. Deliberate Misuse . . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . . 18
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 19
Appendix B. Examples . . . . . . . . . . . . . . . . . . . . . . 20
B.1. Example Use of DKIM Signature Extension Tag . . . . . . . 20
B.2. Example DKIM Reporting TXT Record . . . . . . . . . . . . 20
B.3. Example Use of DKIM ADSP Extension Tags . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
Kucherawy Expires August 15, 2012 [Page 2]
Internet-Draft DKIM Reporting Extensions February 2012
1. Introduction
[DKIM] introduced a mechanism for message signing and authentication.
It uses digital signing to associate a domain name with a message in
a reliable (i.e. not forgeable) manner. The output is a verified
domain name that can then be subjected to some sort of evaluation
process (e.g., advertised sender policy, comparison to a known-good
Show full document text