Henning,
Some WGs issue Informational RFCs that represent WG consensus, but
which are not viewed as suitable Standards track documents, for
various reasons. For example, RFC 3647 is one of the most widely
cited of the PKIX RFCs, yet it is Informational because its a policy
and procedures document, not a protocol document. Some WGs also
choose to publish a requirements spec as Informaitonal, even thought
the document that will meet the requirements will itself be standards
track.
So I think we have a wide variety of document types that wind up as
informational RFCs, even today.
Steve
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf