From: "Thomas Switala" <tis@genotribe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] cRTP and RTP or other Header methods of headercompression
Date: Mon, 25 Aug 2003 07:51:27 +0000 [thread overview]
Message-ID: <marc-lartc-106180163606980@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106136314227258@msgid-missing>
Hi
IPSec with compression is a good idea, but it still add's AH/ESP packet
headers to the system that
I would like to avoid. And voice data is already compressed and no further
compression will happen.
We are limited to bandwidth usage and packet header compression was one of
the options that I am
looking at .
Thomas
----- Original Message -----
From: "Eric Leblond" <eric@regit.org>
To: <lartc@mailman.ds9a.nl>
Sent: Wednesday, August 20, 2003 9:43 AM
Subject: Re: [LARTC] cRTP and RTP or other Header methods of
headercompression
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-08-25 7:51 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 ` [LARTC] cRTP and RTP or other Header methods of header Eric Leblond
2003-08-25 7:51 ` Thomas Switala [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=marc-lartc-106180163606980@msgid-missing \
--to=tis@genotribe.com \
--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