[Teas] draft-bestbar-teas-yang-topology-filter - Routing Policy for filtering topologies

Vishnu Pavan Beeram <vishnupavan@gmail.com> Wed, 10 November 2021 14:19 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 990663A1022 for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 06:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 RlIMHCnqkkrV for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 06:19:06 -0800 (PST)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 33A043A1043 for <teas@ietf.org>; Wed, 10 Nov 2021 06:19:06 -0800 (PST)
Received: by mail-io1-xd31.google.com with SMTP id m9so3025883iop.0 for <teas@ietf.org>; Wed, 10 Nov 2021 06:19:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+3LusTojJU6b6aTkvTcu0LdxIa10O3MSe+M+q/jAs/M=; b=AhgG7Z8OpS3uBNuJecb9IVB8XsTVmuxOH4VkFJFL52xYdFZ0Ls9yNtrR0Yrhvj1K9I 1OY2B9m1JhUaIiEQkXIXa8nDCV8+65dbiKRYXvjbJqMNbeQ4RRojhF4+qBFokbegUEZ/ Cp7fuCcODvl/GBHrV/YPWxN7P8iPCRk3pyjA7pwb+b/a/N/CAwXmRiyTd1Q86J8LMFRq UCqk5g5jtm+vFc4XY/cqpiQv88X1JsXF1/0DBEPX+waJRnSn0ZnQRXIetbc3/BjyFz4O lI2C3KWuA5UM8eEZ31WxMzOlhbHF/KlWZNSUgq4aloXt4cl6+hom/YO9YGRaig9RXtar Ukbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+3LusTojJU6b6aTkvTcu0LdxIa10O3MSe+M+q/jAs/M=; b=Pa4BgwgjkSnLsq7KuNJajhXeQYMoMFgH46b7+0vxGgonknzoFbiXl4jFFaG+E8I3pH ExcOj2A/f/EB+MrQ005Bikbeq0QsmQfgKkQQVehEAbuXbsATEQk262w+j0Tpps1ynRco 08eYGqr/ntLdD3KsruASEioWcXWBDdfp9MpwxF4aOv7mn6jLYlpUBZAF87IdYBactqZY EZsmyHEs0Jm6EY9kS/wpPubEc9PYkxutRa1ythUNnRbO+0aARr1M5jz//PwSsvMqQJqv rG8BH9rKMA9nWa30FknphqFM59asi7em6+Ey+rkKpZzaYspXmjltCA9wOWkA61AUrfpM W2Vg==
X-Gm-Message-State: AOAM530VNfWgcLRCeBbUP2dCM8ThRnENuqLf943Xhx/jnrNtP6oXyx2J WQ6H9nhOkMQ88crWr5uIyQ2OrqML9DFbOYtIooACzUAce68=
X-Google-Smtp-Source: ABdhPJwMnYr9lb+namiHoQdvmYSHuByp5DYIIsa3YDXNFuVLS6TxV1Wj/hUHaFGTgihwisz3P4wNNBNe301f9w51Xu8=
X-Received: by 2002:a05:6602:3d3:: with SMTP id g19mr11078062iov.42.1636553941705; Wed, 10 Nov 2021 06:19:01 -0800 (PST)
MIME-Version: 1.0
References: <CA+YzgTvk-b=mSpyCBbJAjrgdGGEwegN1YQKWw9_444+RvO4zeg@mail.gmail.com>
In-Reply-To: <CA+YzgTvk-b=mSpyCBbJAjrgdGGEwegN1YQKWw9_444+RvO4zeg@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 10 Nov 2021 08:18:50 -0600
Message-ID: <CA+YzgTs+k0hESkrt9LKKe1mESdS=-WCScAYngEfu+qDhU+1Eqg@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000059e8a905d06fe81d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FCL7-_QXh5RGdJ_GWJWBVhp_67M>
Subject: [Teas] draft-bestbar-teas-yang-topology-filter - Routing Policy for filtering topologies
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2021 14:19:08 -0000

I believe the gist of Sue's questions/concerns from yesterday's WG session
is the following (@Sue -- please correct me if that isn't the case):

- Why do we need a topology-filter construct when we have routing policies ?

Routing policies filter routes. The topology-filter construct defined in
this document filters network topologies (more specifically, TE aware
native and customized network topologies that may or may not be learnt via
routing protocols). If the relevant topology database is maintained as a
RIB (I acknowledge implementations can do that), then routing-policies can
play a role in filtering the entries in the RIB. But that isn't the target
implementation for this draft.

We'll add text in the next revision to clarify the scope and motivation
(please see my response to Loa on the target use-cases) behind the
introduction of this construct. We'll also add usage examples in the
appendix. The proposal does not intend to tread on other important work
being done elsewhere and that should become clear after we publish the next
revision (if it isn't already).

Regards,
-Pavan (as a co-author)