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

Header Data

From: “Perry E. Metzger” <perry@piermont.com>
To: Phil Karlton <karlton@netscape.com>
Message Hash: ef0a1b6b06c0793a48676e88a1ef72a021b230c40365eeba9ea1db43811fe486
Message ID: <199603271856.NAA03030@jekyll.piermont.com>
Reply To: <31598E35.1CFB@netscape.com>
UTC Datetime: 1996-03-28 23:57:42 UTC
Raw Date: Fri, 29 Mar 1996 07:57:42 +0800

Raw message

From: "Perry E. Metzger" <perry@piermont.com>
Date: Fri, 29 Mar 1996 07:57:42 +0800
To: Phil Karlton <karlton@netscape.com>
Subject: Re: Edited Edupage, 24 March 1996
In-Reply-To: <31598E35.1CFB@netscape.com>
Message-ID: <199603271856.NAA03030@jekyll.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain

Phil Karlton writes:
> Perry E. Metzger wrote:
> > 2) I strongly hope that Netscape tries to move the product towards
> >    standards based mechanisms like the IETF's RTP protocol, which are
> >    in widespread use, rather than pushing yet more proprietary
> >    systems. Proprietary is bad in this instance.
> Personally, I have some trouble with the work proprietary above.
>     SSL 2 and SSL 3 protocols have been IETF drafts from the beginning.

We aren't talking about SSL, Mr. Karlton. We are talking about RTP
vs. a proprietary audio encapsulation. If you don't know what RTP is,
you to learn before talking about it.

> SSL does depend upon an underlying reliable bytestream. This means it is
> not the best choice for all applications.

Such as internet phone, for example.