Re: [Teas] question on the topology filter draft

Loa Andersson <loa@pi.nu> Wed, 10 November 2021 14:28 UTC

Return-Path: <loa@pi.nu>
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 38C2E3A1049 for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 06:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.227
X-Spam-Level:
X-Spam-Status: No, score=-5.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XgUZJGCVamRH for <teas@ietfa.amsl.com>; Wed, 10 Nov 2021 06:28:33 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BD8A3A1043 for <teas@ietf.org>; Wed, 10 Nov 2021 06:28:33 -0800 (PST)
Received: from [192.168.1.94] (c-e605e353.020-236-73746f24.bbcust.telenor.se [83.227.5.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C059E34A6EB; Wed, 10 Nov 2021 15:28:29 +0100 (CET)
Message-ID: <0e1c95c1-d8c7-938b-0d9b-5c9a88e873dd@pi.nu>
Date: Wed, 10 Nov 2021 15:28:28 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: TEAS WG <teas@ietf.org>
References: <1ac0bf22-f0a9-a3d6-8188-63e006e85834@pi.nu> <CA+YzgTu+tfY+aCkHNof7h=JOm2QDBM5wTB2Qi0SyMquq9uyX1A@mail.gmail.com>
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <CA+YzgTu+tfY+aCkHNof7h=JOm2QDBM5wTB2Qi0SyMquq9uyX1A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xAWBD0NVyfrIdzm7yL0xHSWL0kw>
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 14:28:38 -0000

Pavan,

This mail gives me more (and useful) inforamtion than the draft did, 
e.g. that topology filters are a new concept. And where to find related 
info, would you consider adding it in some for to the draft.

/Loa

On 10/11/2021 13:23, Vishnu Pavan Beeram wrote:
> Loa,
> 
> Please see inline (prefixed VPB)
> 
> Regards,
> -Pavan
> 
> 
> On Tue, Nov 9, 2021 at 11:57 AM Loa Andersson <loa@pi.nu 
> <mailto: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 <mailto:loa@pi.nu>
>     Senior MPLS Expert loa.pi.nu@gmail.com <mailto:loa.pi.nu@gmail.com>
>     Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
>     _______________________________________________
>     Teas mailing list
>     Teas@ietf.org <mailto:Teas@ietf.org>
>     https://www.ietf.org/mailman/listinfo/teas
>     <https://www.ietf.org/mailman/listinfo/teas>
> 

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64