Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

[Rajesh M <[e-mail]>]

WANG had given below use case : But using existing PSP logic this will not work.
In below at PSP router updated SL will be 1 (since END.DT4 is still there) ,so SRH pop won't happen.



   S14.1.   If (updated SL == 0) {

   S14.2.      Pop the SRH

   S14.3.   }

WANG use case:
"For example in SRv6-based L3VPN service scenario, The ingress PE within SRv6-enabled domain can utilize SR-TE policy to enable TE-path function when encapsulating and transiting L3VPN traffic, The Ingress PE push on customer packets with SID list representing SR-TE policy plus END.DT4 as last SRv6 SID in SRH; So I think, each flavor of PSP/USP/USD can be designed to perform in related SRv6 endpoint. Imaging the PSP, the penultimate Endpoint can perform PSP, e.g. copy the last SID (END.DT4) of SRH to destination field of IPv6 header and POP the SRH, then forwarding it toward egress PE identified by DA"







Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <[e-mail]>
Sent: Tuesday, October 15, 2019 10:13 PM
To: Rajesh M <[e-mail]>; SPRING WG List <[e-mail]>
Cc: Srihari Sangli <[e-mail]>; Shraddha Hegde <[e-mail]>
Subject: Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

Rajesh,

This has already been replied less than one week ago. Please see:
https://mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c__;!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7HGIr9o9$>
https://mailarchive.ietf.org/arch/msg/spring/WrYzRZC0HKVgBYaYMCQVcTWrfak<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/WrYzRZC0HKVgBYaYMCQVcTWrfak__;!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7P8QaU_7$>

Thanks,
Pablo.


From: spring <[e-mail]<mailto:[e-mail]>> on behalf of Rajesh M <mrajesh=[e-mail]<mailto:mrajesh=[e-mail]>>
Date: Friday, 11 October 2019 at 03:47
To: SPRING WG List <[e-mail]<mailto:[e-mail]>>
Cc: Srihari Sangli <[e-mail]<mailto:[e-mail]>>, Shraddha Hegde <[e-mail]<mailto:[e-mail]>>
Subject: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24


Wanted to know the use case where we only POP the SRH ?

4.16.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04*section-4.16.1__;Iw!8WoA6RjC81c!W8zXtokq31cYlPoLJ6Ip-BlyXApb7JIhuJzRXW3khd_OAByxCvaxs9Jw7DAv5v98$>.  PSP: Penultimate Segment Pop of the SRH

   The SRH processing of the End, End.X and End.T behaviors are

   modified: after the instruction "S14.  Update IPv6 DA with Segment

   List[Segments Left]" is executed, the following instructions must be

   executed as well:



   S14.1.   If (updated SL == 0) {

   S14.2.      Pop the SRH

   S14.3.   }



Juniper Business Use Only