[New-wg-docs] I-D Action: draft-ietf-dmarc-sender-00.txt

internet-drafts@ietf.org Fri, 25 September 2020 14:44 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: new-wg-docs@ietf.org
Delivered-To: new-wg-docs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B02B3A0CA3 for <new-wg-docs@ietf.org>; Fri, 25 Sep 2020 07:44:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <new-wg-docs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160104507120.29586.5305899979498072709@ietfa.amsl.com>
Date: Fri, 25 Sep 2020 07:44:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-wg-docs/ozEgpmfvjjFbY6rIWE0fM6q9880>
Subject: [New-wg-docs] I-D Action: draft-ietf-dmarc-sender-00.txt
X-BeenThere: new-wg-docs@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <new-wg-docs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/new-wg-docs>, <mailto:new-wg-docs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/new-wg-docs/>
List-Post: <mailto:new-wg-docs@ietf.org>
List-Help: <mailto:new-wg-docs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/new-wg-docs>, <mailto:new-wg-docs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2020 14:44:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain-based Message Authentication, Reporting & Conformance WG of the IETF.

        Title           : DMARC Use of the RFC5322.Sender Header Field
        Author          : Dave Crocker
	Filename        : draft-ietf-dmarc-sender-00.txt
	Pages           : 8
	Date            : 2020-09-25

   Internet mail defines the RFC5322.From field to indicate the author
   of the message's content and the RFC5322.Sender field to indicate who
   initially handled the message.  The RFC5322.Sender field is optional,
   if it has the same information as the RFC5322.From field.  That is,
   when the RFC5322.Sender field is absent, the RFC5322.From field has
   conflated semantics, with both a handling identifier and a content
   creator identifier.  This was not a problem, until development of
   stringent protections on use of the RFC5322.From field.  It has
   prompted Mediators, such as mailing lists, to modify the RFC5322.From
   field, to circumvent mail rejection caused by those protections.

   This affects end-to-end behavior of email, between the author and the
   final recipients, because mail from the same author is not treated
   the same, depending on what path it followed.  In effect, the
   RFC5322.From field has become dominated by its role as a handling

   The current specification augments use of the RFC5322.From field, by
   enhancing DMARC to also use the RFC5322.Sender field.  This preserves
   the utility of RFC5322.From field while also preserving the utility
   of DMARC.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: