Hi, draft-narten-nvo3-overlay-problem-statement-02 / section 3.3 : > [...] routing protocols (e.g., IS-IS, BGP) may have scaling > difficulties if implemented directly in > all NVEs, based on both flooding and convergence time concerns. This > suggests that use of a standard lookup protocol between NVEs and a > smaller number of network nodes that implement the actual routing > protocol (or the directory-based "oracle") is a more promising > approach at larger scale.
I think that the text above really goes far beyond the scope a problem statement. > In summary, there are three areas of potential work. The first area > concerns the oracle itself and any on-the-wire protocols it needs. A > second area concerns the interaction between the oracle and NVEs. > The third work area concerns protocols associated with attaching and > detaching a VM from a particular virtual network instance. The > latter two items are the priority work areas and can be done largely > independent of any oracle-related work. I would infer from the above that the first work area, concerning protocols internal to the "oracle", would not be a priority. I think this is not a good idea. Indeed, redundancy, and very likely the ability to distribute the load, will be needed for the "oracle", not addressing the topic will lead to a situation where possibly you wouldn't have a standard to rely upon to do a real deployment. Moreover, it's not certain for me that the exchanges between the entities forming the "oracle" can be designed independently of the protocol used to query the oracle; at the very least it seems that the redundancy aspect will require describing how an NVE processes information from/to more than one "oracle" entity (ie. does it query all of them, only some of them) and this may depend a lot how the different entities forming the oracle will exchange mapping information internally. By and large I don't think we should downplay the importance of any of those three work areas. -Thomas _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
