* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Process for sending a working group document to the responsible AD for publication

In the old days, when dinosaurs roamed the Earth (and held standards meetings), we requested publication of working group documents by emailing the request and the shepherd writeup to the responsible AD, preferably CCing the IESG Secretary. Manual things ensued thence.

Changes have been made, and the process is now driven automatically by the datatracker. All working group chairs should already have a datatracker login. If you don't, click the "New Account" link on the top left of the datatracker page. If you do, click the "Sign In" link on the top right. It's important to remember to check that you're logged in: currently, the datatracker cookies are too short-lived, and you'll find that you're often logged off when you're not expecting it.

To manage your working group's documents after you log in, go to your working group's datatracker page. You can get there from the Active IETF Working Groups page, or go directly to it by substituting your WG's shortname for "WGNAME" in this URL: http://datatracker.ietf.org/wg/WGNAME

If you click on the filename of one of your documents, you'll see a blue area at the top that has three sections to it. The first section has some fixed information. The second section has the working group status. The third section has the IESG status.

As soon as you assign a document shepherd to a document, you should fill in the "Document Shepherd" field in the second section. When you have the shepherd writeup ready, you should post it to the datatracker in the "Shepherd Write-Up" field. Please do not change the "Consensus" field; that will be done by the AD at the end of the process.

You may use the "IETF State" field to track the status of the document while it's being developed in the working group. When the document is ready to go to your AD with a publication request, the "IETF State" field is the way to submit it, as follows:

  1. Make sure the document shepherd is correctly listed.
  2. Make sure the shepherd writeup is current and correct.
  3. Make sure the document passes ID nits.
  4. Set the "IETF State" field to "Submitted to IESG for Publication".

And that's it: automated magic will happen and everything will be tracked; you no longer need to send email. You should soon see the various IESG state changes, beginning with "Publication Requested". The document shepherd is responsible for driving the process through the AD Evaluation, Last Call, and IESG Evaluation stages... so keep a watch out, and make sure things don't languish.

And if you have any questions, don't hesitate to ask your AD.