Re: [manet] Some comments on draft-funkfeuer-manet-olsrv2-etx-01
Georg Wittenburg <georg.wittenburg@inria.fr> Wed, 18 May 2011 20:16 UTC
Return-Path: <georg.wittenburg@inria.fr>
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 68A53E072C for <manet@ietfa.amsl.com>; Wed, 18 May 2011 13:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 uKY0Ypg5Qsq2 for <manet@ietfa.amsl.com>; Wed, 18 May 2011 13:16:21 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by ietfa.amsl.com (Postfix) with ESMTP id 72CCAE068B for <manet@ietf.org>; Wed, 18 May 2011 13:16:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.65,232,1304287200"; d="scan'208";a="94957164"
Received: from 212-198-208-196.rev.numericable.fr (HELO vaio.localnet) ([212.198.208.196]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 May 2011 22:16:13 +0200
From: Georg Wittenburg <georg.wittenburg@inria.fr>
Organization: INRIA
To: Henning Rogge <hrogge@googlemail.com>
Date: Wed, 18 May 2011 22:16:06 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.38-8-generic; KDE/4.6.3; i686; ; )
References: <201105111610.58611.georg.wittenburg@inria.fr> <201105131623.20102.georg.wittenburg@inria.fr> <136923972.1117761.1305397995016.JavaMail.root@zmbs2.inria.fr>
In-Reply-To: <136923972.1117761.1305397995016.JavaMail.root@zmbs2.inria.fr>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201105182216.06862.georg.wittenburg@inria.fr>
Cc: manet@ietf.org, David Young <dyoung@pobox.com>
Subject: Re: [manet] Some comments on draft-funkfeuer-manet-olsrv2-etx-01
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: Wed, 18 May 2011 20:16:26 -0000
Hi Henning, Teco, David, all, On Saturday 14 May 2011 20:33:15 Henning Rogge wrote: > Answer to Georg Wittenburg, Teco Boot and David Young... > > Am Freitag 13 Mai 2011, 16:23:19 schrieb Georg Wittenburg: > > > The funkfeuer metric drafts suggests to use all RFC 5444 packets for > > > link loss estimation, not only a certain message type. Your suggestion > > > would make it necessary to pad all RFC5444 packets to the maximum MTU, > > > which might be a considerable overhead. > > > > I agree. However, it still remains true that link loss estimation that > > relies excessively on small packets will lead to suboptimal results. I'm > > aware that the original ETX paper doesn't cover this, but it doesn't mean > > that it shouldn't be addressed in this draft. > > > > How about, for example, only incrementing the respective counters for > > packets whose size is above a certain threshold, say MTU / 2 (or even MTU > > / 4)? > > What if no OLSR packets are that large ? Do we add padding to get at least > one or multiple large packets each second ? Sounds like an acceptable trade-off. Another option would be to include data packets in the link loss estimation. Was there any particular reason why you decided against including them? > > > We do this in the Freifunk/Funkfeuer meshs, but in NHDP/OLSRv2 this > > > would be the job of the link hysteresis (which easily could be > > > implemented based on the link cost value). > > > > But since the link cost value depends on the metric used, it would be up > > to this draft to suggest values for this, wouldn't it? > > We had some discussion about this, but it seems that most people here don't > like to use the link metric to do the hysteresis. > > In Freifunk/Funkfeuer, we ignore each link with an link quality below 0.1 > in one direction. > > Am Freitag 13 Mai 2011, 17:53:53 schrieb Teco Boot: > > > How about, for example, only incrementing the respective counters for > > > packets whose size is above a certain threshold, say MTU / 2 (or even > > > MTU / 4)? > > > > How can packet sizes of lost packets be measured? > > Maybe with a second packet sequence number that is only increased for large > packets ? I don't see the problem here. Both sender and receiver can increment their respective packet counters based on the packets (above a certain size, or matching other conditions) which they see and ETX should just work as expected. Am I overlooking something? > Am Freitag 13 Mai 2011, 18:46:30 schrieb David Young: > > You can probably derive a much better metric than ETX by tapping into > > information that the rate adaptation collects. More than one 802.11 > > rate adaptation in the literature has tried to optimize the so-called > > goodput of a link by choosing a suitable bitrate for each packet based > > on packet properties such as size. Advantages of collecting information > > from the rate adaptation are that you avoid duplicating any code or > > computational effort, and you collect the information from a more > > suitable (IMO) place in the network stack. All the world's MANETs are > > not built on 802.11, it is true, but the same general principles apply: > > don't needlessly compute the same metric twice, and collect the link > > metric at the most suitable place. > > Doing this on one operation system with different wireless cards is hard... > doing it for multiple operation systems and different cards will get you > insane pretty quickly... > > I personally like the idea to get the rate control data of the mac80211 > stack in linux, unfortunately that only solves the problem for a very > special case, and only for unicast traffic. > > If you rely on the rate control, you need to send unicast probing packets > to all of your neighbors regularly if you have no traffic in this > direction. Best, Georg -- Dr. Georg Wittenburg Postdoctoral Researcher INRIA / École Polytechnique, HIPERCOM Team Laboratoire d'Informatique de l'École Polytechnique (LIX) Route de Saclay, 91128 Palaiseau (CEDEX) Phone: +33-(0)1-69334126, Fax: +33-(0)1-69334044 http://www.lix.polytechnique.fr/~wittenburg/
- [manet] Some comments on draft-funkfeuer-manet-ol… Georg Wittenburg
- Re: [manet] Some comments on draft-funkfeuer-mane… Henning Rogge
- Re: [manet] Some comments on draft-funkfeuer-mane… Georg Wittenburg
- Re: [manet] Some comments on draft-funkfeuer-mane… Emmanuel Baccelli
- Re: [manet] Some comments on draft-funkfeuer-mane… Teco Boot
- Re: [manet] Some comments on draft-funkfeuer-mane… David Young
- Re: [manet] Some comments on draft-funkfeuer-mane… Henning Rogge
- Re: [manet] Some comments on draft-funkfeuer-mane… Georg Wittenburg
- Re: [manet] Some comments on draft-funkfeuer-mane… David Young
- Re: [manet] Some comments on draft-funkfeuer-mane… Henning Rogge
- Re: [manet] Some comments on draft-funkfeuer-mane… Henning Rogge
- Re: [manet] Some comments on draft-funkfeuer-mane… Abdussalam Baryun
- Re: [manet] Some comments on draft-funkfeuer-mane… Georg Wittenburg
- Re: [manet] Some comments on draft-funkfeuer-mane… Henning Rogge