Re: [homenet] [Babel-users] Detecting bridges

Markus Stenberg <markus.stenberg@iki.fi> Fri, 18 December 2015 12:06 UTC

Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 857481B2B81 for <homenet@ietfa.amsl.com>; Fri, 18 Dec 2015 04:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=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 Jw1qXN_0h1Bl for <homenet@ietfa.amsl.com>; Fri, 18 Dec 2015 04:06:09 -0800 (PST)
Received: from julia1.inet.fi (mta-out1.inet.fi [62.71.2.232]) by ietfa.amsl.com (Postfix) with ESMTP id 70B331B2B77 for <homenet@ietf.org>; Fri, 18 Dec 2015 04:06:09 -0800 (PST)
Received: from poro.lan (80.220.86.47) by julia1.inet.fi (9.0.002.03-2-gbe5d057) (authenticated as stenma-47) id 566976B500463010; Fri, 18 Dec 2015 14:03:21 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87egekyteh.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 18 Dec 2015 14:06:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F9242EA-DFB0-4C85-9586-6E66D4C767EA@iki.fi>
References: <566426C4.9000901@kos.mx> <7ia8pm1uuy.wl-jch@pps.univ-paris-diderot.fr> <5665A96A.8040708@kos.mx> <7izixmz15f.wl-jch@pps.univ-paris-diderot.fr> <56670C48.5000807@kos.mx> <566A976B.9010900@kos.mx> <566A9C87.20209@kos.mx> <C5753B93-CB4A-4620-9168-568B7DE0A868@pps.univ-paris-diderot.fr> <566B1622.5030102@kos.mx> <CAKLmikNcRB9OvgoYUjwePfrTkhApzXY3thvwGOqVDVynyKMrog@mail.gmail.com> <87si38s9u7.wl-jch@pps.univ-paris-diderot.fr> <CAKLmikOsg+TrOsv=h=JTMfgmSYvvYAs0nRdzHnb-5zYaOF_J4Q@mail.gmail.com> <566BFFFD.20704@kos.mx> <877fkjstgi.wl-jch@pps.univ-paris-diderot.fr> <566D569D.20705@kos.mx> <87k2oih2vi.wl-jch@pps.univ-paris-diderot.fr> <566D842C.4010002@kos.mx> <87fuz6gwgu.wl-jch@pps.univ-paris-diderot.fr> <12B9F58B-E806-48CC-BBBB-BA19BACC3406@pps.univ-paris-diderot.fr> <DC2F9C30-7406-4754-99CB-166EDC82F65A@pps.univ-paris-diderot.fr> <87wpsgkflk.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw54JK-HqLt4MW=AGMEk=+vuMzvyMyT3=x9+q9nagEqMGQ@mail.gmail.com> <87egekyteh.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/aDWQ4MLF50k1gxd2D47R8fD6BlE>
Cc: homenet@ietf.org, Philip Homburg <pch-homenet-1a@u-1.phicoh.com>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: Re: [homenet] [Babel-users] Detecting bridges
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2015 12:06:11 -0000

On 18.12.2015, at 11.53, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>> Is there room in the protocol for a router to announce what link type it
>> is on?
> This could be carried by a sub-TLV of Hello (or a sub-TLV of IHU if you
> want to make it per-host).
> 
>> I.e., a router on wifi announces wifi and when a router that is on wired
>> receives an announcement from a router on wifi it knows that there
>> a bridge somewhere.
> 
> Not a bad idea, but I'm a little hesitant to implement that, since it
> would require defining a taxonomy of interface types at the protocol
> level.  (Currently the taxonomy exists in the implementation, but it
> doesn’t appear in the protocol -- the protocol only knows about metrics.)

I am somewhat suspicious about the idea too, although for different reasons. Notably, most things that run routing protocol these days use ethernet plugs for them (+- some wireless ad-hoc people).

Even if I have ‘modern cheapo router’ on both ends of a powerline bridge, odds are, it is just using ethernet plug. So link type autodetection is out of the window, and if I manually need to specify that this ethernet is really powerline, I might as well configure the routing protocol, and I find both ideas non-appealing.

Cheers,

-Markus