A couple of different attempts to catch dropped balls: RFC-Editor's queue vs. IESG datatracker | Datatracker: "on agenda" vs. IESG Evaluation
Understanding the IESG's timeline: document states | damn lies
Understanding the RFC-Editor's timeline: analyzing the RFC-Editor's queue history | grep history for a single document
Analyzing dependencies in the RFC-Editor's queue:
tab-seperated |
html
Visualizations of dependencies:
ps |
pdf .
Visualization key: oval colors map to RFC-Editor state as below.
Arrows indicate dependency.
Box with orange arrows inside indicates a cycle; large cycles are
hard to detect without looking for them.
| color | state |
|---|---|
| green | EDIT |
| red | REF |
| blue | IANA |
| black | other |
| dotted black | Not in queue |
Documents in Authors' 48 hours: History
colon-seperated dump of today's ID tracker state | tab-seperated dump of more state (can you tell exactly how ad-hoc these tools are?)
Database containing all this junk (login ietf; password ietf)
Tracker Exceptions | (when does a document become listed as an exception?)
check here for other ad-hoc stuff
Document dependencies (including downrefs) | visualization (not including downrefs)
xml2rfc plugin for XXE XML Editor | xml2rfc XML validator | check status of references for xml2rfc source