Re: [Anima] two EST question/suggestions

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 03 October 2017 21:22 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 9B81A132D79 for <anima@ietfa.amsl.com>; Tue, 3 Oct 2017 14:22:00 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 ErIKqCTKIRvr for <anima@ietfa.amsl.com>; Tue, 3 Oct 2017 14:21:59 -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 59D161332DF for <anima@ietf.org>; Tue, 3 Oct 2017 14:21:59 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 18E0BE1E5 for <anima@ietf.org>; Tue, 3 Oct 2017 17:27:21 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6975A81949 for <anima@ietf.org>; Tue, 3 Oct 2017 17:21:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <5c00237e-98fa-9764-d816-919307bdd994@gmail.com>
References: <961.1504038708@obiwan.sandelman.ca> <BAA96F8A-C61E-4DE1-9837-7964A0E8B4A2@cisco.com> <2a1cf1e7-f668-cf76-d471-78585d7ad7ba@cisco.com> <8b165f89-3be1-c814-5a88-bf62f708972f@gmail.com> <27231.1505249495@obiwan.sandelman.ca> <ce8e9ee0-6695-b113-94b9-bb56142c537d@gmail.com> <6079.1505260663@obiwan.sandelman.ca> <5c00237e-98fa-9764-d816-919307bdd994@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: Tue, 03 Oct 2017 17:21:58 -0400
Message-ID: <24893.1507065718@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/MM3hW9GRtoZzZ5ghNuh-vKlv4TE>
Subject: Re: [Anima] two EST question/suggestions
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: Tue, 03 Oct 2017 21:22:00 -0000

The text in the ACP document which I'm moving into the BRSKI document says:

               In the above (recommended) example the period could be 60 seconds and the
               indicated ttl of 180000 msec means that the objective would continuously be
               cached by ACP devices even when two out of three messages are dropped in transit
               (which is unlikely because GRASP hop-by-hop forwarding is
               realiable).

In a PPP overlay, the M_FLOOD's can clearly be sent over TCP.
And that part is reliable, but once inside the GRASP daemon, whether or not
an M_FLOOD is relayed really depends upon whether or not there is available
buffer space.

You have to drop traffic going into the TCP links if there is no room
available (vs blocking on write).  So I am not sure the () message above
is justified.

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