> Casn you expand a bit. It is not obvious to me that either IoT or Mobile > Node needs multicast support from LISP for its LISP usage.
On IoT or mobile node may want to send multicast packets. Those multicast packets need to get to receivers. The receivers may be at LISP sites. > For example, people keep talking about multicast video, but in fact we know > that is a corner case and become even less common. If you want to support other transports and you want to stretch L2 subnets, then ARP and IPv6 link-local multicast will need to be supported. That means the overlay needs to transport multicast packets. > Data Center clearly needs some multicast. I can see some argument for VPN. Right. And a node in a VPN site can be anywhere. > Since SDN is simply a way of deploying other things, multicast in VPN > contexts clearly depends upon what problem you are using SDN to solve. SDN, in my mind is a network management mechanism. When we talk about the LISP architecture and protocols, we are talking about in-network control-plane mechanisms (and I mean between nodes in the network in a distributed fashion). Dino > > Yours, > Joel > > On 8/10/15 6:42 PM, Dino Farinacci wrote: >>> - LISP VPN (including integration with IPsec) >>> - NVO3 use case for DC virtualization (including support for VM mobility) >>> - SDN/NFV (including support for service chaining) >>> - IoT (LISP as connecting infrastructure for IoT applications) >>> - Mobile Node (LISP-MN mobility) >> >> And I would say all these use-cases must support multicast packets and >> packets that traverse through NATs. Those are not separate use-cases but >> baselines that each use-case needs to support. >> >> Dino >> > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
