On 4/10/2013 11:56 AM, Lucy yong wrote: > I see. Two cases: 1) if the oracle is on NVE, the control plane > between the NVE and the oracle is just internal API. You will need > the control plane between the oracles. 2) if the oracle is not on > NVE, the control plane between the NVE and the oracle need some > protocols. You may still need the control plane between the oracles > if there are multiple.
I think you can pretty clearly keep a functional separation. The term that was current when VoIP was fresh and young was "decomposed," and in the interest of modularity it's not a bad idea to keep logically distinct components separate, even if they're in the same box. If nothing else, you don't want to force an implementation model on something that hasn't even been designed yet, really. Melinda _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
