IETF Logo Mail Archive

Re: [dmarc-ietf] Recommend adoption of draft-levine-appsarea-eaiauth as WG work

"John Levine" <johnl@taugh.com> Tue, 11 December 2018 00:42 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 0DC5E13133D for <dmarc@ietfa.amsl.com>; Mon, 10 Dec 2018 16:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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.001, SPF_PASS=-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=54eo4MKr; dkim=pass (1536-bit key) header.d=taugh.com header.b=BKlbk6/S
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 w1Psjsr1AaqD for <dmarc@ietfa.amsl.com>; Mon, 10 Dec 2018 16:42:42 -0800 (PST)
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 8C47D12DD85 for <dmarc@ietf.org>; Mon, 10 Dec 2018 16:42:42 -0800 (PST)
Received: (qmail 35017 invoked from network); 11 Dec 2018 00:42:40 -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=88c7.5c0f0800.k1812; bh=3Zg7pO6heB4cRdeeOhbDMVj0Y6auXB+drMZ+cbyIanE=; b=54eo4MKrK0qlKwiSlI0opfiK3ib6tlmh1Y2orvDe3yZ37xS8YiDWTchXtPPjCmVuzAGO/jHiYidP3foJBmg2vu/MkdlsKw5zJf2y9ZTAvd7MU8LUEq7mSegtvYnL/mzmjAB9LRaUKsdZWAjntIe+98odWbshJJ5NRxES13u/M+jfvmSYOKfnsIifyeqdiS5y+sr4qjh9dYa9kpUqFgmZ6Wb+ABk9MQJw2nfyG7LDbhzfRs+LUc0Feh1ukfz5comy
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=88c7.5c0f0800.k1812; bh=3Zg7pO6heB4cRdeeOhbDMVj0Y6auXB+drMZ+cbyIanE=; b=BKlbk6/Src6HSwEz/AAY8bjPEWiPrMS15jEJzjy6dYDmIzIo/AVDLFOz3kmeVnwdNI49QrCn271gR2pMSy3qphgkfpEF1xWgDLMxUsXf/jtDoS6E5uH9A3FYkY8osgcPGGxwsX7hNjssUgd1JzaCdv+wNEHSK3mqj9Z1L12gQBzEZN+mQu86DoYkg+BGb7to3WuKOiuPCxp1TJjhmjkF0LbamsM52HrzPthtIeyo0yQhvraAEqC9GSwa1iF9r70B
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; 11 Dec 2018 00:42:40 -0000
Received: by ary.qy (Postfix, from userid 501) id 52F9F200B3823D; Mon, 10 Dec 2018 19:42:39 -0500 (EST)
Date: Mon, 10 Dec 2018 19:42:39 -0500
Message-Id: <20181211004240.52F9F200B3823D@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: kboth@drkurt.com
In-Reply-To: <CABuGu1rP9Udnzw4Ox1O501+OQc1LeHrQ1BUGGytCU8=-iiyL8w@mail.gmail.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/cPELowrL3g-LlnN38njqIlVBDv8>
Subject: Re: [dmarc-ietf] Recommend adoption of draft-levine-appsarea-eaiauth as WG work
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: Tue, 11 Dec 2018 00:42:44 -0000

In article <CABuGu1rP9Udnzw4Ox1O501+OQc1LeHrQ1BUGGytCU8=-iiyL8w@mail.gmail.com> you write:
>> what was  already implicit; s and l macros will never match if the local
>> part of the email address contains non-ascii characters.
>>
>
>Why not? If the non-ASCII (or non-7bit) characters are puny-coded, it seems
>like they should be able to match without any problems.

No.  No, no, no, no.

In EAI mail, e-mail address local parts are UTF-8.  You cannot
translate them into anything else and you very specifically cannot
"punycode" them.

Using the term punycode in IDNA2003, which is obsolete, was a serious
mistake, since it led people to all sorts of bogus conclusions.

In IDNA2008 domain names, and only in domain names, there are U-labels
which contain a large subset of UTF-8 encoded Unicode, and there are
A-labels which consist of ASCII starting with XN--.  There is a
two-way algorithm to convert between U-labels and A-labels.  There is
no punycode.

R's,
John

v2.23.0 | Report a Bug | By Email