Folks,
I would like to clarify a few points regarding this statement. Specifically,
- It applies only to documents that were published on the IETF stream.
- It does not apply to documents that were published on the IAB, IRTF or Independent streams.
- Reuse of deprecated code points is not a goal of this exercise.
- It does not recommend any change in IETF process.
Today, experiments can be concluded through either of the following actions:
- Obsoleting the EXPERIMENTAL RFC with a Standards Track document
- Publishing an INFORMATIONAL RFC that terminates the experiment and possibly moves the EXPERIMENTAL RFC to HISTORIC
Today, both of these actions require community consensus. Today, both of these actions can be undertaken by anyone. If this IESG statement is published, none of that changes.
Ron
> -----Original Message-----
> From: iesg-bounces@xxxxxxxx [mailto:iesg-bounces@xxxxxxxx] On Behalf Of
> Adrian Farrel
> Sent: Thursday, April 19, 2012 4:31 PM
> To: ietf@xxxxxxxx; wgchairs@xxxxxxxx
> Cc: iesg@xxxxxxxx
> Subject: Proposed IESG Statement on the Conclusion of Experiments
>
> All,
>
> The IESG has been discussing how to tidy up after Experimental RFCs.
>
> We have developed the following draft IESG statement. This does not
> represent a change in process, and continues to value Experimental RFCs
> as an important part of the IETF process. It does, however, seek to
> encourage documentation of the conclusion of experiments.
>
> We are aware that there may be other discussion points around
> Experimental RFCs, and we would like to discuss these, but we also
> believe that there is merit in making small, incremental improvements.
>
> The IESG would welcome your thoughts on this draft before they approve
> the final text on April 26th.
>
> Thanks,
> Adrian
>
> =============
>
> IESG Statement on Conclusion of IETF Experiments
>
>
> Experiments are an established and valuable part of the IETF process.
> A number of core Internet protocols were first published as
> Experimental RFCs while the community gathered experience and carefully
> investigated the consequences of deploying new mechanisms within the
> Internet.
>
> In the case where an experiment leads on to the development of a
> Standards Track RFC documenting a protocol, the new RFC obsoletes the
> old Experimental RFC and there is a clear conclusion to the experiment.
>
> However, many experiments do not lead to the development of Standards
> Track RFCs. Instead, the work may be abandoned through lack of interest
> or because important lessons have been learned.
>
> It is currently hard to distinguish between an experiment that is still
> being investigated, and an old experiment that has ceased to be of
> interest to the community. In both cases an Experimental RFC exists in
> the repository and newcomers might easily be misled into thinking that
> it would be helpful to conduct more research into an abandoned
> experiment.
>
> In view of this, the original proponents of experiments (that is,
> authors of Experimental RFCs, and Working Groups that requested the
> publication of Experimental RFCs) are strongly encouraged to document
> the termination of experiments that do not result in subsequent
> Standards Track work by publishing an Informational RFC that:
>
> - very briefly describes the results of the experiment
>
> - obsoletes the Experimental RFC
>
> - if appropriate, deprecate any IANA code points allocated for the
> experiment
>
> - may request that the Experimental RFC is moved to Historic status.
>
> If there is no energy in the community for the producing such an
> Informational RFC, if the authors have moved on to other things, or if
> the Working Group has been closed down, Area Directors should author or
> seek volunteers to author such an Informational RFC.