Describe the issue
If an I-D lands in the "Approved: announcement sent" state due to operator error, it has no iesg_approved event. Currently, the submitted_to_rpc API that purple uses to feed its queue includes documents based solely on this state. This can lead to confusion / adding a document to the RFC Editor queue prematurely.
At least for IETF stream documents, these I-Ds stand out because their "submitted" date is empty and falls back to the start-of-unix-epoch date (1970-01-01 at midnight UTC). That's because the code that identifies that date looks for the iesg_approved event explicitly.
The submitted_to_rpc API should also apply this check for IETF stream docs. If it's not already the case, the API should also be updated to agree with the submitted-date logic for other streams to guarantee that every submitted-to-rpc I-D has an identified submission time.
Code of Conduct
Agent-assisted triage
- Suggested size: S
- Suggested priority: medium
- Suggested lane: standard
- Affected apps: doc/, api/
- Updated with agent assistance on 2026-09-04
Describe the issue
If an I-D lands in the "Approved: announcement sent" state due to operator error, it has no
iesg_approvedevent. Currently, thesubmitted_to_rpcAPI that purple uses to feed its queue includes documents based solely on this state. This can lead to confusion / adding a document to the RFC Editor queue prematurely.At least for IETF stream documents, these I-Ds stand out because their "submitted" date is empty and falls back to the start-of-unix-epoch date (1970-01-01 at midnight UTC). That's because the code that identifies that date looks for the
iesg_approvedevent explicitly.The
submitted_to_rpcAPI should also apply this check for IETF stream docs. If it's not already the case, the API should also be updated to agree with the submitted-date logic for other streams to guarantee that every submitted-to-rpc I-D has an identified submission time.Code of Conduct
Agent-assisted triage