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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 27 July 2020 20:26 UTC

Return-Path: <brian.e.carpenter@gmail.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 AB0513A0985 for <anima@ietfa.amsl.com>; Mon, 27 Jul 2020 13:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, 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=gmail.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 jGxRH_gSs-Ol for <anima@ietfa.amsl.com>; Mon, 27 Jul 2020 13:26:50 -0700 (PDT)
Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (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 451853A098E for <anima@ietf.org>; Mon, 27 Jul 2020 13:26:50 -0700 (PDT)
Received: by mail-pg1-x543.google.com with SMTP id t6so10585704pgq.1 for <anima@ietf.org>; Mon, 27 Jul 2020 13:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Poz1xo7nnmy5+p3mvLIT0/qlolNc4uwFZisfHgTrJw8=; b=f7+xvjaWPcoZaaOGo7RoWI8e7jU5tcIqI83MAHnW/HTwcbnX7sxz/zFhuefHIuYgBy eNZ0tglAr93XJKG7OWuFXrHrjQ3zy5MVDSYS6ccBUFxmN8QsRTj5dXn5EFce1IPTtOvl jr7xbgSa4K6JBhVYgXcOgajMNUq28DuBCO7ve3DTrJbrgAMCYFf4aTNDSdFIM0xozb+n +84pr2fLlRXZYL/tXT4b6g3kCPCVDBBKdF6smOS2aD8cqeZV1YecJwVW3cHSMMwG9yEO +ywD1bkGe+Z+YqVpU68odtmIFkP8VoXBF8ROGOuC+h6g4n+sCjazD7iGm1ZW6pat1HmE mNOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Poz1xo7nnmy5+p3mvLIT0/qlolNc4uwFZisfHgTrJw8=; b=g2pJcdnRssiqqV9jjq6mYIHoh0wUMeUuJj3tXNFG0St8DN2plU/gLx35A8no+JOt/c brcOKRA05v2wt7dLEtUoUcFROXn1GLX+dCPCcRTMKVcf/WFTsU16m4Iujuo6aZN3CUQY kUJuepZOAA0ZKluQADlkzkpalhvZYFMSD4zsk/cTJUjX2Yw1RKAYXbKCt2BJ+m+uA9UA K2AX/eeoREGwmUK9uz/5Vb0gILepU1ozPsAivATuQWaVk2cGUfXPLh6q5hDwx0s996Ce WQkoW6DNjAysKgrv/8nEuuQah6iMD0JbXCX52k9U/TMCgpVGwuZBcNZJToNA+6YNfve9 rvIQ==
X-Gm-Message-State: AOAM5317GRo6cv1YRSzPLEMLts6jhBcCFOfWWpFd1czCWRLPz+XMiyBm Ckef8UM5+V6dv8ElFGlyZTA=
X-Google-Smtp-Source: ABdhPJxZXEzwBLyiu4iTg3O9Vrbbm8oBM/Nwt9mO17KERYCYiis5grGtK0wP4kF6p5T1fOWF3C+XLw==
X-Received: by 2002:a63:9201:: with SMTP id o1mr19130486pgd.99.1595881609745; Mon, 27 Jul 2020 13:26:49 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id d37sm15876859pgd.18.2020.07.27.13.26.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jul 2020 13:26:48 -0700 (PDT)
To: "Fries, Steffen" <steffen.fries@siemens.com>, 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>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost> <4b900e875bea48e685d430dac3af74c8@siemens.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <173a8001-bee3-4a88-1289-d80ea35cde40@gmail.com>
Date: Tue, 28 Jul 2020 08:26:45 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <4b900e875bea48e685d430dac3af74c8@siemens.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0N0bytWbzYpPsY0Qezg-7TvkDsE>
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 20:26:53 -0000

On 27-Jul-20 17:41, Fries, Steffen wrote:
> 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"

I meant that the update would say
"please *add* /.well-known/brski/requestvoucher"

An extension, not an amendment (draft-kuehlewind-update-tag).

   Brian

>>
>> 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 =-
>>
>>
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
>