Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01

S Moonesamy <sm+ietf@elandsys.com> Thu, 10 April 2014 10:05 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 428061A0675 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level:
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 WaIrGSAJSrEB for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:05:53 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DC31A066A for <ietf@ietf.org>; Thu, 10 Apr 2014 03:05:53 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.71]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3AA5YsB025887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 03:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397124347; bh=9IHwDeZj9eCFkvoYUQxeXHCveAhSGncda/9x8Jn8v04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SGqF7BONSKPMCmRrtw5AtQx/sCukX0rArxRDV5LMQ3SO8mZ7pbroCfU569WepjH2G G8zqe2K/6bW0dg1cgBiBB9785w6u7I8pGjGTYTAFp2aMyt92sIV8AHzgdOcn6L6RYZ uTIBvSwlyElD8xU8Y4+yxYeViYS1iC0hpBUdq3bA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397124347; i=@elandsys.com; bh=9IHwDeZj9eCFkvoYUQxeXHCveAhSGncda/9x8Jn8v04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iMXfzxwJbw9lOV0ZT0tgd0/zq7r3KHrPFYidNuG3k1PGH5C5cemdYnBH5dr7nI2Fn hc2fLvkSuuR3ScSbHyypMB32FBwBznWPrH81vTeUztbxvImWTi75IvYmlUfWhKO2SD k3Wa2/dgyGkTj79sRNBP6ebi0NaafaAZCzUftFtc=
Message-Id: <6.2.5.6.2.20140410022352.0ca49f40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Apr 2014 02:30:37 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Jari Arkko <jari.arkko@piuha.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <53465FFA.1090602@cs.tcd.ie>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <53465FFA.1090602@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OoNRoGTI73mH3F8Ql1M5m884V3Y
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:05:58 -0000

Hi Stephen,
At 02:10 10-04-2014, Stephen Farrell wrote:
>You ask in that message "why the delay?"
>
>As I told you off list before you posted that, we are hoping that
>CFRG will organise a virtual interim meeting for which the main
>topic of discussion will be whether CFRG's advise the IETF that
>some set of new curves (including that required by your draft)
>are good enough for use in IETF standards. That question was
>raised at the CFRG session in London but there were not enough
>people in the room who felt they knew enough about the topic to
>be sure. Aside from you the TLS wg are also waiting on that
>answer. I hope the CFRG virtual interim will happen in the next
>few weeks. That is the reason for delay.
>
>If that CFRG meeting doesn't happen soon, (but I expect it
>will) then I will organise some other way to get an answer on
>this topic, but better if we can get folks who do crypto for
>a living to give us an answer if we can.

Thanks for explaining the delay.  I am okay with waiting a few weeks.

Regards,
S. Moonesamy