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

tony.li@tony.li Wed, 19 February 2020 19:29 UTC

Return-Path: <tony1athome@gmail.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 512E6120086 for <lsr@ietfa.amsl.com>; Wed, 19 Feb 2020 11:29:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ymtZ3zAAqM_O for <lsr@ietfa.amsl.com>; Wed, 19 Feb 2020 11:29:27 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5095120045 for <lsr@ietf.org>; Wed, 19 Feb 2020 11:29:26 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id b22so462500pls.12 for <lsr@ietf.org>; Wed, 19 Feb 2020 11:29:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wUEn38PBSUr6tFuQPffZ3c1IgZaZlueZJk+EZHzDuQM=; b=npI0LtYvECe8PgfllXPlLbSnQ2c/JtxQ01Yvcte/4cYVCxtwBGXVVPEsJlP6g7d2VD CqcvYl57vFhaXC/QkU/6Boa14pbN1F4xwAUE1b46dRFziUkMo946z2DyWjgxoyEKnKsz Bb72LSJ/lHwpS+LeWBxYgp8TtLU0CkoNgsS7mmRUJklLCfzMjZcGljcKdsXh+VgNUckm +CGVZuejuxcrJArutsAMv3gpkAr8sIwxGNKjk9NzdZB8ChJkDHapzuphLTuAvskaLfNI sCLnov7DLi8lUz/rrqMw90pPRwA1sHsOpLCsziBecjaMMruVklSQeJs2OsPm7Oq/OBeV U+Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=wUEn38PBSUr6tFuQPffZ3c1IgZaZlueZJk+EZHzDuQM=; b=T/TEKf72WA77Z9sbFV72KP/oSud277t0SMkKyEXA+DoExRR2K0TMHrseTOZkUNfuMI iFZYYRoKZ5fVrXALpvDuwPEiiryHM1nXPaThD/2oERZ3R6uGAkJxXmqnWF8d7CyBSFil oQd1m9GqziUcKDRdyMIpclDYsk+kaBbMItXl8/7GvmlxoLzvprzbaSzBCdEyYZSEixOD Htt0SV63f6+i31s7+QDa6JJoaX93rODPwfs8oLkFCQ7HMTTnWhnlpTiW/WKP4UEoXhMM hpfNTfnYerBuK3lHIh3bgrNcp329Y7L1onTGt0D+LmfATY1Mg2CsXO4DSpFmqoAVIcEm r/FA==
X-Gm-Message-State: APjAAAWSHVcHkgowuhWFJoPc6tVfRqVu++0mHvz/ECwbwJQNtMjDQNbG ajjbteE1BNFOzKwFKxEdyGw=
X-Google-Smtp-Source: APXvYqzk8q09MkFlb20CVYp/86I8xBlZqn7GyJdihlDGIuYEKyNzHY01wi0Ua1eyQvdVyWd6VcB/sg==
X-Received: by 2002:a17:90a:e28e:: with SMTP id d14mr11094484pjz.56.1582140566380; Wed, 19 Feb 2020 11:29:26 -0800 (PST)
Received: from [10.128.13.33] ([118.127.110.110]) by smtp.gmail.com with ESMTPSA id 64sm414835pfd.48.2020.02.19.11.29.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Feb 2020 11:29:25 -0800 (PST)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: tony.li@tony.li
In-Reply-To: <MW3PR11MB4619C54F5C6160491847AA45C1100@MW3PR11MB4619.namprd11.prod.outlook.com>
Date: Thu, 20 Feb 2020 06:29:21 +1100
Cc: Peter Psenak <ppsenak@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D58369B5-489E-442E-9A60-770E763C349D@tony.li>
References: <5b430357-56ad-2901-f5a8-c0678a507293@cisco.com> <4FC90EB2-D355-4DC5-8365-E5FBE037954E@gmail.com> <f5b56713-2a4d-1bf7-8362-df4323675c61@cisco.com> <MW3PR11MB4619C54F5C6160491847AA45C1100@MW3PR11MB4619.namprd11.prod.outlook.com>
To: Les Ginsberg <ginsberg@cisco.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/EBmgIOB9h27BOVoovtRaXqZNvkM>
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 19:29:28 -0000

Les,

> As you need to send signaling based upon dynamic receiver state and this signaling is contained in unreliable PDUs (hellos) and to be useful this signaling needs to be sent ASAP - you cannot wait until the next periodic hello interval (default 10 seconds) to expire. So you are going to have to introduce extra hello traffic at a time when protocol input queues are already stressed.


I am not proposing that we add additional packets at this time.  Yes, I realize that it may limit the effectiveness of the feedback, but without serious experimentation, the cure may be worse than the disease.  I propose to tread very carefully.


> Given hellos are unreliable, the question of how many transmissions of the update flow info is enough arises. You could make this more deterministic by enhancing the new TLV to include information received from the neighbor so that each side would know when the neighbor had received the updated info. This then requires additional hellos be sent in both directions - which exacerbates the queue issues on both receiver and transmitter.


I am not proposing this.  If the hello is lost, then the transmitter has less information to work with, which is not an unreasonable situation.

Tony