Re: [Lsr] Flow Control Discussion for IS-IS Flooding Speed

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 19 February 2020 17:48 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 DC80012085B for <lsr@ietfa.amsl.com>; Wed, 19 Feb 2020 09:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=fsZQUqJ/; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=TCmNcXtT
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 mvCleqcoITS9 for <lsr@ietfa.amsl.com>; Wed, 19 Feb 2020 09:48:54 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64BA1120111 for <lsr@ietf.org>; Wed, 19 Feb 2020 09:48:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18186; q=dns/txt; s=iport; t=1582134534; x=1583344134; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=aTp7q/ZHk7HkYBhjcP45UkA8KsnmhcNReDsCUFbzpKI=; b=fsZQUqJ/szxUWL3he39wQS3TBuuAdpbO7Z25EuOQu1CqfhfBVXVTuVVC N/tu6xIorbyohUBWAtyempSqXX16ASMC5K7F3d5w1EW+1HUXxq0mtmv+r /U8YHzh+Yx6gTwWmQ3AD1kE5DDxq1Phc5AqTVQRXjE3icQTVNQFdRQM1u w=;
X-IPAS-Result: A0BhBwA4dE1e/4YNJK1mHAEBAQEBBwEBEQEEBAEBgXuBJS8kLAVsWCAECyqEFINGA4pwgl+TMIRhgUKBEANUCQEBAQwBARgBDAgCBAEBhEACF4FtJDgTAgMBAQEDAgMBAQEBBQEBAQIBBQRthTcMhWYBAQEBAwEBEBEKEwEBLAsBDwIBCBEEAQEoAwICAiULFAkIAQEEDgUIGoMFgX1NAy4BAgyjLAKBOYhidYEygn8BAQWBQ0GDLRiCDAMGgTiMJBqBQT+BEAFHgh4uPoJkAQEDAYEsAQwGASMkBwmCWjKCLI1KU4JGhXCKBY89CoI7h0+PLZsrl2iSTAIEAgQFAg4BAQWBaSJncXAVO4JsUBgNjh2Dc4UUhT90gSmLKBAXghsBAQ
IronPort-PHdr: 9a23:0Y4wAhHHCkp2Ecy05tqSSZ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efHraTcwEd5NfFRk5Hq8d0NSHZW2PgeAuHC54D8MFxm6LhJ7drinPInUgoz3z/q155DYfwRPgny6fK92KxK16w7Ws5teiop5IaF3wRzM6ndPdv8ew2R0bV6ehBfz4M6s8fsBuzxdofcg69JNXe3hcqI0QKYQDDM9L3t06Q==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.70,461,1574121600"; d="scan'208,217";a="419026293"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Feb 2020 17:48:53 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 01JHmrjm012538 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2020 17:48:53 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 11:48:52 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 12:48:51 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 19 Feb 2020 12:48:50 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J2sbHwHkaUfRPeyusZa4E2I+yGlZLr7xFhGwt/+BqZgFkrEMM2sj2oK1N/DH/IkhKpyi4aMH8G4Les8KCvtb4+OqFGPbgyqGBLKbQoNOZxw+1OzDvcc4n6nccBII2HA1ssdUTNkBCJl7oqzCXxCrIgkXr33KJv78TlP0rhcCeyhcudV+aFYQgevCZ3I4UUMYK5yuJvyOtqPDzYnJJ8Oo2ejULe2qvYETcGu5LFmtWlBg4hEHAxJ/c6Pl236upe+KjvXFPIwqwcdhOetsVA0QfY7JPzixA2oudmQyxWtaseasSC6Cf5f3qDjxsA7QlYRjp+lEGsAaiHeYT3Y8FA/IXw==
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=aTp7q/ZHk7HkYBhjcP45UkA8KsnmhcNReDsCUFbzpKI=; b=biNqxbFWBcZxv8cQj5ZZsEb+5Dj9YAl5cuZBr4XNbDscJqxkg6TsZp3pcNL378vh2PJ2aObgGri9o1tcRpU++KvYP0IWj5wPZAAcwZewYBmBWuxGf6MO/5Su7UWVhVCFwE3Rbnh0Rk8VPKfyy/1NrWDMnInapc6dFTtAZFAkUa4M5qFnjnJAyhwDGpNFsmap90a+NqtvbjQ4Sd5UStM9oDi8GCDE04/WdwBURQ0dbSR2rtXePm6zoEVjWxjjLD1XQxOKgqxG8or+4iwMd1ofBzkcCR8Vl1C5a5+BediFVJIpfwYLqLJaZBAlK7t8fHICeIf/v4n/Qqol4KRAF/ybqg==
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=aTp7q/ZHk7HkYBhjcP45UkA8KsnmhcNReDsCUFbzpKI=; b=TCmNcXtT429BqtCzI7z2NQE0u6nxjd6MyFdB6YE/u1LZ5FSDOx4n0MRGEeKp+IFbWgnm7ZhnBqwbp/62AaaJbQSfudkoEbIf6UAFRQBS5LZWa+9DIHNZXfcn3R0ERp9t3stCa7/XBV6gtGZIRnku1jGLbyTRAo9uhyvdFtXMzSE=
Received: from MW3PR11MB4619.namprd11.prod.outlook.com (20.181.54.207) by MW3PR11MB4713.namprd11.prod.outlook.com (10.141.72.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.25; Wed, 19 Feb 2020 17:48:49 +0000
Received: from MW3PR11MB4619.namprd11.prod.outlook.com ([fe80::b87d:76f6:5a2e:951c]) by MW3PR11MB4619.namprd11.prod.outlook.com ([fe80::b87d:76f6:5a2e:951c%3]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 17:48:49 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Robert Raszuk <robert@raszuk.net>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Flow Control Discussion for IS-IS Flooding Speed
Thread-Index: AdXmy57fbkJZPBB7TgK3RmmTteJ+KgAOFdkAABH9+fA=
Date: Wed, 19 Feb 2020 17:48:49 +0000
Message-ID: <MW3PR11MB4619E47034C379FB48208C9AC1100@MW3PR11MB4619.namprd11.prod.outlook.com>
References: <MW3PR11MB46191E81D5B22B454D8184A4C1100@MW3PR11MB4619.namprd11.prod.outlook.com> <CAOj+MMEkQRArOZJc_Fhc0PqKT9xSRjqSBj+h0mBtj78W7niuSg@mail.gmail.com>
In-Reply-To: <CAOj+MMEkQRArOZJc_Fhc0PqKT9xSRjqSBj+h0mBtj78W7niuSg@mail.gmail.com>
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:1005::756]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a443adc6-84a2-4a30-6e13-08d7b563f9cc
x-ms-traffictypediagnostic: MW3PR11MB4713:
x-microsoft-antispam-prvs: <MW3PR11MB471362A89118D79302372E78C1100@MW3PR11MB4713.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0318501FAE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(366004)(39860400002)(136003)(396003)(189003)(199004)(81166006)(81156014)(64756008)(66476007)(8676002)(76116006)(478600001)(8936002)(66446008)(966005)(71200400001)(66556008)(2906002)(66946007)(316002)(6916009)(55016002)(9686003)(4326008)(5660300002)(52536014)(33656002)(53546011)(6506007)(86362001)(7696005)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:MW3PR11MB4713; H:MW3PR11MB4619.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: BCL:0;
x-microsoft-antispam-message-info: YTM6arI2sQVU0vfC79yrcf7/8k814P8zPpD9XMBEiIeKxeqQf7NYxNoiuWb/+wWzaVd5aiOJO/fNnUVNCB6V3vu1PJhLcUXQWkqLZ/L3nxY1tpjKvuYfKtYeT3FU2JFLYSADoWqFqG9fQVfxq7AObqjd7DSN2JrBoMMBgynTFXwv5kDvBiygbuzHIezTbr7IsjIhA5beaobNGjkJvUwzXVEadkh7LFygrYiVqBPY2wOm4CsbMcZnPO9Z8GcHymIGCxv9+LgywSywYz3dyv0H+HW0lL/oOiMyI3IJ5/CrJ5h5+mKP8uXAswzC2eoUgICt9g02JRXEjn6F/l/qt3wLrOxHmbuneRXutcB004FbtHe4s2BBUS5QyAqJeGq7Gjkz/v99HVr+pcYfEZO6GvfURcxi9iJNfZZLSl7zhulgSHGgHXE/VZq9EW/yOX6ic1mMpBQ5sIN1cdjvdB7DvDwr7Hm+fL/Xbb/Xdo5ZBm9tGshwYsEqhjQmAfj+/cwWWE6E4QgahYY8uEOuxCvrLqBu4Q==
x-ms-exchange-antispam-messagedata: 6zCVdqGKH8/BLaj00ioZWSG3jDGIWDBF6mtaEYo5K93eXH7MCVK6A0Obbw+8aVScG45tRXReZ8dF4zSz/dAOA6Uz/yxCm/6tKXVNMdMKaiOOofKMEz8RQpPa4ay+a6h61NHT9keepVVomwkpjZFfAMOx5Z4UJBLvZWjA2B+izWo=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB4619E47034C379FB48208C9AC1100MW3PR11MB4619namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a443adc6-84a2-4a30-6e13-08d7b563f9cc
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 17:48:49.1905 (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: jzaokR2ogvoLd1GZUe57KXUSkOp4I+a2PK2jTIlmDwirdP97vv4IFRzRAcU/UiSlFOqbOdV5JnC/diHPBb1UuQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR11MB4713
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/YKkEL_2b4ZiYsyJ--CObVFKXBls>
Subject: Re: [Lsr] Flow Control Discussion for IS-IS Flooding Speed
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, 19 Feb 2020 17:48:57 -0000

Robert –

Thanx for your input.

Note that one of the suggestions in https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-flooding-scale/  is to prioritize the reception of SNPs over LSPs so that we are less likely to drop ACKs.
It is not clear to me why you think SNP generation would be an issue.
Once a received LSP is processed one of the outputs is to set a per interface flag indicating that an ACK (PSNP) needs to be sent (SSN flag). Implementations usually implement some small delay so that multiple ACKs can be sent in a single PSNP – but I do not see why this should be viewed as a bottleneck.

If your concern is that we need to emphasize the importance of sending timely ACKs, I think we could look at text that makes that point.

   Les


From: Lsr <lsr-bounces@ietf.org> On Behalf Of Robert Raszuk
Sent: Wednesday, February 19, 2020 1:07 AM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Cc: lsr@ietf.org
Subject: Re: [Lsr] Flow Control Discussion for IS-IS Flooding Speed

Hi Les & all,

Watching this discussion I would like to state that IMO going with transmitter based rate limiting (I would not call it flow control) is much easier option to deploy and operate. It also has no dependency across other side of p2p adj which is a very important factor. The only issue here is if generation of [P|C]SNPs is fast enough.

Receiver based flow control is simple in flow theory however I have a feeling that if we are to go that path we would be much better to actually run ISIS flooding over DC-TCP and avoid reinventing the wheel.

Thx,
Robert.

On Wed, Feb 19, 2020 at 3:26 AM Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:
Two recent drafts advocate for the use of faster LSP flooding speeds in IS-IS:

https://datatracker.ietf.org/doc/draft-decraene-lsr-isis-flooding-speed/
https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-flooding-scale/

There is strong agreement on two key points:

1)Modern networks require much faster flooding speeds than are commonly in use today

2)To deploy faster flooding speeds safely some form of flow control is needed

The key point of contention between the two drafts is how flow control should be implemented.

https://datatracker.ietf.org/doc/draft-decraene-lsr-isis-flooding-speed/ advocates for a receiver based flow control where the receiver advertises in hellos the parameters which indicate the rate/burst size which the receiver is capable of supporting on the interface. Senders are required to limit the rate of LSP transmission on that interface in accordance with the values advertised by the receiver.

https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-flooding-scale/  advocates for a transmit based flow control where the transmitter monitors the number of unacknowledged LSPs sent on each interface and implements a backoff algorithm to slow the rate of sending LSPs based on the length of the per interface unacknowledged queue.

While other differences between the two drafts exist, it is fair to say that if agreement could be reached on the form of flow control  then it is likely other issues could be resolved easily.

This email starts the discussion regarding the flow control issue.



_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr