<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/27/2015 01:47 PM, Henning Rogge
wrote:<br>
</div>
<blockquote
cite="mid:CAGnRvuqESYr_Ra92EqSoF94wA_v-4dOzykDQk7O2uVFj3SWQjg@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Aug 27, 2015 at 1:20 PM, Nemesis <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:nemesis@ninux.org"><nemesis@ninux.org></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Hey Bastian,
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>On 08/27/2015 12:41 PM, Bastian Bittorf wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>> </span>see <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/interop-dev/netjson/issues/22">https://github.com/interop-dev/netjson/issues/22</a>
<span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>add 'link: type' or 'link: media'
<span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>e.g. wired / wireless / tunnel or even more special:
<span class="moz-txt-citetags">>> </span>'10baseT-HD' or
<span class="moz-txt-citetags">>> </span>'802.11a/n' or
<span class="moz-txt-citetags">>> </span>'bluetooth' or
<span class="moz-txt-citetags">>> </span>'zigbee' or
<span class="moz-txt-citetags">>> </span>'tuntap'
<span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>any comments about that?
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>would be interesting, we also have something like this in nodeshot and I
<span class="moz-txt-citetags">> </span>guess other node-db have similar information too.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Not sure if the routing protocols can know this information though, so
<span class="moz-txt-citetags">> </span>it could be an optional attribute.
</pre>
</blockquote>
<pre wrap="">This sounds more like an "interface" parameter than a "link" parameter
and should be part of the DeviceConfiguration object.</pre>
</blockquote>
<br>
<font face="Helvetica, Arial, sans-serif">Exactly, DeviceC<font
face="Helvetica, Arial, sans-serif">onfiguration <font
face="Helvetica, Arial, sans-serif">has interfaces and
interfaces at the moment have a type attribute.<br>
<br>
<font face="Helvetica, Arial, sans-serif">Although I think
Bastian's request will come up again in the future<font
face="Helvetica, Arial, sans-serif">, it<font
face="Helvetica, Arial, sans-serif"> will be a common
feature request <font face="Helvetica, Arial,
sans-serif">I guess, but it's ok<font face="Helvetica,
Arial, sans-serif">, we <font face="Helvetica,
Arial, sans-serif">don't have to find all the
answers <font face="Helvetica, Arial, sans-serif">right
now, t<font face="Helvetica, Arial, sans-serif">his
<font face="Helvetica, Arial, sans-serif">has
a </font>lower pri<font face="Helvetica,
Arial, sans-serif">or<font face="Helvetica,
Arial, sans-serif">ity than <font
face="Helvetica, Arial, sans-serif">getting
the core objects right</font></font>.<br>
<br>
<font face="Helvetica, Arial, sans-serif"><font
face="Helvetica, Arial, sans-serif">@B<font
face="Helvetica, Arial, sans-serif">astian<font
face="Helvetica, Arial, sans-serif">:
<font face="Helvetica, Arial,
sans-serif">I think you understood
the concept but <font
face="Helvetica, Arial,
sans-serif">I'll repeat it
anyway f<font face="Helvetica,
Arial, sans-serif">or readers
of this list</font>, NetJSON
allows <font face="Helvetica,
Arial, sans-serif">inserting
custom properties<font
face="Helvetica, Arial,
sans-serif">, if you add <font
face="Helvetica, Arial,
sans-serif">key/values in
the "properties" object of
each node/link,
netjsongraph.js will <font
face="Helvetica, Arial,
sans-serif">display them
automatically, but an
implementer might also
add a custom "type"
property on the same
level as "source" and
"target", and use that
to add a <font
face="Helvetica,
Arial, sans-serif">CSS
class on links and
style the class with
CSS<font
face="Helvetica,
Arial, sans-serif">.<br>
<font
face="Helvetica,
Arial, sans-serif">This
way we can let
everybody do
interesting
experiments, and
if some practices
get widely adop<font
face="Helvetica,
Arial,
sans-serif">ted
we can<font
face="Helvetica,
Arial,
sans-serif"> d<font
face="Helvetica,
Arial,
sans-serif">ecide
to standardize
them.</font></font></font></font><br>
<br>
<font
face="Helvetica,
Arial, sans-serif">Federico</font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
</body>
</html>