Subject: [spring] draft-bashandy-isis-srv6-extensions-05

From: Rajesh M <[email-masked]>
Date: Fri, 17 May 2019 02:58:08 +0000

Hi All,

As per section 8 , END.DT4 can be  advertising using ISIS  (via END SID format).
At SRV6 egress router everything will work fine (Egress router we must configure which END.DT4 SID for which vrf table).

But at SRV6 ingress router how to decide which END.DT4 SID to use for which VRF ?
Again we need to configure IPV6 SID list per VRF @ingress side ?

I think its better to use BGP for END.DT4 signalling (draft-dawra-bess-srv6-services-00)

Thanks
Rajesh

Juniper Internal

---

From: Peter Psenak <[email-masked]>
Date: Fri, 17 May 2019 08:50:01 +0200

Rajesh,

The use case for END.DX and END.DT SIDs advertisement in IGPs is different.

The use case for these SIDs is when PLR does not support T.Insert and 
uses T-Encap to enforce the traffic over the computed backup path.

regards,
Peter

On 17/05/2019 04:58 , Rajesh M wrote:
> At SRV6 egress router everything will work fine (Egress router we must
> configure which END.DT4 SID for which vrf table).
>
>
>