Re: [dmarc-ietf] Definition of "value" in RFC8601

John Levine <johnl@taugh.com> Wed, 01 April 2020 00:11 UTC

Return-Path: <johnl@iecc.com>
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 969733A0DE8 for <dmarc@ietfa.amsl.com>; Tue, 31 Mar 2020 17:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.05
X-Spam-Level:
X-Spam-Status: No, score=0.05 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=ruBMd1kK; dkim=pass (1536-bit key) header.d=taugh.com header.b=UA/roSMP
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 vo3oG1J27tVt for <dmarc@ietfa.amsl.com>; Tue, 31 Mar 2020 17:11:39 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E75FB3A0DE7 for <dmarc@ietf.org>; Tue, 31 Mar 2020 17:11:38 -0700 (PDT)
Received: (qmail 23220 invoked from network); 1 Apr 2020 00:11:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5ab2.5e83dc39.k2003; bh=4yefw62ZRwH0OvAlC5YhvGVNBzLxstn1bvEr2ZFsZqs=; b=ruBMd1kKU96qf4LLg1Nj1TiEMlSdEM/y+oN+mq9JoYRxFOt4Ohj1TK7X7YvBTT+GajcE71GI904i9IX3W2XdXc6j0ItX6ii/f0LkvxzRpuQuIXzaTsFgVHa7znNQxjOUWwueofZOSCCsMWvZtOAj1yLsXedqbOfbskLWb6hvztQ5dJoujkWHbiQexj2+jWmJrXhpTbnaYQJYWtFVNItLElfWtXn4tdh+pYGiubDvhI0ZGwZowkboatxMPInTKumE
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5ab2.5e83dc39.k2003; bh=4yefw62ZRwH0OvAlC5YhvGVNBzLxstn1bvEr2ZFsZqs=; b=UA/roSMP+WlwfBEo71GlW35oyoDt+LRIJdDv5XH/NAxKWoFgDu3FtErUdThABpTP6paoal9i7MpPgcl+Kfp9djst2lP0GrgW1+L8PCIwM2rQ+V2iLSpndDLfn8uIkiyrpW/uDAok1Gpsz7iIKmx41NbEiuF0c8zpKFMI0GEYBPMHYl9fG6HVwIb+M7/ohd+iB70KAus1aylDVkHvjfuCv07yIAxc0GC+fHCOYG9dOyl+ca/5zPEcWjeSqY0IVPPu
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 01 Apr 2020 00:11:37 -0000
Received: by ary.qy (Postfix, from userid 501) id 6571D16D8E16; Tue, 31 Mar 2020 20:11:36 -0400 (EDT)
Date: 31 Mar 2020 20:11:36 -0400
Message-Id: <20200401001137.6571D16D8E16@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: rfc@arcsin.de
In-Reply-To: <db264415-fb82-9c2a-e78a-0118ff6a4368@arcsin.de>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Hocgi9dqKPNQ89lz81std2gFaRM>
Subject: Re: [dmarc-ietf] Definition of "value" in RFC8601
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: Wed, 01 Apr 2020 00:11:41 -0000

In article <db264415-fb82-9c2a-e78a-0118ff6a4368@arcsin.de> you write:
>> The intention in 8601 is pretty clear, even though the ABNF doesn't agree:
>
>Yes, the RFC says the authserv-id can contain UTF-8, but its author
>stated that he intended it to be "either a plain old ASCII domain name
>or an A-label". One does not need UTF-8 for that. If authserv-id were not
>
>> authserv-id = value
>
>but
>
>> authserv-id = token ; token from RFC2045
>
>wouldn't the author's intent have been covered as well, without any
>reference to RFC6531/6532?

You'll have to ask Murray what he meant, although as we've seen section 2.5
specifically says that an EAI authserv-id "may be expressed in UTF-8."

In an EAI message, an A-R header has to allow UTF-8 characters in
mailboxes, so it might as well allow them in other places including
domain names and the authserv-id.

R's,
John

PS: for anyone who might suggest one could "punycode" a mailbox, don't even think about it.