Re: [manet] MANET protocols in the community network as Funkfeuer.

Thomas Heide Clausen <ietf@thomasclausen.org> Sun, 14 October 2012 08:28 UTC

Return-Path: <ietf@thomasclausen.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBEC21F84E4 for <manet@ietfa.amsl.com>; Sun, 14 Oct 2012 01:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level:
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.499, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4gSFEqh7Yxq for <manet@ietfa.amsl.com>; Sun, 14 Oct 2012 01:28:22 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id A989321F849D for <manet@ietf.org>; Sun, 14 Oct 2012 01:28:22 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id AACF9A36DA for <manet@ietf.org>; Sun, 14 Oct 2012 01:28:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 907181C072A; Sun, 14 Oct 2012 01:28:20 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.20.10.6] (37-8-188-28.coucou-networks.fr [37.8.188.28]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id C218E1C0562; Sun, 14 Oct 2012 01:28:18 -0700 (PDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: Thomas Heide Clausen <ietf@thomasclausen.org>
In-Reply-To: <CAGnRvupVw30y8g=u5Mj6MiG_kpGUReGsgq2Ncyqv0as5mVDg7w@mail.gmail.com>
Date: Sun, 14 Oct 2012 10:28:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B25D644-2E12-4091-A7B9-98D055C0C28D@thomasclausen.org>
References: <CADnDZ8_M_vVrpMyNZeLwAfQsqia=+E8p3YA-7B1azs5i9fJw4A@mail.gmail.com> <CAK=bVC9MV-6NHMMGUnE=-6ww9TBiTAyk-YqBDSJrWjH3FE-V5Q@mail.gmail.com> <CAGnRvuppa8H5hkPz7tMR7g3xMBTtRc9-6h_N_KVh=ySKp_8hoA@mail.gmail.com> <84665BD8-B7A3-42D0-9C35-C8AB9240C641@thomasclausen.org> <CAGnRvupVw30y8g=u5Mj6MiG_kpGUReGsgq2Ncyqv0as5mVDg7w@mail.gmail.com>
To: Henning Rogge <hrogge@googlemail.com>
X-Mailer: Apple Mail (2.1498)
Cc: manet@ietf.org
Subject: Re: [manet] MANET protocols in the community network as Funkfeuer.
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Oct 2012 08:28:23 -0000

On Oct 14, 2012, at 10:23 , Henning Rogge <hrogge@googlemail.com> wrote:

> On Sun, Oct 14, 2012 at 9:46 AM, Thomas Heide Clausen
> <ietf@thomasclausen.org> wrote:
>> 
>> On Oct 13, 2012, at 23:18 , Henning Rogge <hrogge@googlemail.com> wrote:
>> 
>>> Interesting question... the last time we worked on the draft the
>>> discussion bogged down with the question if this is the "right way" to
>>> do ETX.
>>> 
>>> Maybe a split would be a good idea, we could have an informal document
>>> specifying the strategy we are using at Freifunk/Funkfeuer for ETX.
>>> And then we could work on how to transform this into a good OLSRv2
>>> metric.
>>> 
>> 
>> I do not know if a split is the right thing to do - then again, I do not know that it isn't either.
> 
> Maybe instead of splitting it into two Drafts, splitting the draft
> into two parts... one explaining what is used in the
> Freifunk/Funkfeuer networks currently and another one that suggests a
> way to use this strategy for OLSRv2 metrics.
> 
>> I think that what the previous version of the I-D failed to do, and what caused the bogged-down discussion, was to frame properly what the content was about.
>> 
>> I think that producing an informational RFC saying something of the kind:
>> 
>>        "This is one way of doing ETX, specifically the one way that has shown to work
>>          well in a large deployment in continuous operation. It is probably not the only way,
>>          and perhaps not the best way, of doing ETX, but this is one way that's proven to
>>          work well"
>> 
>> Would be quite useful.
> 
> Another reason why it bogged down was the introduction of the new TLV
> to have a "out-of-band" channel between both end of the link for the
> routing metric calculation. The current Freifunk/Funkfeuer metric
> cannot be done without one.
> 

Yes, but that would (IMO) be fair enough in the "this is one way of doing ETX that we've got operational experience with as working - but, not the only one".

The only snag would be that care should be made that the defined TLV would be "flexible" enough to support other such signaling, but I do not see that as a huge problem....

Thomas

> Henning Rogge
> 
> -- 
> Steven Hawkings about cosmic inflation: "An increase of billions of
> billions of percent in a tiny fraction of a second. Of course, that
> was before the present government."