Re: [Teas] question on the topology filter draft

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 11 November 2021 18:11 UTC

Return-Path: <jie.dong@huawei.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 33A7F3A005F for <teas@ietfa.amsl.com>; Thu, 11 Nov 2021 10:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 2gY_C2YpSOQt for <teas@ietfa.amsl.com>; Thu, 11 Nov 2021 10:11:06 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C4B73A003C for <teas@ietf.org>; Thu, 11 Nov 2021 10:11:06 -0800 (PST)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HqqWz4qGcz67gt0; Fri, 12 Nov 2021 02:10:39 +0800 (CST)
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Thu, 11 Nov 2021 19:11:02 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme704-chm.china.huawei.com (10.1.199.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Fri, 12 Nov 2021 02:11:00 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.2308.015; Fri, 12 Nov 2021 02:11:00 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Loa Andersson <loa@pi.nu>
CC: TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] question on the topology filter draft
Thread-Index: AQHX1ZNW8VkBVVI/wEe//eKs5WZBKqv8KkIAgAJb/YA=
Date: Thu, 11 Nov 2021 18:11:00 +0000
Message-ID: <cdcb36f2622643d2a4af9b2164af47fc@huawei.com>
References: <1ac0bf22-f0a9-a3d6-8188-63e006e85834@pi.nu> <CA+YzgTu+tfY+aCkHNof7h=JOm2QDBM5wTB2Qi0SyMquq9uyX1A@mail.gmail.com>
In-Reply-To: <CA+YzgTu+tfY+aCkHNof7h=JOm2QDBM5wTB2Qi0SyMquq9uyX1A@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.179.251]
Content-Type: multipart/alternative; boundary="_000_cdcb36f2622643d2a4af9b2164af47fchuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/XksuOsLcL66bC6HbTloSd6M4LGQ>
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: Thu, 11 Nov 2021 18:11:11 -0000

Hi Pavan,

Please fine some comments about topology filter and its usage inline:

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: Wednesday, November 10, 2021 8:23 PM
To: Loa Andersson <loa@pi.nu>
Cc: TEAS WG <teas@ietf.org>
Subject: Re: [Teas] question on the topology filter draft

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].

[Jie] Since the term “topology filter” is newly introduced in this YANG model draft, it would be useful to state in the document “who” is the consumer of this information. More specifically, who will use the topology filter in path or route computation.

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

[Jie]  In the last case, why use Flex-Algo with an additional rule of include-affinity blue? The include rule can be defined as part of the Flex-Algo.

And what does “resource-affinity” mean in a topology filter?

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

[Jie] Topology-filter and filter-topology sounds confusing to me. How about simply say “specification of the topology associated with a Network Resource Partition”?

Best regards,
Jie

/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