Re: [manet-dlep-rg] Latency

"Stan Ratliff (sratliff)" <sratliff@cisco.com> Tue, 12 November 2013 15:24 UTC

Return-Path: <sratliff@cisco.com>
X-Original-To: manet-dlep-rg@ietfa.amsl.com
Delivered-To: manet-dlep-rg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C35221E8133 for <manet-dlep-rg@ietfa.amsl.com>; Tue, 12 Nov 2013 07:24:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.563
X-Spam-Level:
X-Spam-Status: No, score=-10.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUX0I4P2MPQD for <manet-dlep-rg@ietfa.amsl.com>; Tue, 12 Nov 2013 07:24:53 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA5121E813F for <manet-dlep-rg@ietf.org>; Tue, 12 Nov 2013 07:24:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4026; q=dns/txt; s=iport; t=1384269893; x=1385479493; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LuWB95AXUnvJFvPoQDeooNg5n2WJ/QvUgVmrBu0h050=; b=QijD2w8+8ClZ3SFsgyymk8NrbWja19xkRpDFs5tWtJkY9HHVBC2QFnZZ MY7ZHrBBVCcFkM0sEAWahWB9J7SitnJ/M+C2fxgpcocYOGSBhyLswzjuj rhJ2eDblh4zJHEzjzFM8hIbKKNVAZJL7fHPjOwhMeGeGHFETg9+Env3xC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFACxHglKtJV2b/2dsb2JhbABZgwc4U78dgScWdIIlAQEBAwEBAQFSGQsFBwQCAQgRBAEBAScHJwsUCQgCBA4Fh3sGDb5mjiAGgQYIKwcCBIMagREDmA+SCoMmgWgJFyI
X-IronPort-AV: E=Sophos;i="4.93,685,1378857600"; d="scan'208";a="283743402"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 12 Nov 2013 15:24:53 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rACFOqcS032572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 15:24:52 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.200]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 09:24:52 -0600
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: "Taylor, Rick" <Rick.Taylor@cassidian.com>
Thread-Topic: [manet-dlep-rg] Latency
Thread-Index: AQHO36pFXYfOk1EbKU2oVOZb7avOP5ohmANAgACD5oA=
Date: Tue, 12 Nov 2013 15:24:51 +0000
Message-ID: <7A32FF9C-066B-438B-B3D1-CD73562823F4@cisco.com>
References: <72FB622921C13746AD6349E70A8D9F307D9192F7@EXC-MBX03.tsn.tno.nl> <CAK=bVC85XAXR3Zkwq+JwELF-dvgrKwbowWCvwvnjeVn7VStnbw@mail.gmail.com> <72FB622921C13746AD6349E70A8D9F307D9193CD@EXC-MBX03.tsn.tno.nl> <5A8A5085482DA84995F4E70F5093AB50268E6C@XCH-BLV-503.nw.nos.boeing.com> <B2BA430A-F4E6-4DED-A7BB-7282A22802B7@inf-net.nl> <D02397F1-9D1B-4B36-81D0-4585ACDBA34A@gmail.com> <5D184300-2D97-4EC1-8D91-76D4A79B2BDA@inf-net.nl> <DDAE98C5-520E-4F8F-9F9B-2AB9A15A70EF@cisco.com> <032D6BF0-5B60-489D-8BC5-9634BEDDBC9F@inf-net.nl> <aa4dd517-7f86-4caf-8a1c-298cf8200c06@SUCNPTEXC01.COM.AD.UK.DS.CORP> <B177F831FB91F242972D0C35F6A0733106FB04EB@SUCNPTEXM01.com.ad.uk.ds.corp>
In-Reply-To: <B177F831FB91F242972D0C35F6A0733106FB04EB@SUCNPTEXM01.com.ad.uk.ds.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.41.107]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E46744521CF0EC4E85EE3C80D132B68B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Henning Rogge <hrogge@googlemail.com>, "DLEP Research Group (manet-dlep-rg@ietf.org)" <manet-dlep-rg@ietf.org>
Subject: Re: [manet-dlep-rg] Latency
X-BeenThere: manet-dlep-rg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DLEP Radio Group <manet-dlep-rg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet-dlep-rg>
List-Post: <mailto:manet-dlep-rg@ietf.org>
List-Help: <mailto:manet-dlep-rg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet-dlep-rg>, <mailto:manet-dlep-rg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 15:24:58 -0000

The radios I've worked with report latency as a "rolling average", in ms, for queueing time + transmission. The total amount of time used for the rolling average is left to the radio implementation. 

Yes, multi-hop mesh radios confuse the issue. Ideally, I'd like to see "END-TO-END queueing time + transmission time", but some approximation thereof might work. I would contend that it's the modem's job to do the approximating (e.g. the modem provides "latency", *not* "Here's a hop count, and some multiplier for that hop count, go knock your lights out…"

Regards,
Stan

On Nov 12, 2013, at 8:43 AM, "Taylor, Rick" <Rick.Taylor@cassidian.com> wrote:

> From my experience:
> 
> My test DLEP devices just make up a number (not very helpful)
> 
> The radios I have used that support DLEP-00 natively report a latency in ms.  What that really is I have no idea.  Again, not very useful.
> 
> I have my own DLEP proxy for some other radios, and I have just reported half of RTT on my control packets, which given I have jitter and back-off, again isn't very useful.
> 
> BUT, Having a latency metric, even if it is almost meaningless, is better than no metric at all.
> 
> I could suggest 100ms * hop-count works in mesh radios, as one of the simplest uses of latency is as an improved hopcount for split-horizoning in routing protocols.
> 
> It's amazing what one will try to use, even if the quality of the data is very poor!
> 
> Rick Taylor
> 
>> -----Original Message-----
>> From: manet-dlep-rg-bounces@ietf.org [mailto:manet-dlep-rg-
>> bounces@ietf.org] On Behalf Of Henning Rogge
>> Sent: 12 November 2013 13:23
>> To: Teco Boot
>> Cc: DLEP Research Group (manet-dlep-rg@ietf.org); Stan Ratliff
>> Subject: Re: [manet-dlep-rg] Latency
>> 
>> Yes, I heard this too in the MANET Meeting...
>> 
>> which made me wonder a bit because I was puzzled what was the
>> difference between the two.
>> 
>> Can maybe the people who already have an implementation for DLEP tell
>> us what kind of Latency they implemented?
>> 
>> Henning Rogge
>> 
>> On Mon, Nov 11, 2013 at 5:15 PM, Teco Boot <teco@inf-net.nl> wrote:
>>> 
>>> Op 11 nov. 2013, om 01:55 heeft Stan Ratliff (sratliff)
>> <sratliff@cisco.com> het volgende geschreven:
>>> 
>>>> Point 11 - I didn't hear that. Really, I didn't hear any conclusions
>> about Latency. Other opinions?
>>> 
>>> We discussed it and all speakers said it is an important metric, so it
>> will be an optional TLV in core document.
>>> 
>>> Wasn't Henning tasked with verifying Latency and EFT?
>>> 
>>> Teco
>>> 
>>> _______________________________________________
>>> manet-dlep-rg mailing list
>>> manet-dlep-rg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet-dlep-rg
>> 
>> 
>> 
>> --
>> We began as wanderers, and we are wanderers still. We have lingered
>> long enough on the shores of the cosmic ocean. We are ready at last to
>> set sail for the stars - Carl Sagan
>> _______________________________________________
>> manet-dlep-rg mailing list
>> manet-dlep-rg@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet-dlep-rg
> The information contained within this e-mail and any files attached to this e-mail is private and in addition may include commercially sensitive information. The contents of this e-mail are for the intended recipient only and therefore if you wish to disclose the information contained within this e-mail or attached files, please contact the sender prior to any such disclosure. If you are not the intended recipient, any disclosure, copying or distribution is prohibited. Please also contact the sender and inform them of the error and delete the e-mail, including any attached files from your system. Cassidian Limited, Registered Office : Quadrant House, Celtic Springs, Coedkernew, Newport, NP10 8FZ Company No: 04191036 http://www.cassidian.com