Re: [dmarc-ietf] Identification of an email author (was - Re: IETF Mailing Lists and DMARC)

ned+ietf@mauve.mrochek.com Mon, 07 November 2016 23:16 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2EE129BE1 for <ietf@ietfa.amsl.com>; Mon, 7 Nov 2016 15:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, 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 Uh20NVV6YlQp for <ietf@ietfa.amsl.com>; Mon, 7 Nov 2016 15:16:41 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5086E129BC2 for <ietf@ietf.org>; Mon, 7 Nov 2016 15:16:41 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01Q71GG4Z9JK01494D@mauve.mrochek.com> for ietf@ietf.org; Mon, 7 Nov 2016 15:12:30 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; Format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01Q6VN8T9668011H9Q@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 07 Nov 2016 15:12:27 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01Q71GG3KUM8011H9Q@mauve.mrochek.com>
Date: Mon, 07 Nov 2016 15:08:08 -0800
Subject: Re: [dmarc-ietf] Identification of an email author (was - Re: IETF Mailing Lists and DMARC)
In-reply-to: "Your message dated Mon, 07 Nov 2016 14:46:54 -0800" <969d43d4-78c9-6e44-e186-ca6ed6fa3445@dcrocker.net>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> <CABa8R6vHdt75NFKW3s6xOzLcq=jmVAHDPX0tjLRdGpYSTP2cYA@mail.gmail.com> <33b100ac-c035-8b49-22e1-edbe47f41919@dcrocker.net> <CABa8R6u7WbbeXzkhkNM46RYtMSw7V9FT2m_LvKLHaFDvF3cw3A@mail.gmail.com> <CO2PR00MB0103566D260F9BFEC7166C9B96A20@CO2PR00MB0103.namprd00.prod.outlook.com> <5FA03832-D38F-47F2-B974-7C903C7513FD@fugue.com> <CO2PR00MB01034350A8C90A1E039336F796A20@CO2PR00MB0103.namprd00.prod.outlook.com> <WM!9664810c615567bf070fc649d954183e561aaa67977ebde37433238a98da7930f34ca08db8c430e48500f1e63f6d7622!@mailstronghold-1.zmailcloud.com> <713098835.18678872.1478547678821.JavaMail.zimbra@peachymango.org> <969d43d4-78c9-6e44-e186-ca6ed6fa3445@dcrocker.net>
To: Dave Crocker <dcrocker@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9OvbZofhiYhggKokpYbvUvnogjs>
Cc: dmarc@ietf.org, IETF <ietf@ietf.org>, Terry Zink <tzink@exchange.microsoft.com>, Franck Martin <franck@peachymango.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2016 23:16:42 -0000

> On 11/7/2016 11:41 AM, Franck Martin wrote:
> > The EAI WG found it was fine to remove the obligation to have an email
> > address part in the mandatory RFC5322.From header, leaving only the
> > display part to assert the original author.

> We had that relaxed permission for From:, in the original
> From/Sender/Reply-to specification of rfc733, with the requirement that
> there be a Sender: email address.  It looks like we removed it for rfc822.

> And while I recall something of the EAI discussion, I'm not recalling
> this permission's being returned.  Nor am I finding it in rfc6854:

>       https://tools.ietf.org/html/rfc6854#section-2

> So, please point to the formal specification that permits a From: field
> to have no email address.

RFC 6854.

> Absent that, there's the small question about how the EAI group would
> have the authority to make such a major change to such a basic email
> feature...

RFC 6854 can speak for itself as to the rationale for allowing no address.

The EAI connection was, as I recall, for use in downgrade formats used to
present EAI messages to non-EAI clients via POP3 and IMAP4.

				Ned