[Lsr] Hi, Here are some clarification questions about the flex-algo draft.

Huzhibo <huzhibo@huawei.com> Thu, 26 April 2018 07:50 UTC

Return-Path: <huzhibo@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 39CDE1241F3 for <lsr@ietfa.amsl.com>; Thu, 26 Apr 2018 00:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 VMs1_vf3txp2 for <lsr@ietfa.amsl.com>; Thu, 26 Apr 2018 00:50:49 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ABEA1204DA for <lsr@ietf.org>; Thu, 26 Apr 2018 00:50:49 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A3871290D04F1 for <lsr@ietf.org>; Thu, 26 Apr 2018 08:50:45 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 26 Apr 2018 08:50:39 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0361.001; Thu, 26 Apr 2018 15:50:28 +0800
From: Huzhibo <huzhibo@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Hi, Here are some clarification questions about the flex-algo draft.
Thread-Index: AdPdME03mb0xHPYJSta1QN72e8qj8Q==
Date: Thu, 26 Apr 2018 07:50:28 +0000
Message-ID: <06CF729DA0D6854E8C1E5121AC3330DF9E0A5D2A@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.219.232]
Content-Type: multipart/alternative; boundary="_000_06CF729DA0D6854E8C1E5121AC3330DF9E0A5D2ANKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/e7JUhZpwbfdfelgy2g3-OrVngKE>
Subject: [Lsr] Hi, Here are some clarification questions about the flex-algo draft.
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 26 Apr 2018 07:50:51 -0000

Hi,
Here are some clarification questions about the flex-algo draft.
1. As described in section 5, in path computation for a flex-algorithm, the node firstly needs to prune the links not included for this flex-algorithm, then run SPF or other algorithm within the pruned topology. If a node supports multiple algorithms, does this mean the node needs to maintain multiple pruned topologies?
2. If one path computed in algorithm-1 with latency metric and another path computed in algorithm-2 with bandwidth metric traverse the same link(s) in the network, can the latency or bandwidth SLA be guaranteed for the service? Or the path may need to be re-computed and adjusted to another link to avoid potential performance degradation?

ZhiBo Hu
发件人: Lsr [mailto:lsr-bounces@ietf.org] 代表 Acee Lindem (acee)
发送时间: 2018年4月17日 22:44
收件人: lsr@ietf.org
主题: [Lsr] LSR Working Group Adoption Poll for Flex Algorithm Drafts

This begins a two-week adoption poll for the following Flex Algorithm drafts:

https://datatracker.ietf.org/doc/draft-hegdeppsenak-isis-sr-flex-algo/
https://datatracker.ietf.org/doc/draft-ppsenak-ospf-sr-flex-algo/

The adoption poll will end at 12:00 AM EST on May 2nd, 2018. Please indicate your support of opposition of the drafts.

Additionally, the authors are amenable to combining the drafts into a single draft. If you have an opinion, please state that as well.

Thanks,
Acee