Re: [Anima] last minute changes to BRSKI to do endpoint discovery

"Fries, Steffen" <steffen.fries@siemens.com> Mon, 27 July 2020 05:41 UTC

Return-Path: <steffen.fries@siemens.com>
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 950753A16E6 for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 22:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 gIAo_4CjKvcl for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 22:41:37 -0700 (PDT)
Received: from gw-eagle2.siemens.com (gw-eagle2.siemens.com [194.138.20.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DAE83A16E4 for <anima@ietf.org>; Sun, 26 Jul 2020 22:41:37 -0700 (PDT)
Received: from mail1.dc4ca.siemens.de (mail1.dc4ca.siemens.de [139.25.224.78]) by gw-eagle2.siemens.com (Postfix) with ESMTPS id B020946800B; Mon, 27 Jul 2020 07:41:34 +0200 (CEST)
Received: from DEMCHDC8A0A.ad011.siemens.net (demchdc8a0a.ad011.siemens.net [139.25.226.106]) by mail1.dc4ca.siemens.de (Postfix) with ESMTPS id 467CD15C6636F; Mon, 27 Jul 2020 07:41:33 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC8A0A.ad011.siemens.net (139.25.226.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Mon, 27 Jul 2020 07:41:33 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003; Mon, 27 Jul 2020 07:41:33 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "anima@ietf.org" <anima@ietf.org>, "max pritikin" <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
Thread-Topic: AW: last minute changes to BRSKI to do endpoint discovery
Thread-Index: AQHWX7nZAFTFfGkZ50WeAMpw9tqZsKkTGwkAgALeAICABPcmQA==
Date: Mon, 27 Jul 2020 05:41:33 +0000
Message-ID: <4b900e875bea48e685d430dac3af74c8@siemens.com>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost>
In-Reply-To: <6971.1595562387@localhost>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.145.220.66]
x-tm-snts-smtp: A6FFAC3F26B48943EFD7A70B05461D7F8F36EBAC626EE07AD93E7D60B0D078CA2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/rtyvH8y_msGI7j-T9gE7SUFDupM>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 27 Jul 2020 05:41:40 -0000

Hi Michael,

> From: Michael Richardson <mcr+ietf@sandelman.ca>
>     > I would appreciate to use /.well-known/brski for the endpoints
>     > specified in BRSKI and use /.well-known/est for those specified in
>     > RFC7030.
>     > This offers more flexibility for future extensions like BSKI-AE.
> 
> Such a change would be large to BRSKI.
> 
> Brian suggests making this an update.
> But, I think it would cause market confusion if we published an RFC with
> /.well-known/est/requestvoucher, and then said, "no sorry, no we meant
> /.well-known/brski/requestvoucher"
> 
> Would there be pledge implementations that would try one and then the
> other?
> I will say that I'm *NOT* keen on including the Resource Link GET, but I can
> tolerate it.
The intention was not to include the discovery mechanism right away into BRSKI. It was rather the question to rename the BRSKI defined endpoints to /.well-known/brski to underline, that the voucher exchange is independent from the chosen enrollment protocol. The discovery should be done in BRSKI-AE, which should update the base specification then. I understand, that we should not state /.well-known/est and the immediately update it afterwards to /.well-known/brski . That would look awkward. If we just rename the endpoints in BRSKI, would that cause such a large change? 

Best regards
Steffen


> 
> 
> I think that we'd need to:
>   1) blessing of our AD.
>   2) pull document out of RFC-editor queue.
>   3) revise it, do a WGLC on revision.
>   4) get AD to put it back in queue.
> 
> The ROLL WG did this for a document last year when we realized that a new
> document obsoleted some of the recommendations.  It took longer than
> planned, but that was partly because the other document had to settle a bit.
> I think we could do this in the time for the 2nd WGLC and about four days.
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
>