If a document is approved during an IESG Telechat (i.e. there are no Discusses and there are sufficient Yes or No Objection ballots), the Secretariat handles the approval automatically.
If the AD can confirm on the Telechat that all the notes are in place, the Secretariat will move the document into "Approved Announcement to be Sent" state. In the next few days, the Secretariat will send out the approval announcement and put the document on the RFC Editor Queue (with those state changes noted in the tracker).
However, sometimes the AD needs to follow a few extra steps.
If a document revision is produced, the responsible AD is expected to check the changes in a manner similar to how AUTH48 changes are being checked, and if substantial changes occur, brings the document back to the IESG review.
In all of these cases, the document is only advanced when the responsible AD considers that all changes and notes are in place. The AD needs to push the document onward by changing the state in the ID-Tracker to "Approved Announcement to be Sent", and must also by send a ticket to the IESG Secretariat to inform them. (This latter is usually done by sending an email to the IESG and the document alias, and BCC'ing the Secretariat. It is useful to note the fact of the BCC in the text of the email.)
If for any reason a document makes it to the RFC Editor Queue but then is pushed back to the IESG, the responsible AD will need to resolve whatever the issue is then decide what to do next.
The content of this page was last updated on 2013-05-19. It was migrated from the old Trac wiki on 2023-02-17.