[rfc-dist] 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: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F07120058 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 31 May 2019 13:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 b2ip3dcOHtwZ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 31 May 2019 13:47:52 -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 014FF1200FF for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 31 May 2019 13:47:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 18C4AB81FDF; Fri, 31 May 2019 13:47:46 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
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
Message-Id: <20190531204745.6A33EB81FDC@rfc-editor.org>
Date: Fri, 31 May 2019 13:47:45 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8601_on_Message_Header_Field_for_Indica?= =?utf-8?q?ting_Message_Authentication_Status?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dmarc@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org