> -----Original Message----- > From: Sean Hefty [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 21, 2007 1:51 PM > To: Yaron Haviv > Cc: Hal Rosenstock; Michael Krause; [email protected] > Subject: Re: [ofa-general] [RFC] host stack IB-to-IB router support > > > Ok, lets assume Sean would finish his experiments with remote_sa, how > > would that find its way into the commercial sm/sa versions that are > > mostly used, how would we guarantee interoperability between all > > implementations, .. ? > > How would that address future routing, security, QoS, .. enhancements ? > > can it ? > > The 'remote sa' as simply a proprietary UD protocol. Whatever data two > 'remote > sa' services exchange shouldn't matter, nor should the fact that each > issues > local SA path records. There's nothing magical about this. > > If I have an app that can query its local SA, there's nothing that > prevents that > app from sending that data to whatever peer it can connect to. It can > even send > the data over TCP if it wants. Keeping the SA subnet local doesn't add > any real > security. > > Coming up with a solution that doesn't work with any existing hardware, > targets, > and SAs isn't very useful. > > - Sean
Sean, If we are doing experiments, wouldn't it be simpler to do in the IP way I suggested: If its not my subnet read the DGID from a table (or even a config for now) And conduct SA query on that one On the remote side, add the reverse lookup rather than use the CM REQ SLID It sounds to me less work and less complexity Yaron _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
