IETF Logo Mail Archive

Re: [Anima] Use of M_FLOOD for discovery of Proxy

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 18 June 2017 16:58 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 CF2FF12949E for <anima@ietfa.amsl.com>; Sun, 18 Jun 2017 09:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 6vE4emTF_nKF for <anima@ietfa.amsl.com>; Sun, 18 Jun 2017 09:58:55 -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 E42A2129482 for <anima@ietf.org>; Sun, 18 Jun 2017 09:58:54 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 72B5A4A002; Sun, 18 Jun 2017 13:00:19 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 83A096380F; Sun, 18 Jun 2017 12:58:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>
cc: Anima WG <anima@ietf.org>
In-Reply-To: <20170617000102.GI20021@faui40p.informatik.uni-erlangen.de>
References: <149566389334.8737.940293315082013190@ietfa.amsl.com> <e24d09bd-9497-3066-7659-895c664bb248@gmail.com> <2540.1497281932@obiwan.sandelman.ca> <20170617000102.GI20021@faui40p.informatik.uni-erlangen.de>
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: Sun, 18 Jun 2017 12:58:53 -0400
Message-ID: <28650.1497805133@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/udvAc7AN6YIdkPm2btuS92vCkVk>
Subject: Re: [Anima] Use of M_FLOOD for discovery of Proxy
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: Sun, 18 Jun 2017 16:58:57 -0000

Toerless Eckert <tte@cs.fau.de> wrote:
    > 2. If we send the M_FLOOD for BRSKI and ACP periodicially once every 30 seconds,
    > i don't think that we should be worried about sending one instead of two packets.

    > From grasp-13 it seems that i can only put a single grasp-message into a single
    > UDP packets. And i can only put a single objective into a single grasp-message.

Because we can announce multiple objectives.

    > I don't think i want a single objective to announce both ACP and BRSKI. Those
    > are features of two different ASA. How would i implement this.

It would be a feature of the single, unpriviledged DULL instance.
That instance would be configured by some larger intent.

If a node doesn't want to announce itself as a proxy, it would omit that
objective.

As for implementation, I've done it. It's a question of about a page of C
code (given a cbor library), or about ten lines of ruby. Probably a similar
number of lines of python.


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

v2.23.0 | Report a Bug | By Email