Les,

Your draft represents a view from only a single domian perspective and a
lot of wording there seems to imply that conflict resolution must be global
per router and does not depend on the  RIB/FIB context.

Perhaps you are not considering identical SIDs to be used for example by
L3VPN customers connecting to SP network with BGP or OSPF and wishing to
use SR within their sites.

Is this accidental or on purpose ?

Can't customers connecting to a given network's different RIBs (via VRFs)
use the same SIDs as other customers or for that matter SP itself ? Nothing
breaks if they do - as their forwarding is hidden under the SP forwarding,
but I see no place in your document to relax conflict resolution in those
deployments.

Same for CSC.

Thx,
R.


On Sun, May 1, 2016 at 7:10 AM, Les Ginsberg (ginsberg) <[email protected]>
wrote:

> Uma –
>
>
>
> We are indeed defining conflict resolution across all the SID
> advertisements regardless of source (protocol or SRMS) – as the sections
> you have quoted clearly state.
>
>
>
> Why? Because we need consistent use of SIDs in the forwarding plane. From
> forwarding perspective it matters not whether the SID was advertised by
> protocol instance #1 or #2 or by an SRMS. What matters is that the SID I
> use to determine what label I install in my forwarding plane is the same
> SID that my neighbors will use. Otherwise forwarding will be broken.
>
>
>
>    Les
>
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to