netdev - Re: [RFC PATCH 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: <20190531190704.07285053cb9a1d193f7b061d@gmail.com>
Date:   Fri, 31 May 2019 19:07:04 +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: [RFC PATCH 6/6] seg6: Add support to rearrange SRH for AH ICV
 calculation

On Fri, 31 May 2019 09:48:40 -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, 
Assuming that IETF process needs to be fixed, then, IMO, should not be on the cost of breaking the kernel process here. 
Let us add to the kernel things that have been reviewed and reached some consensus.
For new features that still need to be reviewed we can have them outside the kernel tree for community to use. 
This way the community does not get blocked by IETF process but also keep the kernel tree stable.
Thanks,
Ahmed

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