IETF Logo Mail Archive

Re: [babel] Interface types in babeld

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 28 March 2019 16:17 UTC

Return-Path: <mjethanandani@gmail.com>
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 1F7B5120284 for <babel@ietfa.amsl.com>; Thu, 28 Mar 2019 09:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 HevBu93zBOJq for <babel@ietfa.amsl.com>; Thu, 28 Mar 2019 09:17:10 -0700 (PDT)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 AFC981200EF for <babel@ietf.org>; Thu, 28 Mar 2019 09:17:10 -0700 (PDT)
Received: by mail-it1-x135.google.com with SMTP id h9so6970913itl.1 for <babel@ietf.org>; Thu, 28 Mar 2019 09:17:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=M59UypB4RlE/x2XX90rq8idf4ek2czsOGIfSqlXM5sE=; b=PtHTZiOnAqFEdgKC4Ngpba6ljQNJhPtucGGp/3dzkoJ243QNVusKXBEpvtfKGWx+L/ JR4+30M91LkDofu+tPVxIxQnrn8rIH2FhmBT6AgEB4vY7E5Tvibr8oKZ9SpZHt37COGX UkR8+xqEOG6xvYAE9z+ugvWq6jRq/h46BmXjsd4CFdjHYT6mEWHP5KCUFb8Vnt7KorrJ T7kpZoplxKLQFtVwEqGV5qfg0FS8PGFq7wQTAfs1/EQjAojQtejFPVKBYobI0xwSAdIj +kL458LjJfFfbwnyqR3FysItbHPhzKeGwhUgcydrbDOPdoC2ZQxpGLXkW2sCEr1nMxwh dBcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=M59UypB4RlE/x2XX90rq8idf4ek2czsOGIfSqlXM5sE=; b=FxHMW2D6BX92bEPKM2nMVkIkOFjXZBMnFSKxFUV3IjVfzvLxPRr6gwOS+/EhSIr2VG K6WhGvE93v7Bfw8PoRjQOw52oB8zvGp6ZyUEpewY51TyENKvvJ+OhSawWsLe+ujvG0QC oQ0dshtgbmWgbuoCI8hP+8SHLbkFG38H2lJg1lqsb3Ot18zPBZqewuDYMc1mQ5WEjKNs fthll/mrYMK+JI5nu+Hu7+ynroERi/7pfyXK8AZ+qgUM1dbtac2WB6dcMd9DFpMh9eqf klZ19ntwRwdH3xpaT+CjUGbz7uxjJAbuhrQKdejcLg8J9YS+HZdlGP4z8LTeBefDNMSF SRQQ==
X-Gm-Message-State: APjAAAWHqidRM5DJ6lDzmTcWUXIOq3TXqHt6UF6DJgnj4erXGgDGdYqk KGEU0xEMXL6sYbvkZ/CD5VA=
X-Google-Smtp-Source: APXvYqzGAWe953/xZmQUeNBlP9vUmZ1MlG9BecHUVZ8/oG/2fmiEzJ5xd8wZisBEB46DAJgocQ+XxA==
X-Received: by 2002:a05:6638:211:: with SMTP id e17mr31387259jaq.35.1553789829952; Thu, 28 Mar 2019 09:17:09 -0700 (PDT)
Received: from [100.90.211.238] ([172.56.12.72]) by smtp.gmail.com with ESMTPSA id b8sm2174757itb.20.2019.03.28.09.17.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Mar 2019 09:17:09 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <87d0mb6os6.wl-jch@irif.fr>
Date: Thu, 28 Mar 2019 17:17:06 +0100
Cc: Barbara Stark <bs7652@att.com>, babel@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AE334B7-E718-49FD-8804-8B197EF2F3D4@gmail.com>
References: <87d0mb6os6.wl-jch@irif.fr>
To: Juliusz Chroboczek <jch@irif.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/wCoJwMpulACPJZVFzvELppDgdXM>
Subject: Re: [babel] Interface types in babeld
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, 28 Mar 2019 16:17:13 -0000


> On Mar 28, 2019, at 3:45 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
> Dear Barbara, dear all,
> 
> Concerning your query about interface types.  In babeld, an interface can
> be configured by setting individual parameters:
> 
>  interface eth0 link-quality true
> 
> or by using an "interface type", which is a consistent bundle of parameters:
> 
>  interface eth0 type wired
> 
> Individual parameters can be overridden; for example
> 
>  interface eth0 type wired split-horizon false
> 
> means that eth0 has all the parameters of the type "wired", except that
> split-horizon is disabled.
> 
> Currently, the interface types are:
> 
>  wired:    cost 256 split-horizon true link-quality false
>  wireless: cost 96 split-horizon false link-quality true
>  tunnel:   cost 96 split-horizon true link-quality false
>            timestamps true max-rtt-penalty 96

I suggest that we model link type as the set of parameters defined here and use the default values indicated here. 

- name e.g. wired, wireless, tunnel
- cost 
- split-horizon 
- link-quality
- timestamps
- max-rtt-penalty

The default values can be improved with each version and based on implementation experience. 

> 
> The interface types are defined as not being stable between versions -- we
> try to keep the individual parameters compatible between versions, but the
> bundle of parameters corresponding to an interface type can be improved
> between versions.
> 
> -- Juliusz

Mahesh Jethanandani 
mjethanandani@gmail.com

> 
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel

v2.23.0 | Report a Bug | By Email