From: David Ahern <dsahern@gmail.com>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: davem@davemloft.net, dsahern@kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next v2 0/2] Support for IOAM encap modes
Date: Sat, 9 Oct 2021 17:39:20 -0600 [thread overview]
Message-ID: <d920c307-a04f-4fc1-0d57-cf6c2a60ecfb@gmail.com> (raw)
In-Reply-To: <20211005151020.32533-1-justin.iurman@uliege.be>
On 10/5/21 9:10 AM, Justin Iurman wrote:
> v2:
> - Fix the size of ioam6_mode_types (thanks David Ahern)
> - Remove uapi diff from patch #1 (already merged inside iproute2-next)
>
> Following the series applied to net-next (see [1]), here are the corresponding
> changes to iproute2.
>
> 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.
>
> [1] https://lore.kernel.org/netdev/163335001045.30570.12527451523558030753.git-patchwork-notify@kernel.org/T/#m3b428d4142ee3a414ec803466c211dfdec6e0c09
>
applied to iproute2-next. Thanks,
next prev parent reply other threads:[~2021-10-09 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:10 [PATCH iproute2-next v2 0/2] Support for IOAM encap modes Justin Iurman
2021-10-05 15:10 ` [PATCH iproute2-next v2 1/2] Add support " Justin Iurman
2021-10-05 15:10 ` [PATCH iproute2-next v2 2/2] Update documentation Justin Iurman
2021-10-09 23:39 ` David Ahern [this message]
2021-10-09 23:40 ` [PATCH iproute2-next v2 0/2] Support for IOAM encap modes patchwork-bot+netdevbpf
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=d920c307-a04f-4fc1-0d57-cf6c2a60ecfb@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).