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

"John Levine" <johnl@taugh.com> Tue, 11 December 2018 00:45 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 7DD2C13133D for <dmarc@ietfa.amsl.com>; Mon, 10 Dec 2018 16:45:07 -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=Db0Eaz1+; dkim=pass (1536-bit key) header.d=taugh.com header.b=g0dprOi+
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 LZJ1M-hFTy_J for <dmarc@ietfa.amsl.com>; Mon, 10 Dec 2018 16:45:06 -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 E136F13133B for <dmarc@ietf.org>; Mon, 10 Dec 2018 16:45:05 -0800 (PST)
Received: (qmail 35607 invoked from network); 11 Dec 2018 00:45:02 -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=8b15.5c0f088e.k1812; bh=0yVluhjxgYo1SpDX9KzzVoipDtf1MT/IzWLKiJtozLo=; b=Db0Eaz1+lXiHgGWKAbxMyDizgnM+TlKtJL5AcbHAtLIXI/xUIJ5nciM5MqapnQDYEJ9zzXGDBCTYjbPTTJS8yLmOqngbUrjk5OpAO65jwQVAQEn0zn4rKaOoBFYZ5dprEObWlTg74CMq7nZtBAWxSjq+XgftO8eeggLvSOrPtWZIdYWejPbC3sKvU8CKFe3Q07ApeurwUsTmwfXXiLkCiIZZDBXjFwbXf0q4Opr4KVcTvxXEG4OTnVjp1DKWV4MH
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=8b15.5c0f088e.k1812; bh=0yVluhjxgYo1SpDX9KzzVoipDtf1MT/IzWLKiJtozLo=; b=g0dprOi+jtg8FwSAc17STsnRdAwWBmX/oRn+pMS6u2wjsQs/d266W6sft1POa7SI4fVSuvDHpMOaiAir97WwQ1zeSy/LRwDht86OzxJJWg4I+kgbsE8IiZJClwSSX6L/Ub622uo/RXT0QeP1SUnkBmVPB0Weup904PA5iL7YuAn3QCtvD3bnLo8qeN63BdfBek/bRwkKKMYrg7W5m9p3oYZW/Wchb77dP4pXYarTmXDk7h636hJfbkwqI515kplr
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:45:01 -0000
Received: by ary.qy (Postfix, from userid 501) id 81025200B3827D; Mon, 10 Dec 2018 19:45:00 -0500 (EST)
Date: 10 Dec 2018 19:45:00 -0500
Message-Id: <20181211004501.81025200B3827D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: kboth@drkurt.com
In-Reply-To: <CABuGu1qHrfOggr=zpc3xM12d7obzEGfvGgET4U_iSE0aU1OChg@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/a6qqi-Vk9uob_1sUksA-d2ccKks>
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:45:07 -0000

In article <CABuGu1qHrfOggr=zpc3xM12d7obzEGfvGgET4U_iSE0aU1OChg@mail.gmail.com> you write:
>> AIUI, local parts don't get puny-coded.
>
>Even when attempting to look them up via the macro mechanism?

No, never.  There is no way to re-code a UTF-8 local part.  Don't even
ask.

If it sounds like I've had this argument before, I have and I really
don't want to have it again.

R's,
John

PS: even if we were to invent some crock like turning UTF-8 into hex,
it would not work because there are a vast number of ways to encode
strings in UTF-8 that look identical, and there is no plausible way to
normalize them all.  It's not like ASCII case folding.