IETF Logo Mail Archive

Re: [Lsr] [draft-ietf-lsr-flex-algo-08] Clarification on ASLA usage for flex-algo

Peter Psenak <ppsenak@cisco.com> Mon, 10 August 2020 15:56 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 3C64B3A07C5; Mon, 10 Aug 2020 08:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.55
X-Spam-Level:
X-Spam-Status: No, score=-10.55 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, NICE_REPLY_A=-0.949, 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 o0pyyiR_xfNO; Mon, 10 Aug 2020 08:56:20 -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 DE97A3A07C3; Mon, 10 Aug 2020 08:56:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1041; q=dns/txt; s=iport; t=1597074980; x=1598284580; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=MQCaIsH2sDCOwXWf6wL1VffMbr5B5iaYDnYndVEhMz0=; b=SgdDiKdz1L6q6ilDymmaD1KVkI+8mlrrBYMkEhMk630tfwaxu6VBnXR7 x2IQ5E+kOoVsMM68mdS3UmlR2qEWSzkv/87DiAv3yarG/uCHnSImktSN3 FVFs/5iVhZRbW8ie0gEvcZJy+LVuzh8fLhpNJsnqquJz1cKeOobiLn3En Y=;
X-IPAS-Result: A0BIAABjbTFf/xbLJq1gGQEBAQEBAQEBAQEBAQEBAQEBARIBAQEBAQEBAQEBAQFAgUqDGVQBIBIshDaJAYgYnBELAQEBDh8QBAEBhEwCgjclOBMCAwEBAQMCAwEBAQEFAQEBAgEGBG2FXAyFcQEBAQMBIw8BBS8SEAsYAgImAgJXBgEMBgIBAYMiAYJcIA+xa3aBMoVSgymBOgaBDioBiQmEH4FBP4ERJ4JpPoJcAQEDhHOCYAS2JoJsgwuFWJEqBQcDHoJ9iViFCY40ki6KPZUfgWojgVczGggbFYMkUBkNjlaHAIFOhUQ/AzA3AgYBBwEBAwmROQEB
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.75,458,1589241600"; d="scan'208";a="26196621"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Aug 2020 15:56:15 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id 07AFuFRS031843; Mon, 10 Aug 2020 15:56:15 GMT
To: tony.li@tony.li, Peter Psenak <ppsenak=40cisco.com@dmarc.ietf.org>
Cc: Sarah Chen <sarahchen=40arista.com@dmarc.ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, "draft-ietf-lsr-flex-algo@ietf.org" <draft-ietf-lsr-flex-algo@ietf.org>
References: <AM0PR07MB6386B2403358CE285F24C423E0480@AM0PR07MB6386.eurprd07.prod.outlook.com> <2504c28e-4cc0-4505-0eff-943a033cbad0@cisco.com> <AM0PR07MB638602985A8BA5F73361C3C2E0480@AM0PR07MB6386.eurprd07.prod.outlook.com> <92f1fd3a-9a53-53a3-1da8-96c91824d742@cisco.com> <FF39BFDE-A195-4919-A331-B528346A2FC5@tony.li> <CADhmtX0nA7QhenXH6XNXaYX6qFbc0LxeGpvh8PrCDNbx4LN3Ow@mail.gmail.com> <1f2c7457-e0bc-14fe-97b7-68b8ba733e09@cisco.com> <3C0FE8B9-1B0A-42CB-BB77-F5FBE9CE56B9@tony.li>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <e5a0b4a4-85d9-9bed-c8d3-ef0f7af8a736@cisco.com>
Date: Mon, 10 Aug 2020 17:56:15 +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: <3C0FE8B9-1B0A-42CB-BB77-F5FBE9CE56B9@tony.li>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/SpKLxLK6fj_nDW6cGYNFdtSEA6E>
Subject: Re: [Lsr] [draft-ietf-lsr-flex-algo-08] Clarification on ASLA usage for 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: Mon, 10 Aug 2020 15:56:22 -0000

Hi Tony,

On 10/08/2020 16:21, tony.li@tony.li wrote:
> 
> Hi Peter,
> 
> 
>>> The flex-algo draft mentions "Min Unidirectional Link Delay as 
>>> defined in [RFC7810 <https://tools.ietf.org/html/rfc7810>]". When 
>>> reading RFC7810, I found two Sub-TLVs:
>>> 4.1. Unidirectional Link Delay Sub-TLV 4.2. Min/Max Unidirectional 
>>> Link Delay Sub-TLV
>>> Could you please clarify which one should be used? If "Min/Max 
>>> Unidirectional Link Delay Sub-TLV" is used, will the max delay 
>>> carried in the subTLV be ignored?
>>
>> flex-algo as defined in the draft uses "Min Unidirectional Link 
>> Delay", which is advertised in the "Min/Max Unidirectional Link Delay 
>> Sub-TLV".
>>
>> The fact that the "Min/Max Unidirectional Link Delay Sub-TLV" carries 
>> some other data (e.g. Max delay) is orthogonal to the flex-algo usage.
> 
> 
> Could we please clarify this by adding a reference to the specific section?

which specific section do you have in mind?

thanks,
Peter


> 
> Thanks,
> Tony
>

v2.23.0 | Report a Bug | By Email