[dmarc-ietf] RFC 8601 on Message Header Field for Indicating Message Authentication Status
rfc-editor@rfc-editor.org Fri, 31 May 2019 20:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF9212010D; Fri, 31 May 2019 13:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8qXTILk0LBx; Fri, 31 May 2019 13:47:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C1B120058; Fri, 31 May 2019 13:47:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6A33EB81FDC; Fri, 31 May 2019 13:47:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmarc@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190531204745.6A33EB81FDC@rfc-editor.org>
Date: Fri, 31 May 2019 13:47:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IOSofwLMMvtVlcbGl5RWxDWHyqA>
Subject: [dmarc-ietf] RFC 8601 on Message Header Field for Indicating Message Authentication Status
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2019 20:47:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8601
Title: Message Header Field for Indicating
Message Authentication Status
Author: M. Kucherawy
Status: Standards Track
Stream: IETF
Date: May 2019
Mailbox: superuser@gmail.com
Pages: 54
Characters: 122384
Obsoletes: RFC 7601
I-D Tag: draft-ietf-dmarc-rfc7601bis-06.txt
URL: https://www.rfc-editor.org/info/rfc8601
DOI: 10.17487/RFC8601
This document specifies a message header field called
"Authentication-Results" for use with electronic mail messages to
indicate the results of message authentication efforts. Any
receiver-side software, such as mail filters or Mail User Agents
(MUAs), can use this header field to relay that information in a
convenient and meaningful way to users or to make sorting and
filtering decisions.
This document obsoletes RFC 7601.
This document is a product of the Domain-based Message Authentication, Reporting & Conformance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC