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

Carsten Bormann <cabo@tzi.org> Thu, 21 July 2016 07:03 UTC

Return-Path: <cabo@tzi.org>
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 94E6012DA55 for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 00:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TuBAU9Yoa0Qu for <anima-signaling@ietfa.amsl.com>; Thu, 21 Jul 2016 00:03:57 -0700 (PDT)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1B7512DA3F for <anima-signaling@ietf.org>; Thu, 21 Jul 2016 00:03:56 -0700 (PDT)
Received: from dhcp-9a4a.meeting.ietf.org (unknown [IPv6:2001:67c:370:152:d927:c758:3112:9a12]) (Authenticated sender: cabo@cabo.im) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 252F6A80DF; Thu, 21 Jul 2016 09:03:53 +0200 (CEST)
Message-ID: <579073DB.50505@tzi.org>
Date: Thu, 21 Jul 2016 09:03:55 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <77afcc64-ca15-003d-661b-a31ed4866149@gmail.com>
In-Reply-To: <77afcc64-ca15-003d-661b-a31ed4866149@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-signaling/RByyWOZRgFn77_CfvEv43FH9SG8>
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 07:03:59 -0000

Is there going to be any security?
Or is a flood message authenticated by the group key protecting the ASA?
If there is data origin authentication, this already provides a source.

Grüße, Carsten


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?
>