[dev-disc] Re: device discovery BOF
CONGDON,PAUL (HP-Roseville,ex1)
paul.congdon at hp.com
Mon Jun 16 18:19:57 EDT 2003
Pedro is correct in identifying the overlap between IEEE 802.1AB and the
current DDP document with respect to the goals and problems that are to be
solved. We in the 802.1AB working group feel we are quite far along with
the document and have the extensibility built within the solution to offer
the IETF a vehicle for addressing presumed discovery needs. That said, it
would be prudent to share this information and explore ideas about how this
might be done (either as an IETF effort or by participating in the IEEE
effort). It is unclear if a BOF is the best forum for this, but it is clear
that we don't want to develop duplicate protocols solving the same needs.
In any case, I'd be happy to request time on the next IEEE agenda to discuss
the IETF needs for 802.1AB. The next IEEE meeting is scheduled for the week
of July 21st in San Francisco.
Paul
> -----Original Message-----
> From: Pedro Roque Marques [mailto:roque at juniper.net]
> Sent: Monday, June 16, 2003 11:15 AM
> To: Thomas Narten
> Cc: Erik Nordmark; device-discovery at puck.nether.net; dward at cisco.com
> Subject: [dev-disc] Re: device discovery BOF
>
>
> Thomas Narten writes:
>
> >> I would like to request a time slot for a BOF on device
> discovery on
> >> the upcoming IETF meeting.
>
> > What is the problem statement for this effort? That is,
> what problem
> > needs to be solved
>
> There are two distinct problems that are usually bundled in this area:
> - populating a topology MIB [RFC 2922]
> - discovery of adajcent devices without relying on correct L3
> configuration.
>
> Both the documents that i refered to bellow discuss the
> problem they are addressing.
>
> >> The purpose of this BOF is to evaluate the interest of the IETF
> >> community in solutions for detecting adjacent systems.
>
> >> Discussion of possible solutions would include: - DDP
> >> (draft-marques-ddp-00.txt) - LLDP (802.1ab)
>
> > It doesn't make sense to spend a lot of time on solutions until we
> > have a good handle on what the problem is that needs solving.
>
> I believe the industry has a good handle on the problem.
> Several vendors have their own solutions in this space which,
> to my knowledge, tend to address the requirements. The only
> concern is that these solutions are not, at the moment,
> publicly documented and interoperable.
>
> The IEEE 802.1ab effort, for instance, is trying to address
> this issue. The question is does the IETF want to participate
> and contribute to the process.
>
> > Also, who is on this list (i.e., how many subscribers?)
>
> ~ 20 people.
>
> > and where has it been advertised?
>
> It has not. Just word-of-mouth.
> Do you have suggestions on this domain ?
>
> thanks,
> Pedro.
> _______________________________________________
> device-discovery mailing list
> device-discovery at puck.nether.net
> http://puck.nether.net/mailman/listinfo/device> -discovery
>
More information about the device-discovery
mailing list