[Anima] Status of renaming endpoint path?

Warren Kumari <warren@kumari.net> Mon, 31 August 2020 21:02 UTC

Return-Path: <warren@kumari.net>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DF23A195D for <anima@ietfa.amsl.com>; Mon, 31 Aug 2020 14:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 tUK2RUXRbE5O for <anima@ietfa.amsl.com>; Mon, 31 Aug 2020 14:02:33 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 472673A1956 for <anima@ietf.org>; Mon, 31 Aug 2020 14:02:33 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id u27so2895284lfm.13 for <anima@ietf.org>; Mon, 31 Aug 2020 14:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=b6xFMp+Ar+GFUxh4YB/60WqVCqnGr5S1ipyHJJi+Y70=; b=X1o7/aWNkQNofObr8HEQCCTX4YRP5g14u2255Zdzl+NpDf0OMzItLF1tcxPj8V8XC9 t9J/VMJBk5ipwTNI8Nd+re/TXQcY93EA7XLi+FmyYScK/sf1cikYYU7trXJ2i2C0V0fL RRz4sc+L0gNO74Bm882kE0cgaYHhTNvWUUp8CYNqU2JQhYeW1VNpdzEAQN9D+hHFS/zx ha0+D4cOTIpnJmc+4KqTjROk0bmJGZ1DPplPP7vswWnbnOihJVRBWMllO/t5elBVHS6e bqx+D79G8E9Rf7Q1hdQZKzLrPqjVhFSrEEKBrpqhzvZsi3C7O+YKp9OoVQ9ZYvrWcwgw 6auw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=b6xFMp+Ar+GFUxh4YB/60WqVCqnGr5S1ipyHJJi+Y70=; b=Ia4olxUcni9Za9LD+yoXIg1wWJp5p2qeNyIkpAKxuoXLGcvMcrX5P/cGp0iBMgFEOH NI8fhGqvrkz0IkqTBlx7ieF01WML0NgftAneSC3sOjxXUWDVrj62uh9EjJGVDTOS9zuO /C7fzo4bbFS6jAVFaiB8/0YGw6txc+UQNcVDipTUw5tz2gDnWX2So+nVlRETDI9nbgMI IXh8dEq0Pj4aZNYtayf6ZGNznCnYJrwQHRqr7Yel2MgjS/tdG7WQXokBCUwtLLDfTnJe 6VN8G+ZEGdmoAlAcYEhzlBc53w92yImBHCEF/I1QiZldvG8tDNhQE5Xu6qkIEarUPvSn LQ6A==
X-Gm-Message-State: AOAM532xvD2UG5Icb/mo5qI+2b+JbL9RAOrnWCG3mawPzrZBnHVtvooo MR0PcfOwQv/XwypHcvFHWqqV5e7EI5GSe2Y+E1BdFEJw5YpnLhs+
X-Google-Smtp-Source: ABdhPJw87S4iRKM/0H4FadsBMoG4pW4tYkOOfHHVCCI049rEuu71pcTzSUcw5dmqhj31pmkrCRqjRTW61p7+6nXygv0=
X-Received: by 2002:a05:6512:3610:: with SMTP id f16mr1497844lfs.8.1598907750202; Mon, 31 Aug 2020 14:02:30 -0700 (PDT)
MIME-Version: 1.0
From: Warren Kumari <warren@kumari.net>
Date: Mon, 31 Aug 2020 17:01:53 -0400
Message-ID: <CAHw9_iJDGhn9W0TaJ6kKQi-RTtuCvFh7UVN-jb_MbP3BbP4z2g@mail.gmail.com>
To: Anima WG <anima@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/HLUvhm7CxWCXfMseact3ffuba4Y>
Subject: [Anima] Status of renaming endpoint path?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2020 21:02:35 -0000

Hi all,

Back in late July Steffan sent:
https://mailarchive.ietf.org/arch/msg/anima/jjusQdqzS3G4WbczolCxF0_YmQQ/
regarding renaming "Handling of endpoint path names (from BRSKI-AE
discussion today)".

Michael has a document ready to do this:
https://www.ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-43&url2=draft-richardson-anima-brski-renamed-00

Brian was concerned that this might add an unknown additional delay:
https://mailarchive.ietf.org/arch/msg/anima/3Ov2s8XxQ6pnQMp6PTd9_yDc-D0/

Luckily, if the WG does want to do this, we should be able to make it
happen without adding any delay (but we are running out of time...).

If the chairs kick off a consensus call, asking for objections **on
this change only**, then I can do a 2 week IETF LC, also asking for
objections **on this change only**.

I've already (mid-August) confirmed that the IESG is OK with this
process, so it would take [however long the Chairs choose to do the WG
consensus call for (1 week? 2 weeks?) ]  + [2 weeks IETF consensus
call] +[a few days of slop] = ~5 weeks...

This document is gated on (at least)
draft-ietf-anima-autonomic-control-plane (which will take some time to
wind its way through the RFC Ed process) so if this were to occur
soon, there would be no added delay...

Just FYI...
W

-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf