It depends on the wording in the Informational.
Scott Brim <sbrim(_at_)cisco(_dot_)com> 06/05/01 01:29PM >>>
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.