Document Processing Time Details for draft-ietf-dnsext-dnssec-online-signing

“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)
2006-06-06 .. 2008-12-2499RFC Published-0--
2006-06-06 .. 2006-06-0699RFC Ed Queue-0--
2006-05-30 .. 2006-06-0699RFC Published-0--
2006-05-03 .. 2006-05-3099RFC Ed Queue-0--
2006-02-06 .. 2006-05-0399Approved-announcement sent-0--
2006-01-31 .. 2006-02-0699Approved-announcement to be sent-0--
2006-01-09 .. 2006-01-3199IESG EvaluationAD Followup022AD
2006-01-09 .. 2006-01-0999IESG EvaluationAD Followup10Authors
2006-01-06 .. 2006-01-0999IESG EvaluationAD Followup23Authors
2005-12-15 .. 2006-01-0699IESG Evaluation-226Authors
2005-12-14 .. 2005-12-1599IESG Evaluation-11Authors
2005-12-08 .. 2005-12-1499IESG Evaluation-06Others
2005-12-08 .. 2005-12-0899Waiting for Writeup-00AD
2005-11-27 .. 2005-12-0899In Last Call-011Others
2005-11-22 .. 2005-11-2799Last Call Requested-05Others
2005-11-21 .. 2005-11-2299AD Evaluation-01AD
2005-11-21 .. 2005-11-2199Publication Requested-00AD

IESG Processing Time Statistics

Document got to the AD/IESG on 2005-11-21 and was approved on 2006-01-31.

According to the speculative analysis, the document waited for AD 23 days, previous AD 0 days, authors 30 days, and others 22 days, a total of 75 days, and was revised 0 times.

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

Overall Processing Time Statistics

Document was in individual and WG process for 189 days, and in IESG/RFC Editor process for 194 days, 383 days in total. This is 1 years and 0 months.

Data Source

Original source data available in the tracker.