Subject: Re: [spring]
https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services
For my understanding, draft-ietf-bess-srv6-services describes this (ch 6):
" When providing best-effort connectivity to the egress PE, the ingress
PE encapsulates the payload in an outer IPv6 header wher
For my understanding, draft-ietf-bess-srv6-services describes this (ch 6):
" When providing best-effort connectivity to the egress PE, the ingress
PE encapsulates the payload in an outer IPv6 header where the
destination address is the SRv6 Service SID associated with the
related BGP ro
Hi Rajesh,
I am afraid you are mixing layers :)
VRF services can be mapped to any color for transport and that color does
not need to be subject to PHP. Flexible Algorithm are layer below services
and are just about transport in the set of closed domains.
If you look at
https://datatracker.ietf
Thanks Ketan,
My query is
If we allocate SRv6 Service SID per-VRF
Let's assume For this VRF locator assigned is 2001:129:1:13::
DT4 SID is-2001:129:1:13::4
DT6 SID is - 2001:129:1:13::6
a) Now how to support Different flex algo for different routes with in a VRF ?
For VRF1 Prefix 10.129.0.0 I w
Hi Rajesh,
The FlexAlgo for SRv6 is described in
https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo/ and that would
require different SRv6 Locators for the FlexAlgo. When the SRv6 Service SID is
allocated from the SRv6 Locator for a FlexAlgo then the service flow will be
forwarded along
Hi All,
As per draft
"When providing best-effort connectivity to the egress PE, the ingress
PE encapsulates the payload in an outer IPv6 header where the
destination address is the SRv6 Service SID associated with the
related BGP route update."
If we allocate SRv6 Service SID per-VRF then how to
