Re: [Anima] some minor questions about ACP -23

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 11 March 2020 14:44 UTC

Return-Path: <mcr+ietf@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 D5D4E3A07BC for <anima@ietfa.amsl.com>; Wed, 11 Mar 2020 07:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, 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 RxSHFuepIrP7 for <anima@ietfa.amsl.com>; Wed, 11 Mar 2020 07:44:05 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E01DA3A07C5 for <anima@ietf.org>; Wed, 11 Mar 2020 07:44:04 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 4C01A38985; Wed, 11 Mar 2020 10:42:49 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 30642AE8; Wed, 11 Mar 2020 10:44:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, anima@ietf.org
In-Reply-To: <c98b5a6e-ddbc-c677-125a-e2ab5b0c6411@gmail.com>
References: <20307.1583842818@localhost> <c98b5a6e-ddbc-c677-125a-e2ab5b0c6411@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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-sha256; protocol="application/pgp-signature"
Date: Wed, 11 Mar 2020 10:44:00 -0400
Message-ID: <18096.1583937840@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0QASGz6aKE0BwmMCdpWG7gUUxts>
Subject: Re: [Anima] some minor questions about ACP -23
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, 11 Mar 2020 14:44:07 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > On 11-Mar-20 01:20, Michael Richardson wrote:
    >>
    >> section 6.1.5 says:
    >>
    >> When BRSKI (see [I-D.ietf-anima-bootstrapping-keyinfra]) is used, the
    >> IPv6 locator of the BRSKI registrar from the BRSKI TLS connection
    >> SHOULD be remembered and used for the next renewal via EST if that
    >> registrar also announces itself as an EST server via GRASP (see next
    >> section) on its ACP address.
    >>
    >> The BRSKI TLS connection is proxied through a join proxy.  The pledge
    >> (new node) never knows what the IPv6 locator of the BRSKI registrar
    >> is.

    > Right, and unless I'm mistaken that remains true even if the registrar
    > is on the same layer 2 link as the pladge; the node containing the
    > registrar also contains a proxy. Pledges don't need a special case for
    > this situation.

yes, my registrar-considerations emphasizes this point and basically
recomments that NOC connect will be mandatory at the beginning.

    mcr> I suggest removing this paragraph, the node should listen for the EST
    mcr> GRASP announcement.


--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-