netdev - Re: [RFC v2 PATCH 0/5] seg6: Segment routing fixes

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: <752a0680-a872-69d9-c67d-687d830e29da@gmail.com>
Date:   Sat, 8 Jun 2019 11:39:11 +0100
From:   David Lebrun <dav.lebrun@...il.com>
To:     Tom Herbert <tom@...bertland.com>, davem@...emloft.net,
        netdev@...r.kernel.org, dlebrun@...gle.com
Cc:     Tom Herbert <tom@...ntonium.net>
Subject: Re: [RFC v2 PATCH 0/5] seg6: Segment routing fixes

On 07/06/2019 19:55, Tom Herbert wrote:
> This patch set includes fixes to bring the segment routing
> implementation into conformance with the latest version of the
> draft (draft-ietf-6man-segment-routing-header-19). Also, segment
> routing receive function calls ip6_parse to properly parse TLVs
> in parsing loop.

Thanks for your patch set !

General comment regarding uapi changes: it might be wise to wait for RFC 
status in case the IESG or IANA decide different type/flags values.