Re: [dmarc-ietf] We're ready with draft-ietf-dmarc-eaiauth

"John Levine" <johnl@taugh.com> Fri, 08 February 2019 22:54 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 765B0131067 for <dmarc@ietfa.amsl.com>; Fri, 8 Feb 2019 14:54:19 -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=UyWiWZEy; dkim=pass (1536-bit key) header.d=taugh.com header.b=NZpkj4bd
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 QI-fSFIwEGoY for <dmarc@ietfa.amsl.com>; Fri, 8 Feb 2019 14:54:18 -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 20123131066 for <dmarc@ietf.org>; Fri, 8 Feb 2019 14:54:18 -0800 (PST)
Received: (qmail 88635 invoked from network); 8 Feb 2019 22:54:16 -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=15a39.5c5e0898.k1902; bh=2Jd6vexsCrmBaPonuLhC/BfZc5fUpcDRBePN/CuDS14=; b=UyWiWZEyXMOqr2dyGMkoRiRZDwb1aPY/5yqXsJlGULbRklLHHWcX7aTH/h4xoHs2y4AVJ+ndI8+Dh60pAMKZ5zUYqyGgQBYvG/rfojQaDGHilyUXr/IdH1l7xNm3NeT/y2njBppJZPE869cvclTy7jAptoQXC5qD36TKqF21O6bErcaarpp6mT5g7Hm3jnk7XntK916cUEZRrL5AE5VxBzvZYciUq8DOLXhtFRh38F5DU96hkYvaV6RQvevyuZm8
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=15a39.5c5e0898.k1902; bh=2Jd6vexsCrmBaPonuLhC/BfZc5fUpcDRBePN/CuDS14=; b=NZpkj4bdfvmnh/KYUv9T48qJF+6MBqHB8IezdA3sB7FFHw3as7jiWeT1X+Kkz0vr1U26RDgX0NrsvRQWD1PrZj6S8IfCIakXGWSRcJhEz23MVkhBu+FClSQavD0UTJZ9NmymQUVL0TdOVs/tbfPMC82a3xtALROx6AltszFraneAe6FFLSXxWmUv8JCj8mIQMNELzd7kNt5D9sYLQOgHL7EO6uDR1K0KpZmFLKI53EGqloCkdpLjb2pyJixA3dCP
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; 08 Feb 2019 22:54:16 -0000
Received: by ary.qy (Postfix, from userid 501) id 628D9200DFF277; Fri, 8 Feb 2019 17:54:16 -0500 (EST)
Date: 8 Feb 2019 17:54:16 -0500
Message-Id: <20190208225416.628D9200DFF277@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: seth@sethblank.com
In-Reply-To: <CAD2i3WPm8VyRN7yCnQYNdpWLATb2XYaq-9jzOcmpcDNz6taSHQ@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/aDMrAuJqTyIxsOgx4E5LKen04ig>
Subject: Re: [dmarc-ietf] We're ready with draft-ietf-dmarc-eaiauth
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: Fri, 08 Feb 2019 22:54:19 -0000

In article <CAD2i3WPm8VyRN7yCnQYNdpWLATb2XYaq-9jzOcmpcDNz6taSHQ@mail.gmail.com> you write:
>> Does anyone have any issues to raise with draft-ietf-dmarc-eaiauth?
>> If I don't see anything within the next week, I will hit the "request
>> publication" button in the datatracker.

I have a version that fixes a few typos and has a new paragraph pointing
out that DKIM relaxed header canonicalization folds the header names to
lower case, but those names are still restricted to ASCII so nothing
changes.