IETF Logo Mail Archive

[babel] Congestion control [was: Open issues...]

Juliusz Chroboczek <jch@irif.fr> Fri, 26 July 2019 21:41 UTC

Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D2A12012D for <babel@ietfa.amsl.com>; Fri, 26 Jul 2019 14:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 IAfRr_0vPsU1 for <babel@ietfa.amsl.com>; Fri, 26 Jul 2019 14:41:37 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 6E5E212006E for <babel@ietf.org>; Fri, 26 Jul 2019 14:41:37 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id x6QLfWbb014914; Fri, 26 Jul 2019 23:41:32 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7B35845750; Fri, 26 Jul 2019 23:41:35 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id eO0l7omx4W2Q; Fri, 26 Jul 2019 23:41:34 +0200 (CEST)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8E9E94574C; Fri, 26 Jul 2019 23:41:34 +0200 (CEST)
Date: Fri, 26 Jul 2019 23:41:34 +0200
Message-ID: <87tvb8eanl.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: Babel at IETF <babel@ietf.org>
In-Reply-To: <CAA93jw7YZp6nPgW_DccAkbaSG=MxeFymesKBMJnOwgk++COHTQ@mail.gmail.com>
References: <87k1c75cn5.wl-jch@irif.fr> <CAA93jw7YZp6nPgW_DccAkbaSG=MxeFymesKBMJnOwgk++COHTQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 26 Jul 2019 23:41:32 +0200 (CEST)
X-Miltered: at korolev with ID 5D3B738C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5D3B738C.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 5D3B738C.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/xvdfCJh07HiEP0qtywC5uM7Oph4>
Subject: [babel] Congestion control [was: Open issues...]
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2019 21:41:40 -0000

> B) As you have larger numbers of routes (1000s), congestion control
> becomes a problem

I'm pretty sure that packet pacing (spreading the announcements over the
update interval rather then sending them all as a burst as we currently do)
would solve your issues, Dave.

This won't happen for 1.9, which I'd like to release before the summer ends.

> My "solution" for some congestion control issues is to start dynamically
> increasing the route announcement interval for stabler routes, while
> still announcing the most important ones (like defaults) in the
> hello. the protocol has an underused feature where we can announce a per
> route interval larger than the default.

Indeed.  This can be done in addition to packet pacing.

-- Juliusz

v2.23.0 | Report a Bug | By Email