[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Stream Cipher Transform -- revisited

To: John Gilmore <gnu@toad.com>
Subject: Re: Stream Cipher Transform -- revisited
From: "C. Harald Koch" <chk@border.com>
Date: Wed, 31 Jul 1996 10:51:15 -0400
Cc: Germano Caronni <caronni@tik.ee.ethz.ch>, ipsec@TIS.COM, skip-info@tik.ee.ethz.ch, markson@incog.com, dpalma@netcom.com, Project SKIP <skip@tik.ee.ethz.ch>, Burkhard Stiller <stiller@tik.ee.ethz.ch>, Bernhard Plattner <plattner@tik.ee.ethz.ch>
In-Reply-To: gnu's message of "Wed, 31 Jul 1996 05:13:40 -0400". <199607310913.CAA23906@toad.com>
Organization: Border Network Technologies Inc.
Phone: +1 416 368 7157
References: <199607310913.CAA23906@toad.com>
Sender: ipsec-approval@neptune.tis.com

In message <199607310913.CAA23906@toad.com>, John Gilmore writes:
> I advise against making *any* design decision that trades off security
> or privacy for MIPS

Agreed, with an explanation. :-)

There are two points on the performance curve worth considering; slow
hardware is one, but high-speed/high-volume data streams are another. Take
a real-time, broadcast-quality, full-motion M-JPEG stream, for example...

I fully support continuing development for supporting stream ciphers within
IPsec. However, to agree somewhat with John, these should be *optional*
transforms.

-- 
C. Harald Koch          | Border Network Technologies Inc.
chk@border.com          | Senior System Developer
+1 416 368 7157 (voice) | 20 Toronto Street, Suite 400, Toronto ON M5C 2B8
+1 416 368 7789 (fax)   | Madness takes its toll. Please have exact change.

References:

Re: Stream Cipher Transform -- revisited

From: John Gilmore <gnu@toad.com>

Prev by Date: Re: Stream Cipher Transform -- revisited
Next by Date: Question on TCP MSS with repsect to IPSEC
Prev by thread: Re: Stream Cipher Transform -- revisited
Next by thread: Re: Authentication using ESP in Transport Mode
Index(es):
- Main
- Thread