| Message ID | 20230215134659.7613-1-andrea.mayer@uniroma2.it (mailing list archive) |
|---|---|
| Headers | show |
| Series | seg6: add PSP flavor support for SRv6 End behavior | expand |
Hello: This series was applied to netdev/net-next.git (master) by Paolo Abeni <pabeni@redhat.com>: On Wed, 15 Feb 2023 14:46:56 +0100 you wrote: > Segment Routing for IPv6 (SRv6 in short) [1] is the instantiation of the > Segment Routing (SR) [2] architecture on the IPv6 dataplane. > In SRv6, the segment identifiers (SID) are IPv6 addresses and the segment list > (SID List) is carried in the Segment Routing Header (SRH). A segment may be > bound to a specific packet processing operation called "behavior". The RFC8986 > [3] defines and standardizes the most common/relevant behaviors for network > operators, e.g., End, End.X and End.T and so on. > > [...] Here is the summary with links: - [net-next,1/3] seg6: factor out End lookup nexthop processing to a dedicated function https://git.kernel.org/netdev/net-next/c/525c65ff5696 - [net-next,2/3] seg6: add PSP flavor support for SRv6 End behavior https://git.kernel.org/netdev/net-next/c/bdf3c0b9c10b - [net-next,3/3] selftests: seg6: add selftest for PSP flavor in SRv6 End behavior https://git.kernel.org/netdev/net-next/c/5198cb408fcf You are awesome, thank you!
Segment Routing for IPv6 (SRv6 in short) [1] is the instantiation of the Segment Routing (SR) [2] architecture on the IPv6 dataplane. In SRv6, the segment identifiers (SID) are IPv6 addresses and the segment list (SID List) is carried in the Segment Routing Header (SRH). A segment may be bound to a specific packet processing operation called "behavior". The RFC8986 [3] defines and standardizes the most common/relevant behaviors for network operators, e.g., End, End.X and End.T and so on. The RFC8986 also introduces the "flavors" framework aiming to modify or extend the capabilities of SRv6 End, End.X and End.T behaviors. Specifically, these behaviors support the following flavors (either individually or in combinations): - Penultimate Segment Pop (PSP); - Ultimate Segment Pop (USP); - Ultimate Segment Decapsulation (USD). Such flavors enable an End/End.X/End.T behavior to pop the SRH on the penultimate/ultimate SR endpoint node listed in the SID List or to perform a full decapsulation. Currently, the Linux kernel supports a large subset of behaviors described in RFC8986, including the End, End.X and End.T. However, PSP, USP and USD flavors have not yet been implemented. In this patchset, we extend the SRv6 subsystem to implement the PSP flavor in the SRv6 End behavior. To accomplish this task, we leverage the flavor framework previously introduced by another patchset required for supporting the efficient representation of the SID List through the NEXT-C-SID mechanism [4]. In details, the patchset is made of: - patch 1/3: seg6: factor out End lookup nexthop processing to a dedicated function - patch 2/3: seg6: add PSP flavor support for SRv6 End behavior - patch 3/3: selftests: seg6: add selftest for PSP flavor in SRv6 End behavior From the user space perspective, we do not need to change the iproute2 code to support the PSP flavor. However, we provide the man page for the PSP flavor in a separate patch. Comments, improvements and suggestions are always appreciated. Thank you all, Andrea [1] - RFC8754: https://datatracker.ietf.org/doc/html/rfc8754 [2] - RFC8402: https://datatracker.ietf.org/doc/html/rfc8402 [3] - RFC8986: https://datatracker.ietf.org/doc/html/rfc8986 [4] - https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-srh-compression Andrea Mayer (3): seg6: factor out End lookup nexthop processing to a dedicated function seg6: add PSP flavor support for SRv6 End behavior selftests: seg6: add selftest for PSP flavor in SRv6 End behavior net/ipv6/seg6_local.c | 352 ++++++- tools/testing/selftests/net/Makefile | 1 + .../selftests/net/srv6_end_flavors_test.sh | 869 ++++++++++++++++++ 3 files changed, 1213 insertions(+), 9 deletions(-) create mode 100755 tools/testing/selftests/net/srv6_end_flavors_test.sh