RFC 6577: Authentication-Results Registration Update for Sender Policy Framework (SPF) Results
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7001.
Current document in this lineage: RFC 8601 — Message Header Field for Indicating Message Authentication Status
In plain English — editorial summary, not part of the RFC
This memo updates the registry of authentication method results in Authentication-Results: message header fields, correcting a discontinuity between the original registry creation and the Sender Policy Framework (SPF) specification. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6577
- Published
- March 2012
- Authors
- M. Kucherawy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Read the full history of Message Header Field for Indicating Message Authentication Status →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6686Resolution of the Sender Policy Framework (SPF) and Sender ID ExperimentsCurrent
July 2012
- RFC 7070An Architecture for Reputation ReportingCurrent
November 2013
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 6008Authentication-Results Registration for Differentiating among Cryptographic ResultsCurrent
September 2010
- RFC 7208Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1Updated
April 2014
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?