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: <cc16923b-74bc-7681-92c7-19e84a44c0e1@gmail.com>
Date:   Sun, 30 May 2021 19:24:07 -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/29/21 10:24 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?

 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.