Hello John,
There are several ways to do it, but from my point of view it is usually
easier to understand if the quantity of interest can be expressed as a
cost metric. I mentioned earlier how to do this with bandwidth, but
very briefly one can formulate a cost metric by massaging the reciprocal
of the bandwidth. If you and others are interested, I'll write more
details tomorrow. Right now it's past time for sleep.
Regards,
Charlie P.
On 9/27/2015 2:31 PM, John Dowdell wrote:
Charlie
On 24 Sep 2015, at 21:48, Charlie Perkins <charles.perkins@xxxxxxxxxxxxx> wrote:Bandwidth is a metric (along with latency, both of which are declared as
Hello John,
Follow-up below...
Bandwidth is not a cost metric. The calculation of LoopFree() might be more
complicated. I don't like non-cost metrics for various reasons. One reason is
that they contradict the entire mathematical formulation for metrics and metric
spaces. On the other hand, some people in the IETF don't have much respect
for mathematics, it seems, and I get tired of complaining about it.
Regards,
Charlie P.
metrics in DLEP). You can use it to influence routing decisions, but I’ll
agree that it doesn’t work to completely drive a route selection in the way
that hop count does. I believe it is also impossible to calculate LoopFree()
just using bandwidth, so maybe you’d have to use a combination of hop count and
bandwidth, but that is a discussion for another draft.
Regards
John
