Linda, > If most TSes are only attached to a single NVE and traffic to NVEs > are not aggregated flows, then the NVE-NVE control plane protocol > doesnât provide much benefits.
I want to flag the first part of the sentence above because this question has been raised before. It suggests that a TS might connect to more than one NVE at a time. >From an architectural perpsective, I think we should say "no". Life is much simpler if a TS connects to a VN through exactly one NVE. More precisely, a TSI always connects to one NVE. If we allowed connections to multple NVEs simultaneously, it would raise all sorts of questions as to when to use one over the other, etc. I don't think I'm actually saying anything new with this... I've always assumed this, documents are written with this in mind, and it hasn't come up (other than in passing) on the list. A TS can still connect to multiple different VNs through different network interfaces, and hence different TSIs, but I think we should have a TSI always connect to exactly one NVE. Any other opinions? Thomas
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
