[dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-sender-01.txt

[Dave Crocker <[e-mail]>]

-------- Forwarded Message --------
Subject: New Version Notification for draft-crocker-dmarc-sender-01.txt
Date: Mon, 27 Jul 2020 05:16:07 -0700
From: [e-mail]
To: Dave Crocker <[e-mail]>


A new version of I-D, draft-crocker-dmarc-sender-01.txt
has been successfully submitted by Dave Crocker and posted to the
IETF repository.

Name:		draft-crocker-dmarc-sender
Revision:	01
Title:		DMARC Use of the RFC5322.Sender Header Field
Document date:	2020-07-27
Group:		Individual Submission
Pages:		8
URL: 
https://www.ietf.org/internet-drafts/draft-crocker-dmarc-sender-01.txt
Status:         https://datatracker.ietf.org/doc/draft-crocker-dmarc-sender/
Htmlized:       https://tools.ietf.org/html/draft-crocker-dmarc-sender-01
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-crocker-dmarc-sender
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-crocker-dmarc-sender-01

Abstract:
    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
    identifier.

    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.

 


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.

The IETF Secretariat



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net