Re: [homenet] Updates to Homenet Architecture Principles doc

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 16 June 2014 20:17 UTC

Return-Path: <alexandru.petrescu@gmail.com>
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 37D081A01E8 for <homenet@ietfa.amsl.com>; Mon, 16 Jun 2014 13:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 2flWF-Si4W39 for <homenet@ietfa.amsl.com>; Mon, 16 Jun 2014 13:17:20 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A2FB1A01E4 for <homenet@ietf.org>; Mon, 16 Jun 2014 13:17:19 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s5GKHIdg005169 for <homenet@ietf.org>; Mon, 16 Jun 2014 22:17:18 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C0F182061DA for <homenet@ietf.org>; Mon, 16 Jun 2014 22:19:02 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B944B20163A for <homenet@ietf.org>; Mon, 16 Jun 2014 22:19:02 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.86.27]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s5GKHHG1023967 for <homenet@ietf.org>; Mon, 16 Jun 2014 22:17:18 +0200
Message-ID: <539F50CD.7050901@gmail.com>
Date: Mon, 16 Jun 2014 22:17:17 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <BEB843C7-EB1D-486A-A9A1-B99D48775D33@nominet.org.uk> <85F978F4-1293-4F9E-B5C7-068F95A0B626@nominet.org.uk> <CAKD1Yr2mzZOvCDwyyEZHef1rk5PAxtNZRVRys43SXnD=gVxLBA@mail.gmail.com> <143C7553-11D4-41A9-910E-FAD26F484635@fugue.com> <CAKD1Yr0hr8Pa_QU_9mjRjbxffQ=mdgOWYSQUyLc5ewkpuf5OmA@mail.gmail.com> <F08A2136-E88F-4785-BE01-14D386B9C2D9@fugue.com> <CAKD1Yr1nhnvG2H_9eeW-Dono3cZqYaxMZaCR1vcueOQgW4xqYQ@mail.gmail.com> <E66DDB31-C318-4025-BF8A-15F2336A2A08@fugue.com> <B289FE60-E0C7-4D3B-BE21-3C7109FAC69C@ecs.soton.ac.uk> <EMEW3|c9eee95ab0d06c016200d4557ca869f9q5CFPa03tjc|ecs.soton.ac.uk|B289FE60-E0C7-4D3B-BE21-3C7109FAC69C@ecs.soton.ac.uk> <539C51BA.6030901@globis.net> <87d2ebbmad.wl%jch@pps.univ-paris-diderot.fr> <539C67AA.4030501@globis.net> <87ioo35w49.wl%jch@pps.univ-paris-diderot.fr> <539D7A9F.5000407@globis.net> <87y4wyqhw8.wl%jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87y4wyqhw8.wl%jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/nBIweNELe5mOyeC3QuG8bXSHdkw
Subject: Re: [homenet] Updates to Homenet Architecture Principles doc
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Jun 2014 20:17:22 -0000

Le 15/06/2014 18:03, Juliusz Chroboczek a écrit :
>>>> "The inclusion of physical layer characteristics including bandwidth,
>>>> loss, and latency in path computation should be considered for
>>>> optimising communication in the homenet."
>
>> Should the text then rather say "Path selection in Homenet needs to be
>> more sophisticated than measuring pure hop count due to the use of
>> heterogeneous link technologies, and therefore the routing protocol should
>> be capable of utilising multiple link-dependent metrics, such as
>> bandwidth, delay, and link reliability", rather than mentioning
>> "optimised"?
>
> I'm happy with either.  The current text leaves it to the protocol people
> to decide what "optimising" means, but I also like the way you spell out
> the requirement.  If you'll allow me to indulge in some minor nit picking
> wrt. your suggested wording:
>
>   - you require "multiple [...] metrics", which is what we do in Babel, but
>     we certainly don't wish to prevent somebody from being smart enough to
>     design a single metric that works satisfactorily on all link layers;
>   - you use "bandwdith" where you mean "throughput" (yeah, I know, I'm
>     a pedant);
>   - I'm on a personal crusade against the utilisation of the verb "to utilise".
>
> So perhaps something like:
>
>    Due to the use of heterogeneous link technologies, path selection in
>    a homenet needs to be more refined than minimising hop count.  The
>    homenet routing protocol should be able to select paths according to
>    criteria such as latency, throughput, link reliability (e.g. measured
>    packet loss) or other performance metrics.

I agree.  Some of the new performance metrics which are unaccounted for, 
but present in deployments, is the quantity of radio energy in the air. 
  This is a real customer issue for which current deployed solutions are 
on/off knobs (I want a knob to turn off all WiFi in my home, turn off 
all cellular in my home, turn off all Bluetooth in my home, etc).  More 
sophisticated solutions would involve metrics which quantify this and 
compare meaningfully.  An example is the DAS parameter for mobile phones.

Alex

>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
>