netdev - Re: [PATCH net-next 6/6] seg6: Add support to rearrange SRH for AH ICV calculation

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: <20190531160535.519fdef1067aa9d681669d29@gmail.com>
Date:   Fri, 31 May 2019 16:05:35 +0200
From:   Ahmed Abdelsalam <ahabdels.dev@...il.com>
To:     Tom Herbert <tom@...bertland.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, dlebrun@...gle.com,
        Tom Herbert <tom@...ntonium.net>
Subject: Re: [PATCH net-next 6/6] seg6: Add support to rearrange SRH for AH
 ICV calculation

On Thu, 30 May 2019 14:50:21 -0700
Tom Herbert <tom@...bertland.com> wrote:

> Mutable fields related to segment routing are: destination address,
> segments left, and modifiable TLVs (those whose high order bit is set).
> 
> Add support to rearrange a segment routing (type 4) routing header to
> handle these mutability requirements. This is described in
> draft-herbert-ipv6-srh-ah-00.
> 

Hi Tom, David,
I think it is very early to have such implementation in the mainline of the Linux kernel.
The draft (draft-herbert-ipv6-srh-ah-00) has been submitted to IETF draft couple of days ago. 
We should give the IETF community the time to review and reach a consensus on this draft.
Thanks, 
Ahmed

-- 
Ahmed Abdelsalam <ahabdels.dev@...il.com>