Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cRTP and RTP or other Header methods of header
Date: Wed, 20 Aug 2003 07:43:15 +0000	[thread overview]
Message-ID: <marc-lartc-106136549329213@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106136314227258@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 288 bytes --]

On Wed, 2003-08-20 at 09:02, Thomas Switala wrote:
> Hi
> dwidth saving. Is there any other method
> that you guys recommend that I have
> a look at.

IPsec with compress turned on ? In most cases you can gain some
bandwidth.

BR,
-- 
Eric Leblond <eric@regit.org>
Regit.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-20  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20  7:02 [LARTC] cRTP and RTP or other Header methods of header compression Thomas Switala
2003-08-20  7:43 ` Eric Leblond [this message]
2003-08-25  7:51 ` [LARTC] cRTP and RTP or other Header methods of headercompression Thomas Switala

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=marc-lartc-106136549329213@msgid-missing \
    --to=eric@regit.org \
    --cc=lartc@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