1996-03-29 - Re: Edited Edupage, 24 March 1996

Header Data

From: “Perry E. Metzger” <perry@piermont.com>
To: jsw@netscape.com
Message Hash: f498df9fc17609f261860137388875389e7056c9afcac4cc7e22b1da5cad6e7e
Message ID: <199603281535.KAA02728@jekyll.piermont.com>
Reply To: <315A3ECA.6E53@netscape.com>
UTC Datetime: 1996-03-29 18:18:01 UTC
Raw Date: Sat, 30 Mar 1996 02:18:01 +0800

Raw message

From: "Perry E. Metzger" <perry@piermont.com>
Date: Sat, 30 Mar 1996 02:18:01 +0800
To: jsw@netscape.com
Subject: Re: Edited Edupage, 24 March 1996
In-Reply-To: <315A3ECA.6E53@netscape.com>
Message-ID: <199603281535.KAA02728@jekyll.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain

Jeff Weinstein writes:
> > 1) I strongly suggest that SSL is *not* in its current form the right
> >    technology, because internet phone type tools probably use UDP, not
> >    TCP.
>   I guess that is what I get for posting when too tired.  Certainly the
> current SSL won't work for UDP based protocols.  Either we will have to
> make a UDP version of SSL or use some existing protocol that gets the job
> done.  Since our acquisition is not complete I haven't really had an
> opportunity to talk to the streaming media guys yet...

You probably want to look into the hooks that RTP audio programs like
VAT use right now to do their cryptography (yes, they do crypto) -- I
belive there is lots of precedent.