IETF Logo Mail Archive

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

Jari Arkko <jari.arkko@piuha.net> Thu, 10 April 2014 10:15 UTC

Return-Path: <jari.arkko@piuha.net>
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 47DA01A01F3 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 7UBykKqg45kw for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:15:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 607781A01E1 for <ietf@ietf.org>; Thu, 10 Apr 2014 03:15:35 -0700 (PDT)
Received: from [188.67.5.132] (188-67-5-132.bb.dnainternet.fi [188.67.5.132]) by p130.piuha.net (Postfix) with ESMTPSA id D2C572CC61; Thu, 10 Apr 2014 13:15:32 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
From: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: iPad Mail (11D167)
In-Reply-To: <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
Date: Thu, 10 Apr 2014 13:12:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uOHYQYU8ZwDgeh5o2VbYFF9eRSY
Cc: "ietf@ietf.org" <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:15:37 -0000

SM,

SSH is obviously important and I am a long-term OpenSSH user myself :-) And I also happen to believe in timely registration of values in registries, particularly when there is running code.

Anyway, I cannot speak for the IESG yet in this case but please do not take lack of a response to a message sent yesterday as a sign that we do not care :-)

I looked at the draft and it seems fine, ready to move forward. I do not personally have any knowledge about ED25519 and I cannot say whether it is something that we should be using in IETF standards. Stephen seems to think that waiting a bit to get an opinion from the crypto experts would be useful. What is your opinion on that, SM? What about others, do you have an opinion? And SM, do you have an idea how soon we need an answer for the implementations to usefully employ the allocated number?

Jari

v2.23.0 | Report a Bug | By Email