Re: iCAP, OPES and the IETF

From rfc-index.txt:

1945 Hypertext Transfer Protocol -- HTTP/1.0. T. Berners-Lee, R.
     Fielding, H. Frystyk. May 1996. (Format: TXT=137582 bytes) (Status:
     INFORMATIONAL)

2068 Hypertext Transfer Protocol -- HTTP/1.1. R. Fielding, J. Gettys,
     J. Mogul, H. Frystyk, T. Berners-Lee. January 1997. (Format:
     TXT=378114 bytes) (Obsoleted by RFC2616) (Status: PROPOSED STANDARD)

Rgds,
John

At 03:29 PM 05/06/01 -0400, Scott Brim wrote:
> On Tue, Jun 05, 2001 at 01:17:02PM -0600, Hilarie Orman wrote:
> > I'd be a lot happier about ICAP if it were taken on as standards track
> > by the IETF.  Taking it as Informational now rules out cleaning up
> > lingering issues wrt to clarity, interoperability, etc.
>
> Not at all, it just makes it an informational RFC -- it doesn't rule out
> anything.  You can then create a standards-track RFC out of it at your
> leisure.  We have precedents for this (of course I can't remember any
> specific ones right now).  Also, even proposed standards have lingering
> issues wrt clarity, interoperability, etc.  You don't lose by publishing
> something informational.  Someone who implements a pre-standard version
> might lose, of course.
>
> ..Scott
---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Scorpius 2                                 Fax: +31 23 567 9699
NL-2132 LR Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------