Thomas,<br>
<br>
<br>
Pedro and others have been working on an IETF draft to standardize a
device discovery protocol. The main reason for this effort is to
provide information about a directly connected neighbor in a
multi-vendor environment. This feature is useful in managing, deploying
and troubleshooting large numbers of network devices. Both an IEEE and
IETF effort have been started to accomplish the same thing. The BOF
should be used to refine the goals of the IETF effort and to see if the
two standards bodies efforts can compliment each other. <br>
<br>
Thanks,<br>
<br>
Ted L.<br>
<br>
<span type="cite">Thomas Narten wrote:</span>
<p> </p>
<blockquote type="cite" > <tt>
> I would like to request a time slot for a BOF on device discovery
on <br>
> the upcoming IETF meeting. <br>
<br>
What is the problem statement for this effort? That is, what problem <br>
needs to be solved <br>
<br>
> The purpose of this BOF is to evaluate the interest of the IETF <br>
> community in solutions for detecting adjacent systems. <br>
<br>
> Discussion of possible solutions would include: <br>
> - DDP (draft-marques-ddp-00.txt) <br>
> - LLDP (802.1ab) <br>
<br>
It doesn't make sense to spend a lot of time on solutions until we <br>
have a good handle on what the problem is that needs solving. <br>
<br>
Also, who is on this list (i.e., how many subscribers?) and where has <br>
it been advertised? I'd like to see discussion on this list that <br>
justifies the need for a BOF prior to going forward with one. And I <br>
think we need to have a collective idea of what problem needs solving. <br>
<br>
Thomas <br>
_______________________________________________ <br>
device-discovery mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:device-discovery@puck.nether.net">device-discovery@puck.nether.net</a> <br>
<a href="http://puck.nether.net/mailman/listinfo/device-discovery">http://puck.nether.net/mailman/listinfo/device-discovery</a> <br>
<br>
</tt> </blockquote>