IETF Logo Mail Archive

Re: [Last-Call] Post approval change on draft-ietf-anima-bootstrapping-keyinfra

Toerless Eckert <tte@cs.fau.de> Mon, 21 September 2020 14:09 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1EF33A0F99 for <last-call@ietfa.amsl.com>; Mon, 21 Sep 2020 07:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 rx1YhIEYO57R for <last-call@ietfa.amsl.com>; Mon, 21 Sep 2020 07:09:35 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AAAE3A0ED2 for <last-call@ietf.org>; Mon, 21 Sep 2020 07:09:34 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id AB12C548441; Mon, 21 Sep 2020 16:09:29 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A22DF440059; Mon, 21 Sep 2020 16:09:29 +0200 (CEST)
Date: Mon, 21 Sep 2020 16:09:29 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Kent Watsen <kent@watsen.net>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, last-call@ietf.org, Mark Nottingham <mnot@mnot.net>, Warren Kumari <warren@kumari.net>
Message-ID: <20200921140929.GI50637@faui48f.informatik.uni-erlangen.de>
References: <CAHw9_iK85gYnPYt4y6qzvYnbXgOD8W88UZ9t_TaP=_M9kvvCjA@mail.gmail.com> <15446.1600268896@localhost> <01000174b0f5e772-3209a6e8-b5a0-4dee-89c2-9dda770b1bfe-000000@email.amazonses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <01000174b0f5e772-3209a6e8-b5a0-4dee-89c2-9dda770b1bfe-000000@email.amazonses.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/RRDCWPoMBmmIQAxWceezWZoglKE>
Subject: Re: [Last-Call] Post approval change on draft-ietf-anima-bootstrapping-keyinfra
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2020 14:09:38 -0000

Thanks, Kent

Reading that rfc8040 section, i am still in the dark which specific problem
this mechanism attempts to solve. Alas, it does not describe this or
points to a specific place in RFC7320.

Or to put it more practically: 

If i can not allocate /.well-known/brski, why would i then be guaranteed to be able to allocate /.well-known/host-meta ?

Cheers
     Toerless

On Mon, Sep 21, 2020 at 01:58:59PM +0000, Kent Watsen wrote:
> FWIW, an equally-good (I think) alternative to hardcoding a .well-known mount point is to use the existing ???host-meta??? document, as RESTCONF describes here: https://tools.ietf.org/html/rfc8040#section-3.1 <https://tools.ietf.org/html/rfc8040#section-3.1>.
> 
> K.
> 
> 
> > On Sep 16, 2020, at 11:08 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> > 
> > 
> > Warren Kumari <warren@kumari.net> wrote:
> >> having to assume EST. Therefore the above BRSKI diff (and BRSKI-AE) propose
> >> to introduce a /.well-known/brski registry.
> > 
> > I believe that I ran the text by Mark, who I believe is the /.well-known
> > expert reviewer.  I believe that he said that it looked good, but it would be
> > great if Mark could confirm that I got it right.
> > 
> >>> Dear ANIMA WG
> >>> 
> >>> This email starts a 2 week call for consensus to modify draft-ietf-anima-bootstrapping-keyinfra
> >>> such that new well-known URIs introduced by BRSKI will use a /.well-known/brski
> >>> prefix instead of the pre-existing /.well-known/est prefix.
> >>> 
> >>> The proposed change can be seen at the following rfcdiff URL:
> >>> 
> >>> https://www.ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-43&url2=draft-richardson-anima-brski-renamed-00
> >>> 
> >>> This consensus call will end on September 14, 23:59 UTC
> >>> This consensus call is ONLY for said change and not for any other aspects of BRSKI.
> > 
> > Existing implementers have agreed to the change.
> > 
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
> >           Sandelman Software Works Inc, Ottawa and Worldwide
> > 
> > 
> > 
> > 
> > -- 
> > last-call mailing list
> > last-call@ietf.org
> > https://www.ietf.org/mailman/listinfo/last-call
> 

> -- 
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call


-- 
---
tte@cs.fau.de

v2.23.0 | Report a Bug | By Email