Document Processing Time Details for draft-ietf-netlmm-nohost-req

“End-to-End Delay from draft-smith to an RFC”

Document Timeline

timeline

IESG Processing

The following table shows the events relating to the document during its IESG processing. The greyed out information is based on the substates and Discuss positions in the tracker. As not all ADs employ substates in the same way, and as all ADs employ them at least somewhat inaccurately, the data in this part of the table is very unreliable.

PERIODVERSTATESUBSTATEDISCUSSESDAYSRESPONSIBLE
(Speculative)
2007-04-23 .. 2008-12-2399RFC Published-0--
2007-04-23 .. 2007-04-2399RFC Ed Queue-0--
2006-12-12 .. 2007-04-2399Approved-announcement sent-0--
2006-12-04 .. 2006-12-1299Approved-announcement to be sent-0--
2006-11-30 .. 2006-12-0499IESG EvaluationAD Followup04AD
2006-11-29 .. 2006-11-3099IESG EvaluationAD Followup11Authors
2006-11-22 .. 2006-11-2999IESG EvaluationAD Followup27Authors
2006-08-31 .. 2006-11-2299IESG EvaluationRevised ID Needed281Authors
2006-08-30 .. 2006-08-3199Waiting for AD Go-Ahead-21Authors
2006-08-30 .. 2006-08-3099Waiting for AD Go-Ahead-10Authors
2006-08-30 .. 2006-08-3099Waiting for AD Go-Ahead-00AD
2006-08-17 .. 2006-08-3099Last Call Requested-013Others
2006-08-11 .. 2006-08-1799In Last Call-06Others
2006-08-11 .. 2006-08-1199AD EvaluationAD Followup00AD
2006-08-03 .. 2006-08-1199AD EvaluationRevised ID Needed08Authors
2006-06-30 .. 2006-08-0399AD Evaluation-033AD

IESG Processing Time Statistics

Document got to the AD/IESG on 2006-06-30 and was approved on 2006-12-04.

According to the speculative analysis, the document waited for AD 37 days, previous AD 0 days, authors 98 days, and others 19 days, a total of 154 days, and was revised 0 times.

The (last) responsible AD for this document was Arkko_Jari.

Overall Processing Time Statistics

Document was in individual and WG process for 148 days, and in IESG/RFC Editor process for 298 days, 446 days in total. This is 1 years and 2 months.

Data Source

Original source data available in the tracker.