Re: [babel] Babel filtering: routing policies

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 26 August 2019 04:52 UTC

Return-Path: <mjethanandani@gmail.com>
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 09C66120823 for <babel@ietfa.amsl.com>; Sun, 25 Aug 2019 21:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=gmail.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 aYT_oBdKs-xI for <babel@ietfa.amsl.com>; Sun, 25 Aug 2019 21:52:43 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2FCA1200A4 for <babel@ietf.org>; Sun, 25 Aug 2019 21:52:42 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id bj8so9376897plb.4 for <babel@ietf.org>; Sun, 25 Aug 2019 21:52:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JRawpdPfeyR05JamX4wz50OGZ9LNI67vlWPccN67Xz8=; b=TSVSE0RyoGfiwhaMGqpncQvCqz2HIMOet7DsQ47FYODBoZB7gY7WmXvfHPF/D/iYxe wSueRKCJ0vg6Fmtg3OXa0vWPHloiHGFyIo3MHt/1mRXyAGe2oh1XRTz2FPLbw4wepGLZ 3bsfDbagUz/PUOdaGT2z3OdB8rb+Ge0csDaSZtiRml8MglQADDvTnc6BtxSU5Kl8OJts CcyjUwHTxG1ugxlDFoL3vXLJokHkMI14IWFAZEzxTdf+awtwWtZcrNppTGQ3TzJpFg9d HdVylnmf6py4XEGrWXv0Lxm+F2FvDrueFWJ/jDvqYJvuf9vXDk5u1AYUGFd+gfDaipkD tNYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JRawpdPfeyR05JamX4wz50OGZ9LNI67vlWPccN67Xz8=; b=NKNzBXzZIIa0AeYVmGUhAhHQPUAS611tITzIAXCFlnXeXRk1ZD8KXe3Vn0N/Qw7SET O2r9ri1ohWaTsttv9U/m7I190hrKT8IQupWKj5J03FIsE7ZKkVA3q92g/p2IhTZrgazA gXLhpXs5rAR+W6NzehsqHOoDDHeA3HuqffBKF5e9tZ7Asg92YgbalCsCwRUIMsH1XMlh HdFStJo5SMdHEVi4scCNut2lQ4pKEb0W9QinU92gao3URxdPMGCKIf9DsyPDS4F1cS+0 /iiJ7BG7gmuqjORDUONvRQb6pysIbpT/NyvGvV5kzS5uo7n+R3seEmuYwbvHvXeUDzEf JfyA==
X-Gm-Message-State: APjAAAV//dIHQCbYk/G3IEZUw5yf3rjd2ocWc/Fi4YBcQH5JlZJNa/c9 sFhCe1g9ZWNJSeqAlgVlO4o=
X-Google-Smtp-Source: APXvYqxAs8uiUuS/EUAabUb2zaV2/BsZrQWO7nmDsNgEcWTHtboZmjhCByifRKVp6N+kPdJN0QPTmQ==
X-Received: by 2002:a17:902:b68f:: with SMTP id c15mr17305957pls.104.1566795162387; Sun, 25 Aug 2019 21:52:42 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:808a:6ea6:5ac:ad11? ([2601:647:5600:5020:808a:6ea6:5ac:ad11]) by smtp.gmail.com with ESMTPSA id c5sm10359935pfo.175.2019.08.25.21.52.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Aug 2019 21:52:41 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <0D53377C-509C-40B2-997C-B184876C6028@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_202D553E-CA59-4914-BFB4-694ED59935CA"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 25 Aug 2019 21:52:39 -0700
In-Reply-To: <874l277c22.wl-jch@irif.fr>
Cc: babel@ietf.org, Barbara Stark <bs7652@att.com>
To: Juliusz Chroboczek <jch@irif.fr>
References: <87lfwn5d3d.wl-jch@irif.fr> <D659D3AF-B73D-417F-9751-3CD4DE36B4E2@gmail.com> <874l277c22.wl-jch@irif.fr>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/FSyQoANMmxQ9ZVAgrVyUePfZY4s>
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: Mon, 26 Aug 2019 04:52:45 -0000


> On Aug 23, 2019, at 3:27 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
>> In order to make sure we are talking the same language, would you say a given
>> chain is equivalent of a “defined set” as defined by
>> draft-ietf-rtgwg-policy-model?
> 
> No.  A chain would correspond to a sequence of policy statements, if
> I read this document right.

According to the routing policy draft.

   Policy statements in turn consist of simple condition-action tuples.

but what you seem to be defining by “install”, “redistribute” and “out” are ...

   The models provides a set of generic sets that can be used for
   matching in policy conditions.  These sets are applicable for route
   selection across multiple routing protocols.  They may be further
   augmented by protocol-specific models which have their own defined
   sets. 

If not, how would you define your sets?
 
> 
>> I understand that these are babel specific,
> 
> I think that only matching on router-id is Babel-specific, all the others
> are fairly generic.
> 
>> will extend the policy model to add these chains as “defined sets".
> 
> I don't think you need to extend anything.  Matching on router-id is not
> essential.
> 
> On the other hand, it looks to me like it's more expressive than anything
> that any implementation of Babel known to me has ever implemented.  Since
> I'm still not sure what's the purpose of the YANG model, I don't know if
> that's a problem or not.

If any particular implementation does not support the more expressive policy statement, they can choose to deviate (not support) these policies. It can choose to support only the policies it defines.

Thanks.

> 
>>    There exist other actions, more specialised -- see the manual page for
>>    details.
> 
>> I see two more, src-prefix and table. Is there more?
> 
> Not in babeld.  I haven't checked BIRD.
> 
> -- Juliusz