Hi Lucy, Proposed solution works within a VPN context. It is not a general design at this point.
I am actually looking what would be the optimal encoding to address the VPN case particulary RFC7024 optimality as well as possibly to also allow for other applications. Enforcing to request host address will not work as PEs do not carry host routes for VPNs .... at least those which are properly configured :) Site addresses are advertised in blocks. Of course if site consists of single tenant VM that would be host address - but this is rather special case for one solution space. To your point of sending to "wrong PE" I do not really see that. At most it may be suboptimal PE for some duration of time ... not wrong one. And the case will self-cure when more specific get's advertised anyway. Best regards, R. On Mon, Nov 11, 2013 at 8:00 AM, Lucy yong <[email protected]> wrote: > When requesting covering prefix, it has the chance that a prefix may apply to > more than on VPN site in the environment of VM mobility. If we just request a > host or a set of host addresses, and give the rule that only PEs that has the > host route replies the request. This may address the issue, isn't it? > Otherwise, due to the response time difference, the ingress PE may send the > packet to the wrong PE, isn't it? But if PE does not have host address > visibility, this will not work. > > IMO: We need a solution to work w/ or w/o RR. > > Lucy > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Robert Raszuk > Sent: Saturday, November 09, 2013 12:51 AM > To: Xuxiaohu > Cc: [email protected]; [email protected] > Subject: Re: ??: [lisp] Prefix overlapping issue for > draft-bonica-l3vpn-orf-covering-prefixes-00 > > Hi Xiaohu, > > Prefix overlap within VPN is either on purpose injected into given VPN or is > due to VPN misconfiguration. > > Detection or mitigation of this as far as I can see is outside of scope of > this draft. > > LISP operates in global space, this draft operates in VPN space. Those spaces > while seemingly similar in reality have very different routing > characteristics. > > Best, > R. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
