RE: Finding PKIX Servers!

[Andrew Probert <AndrewP@xxxxxxxxxxxx>]

Yeah .. apologies, my typing was in haste, I know HTTP is over IP.

I meant to allude to simplicity of the transport i.e. you can Telnet to a
Web server and hand-type HTTP protocol, so the underlying comms is very
simple, but you are pushing a lot of stuff up into the HTTP application.



Andew Probert
Rotek Consulting   http://www.rotek.com.au
a Division of Secure Network Solutions
Tel  +61 3 9690 8877
Fax +61 3 9690 8171



> -----Original Message-----
> From:	EKR [SMTP:ekr@rtfm.com]
> Sent:	Friday, February 12, 1999 11:15 AM
> To:	Andrew Probert
> Cc:	'Phillip M Hallam-Baker'; David P. Kemp; ietf-pkix@imc.org
> Subject:	Re: Finding PKIX Servers!
> 
> 
> Andrew Probert <AndrewP@rotek.com.au> writes:
> > > I don't see a need therefore to use LDAP or X.500 as the transfer
> > > protocol for OCSP. Not only is HTTP considerably more efficient,
> > > the much vaunted data model and replication protocols are a poor
> > > match for the particular needs of an online status protocol.
> > > 
> > 	[Andrew Probert]  Well .. HTTP is an overlay of simple verbs GET,
> > POST over Telnet, with some service controls and it is certainly a
> simple
> > protocol. 
> I don't know where you get the idea that HTTP is an overlay over
> TELNET. It most certainly is not. HTTP runs over a TCP connection,
> as does TELNET, yes, but that doesn't make HTTP an overlay over TELNET
> wny more than FTP is. RFC-854 specifies all sorts of stuff that HTTP
> doesn't have any notion of, including some terminal behavior, control
> information, etc.
> 
> -Ekr
> 
> -- 
> [Eric Rescorla                                   ekr@rtfm.com]