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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <495911022.108075672.1633005173034.JavaMail.zimbra@uliege.be>
Date:   Thu, 30 Sep 2021 14:32:53 +0200 (CEST)
From:   Justin Iurman <justin.iurman@...ege.be>
To:     David Ahern <dsahern@...il.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        yoshfuji@...ux-ipv6.org, dsahern@...nel.org
Subject: Re: [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of
 IOAM

>> 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.

Sure. The inline mode would be the default one when using the old syntax (i.e., without specifying a mode).