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

Re: Simplifying IKE

To: andrew.krywaniuk@alcatel.com
Subject: Re: Simplifying IKE
From: Bill Sommerfeld <sommerfeld@East.Sun.COM>
Date: Tue, 14 Aug 2001 05:12:34 -0400
cc: "'Sandy Harris'" <sandy@storm.ca>, ipsec@lists.tislabs.com, dharkins@lounge.org, Joel.Snyder@Opus1.COM
In-reply-to: Your message of "Tue, 14 Aug 2001 09:36:08 BST." <000b01c1249c$752ac580$0109e982@andrewk3.ca.newbridge.com>
Reply-to: sommerfeld@East.Sun.COM
Sender: owner-ipsec@lists.tislabs.com

> Sorry, I meant "traffic analysis" in the more general sense of analyzing
> anything about the traffic flow, in this case specifically cryptanalysis of
> the data stream. 

most folks using the term "traffic analysis" seems to use it to mean
analysis of everything *except* the encryption..  i.e., looking at
message size, volume, origins, and miscellanous cleartext identifiers
(e.g., ip addresses and SPI's for IPsec).

> I originally did this in the ipsec-properties draft as well until
> someone pointed out that it was vague. Is there a well-defined term
> for this type of traffic analysis? "Data analysis"?

cryptanalysis?  ;-)

sounds like an active chosen-plaintext attack..

						- Bill

References:

RE: Simplifying IKE

From: "Andrew Krywaniuk" <andrew.krywaniuk@alcatel.com>

Prev by Date: Traffic handling and key management "divide and coquer"
Next by Date: having and eating cake? agressive mode with identity hiding
Prev by thread: RE: Simplifying IKE
Next by thread: RE: Simplifying IKE
Index(es):
- Main
- Thread