[babel] Re: RFC 9616 on Delay-Based Metric Extension for the Babel Routing Protocol
Juliusz Chroboczek <jch@irif.fr> Tue, 17 September 2024 12:44 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 C5503C16A126; Tue, 17 Sep 2024 05:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=irif.fr
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fIW_Nq8TOR3S; Tue, 17 Sep 2024 05:44:13 -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-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8198C18DB91; Tue, 17 Sep 2024 05:44:11 -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 48HCi505003843; Tue, 17 Sep 2024 14:44:05 +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 BC6A74EE61; Tue, 17 Sep 2024 14:44:04 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=irif.fr; h= content-type:content-type:mime-version:user-agent:references :in-reply-to:subject:subject:from:from:message-id:date:date :received:received; s=dkim-irif; t=1726577042; x=1727441043; bh= 0cCmYPuYamgezidERIREI4gz/REmgMvOiMc9ogDc1rU=; b=ndMld3j6vI+4eQpB rv/3QCJraZxHr65i7oisBJk4NsNV6arHJ7HGJWe1TieErWOYyL9M636Hc2gR4cwT m6ZpW7jKtJ0WoImsKgZrqPtXOvzHgulfEyItxxnmlo6JnNpHuSr5Edb7ghyxynVs jb8wX7Dn+6OrlqKcanz2eo37r/Lea4ygI6PGjYD9yaPrWqP/Us2tamL1IXJscqhW Gqr7Hd7n3XffFMTUH32Womzfw0IJjXo9uMvlUofOCwriOF2xt5KXhhmM1XmmopTW 5/g5Ix0x+geJlYyeyK68evxgbPPwo1y3Hh1bgnpCiDKcierGsQMXMp03bf+ZLjbu Nql1ew==
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 E1Q0P-X4x83Z; Tue, 17 Sep 2024 14:44:02 +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 B35E34EDE2; Tue, 17 Sep 2024 14:44:01 +0200 (CEST)
Date: Tue, 17 Sep 2024 14:44:00 +0200
Message-ID: <871q1i5u27.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: babel@ietf.org
In-Reply-To: <20240913191748.8EC933B874@rfcpa.rfc-editor.org>
References: <20240913191748.8EC933B874@rfcpa.rfc-editor.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.4 Mule/6.0
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]); Tue, 17 Sep 2024 14:44:05 +0200 (CEST)
X-Miltered: at korolev with ID 66E97995.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 66E97995.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 : 66E97995.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Message-ID-Hash: HKNOXQC4WREFG64R7YKSMQHL7CTC4Q7M
X-Message-ID-Hash: HKNOXQC4WREFG64R7YKSMQHL7CTC4Q7M
X-MailFrom: jch@irif.fr
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-babel.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: manet@ietf.org, Baptiste Jonglez <baptiste@bitsofnetworks.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [babel] Re: RFC 9616 on Delay-Based Metric Extension for the Babel Routing Protocol
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/699UOUpKPQz7LaSS0p8UotpOtZw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Owner: <mailto:babel-owner@ietf.org>
List-Post: <mailto:babel@ietf.org>
List-Subscribe: <mailto:babel-join@ietf.org>
List-Unsubscribe: <mailto:babel-leave@ietf.org>
> A new Request for Comments is now available in online RFC libraries. > > > RFC 9616 > > Title: Delay-Based Metric Extension for the > Babel Routing Protocol > Author: B. Jonglez, > J. Chroboczek > Status: Standards Track For those who weren't following: the reviewers forced me to rework this document quite a bit, and with hindsight they were right. The most notable change is that the second part (oscillation avoidance) has been rewritten in normative language. This makes it slightly more difficult to read (due to all the SHOULDs and MUSTs), but it makes it clear that the algorithm is ready and safe for deployment. I've done my best to imply that it's not the only possible algorithm, and that the first part (the packet format and RTT sampling) can be reused with other algorithms. Pascal Thubert (to whom thanks) coerced me into writing an applicability section, with me screaming and kicking. With hindsight, that was a good idea. (While I remain unconvinced by pure applicability RFCs, I now understand that having an applicability section in an RFC in an otherwise technical RFC is useful even when the applicability can easily be deduced from the rest of the document.) The one negative change is due to one AD insisting (in oh so many words!) that I'm not allowed to use the word "blackhole". I suppose that gravitational singularities are taboo in their culture. In case you're not a Babel fan (why?), this subprotocol is not specific to Babel, and could easily be adapted to any other distance-vector protocol, and with slightly more effort to a link-state protocol. I'm open to collaboration. -- Juliusz
- [babel] RFC 9616 on Delay-Based Metric Extension … rfc-editor
- [babel] Re: RFC 9616 on Delay-Based Metric Extens… Juliusz Chroboczek