RFC 9057 on Email Author Header Field

rfc-editor@rfc-editor.org Wed, 23 June 2021 06:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C433A2B2C for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jun 2021 23:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 66Ingn9J8Ldh for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jun 2021 23:03:42 -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 1545D3A2B28 for <ietf-announce@ietf.org>; Tue, 22 Jun 2021 23:03:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 29BABF4076C; Tue, 22 Jun 2021 23:03:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNTcgb24gRW1haWwgQXV0aG9yIEhlYWRlciBGaWVsZA==?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20210623060336.29BABF4076C@rfc-editor.org>
Date: Tue, 22 Jun 2021 23:03:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/_HPGf3Lwboswr3q9RFvNMu4GmAg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2021 06:03:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9057

        Title:      Email Author Header Field 
        Author:     D. Crocker
        Status:     Experimental
        Stream:     Independent
        Date:       June 2021
        Mailbox:    dcrocker@bbiw.net
        Pages:      7
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-crocker-email-author-04.txt

        URL:        https://www.rfc-editor.org/info/rfc9057

        DOI:        10.17487/RFC9057

Internet mail defines the From: header field to indicate the author
of the message's content and the Sender: field to indicate who
initially handled the message on the author's behalf. The Sender:
field is optional if it has the same information as the From: field.
This was not a problem until development of stringent protections on
use of the From: field. It has prompted Mediators, such as mailing
lists, to modify the From: field to circumvent mail rejection caused
by those protections. In effect, the From: field has become dominated
by its role as a handling identifier.

The current specification augments the altered use of the From: field
by specifying the Author: field, which ensures identification of the
original author of the message and is not subject to modification by
Mediators. This document is published as an Experimental RFC to
assess community interest, functional efficacy, and technical
adequacy.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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