IETF Logo Mail Archive

[babel] Babel-RTT information model and example parameters

Baptiste Jonglez <baptiste.jonglez@imag.fr> Thu, 25 July 2019 15:13 UTC

Return-Path: <baptiste.jonglez@imag.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 9FBB9120398 for <babel@ietfa.amsl.com>; Thu, 25 Jul 2019 08:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 CnDqCwOH0Vrz for <babel@ietfa.amsl.com>; Thu, 25 Jul 2019 08:13:44 -0700 (PDT)
Received: from zm-mta-out-1.u-ga.fr (zm-mta-out-1.u-ga.fr [152.77.200.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C352C120319 for <babel@ietf.org>; Thu, 25 Jul 2019 08:13:34 -0700 (PDT)
Received: from zm-mta-out.u-ga.fr (zm-mta-out.u-ga.fr [152.77.200.58]) by zm-mta-out-1.u-ga.fr (Postfix) with ESMTP id 29E94A02EB; Thu, 25 Jul 2019 17:13:33 +0200 (CEST)
Received: from smtps.univ-grenoble-alpes.fr (mailhost.u-ga.fr [152.77.1.30]) by zm-mta-out.u-ga.fr (Postfix) with ESMTP id 2518CE00A3; Thu, 25 Jul 2019 17:13:33 +0200 (CEST)
Received: from imag.fr (blaine.imag.fr [129.88.55.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jonglezb@univ-grenoble-alpes.fr) by smtps.univ-grenoble-alpes.fr (Postfix) with ESMTPSA id 1FDE7125EB9; Thu, 25 Jul 2019 17:13:33 +0200 (CEST)
Date: Thu, 25 Jul 2019 17:13:32 +0200
From: Baptiste Jonglez <baptiste.jonglez@imag.fr>
To: Barbara Stark <bs7652@att.com>, Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: babel@ietf.org
Message-ID: <20190725151332.ywxjpxpxoritx4ql@imag.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="ijfacgroonlkdlm5"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
X-Greylist: Whitelist-UGA SMTP Authentifie (jonglezb@univ-grenoble-alpes.fr) via smtps-465 ACL (112)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/RVMgNtk2oy7sBupOXrn_N5Lk-mg>
Subject: [babel] Babel-RTT information model and example parameters
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: Thu, 25 Jul 2019 15:13:50 -0000

Hi Barbara, Mahesh,

The discussion about the information model yesterday and Juliusz' email on
policies got me thinking about the parameters of the babel-rtt extension.

Should the information model specify parameters that are not really part
of the spec?  I'm thinking of the example function for metric computation
and its 3 parameters rtt-min, rtt-max, max-rtt-penalty:

  https://tools.ietf.org/html/draft-ietf-babel-rtt-extension-00#section-2.2.1

This metric function is just an example: an implementation is free to do
something totally different.  So, does it make sense to add the
corresponding parameters (as ro or rw) to the information model?

Sorry if this is a dumb question, I'm quite new to this information model / YANG thing.

Thanks,

-- 
Baptiste Jonglez
PhD student
Univ. Grenoble Alpes <https://www.univ-grenoble-alpes.fr/>
LIG lab <https://www.liglab.fr/>
Drakkar team <http://drakkar.imag.fr/>  |  Polaris team at INRIA <https://team.inria.fr/polaris/>

v2.23.0 | Report a Bug | By Email