On 2022-02-28, at 10:55, David Noveck <davenoveck@xxxxxxxxx> wrote: > > I'd like to ask all ADs with documents beyond the AUTH1000 point to investigate and suggest ways to address the issue for real. Apart from the technical mismatches I just brought up, there also is a scheduling problem. Doing AUTH48 even for a medium-sized document such as RFC-to-be 9176 (60 PDF pages; 74 in TXT form) requires setting aside some time. Today, the RPC is essentially a black box that suddenly spews a significant work order at you. Not totally surprising (one can look at the queue, look at average sojourn times, and make guesses), but not plannable either. So in this case I decided to leave all the early AUTH48 work with the main author/editor, and I will only come in when the document is nearly stable, which has given me some time to weave this work into the scheduling. But there just is no way to do this in less than 4 weeks (which is still AUTH672, phew). If we plan to move towards a more author-friendly form of document production, some interaction about scheduling the author work will need to be added. And yes, “kein Plan überlebt den ersten Feindkontakt”… (*). Grüße, Carsten (*): Actually, Moltke said “Kein Operationsplan reicht mit einiger Sicherheit über das erste Zusammentreffen mit der feindlichen Hauptmacht hinaus”. Apparently, he didn’t have an RPC helping him :-)
