DRAGON

[gdt]

Started to look at the DRAGON code. A bit disappointing that they haven't ported from Zebra to Quagga, and I'm wondering if this suggests deeper changes.

When it's time to set up the switch path some RSVP-TE commands are send to the virtual label switch router. The VLSR is a proxy, converting RSVP path establishment into a set of commands for each ethernet switch. DRAGON supports Movaz, Force10 E300 and E600, Raptor E1010. The vendor-dependent magic happens in dragon-sw/kom-rsvp/src/daemon/unix/SwitchCtrl_Session_*.cc.

These files consist of hooks called by a very ethernet-oriented API. It's not clear to me if there is a higher-level API which might be used by the ethernet-oriented API. Let's hope so, I don't particularly want to munge VLANs into SDH paths.

CANARIE has a TL1 proxyi which they use for their UCLP service. Must find out more about that from Rene Hatem. I'd like a proxy to protect the statically-assigned SDH paths from errors by the DRAGON GMPLS path establishment. Asking Google suggests the MonFox TL1 proxy. Perl has a TL1 module, and that might allow simple filtering (which I think is all we actually need).