Re: [Lsr] A question about draft-ietf-lsr-flex-algo

Peter Psenak <ppsenak@cisco.com> Wed, 03 June 2020 12:09 UTC

Return-Path: <ppsenak@cisco.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 6A5903A1078; Wed, 3 Jun 2020 05:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 4-snCORq0gza; Wed, 3 Jun 2020 05:09:31 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C82683A1077; Wed, 3 Jun 2020 05:09:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=561; q=dns/txt; s=iport; t=1591186171; x=1592395771; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=AUIgHpAPPSu/3f2Ej/lHmyFz2Ypq79xiQc4jSeBmO4k=; b=X4WwiP5++NNqMfW2Hj3authv9NO/dCatPcD1Ec5EhmkdvObF3sHDDaq3 U2BWyUqriadQ2kcw1u2V2BpbkJhE2djGO+BBcXsqwZ8GWqbwl/417/roD yCyAZdd6juTV6poNnphwQh42U6bm2ChWCI3e45T+U5dcvGBEiryNF2mzr c=;
X-IPAS-Result: A0ANBABZktde/xbLJq1mHAEBAQEBAQcBARIBAQQEAQFAgUqDbgEgEoRRiQGID5t6CwEBAQ4vBAEBhEQCghwlOBMCAwEBAQMCAwEBAQEFAQEBAgEGBG2FZ4VzAQUjFUEQCxgCAiYCAlcGDQgBAYMign2uDnaBMoVRg1qBQIEOKoxmgUE/gREngmk+h2KCYASZWpoSgmOCfJVxBwMdglUSiQyEa41cryGBaiKBVjMaCBsVgyVPGQ2fCj8DZwIGCAEBAwmOaQEB
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.73,468,1583193600"; d="scan'208";a="24429945"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Jun 2020 12:09:27 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 053C9QR5025121; Wed, 3 Jun 2020 12:09:26 GMT
To: Huzhibo <huzhibo@huawei.com>
Cc: "draft-ietf-lsr-flex-algo@ietf.org" <draft-ietf-lsr-flex-algo@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
References: <06CF729DA0D6854E8C1E5121AC3330DFAF670C89@dggemm509-mbx.china.huawei.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <ead0a5c0-8bac-6fb6-05e9-c4ff7a0c6067@cisco.com>
Date: Wed, 03 Jun 2020 14:09:26 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <06CF729DA0D6854E8C1E5121AC3330DFAF670C89@dggemm509-mbx.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/c_EpWOZUH-Wjtej9NwSsSyKKeKc>
Subject: Re: [Lsr] A question about draft-ietf-lsr-flex-algo
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: Wed, 03 Jun 2020 12:09:33 -0000

Hi Zhibo,

this has been explained in the WG alias already.

Can you please go over archives.

thanks,
Peter

On 03/06/2020 14:06, Huzhibo wrote:
> Hi Peter:
> 
> I noticed that draft-ietf-lsr-flex-algo-07 adds exclude SRLG TLV. SRLG 
> defines a group of risk-sharing link groups. It is generally used to 
> prevent the primary and standby paths from passing the same risk-sharing 
> link group .I don't know why a group of SRLG links should be excluded 
> from the FlexAlgo calculation. What is its usecase?
> 
> Thanks
> 
> Zhibo Hu
>