At 15:12 08-03-2009, Richard M Stallman wrote:
But an experimental RFC is not a Proposed Standard, a proposed
standard, a document that is in the process of being considered
for standardization, or any other sort of standard or
prestandard.
There are people who propose this as a standard; in factual terms,
that makes it a proposed standard. Whether or not the fact of
publication as an experimental RFC would make it one, it is one
already.
In IETF terms:
"Internet specifications go through stages of development, testing,
and acceptance. Within the Internet Standards Process, these stages
are formally labeled "maturity levels"."
"The entry-level maturity for the standards track is "Proposed
Standard". A specific action by the IESG is required to move a
specification onto the standards track at the "Proposed Standard"
level."
As the draft was not approved by the IESG as a "Proposed Standard",
the fact is that most people in the IETF community would not consider
it as a proposed standard.
"The "Experimental" designation typically denotes a specification that
is part of some research or development effort. Such a specification
is published for the general information of the Internet technical
community and as an archival record of the work, subject only to
editorial considerations and to verification that there has been
adequate coordination with the standards process."
Publication as an "Experimental" RFC does make a document a
standard. The "Status of This Memo" which is prominently displayed
on the first page of the RFC mentions that:
"This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind."
Regards,
-sm
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf