Re: [dmarc-ietf] Milestones changed for dmarc WG

Scott Kitterman <sklist@kitterman.com> Thu, 01 November 2018 05:27 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 16ABA123FFD for <dmarc@ietfa.amsl.com>; Wed, 31 Oct 2018 22:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] 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=tV0Z5Oa9; dkim=pass (2048-bit key) header.d=kitterman.com header.b=einG4a04
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 2iXWEgcH7ux4 for <dmarc@ietfa.amsl.com>; Wed, 31 Oct 2018 22:27:01 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B36B130E18 for <dmarc@ietf.org>; Wed, 31 Oct 2018 22:27:00 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1541050018; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=RjIFfbskHs7artUrbEtVZWC5Pl36gN0nU4Mg/lTK4k8=; b=tV0Z5Oa9tf6qCuXmg/JomxB8gmvFbnSq+RBnKIVbKBMM1ftClT/CxQtq JIs4ho51z8NB/+dmCkyPhlRyAWWYAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1541050018; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=RjIFfbskHs7artUrbEtVZWC5Pl36gN0nU4Mg/lTK4k8=; b=einG4a049dikjew3M+KM79P5CG5ibNE51/jPA6XQIl9LFo4NEBxn93RS MeZE2byNrBsrGAk/wILFgAOPK19f42R0zl73YwTo9LMSYXRMpyN0V6tUUW UHXU0iZSqpGGMjhOt6JK4d0VMuz3ubsJBFW+LI+Pga4tlF5JHxnRyAk20R DIsfRytmA5ux4/iJLnfNifU90pUPD3cc7QY6tgWo8/4P2GNx0fSUBeWxrQ XR6AN1wbuNpFCLUrotgUCBDBAbraAfVwZyy9LnxFeORQjyUgtb0NBu6kHP v+xe1L/Wky/WE+dbGo3KtXOUQs6ct2rZguIoDFxRWZ0CEd5UBbtSHQ==
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 mailout03.controlledmail.com (Postfix) with ESMTPSA id 9DBEEC4016F for <dmarc@ietf.org>; Thu, 1 Nov 2018 00:26:58 -0500 (CDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Thu, 01 Nov 2018 01:26:57 -0400
Message-ID: <1640642.kk4O4a0i58@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-158-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <20181031180450.7BCB32007D4B6C@ary.qy>
References: <20181031180450.7BCB32007D4B6C@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/J4vdryV4H40xXDRB6D0OtpcXPGM>
Subject: Re: [dmarc-ietf] Milestones changed for dmarc WG
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: Thu, 01 Nov 2018 05:27:03 -0000

On Wednesday, October 31, 2018 02:04:50 PM John Levine wrote:
> In article <82509274-BC89-495B-BD94-6D1F7846D8CA@kitterman.com> you write:
> >Is this milestone really done?  The protocol document references
> >draft-ietf-dmarc-arc-multi, which isn't done yet.  Doesn't it need to be
> >done too before this gets checked off (there is no separate milestone for
> >multi).
> 
> I gather there are practical issues: we don't see any way to do
> algorithm rotation in a way that is backward compatible with existing
> implemntations, and we'd like to publish something that matches the
> running code.

I think -18 of the protocol document does that reasonably well.  

I reviewed dkimpy with a view towards updating it from roughly -08 to -18 and 
it didn't need a lot of changes.  I did skip oldest-pass and related stuff 
since, per my last call comment, it seems superfluous as well as not extending 
the API to include passing in the connect IP address to include that, but 
there's no interoperability issue there.  Dkimpy 0.9.0 should interoperate 
with other -18 implementations.

Whether we leave this marked done and add a new one for multi or re-open this 
one, I don't care.  We ought to have some kind of milestone open against the 
residual work though.

Scott K