Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[Shraddha Hegde <[e-mail]>]

Hi Authors,

There is a possibility of a usecase that wants to use flex-algo paths if available and if flex-algo paths
Are not available use best effort paths.


"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.  Therefore, the ingress PE SHOULD perform
   resolvability check for the SRv6 Service SID before considering the
   received prefix for the BGP best path computation.
"

The current text says for best effort tunnels Srv6 service SID resolution SHOULD be checked and
I am told that (from previous mailing list exchanges) authors intend to update the text to make it applicable for flex-algo connectivity  as well.

It is not possible to support fallback on best effort tunnels if flex-algo SRv6 service SIDs have to be resolved.
It is possible to support fallback to best effort in SRv6 if packets can be tunneled to egress PE  (destination address being PE's best effort END SID and service SID in the SRH)and
then do a service SID lookup on egress, in which case there is no need to resolve the SRv6 service SIDs on the ingress.

It is not clear whether the authors intend to support these kind of tunnelling to egress cases for
Best effort and flex-algo transport. If it not going to be supported, pls add text indicating clearly
Tunnelling is not required to be supported and hence Fallback to best effort  is also not supported.

If that is not the intention, Its reasonable to update the text to indicate SRv6 service SIDs need not be resolved
If the ingress is tunneling the packet.

Rgds
Shraddha


Juniper Business Use Only
From: spring <[e-mail]> On Behalf Of Aissaoui, Mustapha (Nokia - CA/Ottawa)
Sent: Monday, July 19, 2021 7:34 PM
To: Rabadan, Jorge (Nokia - US/Mountain View) <[e-mail]>; Rajesh M <[e-mail]>; Rajesh M <mrajesh=[e-mail]>; Ketan Talaulikar (ketant) <[e-mail]>; [e-mail]; Clarence Filsfils (cfilsfil) <[e-mail]>; [e-mail]; [e-mail]
Cc: [e-mail]; [e-mail]; Srihari Sangli <[e-mail]>; [e-mail]; Shraddha Hegde <[e-mail]>
Subject: Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Rajesh,
Also you can change the service SID for a subset of prefixes using a policy, to apply a flex-algo for example, but you do not want to change the next-hop for each new service SID.

Mustapha.

From: spring <[e-mail]<mailto:[e-mail]>> On Behalf Of Rabadan, Jorge (Nokia - US/Mountain View)
Sent: Monday, July 19, 2021 9:47 AM
To: Rajesh M <[e-mail]<mailto:[e-mail]>>; Rajesh M <mrajesh=[e-mail]<mailto:mrajesh=[e-mail]>>; Ketan Talaulikar (ketant) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Clarence Filsfils (cfilsfil) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Srihari Sangli <[e-mail]<mailto:[e-mail]>>; Shraddha Hegde <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

Hi Rajesh,

The draft is written so that the next-hop address MAY be covered by the locator, but there are cases in which the next-hop address is not part of the locator prefix, and there are implementations already allowing that, so I don't agree the document should mandate what you are suggesting.

Thanks.
Jorge

From: Rajesh M <[e-mail]<mailto:[e-mail]>>
Date: Monday, July 19, 2021 at 3:24 PM
To: Rajesh M <mrajesh=[e-mail]<mailto:mrajesh=[e-mail]>>, Ketan Talaulikar (ketant) <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, Clarence Filsfils (cfilsfil) <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, Rabadan, Jorge (Nokia - US/Mountain View) <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, Shraddha Hegde <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, Srihari Sangli <[e-mail]<mailto:[e-mail]>>
Subject: RE: SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)
Hi Authors,

Please respond.

Thanks
Rajesh



Juniper Business Use Only
From: spring <[e-mail]<mailto:[e-mail]>> On Behalf Of Rajesh M
Sent: Thursday, July 15, 2021 4:36 PM
To: Ketan Talaulikar (ketant) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Clarence Filsfils (cfilsfil) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Shraddha Hegde <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: [spring] SRv6 BGP based Overlay Services (draft-ietf-bess-srv6-services-07)

[External Email. Be cautious of content]

Hi All,

As per this draft, this is how resolution must work.

1)For Non Intent service Route:
if BGP next hop is not reachable return.
Resolve SRv6 Service SID for forwarding.

2)For Intent service Route (IGP Flex-Algo first then BGP CAR then SR Policy):
BGP next hop is not reachable return.
Resolve SRv6 Service SID for forwarding(To find IGP flex algo).if successfully resolves then return.
Resolve BGP next hop for forwarding (in case above is not success).


Using Service SID (overlay),for resolution is definitely not recommended.

Instead in case of srv6, we always resolve on BGP nexthop. This will be in line with BGP legacy.
In case of best effort/flex algo we must mandate user to set corresponding locator as BGP nexthop for srv6 routes.
I think this is a reasonable mandate.

Thanks
Rajesh


Juniper Business Use Only