Re: [Anima] possible last minute changes to anima-bootstrapping-keyinfra (was Re: Handling of endpoint path names (from BRSKI-AE discussion today))

Michael Richardson <mcr@sandelman.ca> Wed, 05 August 2020 17:05 UTC

Return-Path: <mcr@sandelman.ca>
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 4FE733A0EDA for <anima@ietfa.amsl.com>; Wed, 5 Aug 2020 10:05:19 -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, 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 4CDhvax7ba73 for <anima@ietfa.amsl.com>; Wed, 5 Aug 2020 10:05:16 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30A783A0F80 for <anima@ietf.org>; Wed, 5 Aug 2020 10:04:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E8FF038994; Wed, 5 Aug 2020 12:44:07 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4TKtzgbngmLJ; Wed, 5 Aug 2020 12:43:58 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 72D6938991; Wed, 5 Aug 2020 12:43:58 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8442E114; Wed, 5 Aug 2020 13:04:37 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Mark Nottingham <mnot@mnot.net>
cc: "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <76EE620C-2E4B-4213-A82C-62FD2AFB1522@mnot.net>
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com> <13607.1596542871@dooku> <76EE620C-2E4B-4213-A82C-62FD2AFB1522@mnot.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 05 Aug 2020 13:04:37 -0400
Message-ID: <9180.1596647077@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8fAGr2XNKdayEGUMawoEiRgLLjQ>
Subject: Re: [Anima] possible last minute changes to anima-bootstrapping-keyinfra (was Re: Handling of endpoint path names (from BRSKI-AE discussion today))
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: Wed, 05 Aug 2020 17:05:25 -0000

Thank you for the comments.

Mark Nottingham <mnot@mnot.net> wrote:
    >> On 4 Aug 2020, at 10:07 pm, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    >>
    >>
    >> Hi Mark, this concerns some desired changes to /.well-known/est.
    >>
    >> Specifically, to move the things we did in anima-bootstrapping-keyinfra out
    >> of /.well-known/est into a new /.well-known/brski.
    >> The WG has not concluded to do this as yet, as the above document has passed
    >> IESG review and is in MISREF at the RFC-EDITOR.
    >>
    >> The thread starts at:
    >> https://mailarchive.ietf.org/arch/msg/anima/jjusQdqzS3G4WbczolCxF0_YmQQ/
    >>
    >> I have prepared sample changes which I'd like your opinion on.
    >>
    >> 1) I am now registering /.well-known/brski

    > Sure, we have a process for that ;)  Easiest thing to do is to create an issue here:
    > https://github.com/protocol-registries/well-known-uris

    >> 2) I no longer need /.well-known/est to point to the new document.  Should I
    >> say this?

    > Yes. Best thing to do is to include it in the request above.

    >> 3) Am I creating the /.well-known/brski Registry correctly?
    >> I didn't see any other WK that have sub-registries.

    > How you manage the namespace under your well-known URI is totally up to
    > you. That looks reasonable to me, although if you don't think it's
    > likely there will be additions for a while, you could just say 'update
    > this document to register additional paths'.

We have new drafts that we are considering adopting now.


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [