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

Benjamin Kaduk <kaduk@mit.edu> Mon, 16 November 2020 12:09 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F593A0DBB; Mon, 16 Nov 2020 04:09:01 -0800 (PST)
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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 aHgKcj08W1mN; Mon, 16 Nov 2020 04:08:59 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 77DE43A0D91; Mon, 16 Nov 2020 04:08:58 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AGC8C9X021732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Nov 2020 07:08:16 -0500
Date: Mon, 16 Nov 2020 04:08:12 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Cc: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Robert Moskowitz <rgm@labs.htt-consult.com>, "hipsec@ietf.org" <hipsec@ietf.org>, "draft-ietf-hip-dex@ietf.org" <draft-ietf-hip-dex@ietf.org>, Miika Komu <miika.komu@ericsson.com>, Erik Kline <ek.ietf@gmail.com>, "rene.hummen@belden.com" <rene.hummen@belden.com>, Terry Manderson <terry.manderson@icann.org>, Eric Rescorla <ekr@rtfm.com>, Roman Danyliw <rdd@cert.org>
Message-ID: <20201116120812.GX39170@kduck.mit.edu>
References: <6A729A0C-70B0-458F-BA0E-62EB2108D412@cisco.com> <6bd706b3-7195-5dc5-21b4-bd12f14c5271@labs.htt-consult.com> <ADE665B0-0F02-4BD6-8BCE-E91FDD1CF8E9@cisco.com> <AM8PR07MB7649925FB684DA98154BE21083E30@AM8PR07MB7649.eurprd07.prod.outlook.com> <CABcZeBMYP8RQUjOw=qARcoGiB0g_+W4qfaifTGUaojvRFXC=Qg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CABcZeBMYP8RQUjOw=qARcoGiB0g_+W4qfaifTGUaojvRFXC=Qg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/a6hygQ5S141FZmrCw8HJgummU9Q>
X-Mailman-Approved-At: Mon, 16 Nov 2020 07:58:19 -0800
Subject: Re: [Hipsec] Need to close all draft-ietf-hip-dex-21 pending issues... before 2021-Jan-13...
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2020 12:09:02 -0000

I'm happy to get on a call as well.

-Ben

On Mon, Nov 16, 2020 at 01:40:21AM -0800, Eric Rescorla wrote:
> Certainly happy to do that, though it would need to be the first week of
> December at earliest.
> 
> 
> On Mon, Nov 16, 2020 at 1:35 AM Gonzalo Camarillo <
> gonzalo.camarillo@ericsson.com> wrote:
> 
> > Hi,
> >
> >
> >
> > yes, maybe a quick conference call with the authors and the relevant ADs
> > would be the best way to agree on a way forward.
> >
> >
> >
> > Cheers,
> >
> >
> >
> > Gonzalo
> >
> >
> >
> > *From:* Eric Vyncke (evyncke) <evyncke@cisco.com>
> > *Sent:* Friday, November 13, 2020 23:48
> > *To:* Robert Moskowitz <rgm@labs.htt-consult.com>om>; hipsec@ietf.org;
> > draft-ietf-hip-dex@ietf.org; Miika Komu <miika.komu@ericsson.com>
> > *Cc:* Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>om>; Erik Kline <
> > ek.ietf@gmail.com>gt;; Eric Rescorla <ekr@rtfm.com>om>; rene.hummen@belden.com;
> > Terry Manderson <terry.manderson@icann.org>rg>; Benjamin Kaduk <kaduk@mit.edu>du>;
> > Roman Danyliw <rdd@cert.org>
> > *Subject:* Re: Need to close all draft-ietf-hip-dex-21 pending issues...
> > before 2021-Jan-13...
> >
> >
> >
> > Bob,
> >
> >
> >
> > It is really up to the authors (representing the will of the HIP WG) to
> > get a revised I-D addressing the SEC Ads’ concerns. If they are satisfied
> > with open questions put in an appendix (e.g., “for future work”) and they
> > clear their blocking DISCUSS points, then I will more than happy to give
> > the final go to HIP DEX.
> >
> >
> >
> > Having email/voice exchanges with DISCUSS owners (and Ekr) can probably
> > help as well.
> >
> >
> >
> > Did you consider changing the intended status to ‘experimental’ ?
> >
> >
> >
> > Obviously, the earlier, the better
> >
> >
> >
> > Regards
> >
> >
> >
> > -éric
> >
> >
> >
> > *From: *Robert Moskowitz <rgm@labs.htt-consult.com>
> > *Date: *Friday, 13 November 2020 at 20:10
> > *To: *Eric Vyncke <evyncke@cisco.com>om>, "hipsec@ietf.org" <hipsec@ietf.org>rg>,
> > "draft-ietf-hip-dex@ietf.org" <draft-ietf-hip-dex@ietf.org>rg>, Miika Komu <
> > miika.komu@ericsson.com>
> > *Cc: *Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>om>, Erik Kline <
> > ek.ietf@gmail.com>gt;, Eric Rescorla <ekr@rtfm.com>om>, "rene.hummen@belden.com"
> > <rene.hummen@belden.com>om>, Terry Manderson <terry.manderson@icann.org>rg>,
> > Benjamin Kaduk <kaduk@mit.edu>du>, Roman Danyliw <rdd@cert.org>
> > *Subject: *Re: Need to close all draft-ietf-hip-dex-21 pending issues...
> > before 2021-Jan-13...
> >
> >
> >
> > I have reached the point on going through all the old notes where any
> > attempts at changes only seem cosmetic.  I spend a couple hours a week on
> > it, trying something else.  I need to take a different approach, perhaps.
> >
> > I just completed another round of going through the various emails.
> >
> > What I am thinking about is put together a single note on what I perceive
> > as outstanding issues, and put them in an Appendix.  I would push this out,
> > still this month and see how things go from there.
> >
> > I have really tried to come to some accommodation on the issues raised.
> >
> > Events are somewhat catching up.  NIST LWC selection process may well
> > result in renewing looks at technologies like HIP-DEX for 8-bit processors
> > (see the latest LWC presentations including the build rate for 8-bit
> > processors).
> >
> > I welcome your response.
> >
> > Bob
> >
> > On 11/13/20 9:32 AM, Eric Vyncke (evyncke) wrote:
> >
> > 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
> > <https://protect2.fireeye.com/v1/url?k=79ca9a50-2651a37b-79cadacb-866038973a15-254f733fa2299a75&q=1&e=c8652521-144c-4c45-9db8-f04e01a7aa3d&u=https%3A%2F%2Fwww.rfc-editor.org%2Fcluster_info.php%3Fcid%3DC386>
> >
> > [3] and possibly I will set the state of HIP-DEX as ‘dead’ on the
> > datatracker
> >
> >
> >
> >
> >
> > --
> > Robert Moskowitz
> > Owner
> > HTT Consulting
> > C:      248-219-2059
> > F:      248-968-2824
> > E:      rgm@labs.htt-consult.com
> >
> > There's no limit to what can be accomplished if it doesn't matter who gets
> > the credit
> >
> > -->
> >