Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 26 March 2021 14:39 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A66E73A201B for <lsr@ietfa.amsl.com>; Fri, 26 Mar 2021 07:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 ValxoJ4ElOgH for <lsr@ietfa.amsl.com>; Fri, 26 Mar 2021 07:38:59 -0700 (PDT)
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 6C0733A2041 for <lsr@ietf.org>; Fri, 26 Mar 2021 07:38:58 -0700 (PDT)
Received: from fraeml740-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F6PWZ1CYlz680XV for <lsr@ietf.org>; Fri, 26 Mar 2021 22:30:02 +0800 (CST)
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Fri, 26 Mar 2021 15:38:54 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme752-chm.china.huawei.com (10.3.19.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Fri, 26 Mar 2021 22:38:52 +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.2106.013; Fri, 26 Mar 2021 22:38:52 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03
Thread-Index: AQHXIaOIXRarSEyVMUmCAJHdvcBzqKqVy4ImgACEsIA=
Date: Fri, 26 Mar 2021 14:38:52 +0000
Message-ID: <ad917d594d07492c876529c045991f18@huawei.com>
References: <04A60BCD-4D9C-4210-A213-4D3876595114@cisco.com> <202103261414115805407@foxmail.com>
In-Reply-To: <202103261414115805407@foxmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.182.38]
Content-Type: multipart/alternative; boundary="_000_ad917d594d07492c876529c045991f18huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/X1nbaYYiYRoH2D-uH_qei3FKHyg>
Subject: Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2021 14:39:04 -0000

Hi Acee,

I agree with what Chongfeng said about VTN. It refers to a virtual underlay network with specific topology and resource attributes, and the topology of VTNs can be specified using multi-topology. It is important to understand the difference between a VTN and a logical network topology.

As for the deployment choice and scalability, draft-dong-teas-enhanced-vpn-vtn-scalability gives some detailed analysis. In summary, it says in different network scenarios and phases, the required number of VTNs could be different, thus several options may be provided to meet different requirements, with different cost and time to market.

Best regards,
Jie

From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Chongfeng Xie
Sent: Friday, March 26, 2021 2:14 PM
To: Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org>; lsr@ietf.org
Subject: Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

Hi,Acee,

Regarding to the issues put forward in your mail, I'd like to provide some comments as below,

Q1:I’d like to know of the WG members who supported it, would you really want to market it as a VTN solution?

[CF]:VTN is defined in draft-ietf-teas-enhanced-vpn, and also used in other documents. It is a technical term to refer to virtual underlay networks with specific topology and resource attributes. This document provides an MT based mechanism to build VTNs. If for marketing, perhaps it would be better called "network slicing":-)

Q2:Those of you who operate networks, would you actually consider deploying it?

[CF]:As an operator we will consider the scenarios and the requirements to pick the most suitable solution, IMO this is a good candidate for scenarios where the required number of VTN is not very large, and as it requires no new encodings, it could be ready for shipment soon. we plans to use this approach in some of our network deployment.

Q3:In any case, section 5 needs to be expanded on the scalability and where using MTs to support VTNs would make sense and where it wouldn’t.

[CF]:OK. The current section 5 already has some text to cover this, and it can be expanded further to clarify.

Best regards
Chongfeng


发件人: Acee Lindem \(acee\)<mailto:acee=40cisco.com@dmarc.ietf.org>
发送时间: 2021-03-26 02:20
收件人: lsr@ietf.org<mailto:lsr@ietf.org>
主题: Re: [Lsr]WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03
Speaking as WG chair:

There has been considerable support for this document. However, there has also been objections to the document. The objections are either that there is nothing to standardize given that all pieces exist and that the MT isn’t a viable option for VTNs since it isn’t scalable.

Since most of the draft’s support is from “friends and family”, I’d like to know of the WG members who supported it, would you really want to market it as a VTN solution? Those of you who operate networks, would you actually consider deploying it?

In any case, section 5 needs to be expanded on the scalability and where using MTs to support VTNs would make sense and where it wouldn’t.

Thanks,
Acee


From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org<mailto:acee=40cisco.com@dmarc.ietf.org>>
Date: Tuesday, March 2, 2021 at 6:28 PM
To: "lsr@ietf.org<mailto:lsr@ietf.org>" <lsr@ietf.org<mailto:lsr@ietf.org>>
Subject: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

This information draft describes how MT could be used for VTN segmentation. The authors have asked for WG adoption.

This begins a three week LSR Working Group Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03. I’m giving it three weeks due to the IETF next week. Please register your support or objection on this list prior to the end of the adoption poll on 3/24/2020.

Thanks,
Acee