IETF Logo Mail Archive

Re: [babel] Babel filtering: routing policies

Toke Høiland-Jørgensen <toke@toke.dk> Thu, 25 July 2019 10:56 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 D70D412002F for <babel@ietfa.amsl.com>; Thu, 25 Jul 2019 03:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 q6i71ADDx00W for <babel@ietfa.amsl.com>; Thu, 25 Jul 2019 03:56:05 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2a00:7660:6da:2001::664]) (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 3B6C0120139 for <babel@ietf.org>; Thu, 25 Jul 2019 03:56:05 -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=1564052161; bh=NPqYv6VfCt+hgRA2gzdpLPHH9D41adCwH4lIdFhcILs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=PXsrg1uiVQlse1qBGrKby1e9n4KhsY3h+AuO9v2tT2yjulAPIm+j5aQRv4gge32jb dZ4CNYjAEn7tokiSNvgNrsJ1pThKGOOQZLLOtObDxFfmge/fvHK6OaLGMFwbuyjFNn pHVUw5alQbRWoza8p6Qm/s8OC3Kg08TEdouPXkMX67sjT2kGTANqqhS9VSi5aXE2yX 02wpiJNjVU9E8M75X2+vjLcFVGwyY8fUhUGJii3aYvAErY2f/BMPbrgy5MNbJtnhQz 6FfFR1SAou89Gn4NZeM60kz5Hca3lZECrGPIfulQO4mAQi6fma2pzTg5OpaVW7TgGT nlw2EE9QnGKrA==
To: Juliusz Chroboczek <jch@irif.fr>, babel@ietf.org
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, Barbara Stark <bs7652@att.com>
In-Reply-To: <87lfwn5d3d.wl-jch@irif.fr>
References: <87lfwn5d3d.wl-jch@irif.fr>
Date: Thu, 25 Jul 2019 12:56:00 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87blxiz8lb.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/fxByOkTapPpIQ84n3te6_5HJmgA>
Subject: Re: [babel] Babel filtering: routing policies
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
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 Jul 2019 10:56:08 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

> Dear Barbara, dear Mahesh,
>
> All distance-vector routing protocols, including BGP and Babel,
> intrinsically support flexible routing policies.  In the Babel community,
> we consider the way of defining such policies as an implementation
> feature, and they are not part of the protocol definition.
>
> The following therefore applies to babeld, the "reference"
> implementation.

I'll add that the Bird implementation uses Bird's filtering language,
which allows filtering similar to that but has a whole different syntax
and semantics. See https://bird.network.cz/?get_doc&v=20&f=bird-5.html
for details.

-Toke

v2.23.0 | Report a Bug | By Email