IETF Logo Mail Archive

Re: [Anima] proxy discovery of registrar

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 02 August 2017 19:46 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 DE723132034 for <anima@ietfa.amsl.com>; Wed, 2 Aug 2017 12:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 FJ_BvClZ4uQT for <anima@ietfa.amsl.com>; Wed, 2 Aug 2017 12:46:31 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A7F6127869 for <anima@ietf.org>; Wed, 2 Aug 2017 12:46:31 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 93E5CE032; Wed, 2 Aug 2017 15:48:22 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 47AFB80631; Wed, 2 Aug 2017 15:46:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org
In-Reply-To: <59bab2b2-5cf7-2f5f-d36d-9a7d0956c8b6@gmail.com>
References: <9024.1501634321@obiwan.sandelman.ca> <59bab2b2-5cf7-2f5f-d36d-9a7d0956c8b6@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.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, 02 Aug 2017 15:46:30 -0400
Message-ID: <13869.1501703190@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oJkW2VvFVqBihk2jRziHGyP8vwA>
Subject: Re: [Anima] proxy discovery of registrar
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
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, 02 Aug 2017 19:46:34 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> Toerless has instead written the M_FLOOD mechanism.
    >> We started a thread a few weeks ago about this... what happened to it, I
    >> would have to look.  In either case, I would like to please discuss this
    >> in the context of the BRSKI document, not the ACP.

    > Sure. My understanding was discover/synchronize which is what
    > I put in draft-carpenter-anima-ani-objectives-03 (and in
    > the latest demo code if anyone cares:
    > https://github.com/becarpenter/graspy/blob/master/brski-demo.pdf ).

    > But this needs to be a firm consensus in the BRSKI team.

I did take a look at the code yesterday in the end, and I'll like run it
sometime soon, but I decided I didn't want to reverse engineer the spec from
the code :-)

    >> o  a synchronization objective option

    > That implies that the registrar has something to announce to
    > the proxy (such as "I support foobar and barfoo").

Do we have some preference for "AN_join_register" (and AN_Proxy and AN_ACP),
or is the AN_ prefix unwanted?

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

v2.23.0 | Report a Bug | By Email