IETF Logo Mail Archive

Re: [babel] Mandatory sub-TLVs in Next Hop and Router-ID

Toke Høiland-Jørgensen <toke@toke.dk> Thu, 25 May 2017 11:44 UTC

Return-Path: <toke@toke.dk>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018361294D4 for <babel@ietfa.amsl.com>; Thu, 25 May 2017 04:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level:
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 aivFbvahpExg for <babel@ietfa.amsl.com>; Thu, 25 May 2017 04:44:42 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43F81127BA3 for <babel@ietf.org>; Thu, 25 May 2017 04:44:42 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1495712674; bh=21C3h7myhbNTK8CUsO/weC1+fxpqNHLhWNWk9J2OyDk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=EBV/cQQLF5icI7Yq9uG+mdGL1bO0rx+HL/yy2h3F5ZMXj7pYJieDtJD78ZimsPTf4 hOX4/6yHKMJh/y8ky98gRCv3IxFcDc2qJv0bU8NagY3wcAXQDoVoI4hTlzVbow8Oiz KGscbttgPIZVzarp1n9c8F+Q+GLfboQ1qMRLoEw+OO/iHQaJuoIWFa7zZVJwn88c7l xG3MnpxxP2XW415NcCJvasFUYD6fWOGplmCxX8FIS6wiTwYwZTIHGrdhHGoVBrhexZ 3yocU6Vfvf9O3VI3J/ea2OpT+ZPUy0tcUsrS4/ldC8Skqo/k29ZvkUQM6/TdINRhgk Ezg8ylF9FPIoA==
To: Juliusz Chroboczek <jch@irif.fr>
Cc: babel@ietf.org
References: <87y3tmbg1e.wl-jch@irif.fr> <87zie2gylh.fsf@alrua-x1> <87h90abbp0.wl-jch@irif.fr> <87efvebb9x.wl-jch@irif.fr> <513D2D6A-E00A-4D46-9762-8D57F0E57B22@iki.fi> <8760gqb9ss.wl-jch@irif.fr> <87shjus424.fsf@alrua-karlstad> <87wp969tvn.wl-jch@irif.fr>
Date: Thu, 25 May 2017 13:44:32 +0200
In-Reply-To: <87wp969tvn.wl-jch@irif.fr> (Juliusz Chroboczek's message of "Wed, 24 May 2017 17:06:36 +0200")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87o9uhrwin.fsf@alrua-karlstad>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/EVOikJBiUVa8PCfJw3Q3OYqk_QE>
Subject: Re: [babel] Mandatory sub-TLVs in Next Hop and Router-ID
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 May 2017 11:44:45 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

>> I was thinking along the lines of being able to express "this next-hop
>> is only available from this source prefix (due to, e.g., firewall
>> rules)". Something like:
>
>> nexthop (sub-tlv: only from source-prefix A)
>> nexthop (sub-tlv: only from source-prefix B)
>
>> where the implementation would pick the right one, and an implementation
>> that didn't understand the sub-tlv would ignore both.
>
> Hmm... so that would require the current semantics, the one you've
> been arguing against?

Yeah, realise that. As I said, not sure if it is actually useful; more
of a thought experiment to come up with a reason. I do still think being
consistent is better :)

-Toke

v2.23.0 | Report a Bug | By Email