RE: Unreliable transport

>- UDP and other unreliable transports: I don't think support for an
>unreliable protocol is appropriate for this effort. The current
>(SSL & PCT) both provide protection against an opponent blocking
>this can be detected. In SSL 3.0, truncation attacks can be detected.
>an unreliable underlying transport makes it impossible to provide
>protection against this without essentially creating a stream transport
>top of it. I think the standard we create should provide a certain set
>security features which are provided by all implementations of the
>standard, and that protection against these "interruption" attacks
>be a part of it.
>However, we should think about an unreliable transport standard which
>leverage its cipher negotiation and authentication off of the stream

This is exactly what I have in mind when I talk about "datagram
support"--not a substitute for IPSEC, but merely a defined format for
independently decryptable datagrams, so that key management can be
unified in situations where both a reliable transport and an unreliable
one are being used in parallel.

				Daniel Simon
				Cryptographer, Microsoft Corp.


Received on Friday, 26 April 1996 14:38:05 UTC