Reframing the question:
* Does the draft(oam/network programming) talk about supporting OAM functionality for END/END.X sids with USP/PSP flag set? * If it does, can you please point out to the relevant portion? Why isn't it explicitly stated like it is for USD and other END.D* Sids? Juniper Business Use Only From: Rajesh M <[email protected]> Sent: Monday, September 14, 2020 4:54 PM To: Zafar Ali (zali) <[email protected]>; Ketan Talaulikar (ketant) <[email protected]>; Pablo Camarillo (pcamaril) <[email protected]> Cc: G. Sri Karthik Goud <[email protected]>; SPRING WG <[email protected]>; Deepti Rathi <[email protected]> Subject: RE: SRV6 OAM (USP SID) Please respond. Juniper Business Use Only From: spring <[email protected]<mailto:[email protected]>> On Behalf Of Rajesh M Sent: Monday, September 14, 2020 3:06 PM To: Zafar Ali (zali) <[email protected]<mailto:[email protected]>>; Ketan Talaulikar (ketant) <[email protected]<mailto:[email protected]>>; Pablo Camarillo (pcamaril) <[email protected]<mailto:[email protected]>> Cc: G. Sri Karthik Goud <[email protected]<mailto:[email protected]>>; SPRING WG <[email protected]<mailto:[email protected]>>; Deepti Rathi <[email protected]<mailto:[email protected]>> Subject: [spring] SRV6 OAM (USP SID) [External Email. Be cautious of content] When ingress pings a USP SID, at the egress below code is executed. 4.16.2<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-18*section-4.16.2__;Iw!!NEt6yMaO-gk!UT4dirKx2wi2cm4xC2Xe7EpNCxBtMb0Mu-IVKyBHraSsbA0csQIVsPIh1bky1485$>. USP: Ultimate Segment Pop of the SRH The SRH processing of the End, End.X and End.T behaviors are modified: the instructions S02-S04 are substituted by the following ones: S02. If (Segments Left == 0) { S03.1. Update the Next Header field in the preceding header to the Next Header value of the SRH S03.2. Decrease the IPv6 header Payload Length by the Hdr Ext Len value of the SRH S03.3. Remove the SRH from the IPv6 extension header chain S03.4. Proceed to process the next header in the packet S04. } May be we should explicitly state here "if next header is Upper layer header then execute section 4.1.1" Juniper Business Use Only
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
