I had discussed this with Kyriakos a while ago and did a bit of digging to see if I could find a TLV that looked like the ideal place for the DPID, but didn't find anything that looked perfect. After letting this slide for quite a while, I decided today to just do SOMETHING about it. I wasn't actually aware that people had made attempts to resolve this that hadn't actually made it into NOX until this thread.
Rob and Nick, the System Description TLV seems like both overkill and misuse as well to me. It seems to be designed for advisory type information for humans. Do you include the "full name and version identification of the system's hardware type, software operating system, and networking software"? Do we WANT to do that? Srini's patch used the "network" chassis subtype, which also seems like misuse, as it is intended to be "and octet string that identifies a particular network address family and an associated network address" (using the IANA Address Family Numbers, for which "DPID" does not have an entry!). I was kind of trying to avoid it, but maybe we should actually Do The Right Thing here and use the Organizationally Specific TLV. If we ask nicely, maybe we can use Nicira's OUI? Martin? -- Murphy On Mon, 2010-11-15 at 23:45 -0500, Nicholas Bastin wrote: > On Mon, Nov 15, 2010 at 21:55, James "Murphy" McCauley > <jam...@nau.edu> wrote: > I notice that the chassis ID TLV also has a "local" subtype. > According > to 802.1AB-2005 (which isn't the current version), this is "an > alpha-numeric string and is locally assigned". Can we just > stuff the > DPID in there as a string? Maybe prepend "dpid:" to weed out > anything > else that may use it and to look nice for other tools? > > > There's no real reason to overload the chassis ID TLV like this since > we really do still need the MAC subtype (if we're going to do things > that other devices understand anyhow), we might as well construct a > real LLDP packet (like FlowVisor does, which Rob S. already covered) - > you need to add other TLVs anyhow to make it conform to the spec > (Chassis ID, Port ID, and TTL are required). I believe in FV we use > a System Description TLV (type 6) and drop the DPID in as the > payload. > > > -- > Nick _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
