IETF Logo Mail Archive

Re: [Curdle] sntrup761x25519-sha512

Mouse <mouse@Rodents-Montreal.ORG> Tue, 16 May 2023 17:10 UTC

Return-Path: <mouse@Stone.Rodents-Montreal.ORG>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFF48C15DD5E for <curdle@ietfa.amsl.com>; Tue, 16 May 2023 10:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tg4txEKv4pj2 for <curdle@ietfa.amsl.com>; Tue, 16 May 2023 10:10:10 -0700 (PDT)
Received: from Stone.Rodents-Montreal.ORG (Stone.Rodents-Montreal.ORG [98.124.61.89]) by ietfa.amsl.com (Postfix) with ESMTP id CC588C14CF13 for <curdle@ietf.org>; Tue, 16 May 2023 10:10:09 -0700 (PDT)
Received: (from mouse@localhost) by Stone.Rodents-Montreal.ORG (8.8.8/8.8.8) id NAA16054; Tue, 16 May 2023 13:10:06 -0400 (EDT)
Date: Tue, 16 May 2023 13:10:06 -0400
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <202305161710.NAA16054@Stone.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Tue, 16 May 2023 13:02:58 -0400 (EDT)
To: curdle@ietf.org, ietf-ssh@netbsd.org
In-Reply-To: <0E4AB77A-7C09-41C6-9196-74F4BD202579@akamai.com>
References: <875y8y4ip2.fsf@kaka.sjd.se> <84296E62-5843-4E7A-BD43-430491A5A1F3@akamai.com> <30525ce993ee83050cd8181c15bc84746a002f95.camel@redhat.com> <0E4AB77A-7C09-41C6-9196-74F4BD202579@akamai.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/CJP7k0MCfhGw9zo8jRjluBSCtLw>
Subject: Re: [Curdle] sntrup761x25519-sha512
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2023 17:13:28 -0000

>> (Work on how to use those curves can start earlier, but publication
>> should wait until algorithms are official.
> Can't do interop experiments without putting entries in the IANA
> registries [...]

Hmm?  I can't see why not.  I could (putatively) implement something
today and call it FredBloggsKex; if (say) PuTTY does likewise, we can
interop test with one another even if we never even so much as tell
anyone about it, much less convince the IETF to register the name.

Can't do *open to the world* interop testing, maybe.  But even then,
you can do _almost_ all interop testing with a name@FQDN extension name
rather than the final name.  _Most_ interop problems won't care what
name you advertise it under, after all.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

v2.23.0 | Report a Bug | By Email