A Model for IETF Process Experiments

Klensin, John; Dawkins, Spencer

doi:10.17487/rfc3933

Cited by 5 publications

(5 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Following a community discussion, it was concluded that [RFC3933] is not an appropriate framework for this experiment, primarily because no change is required to any existing process.…”

Section: Process Experimentsmentioning

confidence: 99%

See 1 more Smart Citation

Improving Awareness of Running Code: The Implementation Status Section

Sheffer¹,

Farrel²

2013

View full text Add to dashboard Cite

This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. The process in this document is offered as an experiment. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. The authors of this document intend to collate experiences with this experiment and to report them to the community. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6982.

show abstract

“…Following a community discussion, it was concluded that [RFC3933] is not an appropriate framework for this experiment, primarily because no change is required to any existing process.…”

Section: Process Experimentsmentioning

confidence: 99%

“…The process in this document is offered as an experiment (though not as an [RFC3933] experiment; see Section 5). Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications.…”

Section: Introductionmentioning

confidence: 99%

Improving Awareness of Running Code: The Implementation Status Section

Sheffer¹,

Farrel²

2013

View full text Add to dashboard Cite

show abstract

“…RFC 4693 [RFC4693] established the IETF Operational Notes (IONs) series of documents on the experimental basis [RFC3933]. This series was intended to discuss the set of procedures that the IETF follows, but for which the RFC publication process is an inappropriate documentation vehicle.…”

Section: Moving Rfc 4693 To Historic Statusmentioning

confidence: 99%

“…Per RFC 3933 [RFC3933], in March 2008, the IESG decided to terminate the IONs process experiment [IESG-IONS]. This document moves RFC 4693 to Historic status, per [HISTORIC], to reflect experiment closure.…”

Section: Moving Rfc 4693 To Historic Statusmentioning

confidence: 99%

Moving RFC 4693 to Historic

Yevstifeyev¹

2011

View full text Add to dashboard Cite

“…The document series is a process experiment according to RFC 3933 [RFC3933]. The properties list does not include a "category"; while the set of documents that might be IONs is extremely wide, we do not know yet which categories could make sense.…”

mentioning

confidence: 99%

IETF Operational Notes

Alvestrand¹

2006

View full text Add to dashboard Cite

A Model for IETF Process Experiments

Cited by 5 publications

References 2 publications

Improving Awareness of Running Code: The Implementation Status Section

Improving Awareness of Running Code: The Implementation Status Section

Moving RFC 4693 to Historic

IETF Operational Notes

Contact Info

Product

Resources

About