Re: [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM

[David Ahern <dsahern@gmail.com>]

On 9/28/21 1:03 PM, Justin Iurman wrote:
> 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. Therefore, three explicit encap modes are defined:
> 
>  - inline: directly inserts IOAM inside packets.
> 
>  - 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 type 0x800000 ns 1 size 12 [...]
> 
> Now, an encap mode must be specified:
> 
> (inline mode)
> $ [...] encap ioam6 mode inline trace prealloc [...]

I take this to mean you want to change the CLI for ioam6? If so, that
does not happen once an iproute2 version has shipped with some previous
command line; it needs to be backwards compatible.

> 
> (encap mode)
> $ [...] encap ioam6 mode encap tundst fc00::2 trace prealloc [...]
> 
> (auto mode)
> $ [...] 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.
>