Re: [dmarc-ietf] Errors in RFC 8601, was Question about changes introduced by erratum

Damian Lukowski <rfc@arcsin.de> Sun, 22 March 2020 19:33 UTC

Return-Path: <rfc@arcsin.de>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8618F3A0862 for <dmarc@ietfa.amsl.com>; Sun, 22 Mar 2020 12:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arcsin.de
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 zSwPJIU0aQ7Q for <dmarc@ietfa.amsl.com>; Sun, 22 Mar 2020 12:33:50 -0700 (PDT)
Received: from scalar.arcsin.de (scalar.arcsin.de [185.162.250.16]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C655B3A085B for <dmarc@ietf.org>; Sun, 22 Mar 2020 12:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=arcsin.de; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:date:date:message-id:from :from:references:subject:subject:x-amavis-category; s=dkim01; t= 1584905624; x=1586720025; bh=4bycgEnM8XKjEohaK6cjjJGhBhzxMnbVFLB AfOr9XBw=; b=a6uP5+E8xN5CTSYTFfNxzNxo8n9QQrLhDimk8Q06i34tDWk1zkx YO2zrRyspJ4gZkfW6WlpZCVX5uGbCF9awAB4CSnEhNUdoHs819SW997YTyXUGEfA TcY9TESZcMafEcqrcvftL/P83FPKY9VJdF4H//fMXxbhKb1Ciqv5d82k=
X-Amavis-Category: scalar.arcsin.de; category=CleanTag
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20200322154438.14E02166129A@ary.qy>
From: Damian Lukowski <rfc@arcsin.de>
Message-ID: <09ec8dda-7165-fae8-f8e1-f88561085e47@arcsin.de>
Date: Sun, 22 Mar 2020 20:34:11 +0100
MIME-Version: 1.0
In-Reply-To: <20200322154438.14E02166129A@ary.qy>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BPNeCtgdN2UBxAFiKn2Hje2D0r8>
Subject: Re: [dmarc-ietf] Errors in RFC 8601, was Question about changes introduced by erratum
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2020 19:33:53 -0000

> RFC8601 sec 2.7.2 refers to RFC 7208 for "mailfrom".  RFC 7208 sec 1.1.3
> says that the MAIL FROM, which I whink we can assume is the same thing,
> is the RFC5321.MailFrom from RFC 5598.  RFC 5598 says that's a mailbox,
> not a domain name.

Those definitions are too confusing for me. RFC5598 says

> RFC5321.MailFrom is the address in the SMTP "Mail From" command

So is RFC5321.MailFrom the Reverse-Path from RFC5321, or only the
Mailbox part of a Reverse-Path? I would expect it to be the full
Reverse-path, because

> RFC5321.Return-Path:  Set by - Originator
>  The MDA records the RFC5321.MailFrom address into the
>  RFC5321.Return-Path field.

and a Return-Path field usually contains "<" ... ">", so it cannot be a
plain Mailbox.

But then the term "MAIL FROM" in
>    As such, throughout this document the term "MAIL FROM" will be used,
>    which is defined as the RFC5321.MailFrom (reverse-path) identity
>    described in [RFC5598].

cannot be identical to RFC5321.MailFrom, because if it were, we would
have smtp.mailfrom = "MAIL FROM" = RFC5321.MailFrom = "<" ... ">",
which is not given by the examples.

Another possibility to interpret the quote is that one obtains the "MAIL
FROM" by picking "the" identity out of the RFC5321.MailFrom. But there
are two sensible identities defined in RFC5598 that one could pick: The
mailbox or the domain name.

> The forms of identity used by Internet Mail are: mailbox, domain
> name, [...]

By the way, an RFC5321 mailbox allows address-literals which are not
covered by the right hand side of RFC8601's pvalue, and one cannot use
the left hand side because of

> If the value portion of a "pvalue" construction identifies something
> intended to be an email identity, then it MUST use the right-hand
> portion of that ABNF definition.