Re: [manet] (DLEP) Relative Link Quality and routing metrics

Stan Ratliff <ratliffstan@gmail.com> Fri, 20 April 2018 19:06 UTC

Return-Path: <ratliffstan@gmail.com>
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 7A2C7127599 for <manet@ietfa.amsl.com>; Fri, 20 Apr 2018 12:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zpgoVLN3SFwo for <manet@ietfa.amsl.com>; Fri, 20 Apr 2018 12:06:13 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4EA0126D85 for <manet@ietf.org>; Fri, 20 Apr 2018 12:06:12 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id r22-v6so2630213ioc.12 for <manet@ietf.org>; Fri, 20 Apr 2018 12:06:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nA7fqlh+a3iMeyIJnfZFAc8UQ+O21lK3Bf0w3UPYpGI=; b=L40Bbn0JRCcCpiYdmlJdHCuXCdrjdhpTuoUu4LyVU0aSt9zyuyYewcAlkL5FmodW9R xgOEO4rPjt/z+gpa57ia6KV3b20/qRouBZgPNyrFU2VRV867TZHkLgFK0u/H597d4XDg 5OaHVKXBkk7TgG3LuONmIFqDFhOZVjtAW1WOOXzWxmLQ8qG+rWBwtE/Opa6QmTbcrwVW 8UBt6DkSlaN8PjO5eUB3iMCrshh6waebxuIsG3DKdOUngAD9Afb5jersCYoiIipTI9lG zXsaaeM+K0Vvtw+uroLcyEfuQnrtTUgmjLIVqWo2gkKhRUDCVgtx4A+OO1qNvyUUrRf9 CXUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nA7fqlh+a3iMeyIJnfZFAc8UQ+O21lK3Bf0w3UPYpGI=; b=GXFET+5xesoKwmxCU10s4rLRFIyMNiaB2i+j37sErTJvJfKSDO+iedTID/NtfXd00a 5vuIUAO2TPHzR366CtuudFQqIB0/3+xpEykTpMh5hP+n9X0un62KuBcous33yjDsX2Jy 0HLYvE2rq+CHiT6/bYCQsSCL2LKVBoV56/V8pqEe5q+qkrQjTU5ItPtGJwEx8DyUNHrn P3JrGnZHihi2EozLiTYE64z8vTKlrYA0fEq4pfGm1MpBInv+TlC7d+YScMlwssmvflL3 2Wzu10ofEEzJWEo0SGxNiGd51j3rzV6UIjPkRW9DD9cqfuUJhETUSzA7mEARBYz15XHl 5nDg==
X-Gm-Message-State: ALQs6tDiWFjESTzNg0BtGZbQ9NSFUfa8srp+7BftmsVdIzF5IYxVfSb5 JZ981jDU5YMget6onwaEBULbXKH9TKwuWObaw68=
X-Google-Smtp-Source: AB8JxZqeJxpPOKdqLOMuemBxexjWIHDUwjo6vHUEfm9Qv1Eof/pMFRldD1QifdhzM0amMMlPFfNIi8jUjDVlC+bnMlY=
X-Received: by 2002:a6b:a867:: with SMTP id r100-v6mr11621046ioe.143.1524251172283; Fri, 20 Apr 2018 12:06:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:a119:0:0:0:0:0 with HTTP; Fri, 20 Apr 2018 12:06:11 -0700 (PDT)
In-Reply-To: <CAGnRvup1CUQZ3QwKrVt-FOWkfkUiTpRbOPQQBZNRz1gqN2A8og@mail.gmail.com>
References: <CAGnRvupcyAKbR5mF8be_eKu5oKmAb-kW2xW19BJ7PHmPY_WQuA@mail.gmail.com> <1524222140.1526.7.camel@tropicalstormsoftware.com> <CAGnRvup1CUQZ3QwKrVt-FOWkfkUiTpRbOPQQBZNRz1gqN2A8og@mail.gmail.com>
From: Stan Ratliff <ratliffstan@gmail.com>
Date: Fri, 20 Apr 2018 15:06:11 -0400
Message-ID: <CALtoyonRfYH=RipL5LJLCfKzKcu-85jPdJo9wb5RWJRG1KeMDw@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: Rick Taylor <rick@tropicalstormsoftware.com>, "manet@ietf.org" <manet@ietf.org>, Teco Boot <teco@inf-net.nl>
Content-Type: multipart/alternative; boundary="000000000000ac4b22056a4c6193"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/y6o5l-6jSyWi2e-bdmlaB8gttRU>
Subject: Re: [manet] (DLEP) Relative Link Quality and routing metrics
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Apr 2018 19:06:15 -0000

Henning,


On Fri, Apr 20, 2018 at 7:05 AM, Henning Rogge <hrogge@gmail.com> wrote:

> Sorry,
>
> but this does not help...
>
> lets say I estimate the link cost for a link (based on data-rate) to be
> 1000...
>
> if the radio reports RLQ=100, I would keep the 1000... but how do I
> modify it for a RLQ of 80... or 50... or 1?
>

What we did at Cisco was to add to the route cost, based on how much RLQ
had dropped. A document on the route cost calculations (for OSPF) is at
https://www.cisco.com/c/en/us/td/docs/ios/12_4t/ip_mobility/configuration/guide/ip_manet.html
Look for Section "OSPF Cost Calculation for VMI Interfaces". You'll see we
used a hard-coded '65535' in the calcuations, IIRC, (it's been a few
years), that's the maximum OSPF route cost.

My guess is that this specific equation won't fit your needs, but it might
serve as a template for you.

Regards,
Stan



> If I cannot integrate the value into the cost metric, I have no use
> for the value. Unfortunately it is often the ONLY value the radio
> reports.
>
> Henning
>
> On Fri, Apr 20, 2018 at 1:02 PM, Rick Taylor
> <rick@tropicalstormsoftware.com> wrote:
> > I have always suggested that RLQ should be a measure of how hard the
> > modem is working to maintain the link, i.e. the higher the RLQ, the
> > more stable the link is, and a low RLQ indicates that the link may well
> > radically change metrics, or dissapear soon.
> >
> > One can imagine a sophisticated modem maintiaining a link in very
> > adverse conditions, reporting a low RLQ, but otherwise good metrics.
> >
> > Whether RLQ is a good metric to use as a route cost is a more difficult
> > question.  I've always been of the opinion that RLQ and Resources make
> > a good tie-breakers, but CDR and Latency make better 'primary' metrics.
> >
> > Hope that helps a little?
> >
> > Rick
> >
> > On Fri, 2018-04-20 at 10:00 +0200, Henning Rogge wrote:
> >> Hello,
> >>
> >> I am currently looking for a good way to integrate the RLQ value of
> >> DLEP into a cost based routing metric, e.g. DAT. But I am not sure
> >> how
> >> to do this...
> >>
> >> has anyone here good experience using RLQ and maybe an advise how
> >> "hard" you should penalize a link with a RLQ less than 100?
> >>
> >> Henning Rogge
> >>
> >> _______________________________________________
> >> manet mailing list
> >> manet@ietf.org
> >> https://www.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>