IETF Logo Mail Archive

Re: [Anima] Cloud BRSKI discussion -- Option 1 use cases

Michael Richardson <mcr@sandelman.ca> Mon, 25 November 2019 09:21 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 726661200DE for <anima@ietfa.amsl.com>; Mon, 25 Nov 2019 01:21:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 wK1IcuhHZFM2 for <anima@ietfa.amsl.com>; Mon, 25 Nov 2019 01:21:45 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA93A12006B for <anima@ietf.org>; Mon, 25 Nov 2019 01:21:45 -0800 (PST)
Received: from dooku.sandelman.ca (x2f7f413.dyn.telefonica.de [2.247.244.19]) by relay.sandelman.ca (Postfix) with ESMTPS id 1C4BF1F47D; Mon, 25 Nov 2019 09:21:43 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 0159513A4; Mon, 25 Nov 2019 17:14:42 +0800 (+08)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: "anima@ietf.org" <anima@ietf.org>
In-reply-to: <9c60c895-9e14-c064-9f4a-306c5d7a1105@gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B9299B9FAD2@NKGEML515-MBX.china.huawei.com> <MN2PR11MB3901DD8CF27429ECAF1AA874DB780@MN2PR11MB3901.namprd11.prod.outlook.com> <28576.1574580524@dooku.sandelman.ca> <9c60c895-9e14-c064-9f4a-306c5d7a1105@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Sun, 24 Nov 2019 21:22:46 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 25 Nov 2019 10:14:42 +0100
Message-ID: <1120.1574673282@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yccgpVbsELMT2c6e5lvAJbQooeA>
Subject: Re: [Anima] Cloud BRSKI discussion -- Option 1 use cases
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, 25 Nov 2019 09:21:47 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > One thing that doesn't seem to be clear either in BRSKI or in
    > draft-friel-anima-brski-cloud is where the Cloud Registrar's "well
    > known" URI comes from and how the pledge knows it. Is it vendor
    > specific or what?

It is vendor specific, and it's baked in.

The idea is that we can transform the well-known, but very much proprietary
"call-home" process that many devices use today into something that enables a
transfer of ownership mechanism.

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

v2.23.0 | Report a Bug | By Email