Re: [dmarc-ietf] AD review of draft-ietf-dmarc-rfc7601bis-03.txt

"John Levine" <johnl@taugh.com> Sat, 27 October 2018 16:20 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 F2025130DF1 for <dmarc@ietfa.amsl.com>; Sat, 27 Oct 2018 09:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=okTvRIaA; dkim=pass (1536-bit key) header.d=taugh.com header.b=mK2iiTNt
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 M2fHL7v-Hthe for <dmarc@ietfa.amsl.com>; Sat, 27 Oct 2018 09:20:36 -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 CAFE6127332 for <dmarc@ietf.org>; Sat, 27 Oct 2018 09:20:35 -0700 (PDT)
Received: (qmail 13707 invoked from network); 27 Oct 2018 16:20:33 -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=357d.5bd49051.k1810; bh=ItCimo1vYsSehkmqhhr8vhMSg95gGZ6t1CYfivtNcY0=; b=okTvRIaA80c5RIUAKKbfHw5o74bmt7eQZ5vCyIFpDdsl+YukgWy1saEucp8l+lhdLKkhch7xQTeM7cNjA/Vdj7yAxK0pLsQjMep7ijY59hh6z2cSmmiCI6PeoAmQf0dc/ax5APRXKtJMXpD/oNDmIbQfo1ajdgbojMDG8TLqSA4C4e4e0mRJSbKT5KCCx32YYU9dRdfM8Sut3C3EXwOuik8KQ28WDsYidcTgeP/v3dKAsgljkvKJwkIAIw+bGfim
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=357d.5bd49051.k1810; bh=ItCimo1vYsSehkmqhhr8vhMSg95gGZ6t1CYfivtNcY0=; b=mK2iiTNtwTVSk3tZDCs8ATPYci8G/pC5gFizYWqFocN8z3oqK+SbNS1bE7NO9wdFXPRmyiKUZoV/Bi1so1t4QTeEjgMlEX5c+goNS26gT6HT9s7nvt5Etqstp6MBPrnZumN07/iGl1OMF/qUM/v21qy1fZrgf26Rq9mLFPZX466cQPldEaJZFV0R3gk5/MaXG2FIl49CJyagwAZ+c+KlRTombxhhxcYgGLEgLfis0iyRCFGEJwaj8WAVJ989igoW
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; 27 Oct 2018 16:20:33 -0000
Received: by ary.qy (Postfix, from userid 501) id 1C98620072999E; Sat, 27 Oct 2018 12:20:32 -0400 (EDT)
Date: 27 Oct 2018 12:20:32 -0400
Message-Id: <20181027162033.1C98620072999E@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: alexey.melnikov@isode.com
In-Reply-To: <3eea2f77-8aea-4f49-80f3-d96b639c378a@isode.com>
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/Yt808HuOr8Ribk-FcvWA_S0daRw>
Subject: Re: [dmarc-ietf] AD review of draft-ietf-dmarc-rfc7601bis-03.txt
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: Sat, 27 Oct 2018 16:20:37 -0000

In article <3eea2f77-8aea-4f49-80f3-d96b639c378a@isode.com>; you write:
>   Note that in an EAI-formatted message, this identifier may be
>         expressed in UTF-8.
>
>So I decided to check whether this statement is actually true.

Oops.

>OLD:
>
>"value" is as defined in Section 5.1 of [MIME].
>
>NEW:
>
>"value" is as defined in Section 5.1 of [MIME], with "quoted-string" 
>updated as specified in RFC 6532.

That seems the smallest adequate fix.  In general EAI allows UTF-8 in
fields that humans look at, but not ones just for computers like
message-IDs.  The alternative would be to leave the old text and add a
note that says in the common case that the identifier is a domain
name, IDNs are represented as A-labels.

R's,
John