Dino, what you write make sense, but let me invite the WG to discuss more on the first _IF_ of your logic: “if NVO3 …".
As I pointed out in another mail, we need more discussion on what we are going to support. We cannot write a charter that states “LISP will support NVO3 use-cases”. L. > On 16 Aug 2015, at 00:03, [email protected] wrote: > > The logic follows like this: > > If NVo3 is a requirement for the recharter, then L2 overlay support is > required. If L2 overlay support is required, then you must stretch subnets. > If you stretch subnets, broadcast frame support is required. If broadcast > frame support is needed, then multicast support on the overlay is needed. > > And if L2 overlays are going to be supported in cloud environments, homenet, > or in containers, then NAT-traversal support is required. > > Dino > > On Aug 14, 2015, at 9:18 AM, Damien Saucez <[email protected] > <mailto:[email protected]>> wrote: > >> Hello, >> >> I understand that multicast and nat traversal are potentially required in >> all use cases, but the "must support" sounds extreme to me. Are they >> hypothetical requirements or real demand from the market targeted by LISP, >> new version ? >> >> Damien Saucez >> >> On 12 Aug 2015, at 19:44, Stig Venaas <[email protected] >> <mailto:[email protected]>> wrote: >> >>> >>> On Aug 12, 2015 10:22 AM, "Dino Farinacci" <[email protected] >>> <mailto:[email protected]>> wrote: >>> > >>> > Yes, where but multicast sources as well as multicast receivers are >>> > moving. There are severl military applications for this use-case. >>> >>> Agree >>> >>> Stig >>> >>> > >>> > Dino >>> > >>> > > On Aug 12, 2015, at 10:20 AM, Stig Venaas <[email protected] >>> > > <mailto:[email protected]>> wrote: >>> > > >>> > > I agree we need to consider multicast. There are people that want to do >>> > > multicast over LISP. Some are already doing it. This also includes >>> > > mobility. >>> > > >>> > > Stig >>> > >>> _______________________________________________ >>> lisp mailing list >>> [email protected] <mailto:[email protected]> >>> https://www.ietf.org/mailman/listinfo/lisp >>> <https://www.ietf.org/mailman/listinfo/lisp> > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
