Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting Format
RFC 6652
Document | Type |
RFC - Proposed Standard
(June 2012; No errata)
Updates RFC 4408
|
|
---|---|---|---|
Author | Scott Kitterman | ||
Last updated | 2018-12-20 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Murray Kucherawy | ||
Shepherd write-up | Show (last changed 2012-02-08) | ||
IESG | IESG state | RFC 6652 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Pete Resnick | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) S. Kitterman Request for Comments: 6652 Agari Updates: 4408 June 2012 Category: Standards Track ISSN: 2070-1721 Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting Format Abstract This memo presents extensions to the Abuse Reporting Format (ARF) and Sender Policy Framework (SPF) specifications to allow for detailed reporting of message authentication failures in an on-demand fashion. This memo updates RFC 4408 by providing an IANA registry for SPF modifiers. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6652. 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. Kitterman Standards Track [Page 1] RFC 6652 SPF Auth Failure Reporting June 2012 Table of Contents 1. Introduction ....................................................2 2. Definitions .....................................................3 2.1. Key Words ..................................................3 2.2. Imported Definitions .......................................3 3. Optional Reporting Address for SPF ..............................3 4. Requested Reports ...............................................4 4.1. Requested Reports for SPF Failures .........................5 5. IANA Considerations .............................................5 5.1. SPF Modifier Registration ..................................5 6. Security Considerations .........................................6 6.1. Identity Selection .........................................6 6.2. Report Volume ..............................................6 7. References ......................................................7 7.1. Normative References .......................................7 7.2. Informative References .....................................7 Appendix A. Acknowledgements .......................................8 Appendix B. Examples ...............................................8 B.1. SPF DNS Record for Domain That Sends No Mail but Requests Reports ...........................................8 B.2. Minimal SPF DNS Record Change to Add a Reporting Address ....................................................8 B.3. SPF DNS Record with Reporting Address, Report Percentage, and Requested Report Type ......................8 1. Introduction The Abuse Reporting Format [ARF] defines a message format for sending reports of abuse in the messaging infrastructure, with an eye toward automating both the generation and consumption of those reports. The Sender Policy Framework [SPF] is one mechanism for message sender authentication; it is "path-based", meaning it authenticates the route that a message took from origin to destination. The output is a verified domain name that can then be subjected to some sort of evaluation process (e.g., comparison to a known-good list, submission to a reputation service, etc.). This document extends [SPF] to add an optional reporting address and other parameters. Extension of [ARF] to add features required for the reporting of these incidents is covered in [ARF-AUTHFAIL] and [ARF-AS]. This document additionally creates a an IANA registry of [SPF] record modifiers to avoid modifier namespace collisions. Kitterman Standards Track [Page 2] RFC 6652 SPF Auth Failure Reporting June 2012 2. Definitions 2.1. Key Words The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",Show full document text