Re: [Teas] question on the topology filter draft

Vishnu Pavan Beeram <vishnupavan@gmail.com> Wed, 10 November 2021 12:23 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 454933A0EC0 for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 04:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 K2Oo1MVXEmgM for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 04:23:39 -0800 (PST)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 71D023A0EBD for <teas@ietf.org>; Wed, 10 Nov 2021 04:23:39 -0800 (PST)
Received: by mail-il1-x133.google.com with SMTP id s14so2246969ilv.10 for <teas@ietf.org>; Wed, 10 Nov 2021 04:23:39 -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 :cc; bh=CbZUKuCnQd7t6KPY3YiuClTMQRtOxnI4jQvfxmPKbaA=; b=ovS0MQL/pQUsJ3dRpho2dasJxX9qhmVbyBRODlGvL8FEWOznHTKTzTP6vSKaAwRbIR xx6ShYFij2uv6/deymVQlmqbVJjRzjyQz7KdDzto24a2FGm6HRuCx092rBapQrtEru48 FozC4s0Th3MiJ3A1FcL/EQ5v1yDMK4TZBkU7liyrMMsYX1b43x/kNuAXYMMn4eaUVnF8 1SYmouXjj1mrSMbkeQZs8Nj48txXD4+X3CUN8WJOLIfHW5iaSwSVFd1afHa/vOKU04bY 65cauMX2xMngiNK7+TDFYq9TCVbJIhAjrmoHwW60zi/PgfcUrgSiE0I/8sabnHWnjD/k Oe6A==
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:cc; bh=CbZUKuCnQd7t6KPY3YiuClTMQRtOxnI4jQvfxmPKbaA=; b=XfbKgcZsV4b0eakdnOh7S5tsCfDMWnUZFOrcStYRuENTVvlEVp3Ony1dSvXVOGDR7v KrsRneQkjvlulY4c/lkCfuLqcZDNH35iTpRLAoJjxA+DKHYZWo9aGJi+VhZVh0bfcVSB eZi291nXEQGyV2s36bO+4Eb7K2fyHGztL94ScTOMYyCbXRKsH8jalid7kDTP45b3P4pS RNIKcXmg1aXrtz0ta9Gzi0Q4rmUZAhs5+QEvqSdb7KYyWqWRKQ435DTaA6f5ff+4+UME dPOWQulkBE1CAUYgvKMu93bSVgO4wmK4Tc4u6zcOIUpWtIlvVm9H2HHEnVwscVSrawEA hmQA==
X-Gm-Message-State: AOAM533CNgZ4ReG0Hxm1W/Rdkn+y5M2Ik/jBqE8Hze5HKG5+NrdFZg7Z neEKG9OFRH3yxBbnTJDy4+GGWZs6ffCnGbtam04=
X-Google-Smtp-Source: ABdhPJynMgBqsO2a8OV5sju3mXCGu9gvH+LGcttfUs3SNQpo5f1HAzwwZC0gByOWNe+2FqG9TV7ryxWSHbVtdc5JzhY=
X-Received: by 2002:a05:6e02:144e:: with SMTP id p14mr10683201ilo.18.1636547017501; Wed, 10 Nov 2021 04:23:37 -0800 (PST)
MIME-Version: 1.0
References: <1ac0bf22-f0a9-a3d6-8188-63e006e85834@pi.nu>
In-Reply-To: <1ac0bf22-f0a9-a3d6-8188-63e006e85834@pi.nu>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 10 Nov 2021 06:23:26 -0600
Message-ID: <CA+YzgTu+tfY+aCkHNof7h=JOm2QDBM5wTB2Qi0SyMquq9uyX1A@mail.gmail.com>
To: Loa Andersson <loa@pi.nu>
Cc: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a2f05a05d06e4bb0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/hiHyTR6L5tnIwQ5-Bo-3DkXqz9A>
Subject: Re: [Teas] question on the topology filter draft
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 12:23:43 -0000

Loa,

Please see inline (prefixed VPB)

Regards,
-Pavan


On Tue, Nov 9, 2021 at 11:57 AM Loa Andersson <loa@pi.nu> wrote:

> WG, Pavan, authors,
>
> I was cut off at the end of the queue in the wg discussion. I had a
> fairly simple question,
>
> Where the topology filter(s) defined


[VPB] The term “topology filter” is being introduced in
draft-bestbar-teas-yang-topology-filter (not aware of any other document
where it is defined). As per this data model draft, a “topology filter” is
a data construct that can be applied on either a native topology or a
customized topology to produce a filtered set of topological elements. The
native or customized topology referred to here is a TE aware topology
[RFC8795].

and what benefits do we get from
> using them?
>

[VPB] There are a couple of use-cases that are being targeted with this
construct.

(a) Specification of topology related constraints for TE path computation
(any setup type):
A few examples:
- Compute a path within a specific topology
- Compute a path within the topology associated with a specific IGP domain
- Compute a path within the topology learnt from a specific TE Information
Source
- Compute a path within the topology defined by the application of one or
more topology-filters
** Say, a topology with elements that are learnt via ISIS Level-2 and
include resource-affinity red
** Or, a topology with elements associated with ISIS Flex-Algo 128 and do
not include resource-affinity blue

(b) Specification of filter-topology associated with a Network Resource
Partition


> /Loa
> --
>
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert                          loa.pi.nu@gmail.com
> Bronze Dragon Consulting             phone: +46 739 81 21 64
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>