From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: mathias.krause@secunet.com, netdev@vger.kernel.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH net-next 0/2] Removal of struct esp_data
Date: Tue, 29 Oct 2013 13:11:05 +0100 [thread overview]
Message-ID: <20131029121105.GF31491@secunet.com> (raw)
In-Reply-To: <20131023.154002.1833051243694861649.davem@davemloft.net>
On Wed, Oct 23, 2013 at 03:40:02PM -0400, David Miller wrote:
> From: Steffen Klassert <steffen.klassert@secunet.com>
> Date: Wed, 23 Oct 2013 10:07:16 +0200
>
> > Well, I thought to either take this as a reminder to implement the
> > missing stuff or to take the removing patches if this is really obsolete.
> > I'll do one of both once I'm back from conference week in Edinburgh.
>
> Sounds like a good plan, thanks.
RFC 4303 recommends to use TFC padding instead of the padding field:
'As noted above, the Padding field is limited to 255 bytes in length.
This generally will not be adequate to hide traffic characteristics
relative to traffic flow confidentiality requirements. An optional
field, within the payload data, is provided specifically to address
the TFC requirement.'
So looks like we can remove the padlen field, both patches
applied to ipsec-next. Thanks Mathias!
prev parent reply other threads:[~2013-10-29 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 10:09 [PATCH net-next 0/2] Removal of struct esp_data Mathias Krause
2013-10-18 10:09 ` [PATCH net-next 1/2] net: esp{4,6}: remove padlen from " Mathias Krause
2013-10-18 10:09 ` [PATCH net-next 2/2] net: esp{4,6}: get rid of " Mathias Krause
2013-10-18 17:55 ` [PATCH net-next 0/2] Removal " David Miller
2013-10-22 13:08 ` Steffen Klassert
2013-10-22 18:05 ` David Miller
2013-10-23 8:07 ` Steffen Klassert
2013-10-23 19:40 ` David Miller
2013-10-29 12:11 ` Steffen Klassert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131029121105.GF31491@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=mathias.krause@secunet.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).