What follows has been made clear on the list for a while,
I am re-stating it.
The draft-ietf-spring-srv6-network-programming PSP behavior
strictly follows the letter of RFC 8200.
RFC8200 section 4 says:
Extension headers (except for the Hop-by-Hop Options header) are not
processed, inserted, or deleted by any node along a packet's delivery
path, until the packet reaches the node (or each of the set of nodes,
in the case of multicast) identified in the Destination Address field
of the IPv6 header.
The processing, insertion and deletion restrictions only apply
“until the packet reaches the node identified in the Destination
Address field of the IPv6 header”.
At the penuptimate segment of the segment list, the endpoint IS
“the node identified in the Destination Address field of the IPv6
header” and hence the PSP operation programmed by the source SR
node strictly follows the letter of RFC 8200.
Thanks,
Darren
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
