netdev - Re: [PATCH net-next v2] net: ipv6: support Application-aware IPv6 Network (APN6)

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]

Date:   Wed, 22 Apr 2020 05:34:09 -0700
From:   Dave Taht <dave.taht@...il.com>
To:     "Jianwei Mao (Mao)" <mao-linux@...jianwei.com>
Cc:     netdev <netdev@...r.kernel.org>, davem <davem@...emloft.net>,
        kuznet <kuznet@....inr.ac.ru>,
        yoshfuji <yoshfuji@...ux-ipv6.org>, kuba <kuba@...nel.org>,
        lkp <lkp@...el.com>
Subject: Re: [PATCH net-next v2] net: ipv6: support Application-aware IPv6
 Network (APN6)

as near as I can tell, this is not even an accepted working group item
in ietf 6man. (?). Normally I welcome running code long before rough
consensus, but in this case I would be inclined to wait. There also
seems to be some somewhat conflicting ideas in spring and oam that
need working out.

It would be good to have an example implementation that could actually
parse and "do smart things" with this additional header, e.g a tc
filter, ebpf, etc. It has the same flaws diffserv has always had in
that any application can set these fields arbitrarily, with the
additional flaw of changing the mtu if these headers are added or
modified en-route.