Re: [babel] Genart last call review of draft-ietf-babel-rtt-extension-04

Juliusz Chroboczek <jch@irif.fr> Mon, 02 October 2023 20:15 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 BCB3BC151086; Mon, 2 Oct 2023 13:15:48 -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 G2IvuLot0feR; Mon, 2 Oct 2023 13:15:43 -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 DB385C14CEE3; Mon, 2 Oct 2023 13:15: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 392KFWrr022912; Mon, 2 Oct 2023 22:15: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 90B0B6DD36; Mon, 2 Oct 2023 22:15:31 +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=1696277724; x=1697141725; bh= ot79R1N8FLrLzLEWWJOmuF/8YHufr0f2EMG0a/GGqEU=; b=VCg+NJnmrrQFwXu7 RCjd7aUYP1z2c+Youe4aSQcfHe3ecw1MIyrv2Gt7BXvSSgzsnU3og6A3YIZ31PN0 WhG0agKWLFWtUFH5rjAMlF80OUS48qzZ9vtewUGEcz7ivK012yetPn624reDPQEf aGC1mINEqIbzWxPR2p1w98wPQM3AH9+CYxnG0HGILrgOKf/QB/36tDXpQOAhx8rf 0ARn6Y70OAjT4rblofeT79jkZkJzW4U2c/f5ffYVuA5cNzEwYn5YqKTEeqCZ/o+N 1nH3h7n3nd1cLpRnkwxwEvHh/XIv5N5HjG+ijfvnzB+xTX535mteBttIpu5Xyi2T gpBacg==
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 QsHPUm5Kyjkc; Mon, 2 Oct 2023 22:15:24 +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 802066DCBB; Mon, 2 Oct 2023 22:15:23 +0200 (CEST)
Date: Mon, 02 Oct 2023 22:15:23 +0200
Message-ID: <87pm1wzspw.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Roni Even <ron.even.tlv@gmail.com>
Cc: gen-art@ietf.org, babel@ietf.org, draft-ietf-babel-rtt-extension.all@ietf.org, last-call@ietf.org
In-Reply-To: <169625409085.59483.5646714210495356663@ietfa.amsl.com>
References: <169625409085.59483.5646714210495356663@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/29.1 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]); Mon, 02 Oct 2023 22:15:32 +0200 (CEST)
X-Miltered: at korolev with ID 651B24E4.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 651B24E4.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 : 651B24E4.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/komgSJoTze3ZZiSGlLO-LBEaBxA>
Subject: Re: [babel] Genart last call review of draft-ietf-babel-rtt-extension-04
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 02 Oct 2023 20:15:48 -0000

Thanks for your review, Roni.

> The document was changed in 02 from experimental to standard track. There is
> text in the end of section 4 about the algorithm being experimental

Right.

> from the mailing list i noticed that the reason to make it standard
> track is to allow using the TLVs by other WGs.

My understanding is that the goal is to allow other WGs to depend on the
protocol without incurring the complications of a downref.

Here's some background.  On the one hand, the algorithm has been
extensively tested in simulation, and deployed in production on hundreds of
routers, with no ill effects.  On the other hand, we don't fully understand
why it works -- in fact, I'm surprised it works as well as it does, I'd
expect at least some instability.

Hence, we're quite confident that this protocol is both useful and safe to
deploy on the Internet, which makes it a candidate for a Standards Track
document.  At the same time, we don't want to preclude experimentation
with other algorithms, possibly easier to analyse from a theoretical
standpoint, and hence we prefer to stress that the algorithm is experimental.

> Of course you could split the document to two documents one standard
> track and the other experimental but as i said this is up to the group
> and i have no real objection to publish the document as is.

I'd rather not split the document, since the first part would lack
rationale if we did.  If there are strong objections, we could conceivably
move the algorithm into an appendix, but I'd rather not do that, as I feel
that the document reads well as it stands.

Thanks again,

-- Juliusz