You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IESG recently approved draft-ietf-roll-useofrplinfo. Once the announcement was sent I expected the IESG state to change to "RFC Ed Queue", but it didn't (and remained in "Approved-announcement sent").
The RFC Editor did receive the document and is already editing it, so the incorrect status didn't have an impact there.
I also approved a related document on the same date (draft-ietf-roll-unaware-leaves) which didn't experience the same problem. The one (significant) difference is that draft-ietf-roll-useofrplinfo had already been in the RFC Editor's queue, we took it off for more editing, went though IETF LC, and IESG Evaluation again. I wonder is that is the reason the status was not changed.
[I will go ahead and change it manually.]
Issue migrated from trac:3164 at 2022-03-04 08:08:36 +0000
The text was updated successfully, but these errors were encountered:
type_defect
| by aretana.ietf@gmail.comThe IESG recently approved draft-ietf-roll-useofrplinfo. Once the announcement was sent I expected the IESG state to change to "RFC Ed Queue", but it didn't (and remained in "Approved-announcement sent").
The RFC Editor did receive the document and is already editing it, so the incorrect status didn't have an impact there.
I also approved a related document on the same date (draft-ietf-roll-unaware-leaves) which didn't experience the same problem. The one (significant) difference is that draft-ietf-roll-useofrplinfo had already been in the RFC Editor's queue, we took it off for more editing, went though IETF LC, and IESG Evaluation again. I wonder is that is the reason the status was not changed.
[I will go ahead and change it manually.]
Issue migrated from trac:3164 at 2022-03-04 08:08:36 +0000
The text was updated successfully, but these errors were encountered: