Re: [IPsec] Working group last call for the draft-nir-ipsecme-eddsa-00

Tero Kivinen <kivinen@iki.fi> Wed, 15 February 2017 15:11 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DD9129676 for <ipsec@ietfa.amsl.com>; Wed, 15 Feb 2017 07:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 VgVfYJXiUEUi for <ipsec@ietfa.amsl.com>; Wed, 15 Feb 2017 07:11:13 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9AE12966E for <ipsec@ietf.org>; Wed, 15 Feb 2017 07:11:13 -0800 (PST)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.2/8.15.2) with ESMTPS id v1FFB2Nv022796 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Feb 2017 17:11:02 +0200 (EET)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.2/8.14.8/Submit) id v1FFB1Aj000550; Wed, 15 Feb 2017 17:11:01 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <22692.28549.958589.705943@fireball.acr.fi>
Date: Wed, 15 Feb 2017 17:11:01 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Andreas Steffen <andreas.steffen@strongswan.org>
In-Reply-To: <32d17f6f-3b55-a275-9fe5-960833899780@strongswan.org>
References: <22683.8182.349840.103676@fireball.acr.fi> <D28C9CC6-FD00-4A42-8451-F9B0AA83E4BF@apple.com> <22684.25414.470545.969594@fireball.acr.fi> <32d17f6f-3b55-a275-9fe5-960833899780@strongswan.org>
X-Mailer: VM 8.2.0b under 25.1.1 (x86_64--netbsd)
X-Edit-Time: 5 min
X-Total-Time: 4 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/spREZvg5TcoUkz9vkwhukrlUtKY>
Cc: ipsec@ietf.org, David Schinazi <dschinazi@apple.com>
Subject: Re: [IPsec] Working group last call for the draft-nir-ipsecme-eddsa-00
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 15:11:15 -0000

Andreas Steffen writes:
> I personally think that 0 would have been legitimate for the "Identity"
> hash but the next unassigned value (5) is also ok for me.
> 
> Could you please ask IANA for an early assignment of the code point?
> strongSwan 5.5.2 with Ed25519 support is ready to be deployed,
> thus we would be able to release the stable version as soon as
> the code point has been assigned.

Before we can make code point allocation, we need to agree on whether
it is going to be zero or next number. As you can see from the emails
in this list there is not agreement on this yet, so even if authors
make IANA request to ask for assignment, when it comes to me (as for
expert review) few days later, I would wait for the comments on the
list to agree on which number we are going to allocate.

Now it seems more people are supporting allocating something else than
zero... 

As for the process:

> > As this is expert review registry there is no need to ask for early
> > allocation, the normal process is just to fill in the IANA general
> > request for assignments, which then goes to the IANA and they will
> > then send it to the expert (me) for verification.

And then we will then come back to this list to finish this
discussion...
-- 
kivinen@iki.fi