Re: [Hipsec] Need to close all draft-ietf-hip-dex-21 pending issues... before 2021-Jan-13...
Eric Rescorla <ekr@rtfm.com> Mon, 16 November 2020 09:41 UTC
Return-Path: <ekr@rtfm.com>
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 46E4C3A168E for <hipsec@ietfa.amsl.com>; Mon, 16 Nov 2020 01:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level:
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 tLdFXe9gtC1f for <hipsec@ietfa.amsl.com>; Mon, 16 Nov 2020 01:40:59 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C01FF3A1689 for <hipsec@ietf.org>; Mon, 16 Nov 2020 01:40:58 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id e139so4745518lfd.1 for <hipsec@ietf.org>; Mon, 16 Nov 2020 01:40:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=g8Y7zNs+1s1fw3thRrlw5NzOL7miPNXYb2hJANF4Vvk=; b=xxeDqiw495Fn5Dg0n0+hbWxafJ5IK0zC5YaMEys2eUz423MxqpHMECcFmK5q33lGJU ZMBXm9JC34LEJJDWcs/Ue1A6Q0mn4r++uObC0pV1hmAy2fR4hAi/SVs75vXOKhk8lbq5 TNBQM+hor8CxdIzmgg/nb8zrrgUEc743OEXx8/186OyvxyPTjEbiDM+8rgJLqq78E8u6 HWn41TnIzDpBqvf+fHhdYjA8Z1xrK1fhTYOOEfLx76GENbgaDGagum0Kzhx1YPCZnFQn 3Gx77p32PYTo1ZitYRYjcoBEsitnujNglVO5Ru5/nE2LB0UmcJdtncthJPJfv0ZJPkJV bMLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=g8Y7zNs+1s1fw3thRrlw5NzOL7miPNXYb2hJANF4Vvk=; b=ttoqYLWt5oQwVj4WLODutOtTQAIOlD7ywRog5RC8qsJiUIqjQ9sYVWzPpnlODo21pF zcL4gnQXFC4CQRHEtb0OeccjgmORPLqn5OMVGsK4AV3vttwPtKv3yewZLqudsb3HNJJm FZiy2pboVVjmUlYWZce/vid33w9dLjChUKxSlxUw7gpaTbSRQ+1EwXu5raSYJUVxoLNy L+8uqV4nDdfcAaT8fBeeEHxGvlGTGAVoA/SXsRvNaCzsxd8ashhap+DPJVKrva3iQn9z OO0lIp754SvvjbfeMYNmu6wCWuvuUpj5WUTqAG+ym7zt6d0w54MQ0req9F1DM2urYLpc f6lg==
X-Gm-Message-State: AOAM532GP9ygWsacCajAig0nuUVuJfyIYrOMz5Hc3kHxTCRibGj/zr60 K1Yf20teSy7vyPSQsPvcP7oN/uW9Um651oyfnwpukA==
X-Google-Smtp-Source: ABdhPJxSqF2qYMNI5w3522zYFUCFY3rOTHuSoqVD2f/oyS5q1aBKE48gJ+1s08UQqQC8jytZYaMyPwabyMDotZfs8Bw=
X-Received: by 2002:a05:6512:696:: with SMTP id t22mr4819973lfe.516.1605519656958; Mon, 16 Nov 2020 01:40:56 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <AM8PR07MB7649925FB684DA98154BE21083E30@AM8PR07MB7649.eurprd07.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 16 Nov 2020 01:40:21 -0800
Message-ID: <CABcZeBMYP8RQUjOw=qARcoGiB0g_+W4qfaifTGUaojvRFXC=Qg@mail.gmail.com>
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>, Benjamin Kaduk <kaduk@mit.edu>, Roman Danyliw <rdd@cert.org>
Content-Type: multipart/alternative; boundary="000000000000d556b405b4362ce7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/4WQM4h49QBarS27CjYg59Mh4IKs>
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 09:41:01 -0000
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>; hipsec@ietf.org; > draft-ietf-hip-dex@ietf.org; Miika Komu <miika.komu@ericsson.com> > *Cc:* Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>; Erik Kline < > ek.ietf@gmail.com>; Eric Rescorla <ekr@rtfm.com>; rene.hummen@belden.com; > Terry Manderson <terry.manderson@icann.org>; Benjamin Kaduk <kaduk@mit.edu>; > 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>, "hipsec@ietf.org" <hipsec@ietf.org>, > "draft-ietf-hip-dex@ietf.org" <draft-ietf-hip-dex@ietf.org>, Miika Komu < > miika.komu@ericsson.com> > *Cc: *Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Erik Kline < > ek.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, "rene.hummen@belden.com" > <rene.hummen@belden.com>, Terry Manderson <terry.manderson@icann.org>, > Benjamin Kaduk <kaduk@mit.edu>, 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 > > --> >
- [Hipsec] Need to close all draft-ietf-hip-dex-21 … Eric Vyncke (evyncke)
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Vyncke (evyncke)
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Gonzalo Camarillo
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Rescorla
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Benjamin Kaduk
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Vyncke (evyncke)
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Vyncke (evyncke)
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Rescorla
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Vyncke (evyncke)
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Robert Moskowitz
- Re: [Hipsec] Need to close all draft-ietf-hip-dex… Eric Rescorla