| Message ID | 20211003184539.23629-1-justin.iurman@uliege.be (mailing list archive) |
|---|---|
| Headers | show |
| Series | Support for the ip6ip6 encapsulation of IOAM | expand |
Hello: This series was applied to netdev/net-next.git (refs/heads/master): On Sun, 3 Oct 2021 20:45:35 +0200 you wrote: > v2: > - add prerequisite patches > - keep uapi backwards compatible by adding two new attributes > - add more comments to document the ioam6_iptunnel uapi > > In the current implementation, IOAM can only be inserted directly (i.e., only > inside packets generated locally) by default, to be compliant with RFC8200. > > [...] Here is the summary with links: - [net-next,v2,1/4] ipv6: ioam: Distinguish input and output for hop-limit https://git.kernel.org/netdev/net-next/c/52d03786459a - [net-next,v2,2/4] ipv6: ioam: Prerequisite patch for ioam6_iptunnel https://git.kernel.org/netdev/net-next/c/7b34e449e05e - [net-next,v2,3/4] ipv6: ioam: Add support for the ip6ip6 encapsulation https://git.kernel.org/netdev/net-next/c/8cb3bf8bff3c - [net-next,v2,4/4] selftests: net: Test for the IOAM encapsulation with IPv6 https://git.kernel.org/netdev/net-next/c/bf77b1400a56 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
v2: - add prerequisite patches - keep uapi backwards compatible by adding two new attributes - add more comments to document the ioam6_iptunnel uapi In the current implementation, IOAM can only be inserted directly (i.e., only inside packets generated locally) by default, to be compliant with RFC8200. This patch adds support for in-transit packets and provides the ip6ip6 encapsulation of IOAM (RFC8200 compliant). Therefore, three ioam6 encap modes are defined: - inline: directly inserts IOAM inside packets (by default). - encap: ip6ip6 encapsulation of IOAM inside packets. - auto: either inline mode for packets generated locally or encap mode for in-transit packets. With current iproute2 implementation, it is configured this way: $ ip -6 r [...] encap ioam6 trace prealloc [...] The old syntax does not change (for backwards compatibility) and implicitly uses the inline mode. With the new syntax, an encap mode can be specified: (inline mode) $ ip -6 r [...] encap ioam6 mode inline trace prealloc [...] (encap mode) $ ip -6 r [...] encap ioam6 mode encap tundst fc00::2 trace prealloc [...] (auto mode) $ ip -6 r [...] encap ioam6 mode auto tundst fc00::2 trace prealloc [...] A tunnel destination address must be configured when using the encap mode or the auto mode. Justin Iurman (4): ipv6: ioam: Distinguish input and output for hop-limit ipv6: ioam: Prerequisite patch for ioam6_iptunnel ipv6: ioam: Add support for the ip6ip6 encapsulation selftests: net: Test for the IOAM encapsulation with IPv6 include/net/ioam6.h | 3 +- include/uapi/linux/ioam6_iptunnel.h | 29 +++ net/ipv6/Kconfig | 6 +- net/ipv6/exthdrs.c | 2 +- net/ipv6/ioam6.c | 11 +- net/ipv6/ioam6_iptunnel.c | 300 ++++++++++++++++++++------- tools/testing/selftests/net/ioam6.sh | 209 ++++++++++++++----- 7 files changed, 422 insertions(+), 138 deletions(-)