<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/30/2014 10:19 AM, Henning Rogge
wrote:<br>
</div>
<blockquote
cite="mid:CAGnRvurk9kuw_dg+UA=wRL3nGQAU70j136t-6dGQc2UBrs3XoA@mail.gmail.com"
type="cite">
<pre wrap="">Just define a routing-protocol with the well-known name "static". This
makes it very easy to parse the routes of multiple protocols including
static routes. No special case for static routes required. The "cost"
of the static routes is the only thing that could be a bit tricky.</pre>
</blockquote>
<br>
<font face="Helvetica, Arial, sans-serif">You mean we could putt all
the routes in the <font face="Helvetica, Arial, sans-serif">"routing_protocols"
sections?<br>
<br>
<font face="Helvetica, Arial, sans-serif">If yes I was thinking,
peraphs we could rename "routing_<font face="Helvetica, Arial,
sans-serif">protocols<font face="Helvetica, Arial,
sans-serif">" to "routes"</font></font></font> and we
could use a list of <font face="Helvetica, Arial, sans-serif">NetworkRoutes<font
face="Helvetica, Arial, sans-serif"> objects as defined in<font
face="Helvetica, Arial, sans-serif">:
<a class="moz-txt-link-freetext" href="https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json">https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json</a><br>
<br>
<font face="Helvetica, Arial, sans-serif">In which <font
face="Helvetica, Arial, sans-serif">sense you mean</font>
"cost"</font> for static routes is tricky? Tricky to
determine? Doesn't have much sense?<br>
<br>
<font face="Helvetica, Arial, sans-serif">Federico</font><br>
</font></font></font></font></font>
</body>
</html>