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

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> Fri, 18 December 2015 09:53 UTC

Return-Path: <jch@pps.univ-paris-diderot.fr>
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 ECDEC1B3518 for <homenet@ietfa.amsl.com>; Fri, 18 Dec 2015 01:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 YokSYIA_JrHT for <homenet@ietfa.amsl.com>; Fri, 18 Dec 2015 01:53:44 -0800 (PST)
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 4EFF61B34C8 for <homenet@ietf.org>; Fri, 18 Dec 2015 01:53:44 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id tBI9rg6C021971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 Dec 2015 10:53:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id tBI9rgM9031890; Fri, 18 Dec 2015 10:53:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 6261C61FA2; Fri, 18 Dec 2015 10:53:42 +0100 (CET)
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 XmnT5-pL-6lw; Fri, 18 Dec 2015 10:53:40 +0100 (CET)
Received: from trurl.pps.univ-paris-diderot.fr (col75-1-78-194-40-74.fbxo.proxad.net [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id ADB3E61FA1; Fri, 18 Dec 2015 10:53:40 +0100 (CET)
Date: Fri, 18 Dec 2015 10:53:42 +0100
Message-ID: <87egekyteh.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Philip Homburg <pch-homenet-1a@u-1.phicoh.com>
In-Reply-To: <m1a9YEk-0000J3C@stereo.hq.phicoh.net>
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>
User-Agent: Wanderlust/2.15.9
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 [IPv6:2001:660:3301:8000::1:2]); Fri, 18 Dec 2015 10:53:42 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 18 Dec 2015 10:53:42 +0100 (CET)
X-Miltered: at korolev with ID 5673D7A6.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5673D7A6.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5673D7A6.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5673D7A6.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5673D7A6.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5673D7A6.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PGSPg6Dwym5u7TQ0RPOZEuxvdzA>
Cc: homenet@ietf.org, "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 09:53:46 -0000

> 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.)

-- Juliusz