Re: [dmarc-ietf] Fwd: Proposed charter spiff to accept EAI clarification within email authentication stack

Scott Kitterman <sklist@kitterman.com> Tue, 22 January 2019 21:19 UTC

Return-Path: <sklist@kitterman.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 A8D081310FC for <dmarc@ietfa.amsl.com>; Tue, 22 Jan 2019 13:19:31 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=2Gxgb9oO; dkim=pass (2048-bit key) header.d=kitterman.com header.b=oQ/liU1m
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 V7zVudytO3ek for <dmarc@ietfa.amsl.com>; Tue, 22 Jan 2019 13:19:30 -0800 (PST)
Received: from softlayer.kitterman.com (softlayer.kitterman.com [169.62.11.132]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4488D1310F8 for <dmarc@ietf.org>; Tue, 22 Jan 2019 13:19:30 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201812e; t=1548191969; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=EEGdSqsZmYkToIc4W65P3S3X8nGbdYZ33/F25NUXtoA=; b=2Gxgb9oOmz1kHRdx3Zt5Tkkz63PGlFCORsjhOwK/OzLX907H59TRC4Zf sfF11eJAzJpI7rj0yn7y5i7JtnUSBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201812r; t=1548191969; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=EEGdSqsZmYkToIc4W65P3S3X8nGbdYZ33/F25NUXtoA=; b=oQ/liU1mpL8STvqioZM+RaMGVoASVyWtrmoxaauDQrxHZsVnJkFMcSuK W5tERWq+Sy9hQ7Xqo8ro4wCmjgRb6MaWfCdXeNr5jlRwfEEymQfX2BR92k dU+3RIz62GSdCoN5w5GUX7wt8vEND90WMQSjMQDv7QJLmeESZoyYwBwwKa h+QpSTQ0lR1r+L45o6IsxnYYIalaDTm0cBliefQbAP5R0OARzWUDqjPCGu jm7BZZJiQZkU2xa5IRF9AHEsAPt5IOzidEJlnk6oL0Tq5EvWvbcEqZuPQp fP/AE3gyFXKXyDqyOLsluuakJyf5XBRwgMCivuejoPZqW8u3EQGeVw==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by softlayer.kitterman.com (Postfix) with ESMTPSA id 5F1B22D404E4 for <dmarc@ietf.org>; Tue, 22 Jan 2019 15:19:29 -0600 (CST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 22 Jan 2019 16:19:28 -0500
Message-ID: <3742451.8nFmiOgACY@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-164-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAD2i3WO_YJhMC_xqATOW6eDePRx4Q0H+=xpaJm7=eK8sVfBiMw@mail.gmail.com>
References: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com> <5694407E-6D84-4266-93DE-21FB90D803B2@kitterman.com> <CAD2i3WO_YJhMC_xqATOW6eDePRx4Q0H+=xpaJm7=eK8sVfBiMw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mEf56cdVu-kHe3EUVuN3xKAkdIU>
Subject: Re: [dmarc-ietf] Fwd: Proposed charter spiff to accept EAI clarification within email authentication stack
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, 22 Jan 2019 21:19:32 -0000

For avoidance of doubt:

It's draft-ietf-dmarc-eaiauth and no.  It's fine.

Scott K

On Tuesday, January 22, 2019 10:08:41 AM Seth Blank wrote:
> Scott, does this need to be addressed during WGLC for draft-levine-eaiauth?
> 
> ---------- Forwarded message ---------
> From: Scott Kitterman <sklist@kitterman.com>
> Date: Sun, Nov 4, 2018 at 9:14 PM
> Subject: Re: [dmarc-ietf] Proposed charter spiff to accept EAI
> clarification within email authentication stack
> To: Kurt Andersen (b) <kboth@drkurt.com>
> Cc: dmarc@ietf.org <dmarc@ietf.org>
> 
> 
> 
> 
> On November 5, 2018 3:21:15 AM UTC, "Kurt Andersen (b)" <kboth@drkurt.com>
> 
> wrote:
> >This came out of this morning's DISPATCH meeting at IETF103 (
> >https://tools.ietf.org/wg/dispatch/agenda) to be able to accept
> >http://tools.ietf.org/html?draft=draft-levine-appsarea-eaiauth into the
> >WG
> >for advancing it to an RFC (probably informational).
> 
> Thanks.  It doesn't appear that it proposes any changes for SPF.  It merely
> documents that non-ascii local parts don't match the related macros.
> During the SPFbis working group we looked at this and explicitly decided on
> it.  It's not by accident.
> 
> Since local part macros are very rarely used, it seemed like very much a
> corner case not worth it to break the installed base over.
> 
> If there's going to be a charter change around this, I think it needs some
> words to constrain the work to limit interoperability implications.
> 
> I know less about the implications for DKIM and DMARC, but would imagine
> backward compatibility is important there too.
> 
> Scott K
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc