IETF Logo Mail Archive

Re: [Anima-signaling] Concern about GRASP Flood message

Toerless Eckert <eckert@cisco.com> Thu, 21 July 2016 09:24 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: anima-signaling@ietfa.amsl.com
Delivered-To: anima-signaling@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD1212DC06 for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 02:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 4_D4T7jrAMMC for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 02:24:03 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE3B0127078 for <anima-signaling@ietf.org>; Thu, 21 Jul 2016 02:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1199; q=dns/txt; s=iport; t=1469093043; x=1470302643; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=sZSis8nkGbGnCOotp5TgmBhoFeNHy9ZZc3zlufay9DI=; b=hfpuGRgEc47cQMGL0wZQ3r3ohvoLlL40dh/HeBn/fQxe7RcDSiE+bwcP 6bdYGPnYaikOz48y00/S7znvhaLNKStEA9cEZtVTMjbrsIcl2tGZdTsBx ByPaqMd5JpPg8ME1UfCrrCZPC9eXTAaUopP19ZQDTp7wschseRbmO6JPv U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAwBUlJBX/4kNJK1dgz+BUrZVgg+Be?= =?us-ascii?q?4YaAoEsOBQBAQEBAQEBZSdBDgGEDQEFOj8QCxgJJQ8FSROIML1HAQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBHIp3ihsFjwGEPIVpjmEKjzqQIR42hBMcMoRagn4BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,398,1464652800"; d="scan'208";a="128298915"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Jul 2016 09:23:37 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u6L9NaE8005809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2016 09:23:36 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id u6L9NaeJ023087; Thu, 21 Jul 2016 02:23:36 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id u6L9NaAV023086; Thu, 21 Jul 2016 02:23:36 -0700
Date: Thu, 21 Jul 2016 02:23:36 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20160721092336.GQ7377@cisco.com>
References: <77afcc64-ca15-003d-661b-a31ed4866149@gmail.com> <579073DB.50505@tzi.org> <00b894f9-61ca-c5cf-b8d8-aae1a8262c04@gmail.com> <20160721075059.GJ7377@cisco.com> <aa089c05-9465-4192-72dd-5b66d78c77d5@gmail.com> <57908BB9.4030307@tzi.org> <15ed0e03-bf1e-6e04-67ac-dbbaa428711f@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15ed0e03-bf1e-6e04-67ac-dbbaa428711f@gmail.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-signaling/IkJdwYT2vBhyWwYeQDRCSa2UU3A>
Cc: Carsten Bormann <cabo@tzi.org>, Anima signaling DT <anima-signaling@ietf.org>
Subject: Re: [Anima-signaling] Concern about GRASP Flood message
X-BeenThere: anima-signaling@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the signaling design team of the ANIMA WG <anima-signaling.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-signaling/>
List-Post: <mailto:anima-signaling@ietf.org>
List-Help: <mailto:anima-signaling-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 09:24:05 -0000

Btw: There where two other flooding refinements we discussed:

Store the original-loop-count in the packet so the GRASP API on
receivers could provide the hopcount distance of the announcer
distance = original-loop-count - loop-count.

Refine flood pruning as: 
 If the distance of a received announcement is smaller than the
 distsance of the cached announcement, flood the new packet (and put
 into cache). 

Cheers
    Toerless

On Thu, Jul 21, 2016 at 09:06:02PM +1200, Brian E Carpenter wrote:
> On 21/07/2016 20:45, Carsten Bormann wrote:
> > Brian E Carpenter wrote:
> >> There is already one use case emerging: using Flood
> >> to announce bootstrap Registrars to all bootstrap Proxies. A proxy needs to
> >> be able to choose which registrar to use, so needs to
> > 
> > Well, the content of the message then appears to be "x is offering to be
> > bootstrap registrar".  This can of course alternatively be represented
> > by "x says: 'I am offering to be bootstrap registrar'".
> 
> Exactly, but the Flood mechanism loses track of x when the message is relayed.
> That would need a protocol change.
> 
>    Brian

-- 
---
Toerless Eckert, eckert@cisco.com

v2.8.7 | Report a Bug | By Email