IETF Logo Mail Archive

Re: [Lsr] Dynamic flow control for flooding

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 24 July 2019 04:03 UTC

Return-Path: <ginsberg@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 F11EE12008F for <lsr@ietfa.amsl.com>; Tue, 23 Jul 2019 21:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 header.b=fClaQZx4; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Xhr5TX9Q
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 KAoNuyr7EOcF for <lsr@ietfa.amsl.com>; Tue, 23 Jul 2019 21:03:42 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B08120047 for <lsr@ietf.org>; Tue, 23 Jul 2019 21:03:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2033; q=dns/txt; s=iport; t=1563941022; x=1565150622; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=bSZJjiZVsDZQjhxXk6iWZRilvq7qTxiN1ZnTYcmRbG8=; b=fClaQZx4bS9LviAXVTiD8pMNF3YQR0HRDdqd91dobmIVdMQ5d7zpy/XF vi7GxkOLrkgzQju7RwI1ciPGFcdp8F5BS9Dp22EvpL8AV4HHlH/YBkHsp 2b/vi2wseDnSE3aJBToooVx8Z5BCOmK4khau64IfklXSn6ewriQa1Z0th U=;
IronPort-PHdr: 9a23:ClNlHRYf1njRIbIgb6CdKN7/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavlbiohFslYW3du/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B7AADr1zdd/5BdJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBZ4FEUAOBQiAECyqHZAONf4Jbl1CCUgNUCQEBAQwBAS0CAQGEQAKCTiM4EwEDAQEEAQECAQZthR4MhUoBAQEBAxIoBgEBNwELBAIBCA4DBAEBAR0BEDIdCAIEDgUIGoRrAx0BAqEhAoE4iGCCI4J5AQEFhQ0YghMJgTSLXxeBQD+BV4IXBy4+hEaDO4ImqmkJAoIZlCmYCqUIAgQCBAUCDgEBBYFnIYFYcBWDJ4JCg3GDRocNcoEpijMFgk0BAQ
X-IronPort-AV: E=Sophos;i="5.64,300,1559520000"; d="scan'208";a="297235464"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Jul 2019 04:03:41 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x6O43fEt032416 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 24 Jul 2019 04:03:41 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 23:03:40 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Jul 2019 23:03:39 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 24 Jul 2019 00:03:39 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GaBz4EUp2zq/I9tSIPUQIKcn63mNgwe772PDzjLNCyIdYjWBzd72BpwlC8CPNObcprN8py4JdoDLNwEuVG92Ts7zMC4uI7FbX2oz5O9nI8gkJrgGrP6a0GbtvGrshdXyaTD03VFfVO6fZDQXitDkbzlCIvbA+KF1b6GN+pvscHASUw7BNt1Fh8q/ONnATdOg59hAGQqVzU+t93bt/I+lG4C+5BOUgci5ur5oe+iI5kX/MW3SdfkfX2WC0Z0JRmhdkitmx8OUaSPJzdTYfmgXnrP8gnQIca54OJiE7z4lAt4Qev6nmqik4maeLDa+NCYC2s7EGmXFii+UYfdzh8vu/A==
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=0+iN9losHEGfxl2Juf8jDFOmBLNWJAlBl/kDzlyAoS4=; b=ZAoZkbx57mT9qJhIUw5oghSIUV+xFXcr50///DLBmZIxc1gQhpk1naFQo738zf/JnRaG/xhGvtgQfzTFPsPQ0+sDYQKj+pOI/plkDu2Bm4aysxXws0UWonXgm+XoBz6We4fvfhR61hiQin64ny4RerWGAbD9yJ7mfBOrgynv20YcSzxqoer9dweEt1cSN1WsObrWt6/jFG0Xqm6zFPLR/sqT0JPYA393k2LcXyaYFRCljxHjggzK6p/Csf+qlWGU+3oDuoZQ8QBZ7W992+3VxS3rBXBtA4NC+/M1NfjuLtBHo/E/7EbD1ozOI0RDkNK7eHqI/33pTkdsJt+fiuOkxg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0+iN9losHEGfxl2Juf8jDFOmBLNWJAlBl/kDzlyAoS4=; b=Xhr5TX9QvQkY2twC4C4Bb+xfwzXZ5PO2S5pCHe6sQk8Bf+TCwYpfeBMyNptSXKT2gLmdwSda4/SyLChoi4Ph6WrbO7SHoIiARJF6hoIkRABxHkJAVwG0j7mKPFn6bIJ9DpgQV63WG9mJtZIsRjQEDR94zp3f0pow9qUUAlYuFzM=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3096.namprd11.prod.outlook.com (20.177.227.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.10; Wed, 24 Jul 2019 04:03:38 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::c8b3:b0b0:581d:e1ce]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::c8b3:b0b0:581d:e1ce%6]) with mapi id 15.20.2115.005; Wed, 24 Jul 2019 04:03:38 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: David Lamparter <equinox@diac24.net>
CC: Tony Li <tony.li@tony.li>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Dynamic flow control for flooding
Thread-Index: AQHVQVt0dc+yhfYADEyrMMJ609g9uKbYO7RggAB4moCAAHB1YA==
Date: Wed, 24 Jul 2019 04:03:38 +0000
Message-ID: <BYAPR11MB3638BFCE5A0200ED0A0B1191C1C60@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <CAMj-N0LdaNBapVNisWs6cbH6RsHiXd-EMg6vRvO_U+UQsYVvXw@mail.gmail.com> <BYAPR11MB36382C89363202D1B5659614C1C70@BYAPR11MB3638.namprd11.prod.outlook.com> <20190723211345.GH258193@eidolon.nox.tf>
In-Reply-To: <20190723211345.GH258193@eidolon.nox.tf>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [2001:420:c0c8:1006::374]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3b05f5cd-4a98-4844-a037-08d70febe831
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3096;
x-ms-traffictypediagnostic: BYAPR11MB3096:
x-microsoft-antispam-prvs: <BYAPR11MB30969C653EF0B38FED8A4DDEC1C60@BYAPR11MB3096.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0108A997B2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(39860400002)(396003)(366004)(136003)(13464003)(189003)(199004)(33656002)(6436002)(478600001)(6246003)(6506007)(53936002)(7736002)(74316002)(76176011)(71200400001)(71190400001)(7696005)(14454004)(186003)(6116002)(229853002)(99286004)(102836004)(305945005)(53546011)(25786009)(8936002)(8676002)(86362001)(486006)(66446008)(2906002)(14444005)(52536014)(54906003)(5660300002)(76116006)(81156014)(66556008)(64756008)(66476007)(81166006)(476003)(11346002)(9686003)(66946007)(446003)(68736007)(316002)(55016002)(46003)(6916009)(4326008)(256004); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3096; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: d7jexGUG4ID8TkN7YX84mcqLCQFMM48k9K6vlAsC7T7t25+0q+0pWYFy9Yw+IW0Bp20YirJwKg28lp3i5cC0LzRzj2P0mj9XRYG7MgjaHCIPLfbuuvryeBdpIG3lhsCLrCRGBxQXyUwWy9jb7duu4CxwXjbRTzlqom1nPvQWo8trF2JSOI9e9qY31nrLx8PNwm6QmFOc0dYiPOuLYM/G9ycJ5/LAbUJzogianU/ZbbhuiT/RDenQwkbBBGweWZp28vN7VK//wyoBhcd3snfjTkvF2jJwjococQSsIODaiztEd8j4BzARtBx9LiGjKNG4lr/zevYhGaJrkQIysVY1RQAAoRn8Xnk7dZ5nbnnksPGMPzO8qzyWOqn+XzL/ngZTUdkK6Wo0MQQxM3WSGzYZuf2vR0mJhkBtARv0mQcb3Zo=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3b05f5cd-4a98-4844-a037-08d70febe831
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jul 2019 04:03:38.1203 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ginsberg@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3096
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/HIqBM0h8AZYWOuXlCinqUBSdVBU>
Subject: Re: [Lsr] Dynamic flow control for flooding
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, 24 Jul 2019 04:03:44 -0000

David -

Let's take Tony's example test case.

A large network is partitioned and heals. As a result I now have 1000 LSPs which need to be flooded.

Let's suppose on most links/nodes in the network I can support receiving of 500 LSPs/second.
But on one link/node I can only support receiving 33 LSPs/second.

This means we are at risk for part of the network converging the LSPDB in 2+ seconds and part of the network converging the LSPDB in 33+ seconds.

Having the means for the node which only supports 33 LSPs/second to signal its "upstream neighbors" to not overflow its receive queue isn't going to help network convergence.

That's all I am saying.

   Les


> -----Original Message-----
> From: David Lamparter <equinox@diac24.net>
> Sent: Tuesday, July 23, 2019 2:14 PM
> To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
> Cc: Tony Li <tony.li@tony.li>; lsr@ietf.org
> Subject: Re: [Lsr] Dynamic flow control for flooding
> 
> Hi Les,
> 
> 
> On Tue, Jul 23, 2019 at 08:29:30PM +0000, Les Ginsberg (ginsberg) wrote:
> > [...] As network-wide convergence depends upon fast propagation of LSP
> > changes -
> 
> you're losing me between that previous part and the next:
> 
> > - which in turn requires consistent flooding rates on all interfaces
> > enabled for flooding [...]
> 
> I understand and follow your reasoning if we have a classical timer that
> limits flooding rates per LSP.  If we get multiple updates to the same
> LSP, dissimilar flooding rates imply we might just have sent out the
> previous now-outdated state, and we block for some potentially lengthy
> time before sending out the most recent version of that LSP.
> 
> I don't understand how we get delayed propagation of LSP changes if we
> employ some mechanism to raise the flooding rate to something based
> around the target system's capabilities.
> 
> Could you elaborate on how we get delayed LSP propagation in this
> scenario?
> 
> Thanks,
> 
> 
> -David

v2.23.0 | Report a Bug | By Email