Re: [Hipsec] Need to close all draft-ietf-hip-dex-21 pending issues... before 2021-Jan-13...

["Eric Vyncke (evyncke)" <[e-mail]>]

Two months after the email below, I sending a kind reminder to authors and WG.

With the -22, a lot of (if not all ) SEC ADs’ DISCUSS points should have been addressed.

As far as I can tell, the other remaining issue was Ekr’s one about why forfeiting FS when some algorithm could do it in a reasonable time. In an email to authors and ADs, Eric R. wrote “it defines a set of parameters (the NIST curves) which are slower w/o FS than other parameters (X25519) are w/ FS. This fact calls into question the need to dispense with FS.”

While 2 months ago I put a deadline for tomorrow, I (as the responsible AD) am flexible of course but we cannot linger anymore. I know that a -23 is in the work for weeks => let’s publish it in the coming days.

Else, next week we will need to either change the intended status to experimental or declare the document dead by lack of energy. The latter does not have my preference obviously.

Regards

-éric


From: Hipsec <[e-mail]> on behalf of "Eric Vyncke (evyncke)" <evyncke=[e-mail]>
Date: Friday, 13 November 2020 at 15:32
To: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, Robert Moskowitz <[e-mail]>, Miika Komu <[e-mail]>
Cc: Roman Danyliw <[e-mail]>, Eric Rescorla <[e-mail]>, Gonzalo Camarillo <[e-mail]>, "[e-mail]" <[e-mail]>, Benjamin Kaduk <[e-mail]>, Erik Kline <[e-mail]>
Subject: [Hipsec] Need to close all draft-ietf-hip-dex-21 pending issues... before 2021-Jan-13...

Dear HIP, dear authors,

This document was requested for publication [1] in February 2018 (2.5 years ago), then its IESG evaluation has been deferred, then I took over this document from Terry Manderson in March 2019, then it went again through IESG evaluation in July 2020 and there are still DISCUSS points to be addressed even after a couple of revised I-D...

Difficult not to observe that this document does not progress very fast.

Moreover, this document is a normative reference for rfc4423-bis waiting in the RFC editor queue since March 2019... So, also blocking the HIP-NAT document [2].

After discussion with the HIP chair, Gonzalo in cc, we have taken the following decision: if a revised I-D addressing remaining DISCUSS points + Ekr’s ones is not uploaded within 2 months (13th of January 2021), then I will request the HIP WG to accept the complete removal of section A.3.3 of the rfc4423-bis document (1 page about HIP-DEX in the appendix) + the reference to the HIP-DEX document [3]. This will allow the immediate publication of the rfc4423-bis and HIP-NAT documents.

The HIP DEX authors may also select to change the intended status of the document to ‘experimental’ (if the HIP WG agrees) as this may reduce the security requirements by the SEC AD and Ekr.

Gonzalo and I are still hoping to get a revised HIP-DEX shortly,

Regards

-éric

[1] https://datatracker.ietf.org/doc/draft-ietf-hip-dex/history/
[2] https://www.rfc-editor.org/cluster_info.php?cid=C386
[3] and possibly I will set the state of HIP-DEX as ‘dead’ on the datatracker