Re: [IPsec] draft-ietf-ipsecme-qr-ikev2 has been in RFC Editor queue for 123 days?

[Benjamin Kaduk <[e-mail]>]

On Tue, May 19, 2020 at 10:00:58PM +0300, Valery Smyslov wrote:
> Hi,
> 
> > On Tue, 19 May 2020, Benjamin Kaduk wrote:
> > 
> > >> Can the WG chairs or AD see about getting this unstuck and out the
> > door?
> > >
> > > There's a giant backlog in the "RFC-EDITOR" state (see
> > > https://www.rfc-editor.org/current_queue.php); my understanding is
> > that
> > > this accumulated in the gap period between Heather and John, and
> > there's
> > > not really a way to make the overall queue move faster.
> > 
> > Oh, I see.
> 
> Ben, thank you for the explanation. The draft has already 
> endured unfortunate delay in the WG, this one is just another unfortunate
> one.
> That is that.
> 
> > >  It is possible for
> > > the IESG to request expedited processing of a specific document, if
> > needed
> > > -- is there a timely need for an RFC number for this document that we
> > > should do so?
> > 
> > Ahh, no there is no reason for an expedited processing.
> 
> I agree with Paul (with co-author hat on).
> The code-points are already allocated and several vendors have implemented
> the draft.
> The only thing left is an RFC number to refer to, but we can wait for it.

Amusingly enough, it just entered AUTH48 this evening (and thus,
provisionally has an RFC number assigned).

-Ben