Hi Eric. Gray <[email protected]> writes:
> Thomas, > > A couple of subtle points about this discussion: > > 1) if the intent is to document the architecture agreed to within > the NVO3 working group, it would be clearer if we cleaned up > the first paragraph in the Introduction so that it is > consistent with this goal. In particular, the first sentence > in the section indicates that the draft "presents a high-level > overview of a possible architecture" (which begs a question â > "have other possibilities been considered/addressed?"). Agreed, and I've removed it. > 2) if we want to ensure that we have an architecture likely to have > any long-term viability, we should use some care in making sure > that it doesn't break under some set of reasonable use-cases we > are discussing already. Agreed! > This said, I believe the fact that â even with extensive colocation > of NVA functionality â unless we contemplate requiring this, there > will be a need to define a standard way for one vendor's NVE to > conduct transactions with another vendor's NVA (and vice versa). I assume that when you say "colocation" you mean colocation of the NVE and NVA functionality on the same device, and specifically, an edge device that connects to a TS and does the NVE functions such as encap/decap. > So the thing we might want to ensure is that we do not impose any > unreasonable architectural restrictions that would preclude > solutions that rely on (or support) some arbitrary degree of > co-location of (for instance) NVE and NVA functionality. I think you are now actually getting into internal NVA design (something we haven't talked about much). If one wants to implement NVAs in a more distributed fashion, with more NVA functions co-located on the same edge device as the NVE, that is one design. But it seems to me that one of the design benefits of an NVA is that it doesn't need to have a component reside on every edge device housing an NVE. That would presumably have some scalability issues compared to a model where the NVA at a site can be implemented on a relatively small number of nodes, and certainly an order of magnitude fewer nodes than NVEs. Thomas
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
