From: Justin Iurman <justin.iurman@uliege.be>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
tom@herbertland.com
Subject: Re: [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated Trace with IPv6
Date: Mon, 31 May 2021 14:04:14 +0200 (CEST) [thread overview]
Message-ID: <1439349685.35359322.1622462654030.JavaMail.zimbra@uliege.be> (raw)
In-Reply-To: <cc16923b-74bc-7681-92c7-19e84a44c0e1@gmail.com>
>> Actually, February 2021 is the last update. The main draft
>> (draft-ietf-ippm-ioam-data) has already come a long way (version 12) and has
>> already been Submitted to IESG for Publication. I don't think it would hurt
>
> when the expected decision on publication?
Hard to tell precisely, a couple weeks probably. There are still some comment/discuss to clear and our next IETF working group meeting is in July. However, it shouldn't be a concern (see below).
> that much to have it in the kernel as we're talking about a stable
> draft (the other one is just a wrapper to define the encapsulation of
> IOAM with IPv6) and something useful. And, if you think about Segment
> Routing for IPv6, it was merged in the kernel when it was still a draft.
>
> The harm is if there are any changes to the uapi.
Definitely agree. But, I can assure you there won't be any uapi change at this stage. None of the comment/discuss I mentioned above are about this at all. Headers definition and IANA codes are defined for a long time now and won't change anymore.
next prev parent reply other threads:[~2021-05-31 12:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 15:16 [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated Trace with IPv6 Justin Iurman
2021-05-27 15:16 ` [PATCH net-next v4 1/5] uapi: IPv6 IOAM headers definition Justin Iurman
2021-05-27 15:16 ` [PATCH net-next v4 2/5] ipv6: ioam: Data plane support for Pre-allocated Trace Justin Iurman
2021-05-29 21:05 ` Jakub Kicinski
2021-05-30 10:36 ` Justin Iurman
2021-05-30 14:50 ` Justin Iurman
2021-05-30 20:05 ` Jakub Kicinski
2021-05-31 11:50 ` Justin Iurman
2021-06-01 4:20 ` Jakub Kicinski
2021-05-30 20:02 ` Jakub Kicinski
2021-05-31 11:43 ` Justin Iurman
2021-06-01 4:21 ` Jakub Kicinski
2021-05-27 15:16 ` [PATCH net-next v4 3/5] ipv6: ioam: IOAM Generic Netlink API Justin Iurman
2021-05-29 21:06 ` Jakub Kicinski
2021-05-30 11:18 ` Justin Iurman
2021-05-30 20:13 ` Jakub Kicinski
2021-05-27 15:16 ` [PATCH net-next v4 4/5] ipv6: ioam: Support for IOAM injection with lwtunnels Justin Iurman
2021-05-29 21:06 ` Jakub Kicinski
2021-05-30 10:48 ` Justin Iurman
2021-05-27 15:16 ` [PATCH net-next v4 5/5] ipv6: ioam: Documentation for new IOAM sysctls Justin Iurman
2021-05-29 15:58 ` [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated Trace with IPv6 David Ahern
2021-05-29 16:24 ` Justin Iurman
2021-05-31 1:24 ` David Ahern
2021-05-31 12:04 ` Justin Iurman [this message]
2021-06-03 3:31 ` David Ahern
2021-05-29 21:10 ` Jakub Kicinski
2021-05-30 10:49 ` 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=1439349685.35359322.1622462654030.JavaMail.zimbra@uliege.be \
--to=justin.iurman@uliege.be \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
/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).