> If IP-based tunnels (e.g., MPLS-in-GRE or MPLS-in-UDP) are used between PE > routers, is there still any difference on applicability between these two VPN > technologies?
The mechanism and location of tunneling is not important. It is the type of service the solution can offer and what was intended in its initial design. There is a lot of difference when you look at the type of services ISP based VPNs offer and what LISP VPNs offer with all the other solutions LISP can offer along with VPNs. > >>> From the data plane perspective, given the fact that there is unprecedented >> enthusiasm for defining various data plane encapsulations (e.g., VXLAN, >> NVGRE, >> VXLAN-GPE, GUE-NVO, GENEVE...) , it seems no surprise to add two more (e.g., >> LISP and LISP-GPE). From the control plane perspective, as BGP could be used >> as >> a pull-based control plane as well due to its prefix-ORF mechanism, what's >> the >> major advantage of LISP over BGP? >> >> There have been many pros and cons using BGP as a push control-plane and >> LISP as a control-plane. At the high-level, I’ll state one difference. The >> LISP >> control plane (the mapping database nodes), are in less places in the network >> than BGP nodes. So that means less coordination and management. > > In the data center network environment, route reflectors could be run over > spine nodes or even servers. As such, these route reflectors could be looked > as mapping database nodes. Hence, from the coordination and management > perspectives, these two approaches seem almost the same, No? Yes, but the information is pushed. At some point any protocol and architecture can be changed, used, or misused to look like another. But what is important is how it was designed from the beginning. > Due to the new mobility requirements in 5G architecture (e.g., ultra-low >> latency), LISP-MN mobility may be a competitive candidate. >> >> Why do you say that? Compared to other solutions its better. Or some >> technical >> aspect? > > Compared to other HA-based mobile IP solution, I think id/locator split > solution looks better in the long run since it has the potential of > eliminating the path stretch issue. Right, agree. Dino > > Best regards, > Xiaohu _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
