Re: [RFC v2 00/14] Generic TCP-option framework and adoption for TCP-SMC and TCP-MD5

2018-02-02 Thread Christoph Paasch
Hello, On 01/02/18 - 10:15:46, David Miller wrote: > From: Christoph Paasch > Date: Wed, 31 Jan 2018 16:07:02 -0800 > > > TCP-options like TCP_MD5 and SMC are rather rare use-cases, but their > > implementation is rather intrusive to the TCP-stack. Other, more recent > > TCP extensions like TCP-

Re: [RFC v2 00/14] Generic TCP-option framework and adoption for TCP-SMC and TCP-MD5

2018-02-01 Thread David Miller
From: Christoph Paasch Date: Wed, 31 Jan 2018 16:07:02 -0800 > TCP-options like TCP_MD5 and SMC are rather rare use-cases, but their > implementation is rather intrusive to the TCP-stack. Other, more recent > TCP extensions like TCP-crypt, MPTCP or TCP-AO would make this situation > even worse.

[RFC v2 00/14] Generic TCP-option framework and adoption for TCP-SMC and TCP-MD5

2018-01-31 Thread Christoph Paasch
Resubmit as v2 RFC to get some feedback before net-next opens up again. Only minor changes (see below). This patchset introduces a generic framework for handling TCP-options. TCP-options like TCP_MD5 and SMC are rather rare use-cases, but their implementation is rather intrusive to the TCP-stack