IETF Logo Mail Archive

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

Toerless Eckert <eckert@cisco.com> Thu, 21 July 2016 08:13 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 A149012DB01 for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 01:13:14 -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 8q4OHd6SqfVb for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 01:13:13 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CA2F12DA08 for <anima-signaling@ietf.org>; Thu, 21 Jul 2016 01:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1848; q=dns/txt; s=iport; t=1469088793; x=1470298393; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=SGy1B5y11zCXCAqnV6LihTCxniJVUjFG3MOlH5syboY=; b=MYB5kMeJ3DqqDCWvS00fIkAuw5weIIzZUrZGABUwhgvnLflM7dDtXSKN ETzDH8jrFmtPQKLTfgkhDiuulgft8QoX9+Uhyxni0E3uuPIY3OBWPb6lo 726h4bnTDrT22iAiRLw6IBjmJOeVBmrNITo9pARAIb7MyKbL8/uf/+Cg8 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtAwCxg5BX/5NdJa1dgz9WfLhigXsih?= =?us-ascii?q?XgCgSw4FAEBAQEBAQFlJ0EOAYQNAQUBATg0CxALGAklDwUTNhOIMA69KwEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBARcFineKGwWPAYQ8hWmOYQqPOpAhHjaEExwyhFqCf?= =?us-ascii?q?gEBAQ?=
X-IronPort-AV: E=Sophos;i="5.28,398,1464652800"; d="scan'208";a="300335137"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jul 2016 08:13:11 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u6L8DBTI010911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2016 08:13:11 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 u6L8DBOf019563; Thu, 21 Jul 2016 01:13:11 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id u6L8DAma019562; Thu, 21 Jul 2016 01:13:10 -0700
Date: Thu, 21 Jul 2016 01:13:10 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20160721081310.GK7377@cisco.com>
References: <77afcc64-ca15-003d-661b-a31ed4866149@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <77afcc64-ca15-003d-661b-a31ed4866149@gmail.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-signaling/P8C07NMmON_FrFiORrPT4TI4HrA>
Cc: 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 08:13:14 -0000

Coouple of thoughts:

Typically, objectives (synchronization) data would include a locator
for some locator(s) of the objective. Like the EST locator of
a registrar objective. 

The locator ultimately needs to be (address, proto(udp/tcp),port).

Most of the time the address is that of the announcer. If not, then
itswhat i'd call a "third-party" locator.

Its nice if one can logically distinguish normal from third-party
locators. Its nice if you do not need to repeat encoding the
address if you have emultiple locators.

So i would like to see the address of the originator of flood messages
to be available, and locators would have the possibility for the
address filed to be length 0, in which case the address is assumed to be
the one of the originator.

Cheers
    Toerless

On Thu, Jul 21, 2016 at 06:58:18PM +1200, Brian E Carpenter wrote:
> During various discussions this week, I decided there is an issue to decide
> around the GRASP Flood message.
> 
> As it's currently defined, the node/ASA that receives a flooded objective
> doesn't know where it came from; the flood relaying mechanism simply
> loses the original source locator.
> 
> Is this a problem? Does the recipient of a flooded objective sometimes
> need to know the source?
> 
> If so, we'd have to add a field to the Flood message. For example, we could
> allow it to carry a Locator option.
> 
> BTW, flooded objectives have no lifetime - they are valid until overwritten
> by a subsequent Flood message.
> 
> Comments?
> 
> -- 
> Regards
>    Brian Carpenter
>    (Don't blame me, I voted Remain.)
> 
> 
> _______________________________________________
> Anima-signaling mailing list
> Anima-signaling@ietf.org
> https://www.ietf.org/mailman/listinfo/anima-signaling

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

v2.8.7 | Report a Bug | By Email