IETF Logo Mail Archive

Re: [dmarc-ietf] Fwd: New Version Notification for draft-srose-dkim-ecc-00.txt

"John R Levine" <johnl@taugh.com> Fri, 07 April 2017 15:48 UTC

Return-Path: <johnl@taugh.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 EAA4112940A for <dmarc@ietfa.amsl.com>; Fri, 7 Apr 2017 08:48:35 -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=pass (1536-bit key) header.d=iecc.com header.b=SEpr7os+; dkim=pass (1536-bit key) header.d=taugh.com header.b=GCJlLg5P
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 inPPateg8JV3 for <dmarc@ietfa.amsl.com>; Fri, 7 Apr 2017 08:48:34 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C761294C2 for <dmarc@ietf.org>; Fri, 7 Apr 2017 08:48:33 -0700 (PDT)
Received: (qmail 92633 invoked from network); 7 Apr 2017 15:48:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=169d7.58e7b4c6.k1704; bh=oMI4vBkQL8DVM4fDu6YWBifQYQZWf3prUDVVohpuDiM=; b=SEpr7os+OWBQUdW6BzHJIz1atGx/gnUcbRiWH4YSx14QzJrrk2mmC3oZE7Hmk6VWgGGrXdaIxdE3hPYoLxPxClVOmA3DP5PuNZ/BrllR8D1ki97qYdzIGKsktz81h/hMSkEGQJc12PEHQMor4MAm73H6YNyNi0xkEh9qePdMLUh2iZLlqCAGeJrkQzacAiwDawV5XQhzqaa2Vt2VOqkP7qxJx65iQ0PgnZUt/c1s3t/vA/1TUtzMUfBQPyJ0N4DK
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=169d7.58e7b4c6.k1704; bh=oMI4vBkQL8DVM4fDu6YWBifQYQZWf3prUDVVohpuDiM=; b=GCJlLg5PjJqqwxyvToA3oCtJ3vwWgaQaJinvt73WSHeRXzb9cirnIO9IPidI5A/OrmaWNbSSbZbyPl+le5fSyAp4o3ddYEZ2mlVgLWKB+6tvHZM93Csdavv+lmxFJjwpq+I0LDJ44i436wvVeeLdArcsRrYgrE278kDHHt7eXtJ4PJKCh/2HFZoePG9eRJ9Op+VFJ7Q/CtFTVbeYxvM1DzHfAluEZRDnbQ4IQDpvpus6Ry8fr3J5tFtOHkkiQ4Rj
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 07 Apr 2017 15:48:22 -0000
Date: Fri, 07 Apr 2017 11:48:22 -0400
Message-ID: <alpine.OSX.2.20.1704071147200.55219@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Peter Goldstein <peter@valimail.com>
Cc: dmarc <dmarc@ietf.org>
In-Reply-To: <CAOj=BA2P5e1o-QsZGAxGCV6rM1D=sNiL_ciL4BDtMkbQU1tSXA@mail.gmail.com>
References: <d91de205-05b4-0b59-b3a3-568fc0f57375@corp.mail.ru> <20170406235815.47843.qmail@ary.lan> <CAOj=BA2P5e1o-QsZGAxGCV6rM1D=sNiL_ciL4BDtMkbQU1tSXA@mail.gmail.com>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Y0LoAfSxl4e3U7emzvhTQTalGO0>
Subject: Re: [dmarc-ietf] Fwd: New Version Notification for draft-srose-dkim-ecc-00.txt
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Apr 2017 15:48:36 -0000

> Does this initiative include an intention to update the cryptographic
> guidance from RFC 6376 sections 3.3 and 3.3.3 ?  The proposed charter
> speaks of adding new algorithms, but doesn't discuss deprecating/removing
> old ones.

We haven't decided yet.  I'd think that'd be something DCRUP could 
consider.

R's,
John

v2.23.0 | Report a Bug | By Email