netdev - Re: [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated Trace with IPv6

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: <1439349685.35359322.1622462654030.JavaMail.zimbra@uliege.be>
Date:   Mon, 31 May 2021 14:04:14 +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,
        tom@...bertland.com
Subject: Re: [PATCH net-next v4 0/5] Support for the IOAM Pre-allocated
 Trace with IPv6

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