Re: [Uri-review] draft-larmouth-oid-iri-01 editorials

[Alfred Hönes <[e-mail]>]

Ira,

I wouldn't be so pessimistic as you said below.
(For details, see below.)

As I already have pointed out, for documents of this kind
Proposed Standard might only take a small amount of time
in excess of what will be needed for Informational,
(albeight the AD might even omit IETF LC for Informational).

> Hi John,
>
> This is an informal answer - your mileage will certainly vary...
>
> To publish as an RFC, an appropriate IETF Area Director
> (Applications??) has to briefly review the document (1 month)
> and start an IETF Last Call (1 month).
>
> Then, the IETF AD has to take the document to the IESG
> for approval as an Informational RFC (several months).
>
> Then the RFC Editor has to publish it (four to twelve months).

That's not true (currently).  To be fair to the RFC Editor staff:
Most documents without 'built-in' road blockers (in particular
Normative References to documents not yet approved, not yet
finalized, or even not yet written at all!) or awaiting completion
of IANA processing, currently can be observed to arrive in the
final Author's review stage (AUTH48 state in the RFC Editor Queue)
very quickly.
Things got much worse for the Independent Submission stream due
to Copyright issues with the IETF Trust after RFC 5378, but that
should be entirely out of scope here.

Details:

Looking at the RFC-Ed Queue at this moment, you can see that *all*
Informational drafts on the IETF stream delivered to the RFC Editor
and not blocked by missing references or IANA processing already
have arrived in the final RFC Editor review stage (RFC-EDITOR state),
or in AUTH48.
Standards Track documents are similar, but due to larger volume
and size at average, and due to much more older documents having
become unblocked recently by new arrivals and thus consuming cycles,
a single document (arrived at the RFC Editor on Sep 25) is in
editorial processing among them.
Currently, the duration of final review by the authors (and if there
were nontrivial changes, by the AD) has much more influence on the
time needed from IESG approval to RFC publication -- 33 RFCs-to-be
from the IETF stream are in AUTH48 currently.
(Note that the figures at http://www.RFC-Editor.ORG/CurrQstats.txt
include ISR documents etc.; I have discounted for these above.
This summary is a snapshot apparently taken before the most recent
queue changes on Friday.)

So, including final author review, 2 months would perhaps be more
realistical, not 4..12.

>
> That is to say, a pretty long time.

Pretty long anyway, but not so much as you fear.


Attempts to increase the numbers of hours per day (in order to
give the IESG et al. more working cycles) have not arrived at
IETF consensus in the past, and would have collided with the
firm opinion of other SDOs anyway.  :-)

>
> Cheers,
> - Ira
>

Kind regards,
  Alfred.