<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hey People,<br>
<br>
thank you for all your inputs.<br>
<font face="Helvetica, Arial, sans-serif"><br>
I've thought about all the inputs<font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif"> and I
spent some time looking at the <font face="Helvetica, Arial,
sans-serif">terminology used for "metrics", <font
face="Helvetica, Arial, sans-serif">"costs<font
face="Helvetica, Arial, sans-serif">" etc and I found
that these things are <font face="Helvetica, Arial,
sans-serif">very often referred as to "routing
metrics"<font face="Helvetica, Arial, sans-serif">.<br>
<br>
</font></font></font></font></font></font><font
face="Helvetica, Arial, sans-serif">So peraphs we <font
face="Helvetica, Arial, sans-serif">could call <font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif">it<font face="Helvetica, Arial,
sans-serif"></font></font></font> "<b>routing_metric</b>"<font
face="Helvetica, Arial, sans-serif"> and define it as the
name of main routing metric used by the routi<font
face="Helvetica, Arial, sans-serif">ng protocol to
determine the be<font face="Helvetica, Arial,
sans-serif">st ro<font face="Helvetica, Arial,
sans-serif">utes<font face="Helvetica, Arial,
sans-serif"> to take<font face="Helvetica, Arial,
sans-serif"> when sendin<font face="Helvetica,
Arial, sans-serif">g pac<font face="Helvetica,
Arial, sans-serif">kets</font></font></font></font></font>.<br>
<br>
<font face="Helvetica, Arial, sans-serif">While for "<b>cost</b>"
we intend <font face="Helvetica, Arial, sans-serif">the
value of the ro<font face="Helvetica, Arial,
sans-serif">uting metric, that can be positive
if it means that the lower the cost the better<font
face="Helvetica, Arial, sans-serif"> but it
can also be negat<font face="Helvetica, Arial,
sans-serif">ive</font> to indicate that a
higher cost <font face="Helvetica, Arial,
sans-serif">is better.</font></font></font></font></font><br>
</font></font></font></font></font><br>
<font face="Helvetica, Arial, sans-serif">If for version 0 we
support only one routing metric per JSON object<font
face="Helvetica, Arial, sans-serif"> (because getting right
a<font face="Helvetica, Arial, sans-serif"> multi<font
face="Helvetica, Arial, sans-serif"> metric <font
face="Helvetica, Arial, sans-serif">JSON structure</font></font></font>
for all the main routing protocols at the first atte<font
face="Helvetica, Arial, sans-serif">mpt</font></font></font>
<font face="Helvetica, Arial, sans-serif">is too much for <font
face="Helvetica, Arial, sans-serif">us right now), <font
face="Helvetica, Arial, sans-serif">it makes sense to
mention the routing metric name just once<font
face="Helvetica, Arial, sans-serif">:</font><br>
<br>
</font></font></font></font></font>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
{<br>
"routing_protocol": {<br>
"name": "olsr1",<br>
"routing_metric": "etx",<br>
"routes": [<br>
{<br>
"destination": "ID",<br>
"source": "ID",<br>
"next" : "ID",<br>
"device": "DEVICE",<br>
"cost": "VALUE"<br>
}<br>
]<br>
}<br>
}<font face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif"><font face="Helvetica,
Arial, sans-serif"><br>
<br>
<font face="Helvetica, Arial, sans-serif">What do you
think?</font><br>
<br>
<font face="Helvetica, Arial, sans-serif">Feel free to
propose better<font face="Helvetica, Arial, sans-serif">
definitions</font></font>!<br>
</font></font></font></font></font>
</body>
</html>