Hi Alia,
--szb On Oct 2, 2014, at 10:47 AM, Alia Atlas <[email protected]<mailto:[email protected]>> wrote: Hi Fabio, On Thu, Oct 2, 2014 at 1:40 PM, Fabio Maino <[email protected]<mailto:[email protected]>> wrote: Alia, what's the rationale of adding LISP to the last sentence? Is it expected that LISP extensions for DC will happen in the LISP WG, as with BGP? Yes, there is a WG for LISP and work, if and when in charter, should happen there. This is really about being clear on the solution for NVO3 - which is focused on an orchestration approach for the NVA. Does "orchestration" imply that all address to tunnel mappings must be pre-pushed everywhere. This will make it hard to use NVO3 for north-south traffic reaching a datacenter. Too many addresses which can end up on any NVA. If orchestration will also allow for pull of mapping information then it will be good to incorporate the Lisp mechanisms and capabilities in this area. There may be multiple ways of having a DC VPN - but NVO3 needs to focus on just that one. Getting focus and agreement will be challenging enough. Thanks for raising the question. Regards, Alia Thanks, Fabio On 10/2/14, 10:02 AM, Alia Atlas wrote: The NVO3 recharter is now going to external review. The version approved has a couple minor changes or clarifications. Do take a look at: http://datatracker.ietf.org/doc/charter-ietf-nvo3/ Thanks, Alia _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ lisp mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
