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

ports in the clear...

To: Ran Atkinson <rja@cisco.com>
Subject: ports in the clear...
From: Greg Minshall <minshall@ipsilon.com>
Date: Mon, 22 Apr 1996 15:43:04 -0700
Cc: ipsec@TIS.COM
In-Reply-To: Your message of "Mon, 22 Apr 1996 14:42:29 PDT." <199604222142.OAA00456@puli.cisco.com>
Sender: ipsec-approval@neptune.tis.com

> It is not clear to me that it is feasible to prevent traffic analysis
> anywhere above the link layer.  Folks really interested in this might want
> to consult [VK85] for relevant background material.

Did i mention my desire to expose the source and destination TCP/UDP ports 
(via some new fields in the IPSEC header) when doing encryption?

There are lots of reasons, from bean counting ("what % of the internet traffic 
is web traffic?") to firewalls to "best effort QoS" (make telnet port low 
latency; make ftp data port high throughput).

Greg

Follow-Ups:

ports in the clear...

From: Tatu Ylonen <ylo@ssh.fi>

Re: ports in the clear...

From: "Perry E. Metzger" <perry@piermont.com>

References:

Re: Routing Header info of IPng against traffic analysis?

From: Ran Atkinson <rja@cisco.com>

Prev by Date: Re: Routing Header info of IPng against traffic analysis?
Next by Date: Re: ports in the clear...
Prev by thread: Re: Routing Header info of IPng against traffic analysis?
Next by thread: ports in the clear...
Index(es):
- Main
- Thread