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

Scott Kitterman <sklist@kitterman.com> Tue, 30 October 2018 18:47 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 9E5B3130DCD for <dmarc@ietfa.amsl.com>; Tue, 30 Oct 2018 11:47:33 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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=QfUe6J//; dkim=pass (2048-bit key) header.d=kitterman.com header.b=jFcvzD00
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 KOYH4AMvkFPj for <dmarc@ietfa.amsl.com>; Tue, 30 Oct 2018 11:47:32 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0FD9127333 for <dmarc@ietf.org>; Tue, 30 Oct 2018 11:47:32 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1540925251; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : date : subject : from; bh=1Jg+sN25HQxVDFOW2jlQKpP7JI9Qc/I3qAHDF6sGECQ=; b=QfUe6J//4IPFNp3yCdKWw85JP4UxolhcLkl6SH9grEK2RdqXhqgkmNxq 2lTTzGr2wpY1l1PDiGo8qHGgzQHPCg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1540925251; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : date : subject : from; bh=1Jg+sN25HQxVDFOW2jlQKpP7JI9Qc/I3qAHDF6sGECQ=; b=jFcvzD00R/r50GrIzO2UdgTghasAKE8S5R3U9B8F7n/4Y1JREH8+12jm v9ETOpPzmGW/oMRB61lIY6W5x1/vu6Z0tFAq5v0ZFAt0cse9f8HbklskLj C5gRwa3xficBU4kXc+Q9P4xp5xBhabarlwH99J/Qx+C4oc6tc6yZ9yJvaZ znD5rXR2Ojmt3SbnoZD8fYv48w0Y3voVe+5JSeaIl3+niyJOTzK37mGk11 Y5uphmNzEhMuIeo5ipQ/EomRNr9ZQWv1rJM3dyZPVraEmwEvzjF+JAmCOd wNf6JdNq8BE0Qxz2hvVkI0c0C++Ud7A5OAEq72zmhIc5NaO5E67tyg==
Received: from [10.114.157.227] (mobile-166-170-29-135.mycingular.net [166.170.29.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 47B99C4027F; Tue, 30 Oct 2018 13:47:31 -0500 (CDT)
Date: Tue, 30 Oct 2018 18:47:23 +0000
In-Reply-To: <154046776431.16354.10167967721898242672.idtracker@ietfa.amsl.com>
References: <154046776431.16354.10167967721898242672.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dmarc@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <82509274-BC89-495B-BD94-6D1F7846D8CA@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Uh2z6_WBeYG9YNSy3-63_WXQ7Xw>
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: Tue, 30 Oct 2018 18:47:34 -0000

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).

Scott K

On October 25, 2018 11:42:44 AM UTC, IETF Secretariat <ietf-secretariat-reply@ietf.org> wrote:
>Changed milestone "Complete Authenticated Received Chain (ARC) protocol
>spec", resolved as "Done".