IETF Logo Mail Archive

Re: [Cfrg] Citing specs in specs

Watson Ladd <watsonbladd@gmail.com> Mon, 03 March 2014 02:51 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C31F1A0C44 for <cfrg@ietfa.amsl.com>; Sun, 2 Mar 2014 18:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 4VeKyiVzJBfk for <cfrg@ietfa.amsl.com>; Sun, 2 Mar 2014 18:51:39 -0800 (PST)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id AE4511A0C1F for <cfrg@irtf.org>; Sun, 2 Mar 2014 18:51:39 -0800 (PST)
Received: by mail-yh0-f45.google.com with SMTP id i57so3052129yha.18 for <cfrg@irtf.org>; Sun, 02 Mar 2014 18:51:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yIEjPp4o/1N6ZwwnlEGBhwXdF/2nHNmgBf9g4AHftPk=; b=Cgllt7jgEyezzPQd798wP+eWJNuNP5BgReauTgATIjrKL1Ra6Yebt73UBCtQu0AoMo xiAHoMHh+aP71LL/SIcyD3Nko3+48D1+ys4s4rnPfvZhYhb4N51bVfHNfPw20fszxJ2s YxzB47PjfXUG3pGi4s/TQcw68NPmcX311puSDZopZwXC76uZS+wJyVBDflNAukuT1ope 6gINviBRveNDcNuM5tChdY/tJPhFWMwLQ14UJEOtVLHhzIMtsraoPJqj4xyjJA1Z8qPI cRJHkB8FGeYJIqQ6T2inZizny2gdd4/JQpuKNK+WQwf6e6dXSwpqK7e8X7vcR88W4+d6 mnLA==
MIME-Version: 1.0
X-Received: by 10.236.142.198 with SMTP id i46mr4264936yhj.66.1393815096737; Sun, 02 Mar 2014 18:51:36 -0800 (PST)
Received: by 10.170.92.85 with HTTP; Sun, 2 Mar 2014 18:51:36 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140302175050.0b3b1558@elandnews.com>
References: <530FDC7A.4060404@cisco.com> <CABqy+srTqCXjOR4DMNgWyxf2pZ7dwZfWyznhBuJaY5w8VeuR4Q@mail.gmail.com> <5310B12E.4070603@cisco.com> <CABqy+srrbtdHOckjPqTj5SFuQwQEqXBjgc8kwagMi8E6ZRf=qg@mail.gmail.com> <28A7736F-A791-4552-8D42-DB99AC7B7F9B@vpnc.org> <CF37EA5F.338D8%paul@marvell.com> <CACsn0cmewBrOzaRF5XXC1p1A_gUSwkdE1_7V-1x8nta-ESyA+A@mail.gmail.com> <CF38F2D4.33940%paul@marvell.com> <2A0EFB9C05D0164E98F19BB0AF3708C711EF97AD05@USMBX1.msg.corp.akamai.com> <7BAC95F5A7E67643AAFB2C31BEE662D018B8516C6E@SC-VEXCH2.marvell.com> <6.2.5.6.2.20140302175050.0b3b1558@elandnews.com>
Date: Sun, 02 Mar 2014 18:51:36 -0800
Message-ID: <CACsn0cmK8_+4xgOjy5brKn1n7SLsqg7djpJrE8zJ4h-W+LG5Sg@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/cfrg/wv-KkVa7UbnsexLyClUZHOgVTko
Cc: "Salz, Rich" <rsalz@akamai.com>, "cfrg@irtf.org" <cfrg@irtf.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [Cfrg] Citing specs in specs
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 02:51:41 -0000

On Sun, Mar 2, 2014 at 6:14 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Paul,
>
> At 15:40 02-03-2014, Paul Lambert wrote:
>>
>> Implementations are possible by using the readily available open source
>> implementation.  This is a good thing, but it is also desirable
>> to have a unambiguous description of the algorithms that is not
>> a C code file.  This is why we write RFCs...
>
>
> A Proposed Standard is about interoperability.  It does not prescribe a
> method.  The test is to determine whether the standard actually works is see
> whether there are different implementations which have been deployed.

>From that perspective let me note that DJB's original assembly
language implementation, Matthew Dempsky's 32 bit C implementation,
and Adam Langley's 64 bit C implementations, were all independently
developed from the paper. Furthermore, I've been able to do the same
in a few hours, if not extremely concerned with speed.

Sincerely,
Watson Ladd

>
> There is a Proposed Standard which contains the source code for a reference
> implementation.  That was unusual.
>
> Please note that I currently have a draft referencing ED25519 [1].
>
> Regards,
> S. Moonesamy
>
> 1. http://tools.ietf.org/html/draft-moonesamy-sshfp-ed25519-00



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin

v2.23.0 | Report a Bug | By Email