From: David Ahern <dsahern@gmail.com>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org
Subject: Re: [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM
Date: Wed, 29 Sep 2021 21:20:04 -0600 [thread overview]
Message-ID: <590592ba-0e79-b649-e03b-6b735a575fc3@gmail.com> (raw)
In-Reply-To: <20210928190328.24097-1-justin.iurman@uliege.be>
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.
>
next prev parent reply other threads:[~2021-09-30 3:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:03 [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM Justin Iurman
2021-09-28 19:03 ` [PATCH net-next 1/2] ipv6: ioam: Add support for the ip6ip6 encapsulation Justin Iurman
2021-09-30 3:26 ` David Ahern
2021-09-30 15:19 ` Justin Iurman
2021-09-30 18:20 ` David Ahern
2021-10-01 11:38 ` Justin Iurman
2021-10-01 14:06 ` David Ahern
2021-10-01 14:10 ` Justin Iurman
2021-09-28 19:03 ` [PATCH net-next 2/2] selftests: net: Test for the IOAM encapsulation with IPv6 Justin Iurman
2021-09-30 3:20 ` David Ahern [this message]
2021-09-30 12:32 ` [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM Justin Iurman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=590592ba-0e79-b649-e03b-6b735a575fc3@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).