<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hey Mario,<br>
<br>
On 08/11/2015 01:15 PM, Mario Behling wrote:<br>
</div>
<blockquote
cite="mid:CALaXfOXqNM8adPnzoYzv4BXJBN6Ni7FYtbuTnBznzAr_=Upxcg@mail.gmail.com"
type="cite">
<pre wrap="">Thanks for following up on this point. What is your personal idea?
What other fields might be unclearly defined?
</pre>
</blockquote>
<br>
Ok, I'll answer below with what I remember.<br>
<br>
<blockquote
cite="mid:CALaXfOXqNM8adPnzoYzv4BXJBN6Ni7FYtbuTnBznzAr_=Upxcg@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, Aug 11, 2015 at 1:10 PM, Nemesis <a class="moz-txt-link-rfc2396E" href="mailto:nemesis@ninux.org"><nemesis@ninux.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi everybody,
following the previous discussion on the interop-dev ML:
<a class="moz-txt-link-freetext" href="https://lists.funkfeuer.at/pipermail/interop-dev/2015-July/000482.html">https://lists.funkfeuer.at/pipermail/interop-dev/2015-July/000482.html</a> and
at the battlemesh, we need to clarify what an ID is and make sure that is
compatible with all the routing protocols.
So here's 3 questions:
Github issue: <a class="moz-txt-link-freetext" href="https://github.com/interop-dev/netjson/issues/19">https://github.com/interop-dev/netjson/issues/19</a>
make clear what an ID is (eg: can it be also a non-address, like a hash?)</pre>
</blockquote>
</blockquote>
<br>
an ID is the way a router/node is identified in "NetworkRoutes" and
"NetworkGraph", it can be any string.<br>
Feel free to propose a better definition.<br>
<br>
<blockquote
cite="mid:CALaXfOXqNM8adPnzoYzv4BXJBN6Ni7FYtbuTnBznzAr_=Upxcg@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">you use the concept of ID also for routes but you expect addresses, please
clarify</pre>
</blockquote>
</blockquote>
<br>
Probably routes in NetworkRoutes should expect addresses only and
avoid confusion with router IDs,<br>
<br>
In NetworkGraph instead, source and target should probably allow the
usage of router IDs. <br>
<br>
<blockquote
cite="mid:CALaXfOXqNM8adPnzoYzv4BXJBN6Ni7FYtbuTnBznzAr_=Upxcg@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">which attributes do refer to IDs in NetworkGraph and NetworkRoutes
</pre>
</blockquote>
</blockquote>
<br>
In NetworkRoutes:<br>
<ul>
<li>router_id</li>
</ul>
<p>In NetworkGraph:<br>
</p>
<ul>
<li>router_id</li>
<li>source<br>
</li>
<li>target</li>
</ul>
<p>Federico<br>
</p>
</body>
</html>