Hi Acee, On 8/3/15, 4:11 PM, "Acee Lindem (acee)" <[email protected]> wrote:
>Hi Pushpasis, > >On 8/3/15, 6:13 AM, "spring on behalf of Pushpasis Sarkar" ><[email protected] on behalf of [email protected]> wrote: > >>Hi Les, >> >>On 8/1/15, 4:56 AM, "Les Ginsberg (ginsberg)" <[email protected]> wrote: >> >>>What is more problematic is supporting multiple labels for the same >>>prefix - which is one of the consequences of the per-protocol SRGB >>>approach. I am not saying this is unsupportable - just that it is a more >>>difficult problem to solve. >>[Pushpasis] If we can support multiple protocol routes (each providing an >>IP next hop) per IP prefix, I don¹t see why there should be problem >>supporting multiple protocol routes (each providing a labeled next hop) >>for the same IP prefix. > >In the simple next-hop case, only the most preferred protocol (lowest >admin distance or precedence) route will be installed in the data plane. [Pushpasis] You are right as long the route we are talking is the IP/V6 prefix applicable on the ingress which encapsulates an incoming IP/V6 packet into the MPLS packet. What we are saying is that all routers participating in SR with multiple protcols (whenever there is at all a need) can setup parallel MPLS data planes and the ingress can inject the incoming IP/V6 packets into a MPLS data plane of their choice indicated by the protocol preference. >If I understand correctly, in this case the most preferred protocol would >install the NHLFE and a cross-connect. Additionally, other less preferred >protocols would install additional cross-connects using different labels. >Correct? [Pushpasis] Yes that is correct for a given ingress router. However if the protocol preference is different on different ingress routers (which might be the case in migration scenarios) they are pushed in using different MPLS labels. > > >Thanks, >Acee > > >> >>Thanks >>-Pushpasis >>> >> >>_______________________________________________ >>spring mailing list >>[email protected] >>https://www.ietf.org/mailman/listinfo/spring > _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
