ietf-openproxy
[Top] [All Lists]

RE: HTTP as OCP transport, ICAP/2.0

2003-04-22 17:48:08
Hilarie,
Based on my understanding. This is correct.

Marshall, can we have your 2 cents.

Abbie


-----Original Message-----
From: Alex Rousskov [mailto:rousskov(_at_)measurement-factory(_dot_)com] 
Sent: Tuesday, April 22, 2003 7:35 PM
To: ietf-openproxy(_at_)imc(_dot_)org
Subject: Re: HTTP as OCP transport, ICAP/2.0




On Tue, 22 Apr 2003, The Purple Streak, Hilarie Orman wrote:

I thought BEEP's security was the same as HTTP's: use TLS.

My understanding is that BEEP can _negotiate_ security 
profile for a BEEP session (so that we do not have to worry 
about that at all). Please correct me if I am wrong.

I know that HTTP has no idea it is being (or can be) wrapped 
with TLS. Thus, we, as OCP writers, would have to worry about 
negotiating and then enabling TLS.

Alex.


<Prev in Thread] Current Thread [Next in Thread>