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

S Moonesamy <> Thu, 10 April 2014 08:57 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C47D01A0169 for <>; Thu, 10 Apr 2014 01:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qAGRitz3dq2y for <>; Thu, 10 Apr 2014 01:57:32 -0700 (PDT)
Received: from ( [IPv6:2001:470:f329:1::1]) by (Postfix) with ESMTP id 9FF251A0049 for <>; Thu, 10 Apr 2014 01:57:32 -0700 (PDT)
Received: from ([]) (authenticated bits=0) by (8.14.5/8.14.5) with ESMTP id s3A8vJcI023154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 01:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail2010; t=1397120251; bh=a38RaOkKpbfMgHgEPZBli9vBtjFgf72giYdlQBh+q58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4cksBX3Sa0dl8+lajqrHxXKPuUP8aOo0hI4J5i4e8VPBDKBUu0RiG0CMRzn4EjMYP K9a7jqgvK8CgmBXilXNHxiN1f8Dy8D1Y62eGYjjFHPv1wWMJ4kOktN23/qb3zY6LkO zH1BnOlJY1akabcmXB3Hmg7F/jTP0J/XZqh/XFKA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail; t=1397120251;; bh=a38RaOkKpbfMgHgEPZBli9vBtjFgf72giYdlQBh+q58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Uuc2T/0mZAhVCeOJI8H0JY6XhE2B0p/u4+NkoK2YNk5UZs7+JjUx1CUabfDqVjom9 b0b51GapB854QPUxczQXFo7uubIhFRG1V5vTUx0D51ywdKxqEqVu5LdywoHSeyX9Iz VxqnDH7Q5XWHqavF0pco5zkpjDVHdw1SlEZ0PH/Q=
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version
Date: Thu, 10 Apr 2014 01:54:16 -0700
To: Jari Arkko <>
From: S Moonesamy <>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <>
References: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 10 Apr 2014 08:57:36 -0000

Hi Jari,

I sent a message to the IESG yesterday (see 
).  As the wasn't any response from the IESG there might be a 
perception that the IESG isn't responsive to concerns when the matter 
affects OpenSSH code.  For what it is worth OpenSSH is widely 
deployed.  It is easy to assess whether what I wrote is true by 
looking at a few open source operating systems.

It has been stated that:

   'To break the deadlock, document authors often choose some "seemingly
    unused" code points, often by selecting the next available value from
    the registry; this is problematic because these may turn out to be
    different from those later assigned by IANA.  To make this problem
    worse, "pre-RFC" implementations are often developed and deployed
    based on these code point selections.'

I did not choose a "seemingly unused" code point (see 
draft-moonesamy-sshfp-ed25519-01).  I followed what the IETF 
documentation says and the advice I have been given.  I requested 
feedback from CFRG even though it is not an IETF Working Group.  I 
could have objected to that given what has been said in the news.

According to RFC 2026:

   "If an individual should disagree with an action taken by the IESG in
    this process, that person should first discuss the issue with the
    ISEG Chair."

The problem is that the IESG has not taken any action.  In my opinion 
it is constructive to be open to discussion.

S. Moonesamy