[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e619169e-adfe-4b77-b359-6378c83b3ce3@gmail.com>
Date: Wed, 2 Jun 2021 21:31:48 -0600
From: David Ahern <dsahern@...il.com>
To: Justin Iurman <justin.iurman@...ege.be>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
tom@...bertland.com
Subject: Re: [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated Trace
with IPv6
On 5/31/21 6:04 AM, Justin Iurman wrote:
>>> 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).\
Ok.
>
>> 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.
>
Please add tests to tools/testing/selftests/net to cover the
functionality added.
Powered by blists - more mailing lists