Hello Stan,
Regarding the metric type discussion, I'll send a note about that soon.
I did address your scenario, but I will point out more explicitly
exactly how in a few minutes.
Regarding your points below...
- 24 bits of resolution 0.1 picosecond allows measurements from 10
Tbit/sec to under 1 Mbit/sec. But perhaps that's not enough. I will
revise it to have characteristic and mantissa fields, which will extend
the range greatly.
- LoopFree() is needed for AODVv2, and you are correct that for TDPB and
other additive monotonic metrics, "lower cost" ==> TRUE. That is a quick
consequence of the definition, and one of the reasons why additive
monotonic metrics are so much preferable. However, the formulation by
way of LoopFree() allows utilization of other kinds of metrics, even if
we don't know how to specify them right now.
Regards,
Charlie P.
On 10/1/2015 11:35 AM, Ratliff, Stanley wrote:
Charlie,
My comments (after an admittedly quick read):
- As for the unit of measurement being 0.1 picosecond; I didn't do the math to
see how it works out, but how does that play on optical links? It would be nice
if the metric spanned all link types; that way, it could potentially be folded
into IGPs like OSPF.
- I don't understand the usefulness of creating a LoopFree() function based on TDPB. The
pseudo-code doesn't look like "loop free"; it looks like "which of these paths is
lower cost?"
Regards,
Stan
-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Thursday, October 01, 2015 1:51 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Transmission Duration Per Bit (TDPB) Cost Metric
Hello folks,
Here's a way to pick routes with the best bandwidth using a cost metric. This
is relevant to some of our recent discussion.
I reckon I will submit it to [manet] soon, but I'd be very interested to get
your
comments.
Regards,
Charlie P.
_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________
