Re: [Lsr] New draft on Flex-Algorithm Bandwidth Constraints

William Britto A J <bwilliam@juniper.net> Sat, 27 February 2021 18:22 UTC

Return-Path: <bwilliam@juniper.net>
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 A26803A11ED for <lsr@ietfa.amsl.com>; Sat, 27 Feb 2021 10:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level:
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b=arl46IP6; dkim=pass (1024-bit key) header.d=juniper.net header.b=VWYQZQnx
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 MI4Keru5hM3f for <lsr@ietfa.amsl.com>; Sat, 27 Feb 2021 10:22:05 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 8A8113A11EB for <lsr@ietf.org>; Sat, 27 Feb 2021 10:22:05 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 11RIKg6U001078; Sat, 27 Feb 2021 10:22:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=akoXxIqlkhflZiqeDX5GUL4sK+RhgOPtOienVLQ8FYw=; b=arl46IP6YtQDX2IpS2HBqsnuMEucGHDip5bZoZ3JaerPcmHKsptqZIOB0M29IEvfBiJG cTKAfz5x/v9Ou9AGxjM5abnDNq0B022OyTL2AbuaOJq2cEwly9cqyE9gU4zaJxE1dhyC PQyLoyHqnx+0h3Tq2Yvcrst/zB/sCbLJMcpNw7ukPVirivzhM9+9jCQC4UqDBt/kAor2 p6ob5mc8Wg2lUJ8xhgJed6CK7sPAKsLWz8NP/UqyJerg7Dj8UAyZUaTzziZSMOThiXiS 7TscPoWj018ZlIrrkdGpR70EVO9jjV0DqqYLWbauN5VjQNwYD9D/YHSImORR6BEQBRsz bQ==
Received: from nam10-mw2-obe.outbound.protection.outlook.com (mail-mw2nam10lp2105.outbound.protection.outlook.com [104.47.55.105]) by mx0b-00273201.pphosted.com with ESMTP id 36ymvn0cne-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 27 Feb 2021 10:22:04 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RG6JNeaQ1XkuzjYSNIQgfON34AxTYIDGnDlKgoZT6aWO3aJ0sOsmG5VmMK9MvcDVEEMGIbx+WAvki4C8o3NkPIu0DgXmAk0wMXJuRjy7RInYZHs0HOujRiBI4Jd4PZ5nx0ibp5lOGEV0+T6eMXnlUsos16yP2KYVZ4Qx/uP/0flVaz38GPBR50qLPU4dENaLuktenWPqYwA8vSmV5rAjezFKf5XrCqFqWg2J3ZYSQBYINGQNBffk45rChOi37cpU26JSZY1PwZA3X/iy4t+rhiKb1xu2Mh3CUAvCvHJgzrqXMnmDLpiKAiSEY/TDTaL9k5QnHULDTyeM+Go1CveOaQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=akoXxIqlkhflZiqeDX5GUL4sK+RhgOPtOienVLQ8FYw=; b=Ao7DPxIC5tAPUyAreBHvvaw8121cna5oaKa8mxBczBmACplUFRiwBCCIKVGIQWMUC3sSuD1DeSODMjEzu+sGBrGOXLlqt6RL/wDOGx9ImL+ywyHheGTGMXvv5Litx6+A+an46MVu1ZFrzPrpaUegL4byAPZujDzFVn+6MCp2aFIVklKZzlKPx3fUH2h4H7zgyfmbkPF407Oq8oVWepGb7x+L1T1uJ6Ctr1VImiXUPxlqN0Fw+YPDRRw3rI8J0w3hs5WGruXzk4McZD1q3huy2MDtFtrwffZWABbJk6EJ7zdvULk8ncDu1SPmxLgigFfLgHaU8RBpld6T+ASwCDthEg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=akoXxIqlkhflZiqeDX5GUL4sK+RhgOPtOienVLQ8FYw=; b=VWYQZQnxxBR3u9yQYV8Rw0/ZBdnulRcAbLtUPfUmHwFrFi7POXrwk+FUU6gs+CstkovuVm+1J2vIN5aLg9skXiiTXgvTYOWB+cU0HGxCc8eRVDxjs0uxCcFYCHxh0QWy2lGayuvin/KxRRsJ6YmdgmPG6O6DZEnkuB0UsQCA2qU=
Received: from DM5PR0501MB3800.namprd05.prod.outlook.com (2603:10b6:4:7b::10) by DM6PR05MB4905.namprd05.prod.outlook.com (2603:10b6:5:fc::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.11; Sat, 27 Feb 2021 18:22:01 +0000
Received: from DM5PR0501MB3800.namprd05.prod.outlook.com ([fe80::537:9ad7:1e60:65a3]) by DM5PR0501MB3800.namprd05.prod.outlook.com ([fe80::537:9ad7:1e60:65a3%5]) with mapi id 15.20.3912.009; Sat, 27 Feb 2021 18:22:01 +0000
From: William Britto A J <bwilliam@juniper.net>
To: Tony Li <tony.li@tony.li>
CC: "lsr@ietf.org" <lsr@ietf.org>, Rajesh M <mrajesh@juniper.net>, Shraddha Hegde <shraddha@juniper.net>, DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>
Thread-Topic: [Lsr] New draft on Flex-Algorithm Bandwidth Constraints
Thread-Index: AQHXDBIWT9mc4YXF3E+r+hn24uWzgqprP2qAgAD/x84=
Date: Sat, 27 Feb 2021 18:22:00 +0000
Message-ID: <DM5PR0501MB3800B7976376E6167378FFB2CD9C9@DM5PR0501MB3800.namprd05.prod.outlook.com>
References: <161401476623.19237.3808413288895066510@ietfa.amsl.com> <DM5PR0501MB380079CFD75C78610130D81BCD9D9@DM5PR0501MB3800.namprd05.prod.outlook.com>, <AEEC6707-7E76-41FF-9388-EA2AFE9FF5D1@tony.li>
In-Reply-To: <AEEC6707-7E76-41FF-9388-EA2AFE9FF5D1@tony.li>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2021-02-27T17:12:02.6840073Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=0; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Privileged
authentication-results: tony.li; dkim=none (message not signed) header.d=none;tony.li; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [116.197.184.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 5a9a4a2c-8287-490b-0d11-08d8db4c937e
x-ms-traffictypediagnostic: DM6PR05MB4905:
x-ms-exchange-minimumurldomainage: ietf.org#9485
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DM6PR05MB4905F8877C87F983AEF12DEECD9C9@DM6PR05MB4905.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: OoXg0G0VHnwKnPiZ3ta+Au8cF49KvLwWecv9J1qiZCqVOXK5Q1qO81uohyItzRvn2qUjoEU3cAKbKQH16Fd9G4Rf3roKrtwbNcbcy4VkVYsqBDyuecJarWnE6SZeQ5KWrYl769lewoYS9jGrGMxEXxrj+wl9BNZzugwFhL6yyVPclDcEBRygsLTEyrgy8GbFzjcVquxuDmbHWWZL7IG/8pJ/3965WmMGRJAoYxsz2bixTlQhnOk6mqVx3wo2dAo+W3XZjErps1KUbSm/iY7k6AS52xd7ZsGIX3jAwyHLbnkVD+a6yMYen9EfXw3w7515Ws1zIalsKAkTcyJoWpbCFMO5r7uPTptJ4Lt9GQVNrkLVeSwDfjD+3i4koA+jssfoAvxLjk1g1/skAkYu7x2QzESdKvkqf7b/yLatKMVmn0q/ZUtMPkrahwicSljhG7+U0uEmMMD2MnnlqydPuptsJP3fopJULr2SsPDUiaJZ57/AiNe20h+7HnPw2kmJnOIFA8YcV+o+pqRiGio64wMFaP0Ej2YMRlNjDx3XQSFtC2mVsOk8Tl3/T6LBWptQcxEktcijvVE6WA4K9TA83RV6BMm1kJcWmcpOSMy9PA3Ft1I=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM5PR0501MB3800.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(366004)(39860400002)(396003)(136003)(346002)(186003)(66574015)(91956017)(54906003)(66946007)(66446008)(76116006)(6916009)(66556008)(64756008)(66476007)(166002)(9326002)(83380400001)(86362001)(71200400001)(26005)(9686003)(55016002)(478600001)(316002)(6506007)(5660300002)(53546011)(966005)(8676002)(2906002)(7696005)(52536014)(4326008)(33656002)(8936002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?Windows-1252?Q?5XlMwi4I61uOST97CTilt1n0gYxG1Hxnczkqn5QNpijfYLdggV7lcdB1?= =?Windows-1252?Q?+dmbhEgzRHTOChgDqhEc5CZv0krzS/22BGIGcGChheoYXNWY2yj//7Ry?= =?Windows-1252?Q?khdpsPfPJiH0p3Nd5Ap0bgtrAaOv1WO4VTfmNyNThsidtsa9NzKAq+5w?= =?Windows-1252?Q?06qPOtGzrlvA1odIf+hfPsB1oScbyJ8c1H1fCC3kmtVOYKgX2Vf4uffc?= =?Windows-1252?Q?1MGuEoRfspnXDSG4C8M3/uynohuSAuIofZo8MfNBnQ5jJpP+BA9Mu/lz?= =?Windows-1252?Q?uc56sruNEZhh502NoaXX1HtbD3ZFmgCKPmZtB6AEWbt4jvc6JzYQ4IMw?= =?Windows-1252?Q?r1Kb5YvyPLTcfdeYU5/ME/CMCuqwDNVgmSnP6BqXeCC+oGHQPIGwVyQ1?= =?Windows-1252?Q?FvAPY3Vgtp4jRS8AyvndsRcRlPF1OlnnoxzGBz3E7glIewtXDJv5FrLm?= =?Windows-1252?Q?+Z3kAjdTVziQ5hYVW2jGx6rgYYNwqJHLggZHY3dIpGnLHcPlgqwxdZ4m?= =?Windows-1252?Q?dD06ldBXkAngXaLyaxjVRboH+aSfNYyQUD987v2d2ZNDm4ZWXyaK5xq4?= =?Windows-1252?Q?Kibhc7i/sEQEHApVFon/37b9GOzkJA0/Zh8ZdGBb2cKQd6+BfL6akOWx?= =?Windows-1252?Q?9sz76kkYHnxPuknwap2XTfiXim+ap1hZnv6BdTL7y6XjnZxXGAMtOUBX?= =?Windows-1252?Q?rtFHG1E/h2V9lDbvwDvC1Vk81TGCL3SLpeLXfaeW4WCckKN8Szzi+d5R?= =?Windows-1252?Q?ELOQfvM+UsWet1Dt8rB58SbiAdygEL04gKojr3lBFi/YW5DDQV92SwHE?= =?Windows-1252?Q?uPfJGv1iQwUArJrsfQ0nRkHZKeddUDBTh/8ILrJfVp1+QCJkQmRAgrKB?= =?Windows-1252?Q?2U2hLFNojsZ4oqru27xHF5ZmB+JNhrO6gzfr8Jj0VXhBRR5zpsNyN4L4?= =?Windows-1252?Q?5F6Ghmxb+4GnjBYq6IYyLoDF2fv9hipR21Qq+4hxAvKpPBIv/XGXizbl?= =?Windows-1252?Q?a6LZShlaGCAGYlG1W18cs9qr/tdLoyFotl2J2dcCe6WyOLhPxtxGUnnj?= =?Windows-1252?Q?bc1SAUO7xaeySk/gk98hqCi4SUkkS4yDZYSRNQeNCWeb5YIoaD7GXlVk?= =?Windows-1252?Q?NgR7z6n+oF6dZ4eRG2MP2lW1gwiMaVoaAEcf+BG3dVeb40Hof6FyyB1q?= =?Windows-1252?Q?7APIZNomVeXGW1NCV8Cd8D4nFZmIiCr/cMUlQxIx4bUW1EktkDGW3FZg?= =?Windows-1252?Q?BsPV3im+KmNSmJNRRjzHHtlXZjkzkB51bbKV0hWDOWoJGN1hTi1eZ0Yn?= =?Windows-1252?Q?ghqQ+fUAPyRT0uecW1R5bLI2Sr7AceWIoBP9WOSFT6fZyOfcHvF1SnoZ?= =?Windows-1252?Q?qoI85kLDwefVrA+7KuT/YT8qVQ3vTQp/OcDXBaQZSrroZP6WojSOkgWF?= =?Windows-1252?Q?9YhvJ2bA///uE1ZNEuympg=3D=3D?=
Content-Type: multipart/alternative; boundary="_000_DM5PR0501MB3800B7976376E6167378FFB2CD9C9DM5PR0501MB3800_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM5PR0501MB3800.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5a9a4a2c-8287-490b-0d11-08d8db4c937e
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2021 18:22:00.9155 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: AZQhI1Dssr0UhIMUfsybSt1uwkOzsq6Mhs/jpgcr9cW+5LO0Yv2bUOYHkDuaqk+iv/XWKpnxKFKJmiGme8PwKg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4905
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-27_10:2021-02-26, 2021-02-27 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 suspectscore=0 impostorscore=0 clxscore=1011 mlxscore=0 bulkscore=0 adultscore=0 mlxlogscore=999 malwarescore=0 spamscore=0 lowpriorityscore=0 phishscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102270158
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/Na7lVs5xjMV8rz1xIMIPAkjII4g>
Subject: Re: [Lsr] New draft on Flex-Algorithm Bandwidth Constraints
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: Sat, 27 Feb 2021 18:22:08 -0000

Hi Tony,

Thank you for your comments. Please find replies inline.

From: Tony Li <tony1athome@gmail.com> on behalf of Tony Li <tony.li@tony.li>
Date: Saturday, 27 February 2021 at 7:26 AM
To: William Britto A J <bwilliam@juniper.net>
Cc: lsr@ietf.org <lsr@ietf.org>rg>, Rajesh M <mrajesh@juniper.net>et>, Shraddha Hegde <shraddha@juniper.net>et>, DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>
Subject: Re: [Lsr] New draft on Flex-Algorithm Bandwidth Constraints
[External Email. Be cautious of content]


Hi William & co-authors,

Thank you for your contribution. It’s definitely interesting. As bandwidth management is one area where FlexAlgo lags legacy traffic engineering, this is definitely one small step in the right direction.

But I have many comments…

1) I’ll start with the title: there is MUCH more here than bandwidth constraints. Perhaps this should be generalized somehow? Sorry, I don’t have a constructive suggestion.
[William] Agree. We are introducing few ‘definitions’ for a bandwidth based Flex-Algo, along with couple of link constraints which can be used for any type of flex-algo. Any suggestions are welcome.

2) Section 2: I concur that bandwidth is an important consideration in path computation. At a first reading, it is not at all clear to me that it is optimal to somehow transmogrify things into a metric. Why not simply deal with the bandwidth directly?  I did (eventually) realize that you did this because you want SPF to somehow select the path with the minimum product of (# links) * bandwidth.  I think you need to be explicit about this motivation and also mention that traditional SPF is not set up to deal with a floating point metric. Note that a bandwidth metric is STILL somewhat counter-intuitive to me, as I would expect that you’d mostly want to route things along the highest bandwidth paths, not the lowest ones. More motivation behind the bandwidth metric would be most welcome.
[William] We will try to address this in the next version.

3) Section 2.1: To be consistent with the rest of FlexAlgo, shouldn’t this be advertised as part of the Application Specific Link Attributes?
[William] Agree. Will add relevant text clarifying the same.

4) Sectiion 2.1: Why are there two octets reserved in this sub-TLV? If you’re hoping for alignment within an IS-IS LSP, you’ve already lost. Nothing in IS-IS is aligned.
[William] Apologies. This was an error in the figure. Intention was one octet for Reserved/future flags, hence the Length of 5 octets. Will correct this in the next version.

5) Section 3.1.1: Here you have chosen to refer directly to subTLV 9.  To be consistent with the rest of FlexAlgo, should we use subTLV 9 inside of the Application Specific Link Attribute subTLV.
[William] Shouldn’t there be only one Max link BW per link applicable for all applications? However, agree that it could still be in a common ASLA. Will add relevant text to clarify this.

Also, I believe that it would be more clear to call this the “Minimum Bandwidth subTLV”. The word ‘exclude’ doesn’t seem to add value here and every word makes our acronyms harder.
[William] The intent was to be explicit (in the name) that this is an ‘exclude constraint’. Eg: Consider a FAD which has the above mentioned sub-tlv as a constraint along with some admin-group constraints. If a link has a Max Link BW which is greater that the Min BW constraint defined, that alone won’t qualify this link to be part of that Flex-Algo. IOW, this is not a minimum bw constraint to include a link that satisfies the requirement into Flex-Algo, but rather to exclude a link that doesn’t meet the criteria. Having said that, if its more clear without the ‘explicit’ in the name, we can do away with it. We are planning to add a section in the next version of this draft as an extension to section 13 – “Calculation of Flexible Algorithm Paths” of [I-D.ietf-lsr-flex-algo<https://datatracker.ietf.org/doc/html/draft-hegde-lsr-flex-algo-bw-con-00#ref-I-D.ietf-lsr-flex-algo>]o>]. Will clarify this there.


6) Section 3.1.2: I’m unclear on the utility of this. I can understand optimizing for path delay against the path metric. I can even understand putting an upper bound on the total path delay. I don’t understand why a bound on an individual link delay is important.  If my path delay budget is 100ms, then does it matter if it is exceeded in one hop or ten? Could you please provide more motivation here? Also, wouldn’t a FlexAlgo system be advertising the link delay in the Application Specific Link Attributes subTLV?
[William] This constraint could be useful in a Flex-Algo whose Metric-type is anything but Link-delay. Here, Link-delay doesn’t influence the ‘cost’ of a link in that Flex-Algo, but can be used to prune out certain links with very high delay from that Flex-Algo.

I’ll stop here for now, but I promise you more comments are still to come.
[William] Thanks. Looking forward to it.

Regards,
Tony



On Feb 25, 2021, at 11:36 PM, William Britto A J <bwilliam=40juniper.net@dmarc.ietf.org<mailto:bwilliam=40juniper.net@dmarc.ietf.org>> wrote:

All,

We would like to draw your attention to a new ID: https://datatracker.ietf.org/doc/html/draft-hegde-lsr-flex-algo-bw-con-00<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-hegde-lsr-flex-algo-bw-con-00__;!!NEt6yMaO-gk!UtNPytCuEZtqnycoTXAZws2cmdypbPSgYaTM8G0FTw3BnJnDBXqI-YJwYoyG5Heq8Q$>

The draft talks about introducing link bandwidth related constraints in Flex-Algorithm which can be used to define a Flex-Algorithm based on bandwidth based metric.

Please review. Any questions and comments are welcome.

Thanks,
William


From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Monday, 22 February 2021 at 10:56 PM
To: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>, Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>, Rajesh M <mrajesh@juniper.net<mailto:mrajesh@juniper.net>>, Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>, William Britto A J <bwilliam@juniper.net<mailto:bwilliam@juniper.net>>, William Britto A J <bwilliam@juniper.net<mailto:bwilliam@juniper.net>>
Subject: New Version Notification for draft-hegde-lsr-flex-algo-bw-con-00.txt
[External Email. Be cautious of content]


A new version of I-D, draft-hegde-lsr-flex-algo-bw-con-00.txt
has been successfully submitted by Shraddha Hegde and posted to the
IETF repository.

Name:           draft-hegde-lsr-flex-algo-bw-con
Revision:       00
Title:          Flexible Algorithms Bandwidth Constraints
Document date:  2021-02-22
Group:          Individual Submission
Pages:          21
URL:            https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-hegde-lsr-flex-algo-bw-con-00.txt__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD3v6TruoA$<https://urldefense.com/v3/__https:/www.ietf.org/archive/id/draft-hegde-lsr-flex-algo-bw-con-00.txt__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD3v6TruoA$>
Status:         https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-hegde-lsr-flex-algo-bw-con/__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD1VexjHPQ$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-hegde-lsr-flex-algo-bw-con/__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD1VexjHPQ$>
Htmlized:       https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-hegde-lsr-flex-algo-bw-con__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD3X5nPQbA$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-hegde-lsr-flex-algo-bw-con__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD3X5nPQbA$>
Htmlized:       https://urldefense.com/v3/__https://tools.ietf.org/html/draft-hegde-lsr-flex-algo-bw-con-00__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD2aqSYcuQ$<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-hegde-lsr-flex-algo-bw-con-00__;!!NEt6yMaO-gk!QGg36p91zPfVMznYY91xs-zx70Qp5BE1nJx-Thnl14sTCkvwgOjEzjGBtD2aqSYcuQ$>


Abstract:
   Many networks configure the link metric relative to the link
   capacity.  High bandwidth traffic gets routed as per the link
   capacity.  Flexible algorithms provides mechanisms to create
   constraint based paths in IGP.  This draft documents a set of
   bandwidth related constraints to be used in Flexible Algorithms.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<https://urldefense.com/v3/__http:/tools.ietf.org/__;!!NEt6yMaO-gk!UtNPytCuEZtqnycoTXAZws2cmdypbPSgYaTM8G0FTw3BnJnDBXqI-YJwYoxRR9xeDg$>g$>.

The IETF Secretariat




Juniper Business Use Only
_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/lsr__;!!NEt6yMaO-gk!UtNPytCuEZtqnycoTXAZws2cmdypbPSgYaTM8G0FTw3BnJnDBXqI-YJwYozBwudP8w$>



Juniper Business Use Only