IPP> Re: V1.1 Last Call

IPP> Re: V1.1 Last Call

IPP> Re: V1.1 Last Call

Keith Moore moore at CS.UTK.EDU
Thu Mar 11 11:50:05 EST 1999

Without commenting specifically on whether 1.1 is ready for
the standards track (since I haven't reviewed it), I do want 
to direct attention to the language in RFC 2026 describing the 
criteria for Proposed Standard.  In particular, note that 
"neither implementation nor operational experience is required" 
but there should be "no known technical omissions".


   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  However, further experience
   might result in a change or even retraction of the specification
   before it advances.

   Usually, neither implementation nor operational experience is
   required for the designation of a specification as a Proposed
   Standard.  However, such experience is highly desirable, and will
   usually represent a strong argument in favor of a Proposed Standard

   The IESG may require implementation and/or operational experience
   prior to granting Proposed Standard status to a specification that
   materially affects the core Internet protocols or that specifies
   behavior that may have significant operational impact on the

   A Proposed Standard should have no known technical omissions with
   respect to the requirements placed upon it.  However, the IESG may
   waive this requirement in order to allow a specification to advance
   to the Proposed Standard state when it is considered to be useful and
   necessary (and timely) even with known technical omissions.

   Implementors should treat Proposed Standards as immature
   specifications.  It is desirable to implement them in order to gain
   experience and to validate, test, and clarify the specification.
   However, since the content of Proposed Standards may be changed if
   problems are found or better solutions are identified, deploying
   implementations of such standards into a disruption-sensitive
   environment is not recommended.

More information about the Ipp mailing list