IETF Logo Mail Archive

Re: [Dcrup] we need to do the work, was draft-ietf-dcrup-dkim-usage and document shepherds

"John R Levine" <johnl@taugh.com> Sat, 10 June 2017 18:43 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755BE129420 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 11:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.com header.b=mM/WCwjV; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=DmBAp6YM
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 0uJzv81eu2gj for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 11:43:04 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8DB012773A for <dcrup@ietf.org>; Sat, 10 Jun 2017 11:43:03 -0700 (PDT)
Received: (qmail 96269 invoked from network); 10 Jun 2017 18:43:02 -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=1780b.593c3db6.k1705; bh=Q6NDyJXAWec+Z3IE0kNoBJzUxnQyDcBCHChT+75O7Fg=; b=mM/WCwjV2xqQOy6w3vYfNFDyYdMZ1ndhUpE0mmCoAD4EiS4F6yFZy8x8tz6HjQbi4q4pQ3JTjQ/k9eC79S2hq97AIn7thUf6R9ix0cpUT9kB2vg/ytPolffPWtNij8G+06pi2cSwC5IrgnYDKsWJRr2Q6uKojPxB7pVQJ6hPwypJYVZ8vrTlVoWdss9BIpoBFIrDRvZCV6xsHT5iq7PvDel+XdNjYwGbC/CBCOTHvEonfaiL+pqn0QtKaq5YtO8U
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=1780b.593c3db6.k1705; bh=Q6NDyJXAWec+Z3IE0kNoBJzUxnQyDcBCHChT+75O7Fg=; b=DmBAp6YMvVxaI2+hHBVjW4UPzF17wLMh3OtS0fDOroA1uktJhmgJfW1E+OM78JTAJOcKgzHkc1tFiRwOfl0acdMm9bMUpoRSR7bUoZXz+kEVK0F8TXsdXDEBw6h3ZIHu+hyCHSvwhrjnT+qeaDfV8NVyNJbj0yIIdvDfQ4l8JQh2aQzNKDhCUe1jfbhFX9huKwdv+5RFNYLmoeh9lUv1uu7iQNp/6BHgub5S83fD+419RBTP3LlunZWh9rLshP9l
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; 10 Jun 2017 18:43:02 -0000
Date: Sat, 10 Jun 2017 14:43:02 -0400
Message-ID: <alpine.OSX.2.21.1706101442000.17469@ary.qy>
From: John R Levine <johnl@taugh.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "dcrup@ietf.org" <dcrup@ietf.org>
In-Reply-To: <68d03c39527d4f3d972e45c877d248ba@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <DE201939-EA16-4957-B160-2B45B3BA60C1@kitterman.com> <20170610125300.14197.qmail@ary.lan> <68d03c39527d4f3d972e45c877d248ba@usma1ex-dag1mb1.msg.corp.akamai.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/xKacLeOij4GGhVon7EjS8HE1jPE>
Subject: Re: [Dcrup] we need to do the work, was draft-ietf-dcrup-dkim-usage and document shepherds
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jun 2017 18:43:05 -0000

> If there is any reason why DKIM cannot use the signature methods 
> just-defined by CURDLE for CMS 
> https://datatracker.ietf.org/doc/draft-ietf-curdle-cms-eddsa-signatures/

As far as I know, that would probably work, although DKIM has no CMS or 
ASN.1, just bare base64 keys and signatures.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.28.0 | Report a Bug | By Email | System Status