<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/21/2014 11:20 AM, Ralf
Schlatterbeck wrote:<br>
</div>
<blockquote cite="mid:20141121102050.GB17362@runtux.com" type="cite">
<pre wrap="">On Thu, Nov 20, 2014 at 11:10:50PM +0100, Henning Rogge wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
The number of metrics doesn't matter if you don't know which one is
good and which one is bad.
What would do with the metric field? Except for "displaying it on
screen without knowing what it is".
</pre>
</blockquote>
<pre wrap="">
I'm with Henning here: We need to know if the metric is "good" or "bad".
Still naming it "cost" and using negative values if some metric choses
to measure benefit instead of cost looks nice to me (although
implementers of protocols with benefit metrics may have a different view
here :-)
</pre>
</blockquote>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
So, if using the positive/negative flip, would this be ok:<br>
<br>
{<br>
destination: "<id>",<br>
next: "<id>",<br>
source: "<id>",<br>
device: "<device>",<br>
metric: "<metric value>",<br>
metric_type: "<name of algorithm>"<br>
}<br>
<br>
Or you still prefer:<br>
<br>
{<br>
destination: "<id>",<br>
next: "<id>",<br>
source: "<id>",<br>
device: "<device>",<br>
cost: "<metric value>",<br>
cost_type: "<name of algorithm>"<br>
}<br>
<br>
Notice I removed "routing_table" to keep it simple.<br>
We don't have to have everything from version 0, we could gradually
add what we think is needed. <br>
<br>
Federico<br>
</body>
</html>