From: Martin Willi <martin@strongswan.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
Date: Wed, 08 Dec 2010 10:20:41 +0100 [thread overview]
Message-ID: <1291800041.2005.25.camel@martin> (raw)
In-Reply-To: <20101208084954.GA15252@gondor.apana.org.au>
> In particular, why would we need a boundary at all? Setting it to
> anything other than the PMTU would seem to defeat the purpose of
> TFC for packets between the boundary and the PMTU.
I don't agree, this highly depends on the traffic on the SA. For a
general purpose tunnel with TCP flows, PMTU padding is fine. But if
there are only small packets (maybe SIP+RTP), padding to the PMTU is
very expensive.
The administrator setting up the SAs probably knows (or even controls
directly) what traffic it is used for, and might lower the boundary
accordingly.
Regards
Martin
next prev parent reply other threads:[~2010-12-08 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 10:29 [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v2) Martin Willi
2010-12-07 10:29 ` [PATCH 1/3] xfrm: Add Traffic Flow Confidentiality padding XFRM attribute Martin Willi
2010-12-07 10:29 ` [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP Martin Willi
2010-12-08 8:49 ` Herbert Xu
2010-12-08 9:20 ` Martin Willi [this message]
2010-12-08 9:24 ` Herbert Xu
2010-12-07 10:29 ` [PATCH 3/3] xfrm: Traffic Flow Confidentiality for IPv6 ESP Martin Willi
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 14:37 [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3) Martin Willi
2010-12-08 14:37 ` [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP Martin Willi
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=1291800041.2005.25.camel@martin \
--to=martin@strongswan.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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).