Return-Path: 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 064441292AE for ; Sun, 11 Jun 2017 11:54:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.79 X-Spam-Level: X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] 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=t3RNZ/wK; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=lQBEvSPb 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 h7yqVLd88lTL for ; Sun, 11 Jun 2017 11:54:07 -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 6CDF61293E4 for ; Sun, 11 Jun 2017 11:54:05 -0700 (PDT) Received: (qmail 52985 invoked from network); 11 Jun 2017 18:54:04 -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=cef7.593d91cc.k1705; bh=jCFnT+ckuXq4dbHNf55RZK/ORqpocIFw/jNpm2EXC+E=; b=t3RNZ/wKDFRV9nGd+QkQCW5rhVtSSkz1r2gX1qEtE39d+l5rnPVMh99DC02s7O7qz7El/8U0gooOKWlSy8U/Ewx2Un9eIqXHGlYkik2+WOgobk9u8IhJTIqd3nhNzfMw+80D61bZ3e/UdKyZON190/hAe0UNuAcLREBqsOTqtZ+ByZwUvHvM4DgiVNQbwvxiqXyfm7SBfZAh4+Lq474uy/F7HGL28Rsc/5DA57Io8QgaIgvNs90Rxw+j/LJ9y1+x 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=cef7.593d91cc.k1705; bh=jCFnT+ckuXq4dbHNf55RZK/ORqpocIFw/jNpm2EXC+E=; b=lQBEvSPb7xw3m44L8eCsxP0DAGk1ipF/VZzfhYrqGBGgQvvs15DsEUBJeLmvsmLVpNEoCVi6a6BoEQTZQEBhLd48aJQ2PuFrvQhujG+EQ7qgJbXeRWxXht/jBTkEgsgRDn4oJ8jthqLJn6Apxx8lFFzPdVheuu8hxSfcltw6d7emD55MoDt/6Gk0ahobq/8/lmesezIMCCieMXyQJ1l9bC4VIrMFKisPWOIJR95uBEazvifA61dWfBcF7UGE9ItY 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; 11 Jun 2017 18:54:03 -0000 Date: 11 Jun 2017 19:54:02 +0100 Message-ID: From: "John R Levine" To: "Phillip Hallam-Baker" Cc: "dcrup@ietf.org" In-Reply-To: References: <20170610125545.14232.qmail@ary.lan> <152cd69567124a1aa2fec7fbe63c936c@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: Subject: Re: [Dcrup] Hey, crypto experts, what signing algorithm should we add X-BeenThere: dcrup@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DKIM Crypto Update List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2017 18:54:09 -0000 > Which flavor of Ed25519? > > Are we talking about RFC 8032 or something else. Because there really needs > to be a very very good reason not to use the standard as written. I'm not aware of any reason to use anything other than RFC 8032. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly