IESG Quick Links and Semi-Complete Guide

Notice an omission or error? Please work with the IESG and edit this page.

Most-used Wiki pages

  • InformalAgenda - the agenda for the next informal telechat; add items here
  • UpcomingIetf - booking the IESG breakout room and showing arrival times
  • RetreatInfo - information about the upcoming IESG retreat
  • Workshop-2022Q1 Joint IAB/IESG Workshop Jan 2022
  • Workshop IESG IAB and LLC Workshop - information about the October 2021 Workshop

IESG Roles

IESG Liaisons To Other Things
IESG Liaisons Group
Warren K. IAB
Martin D. NomCom
Éric V. Tools Team
Alvaro R. EDU Team / EMODIR
Warren, Ben, Martin D., Roman, John, Zahed Comms Review

IESG Mailing List Admins
Murray Kucherawy
Roman Danyliw
The Secretariat

Meeting with Leaders of other Standards Bodies

Some Things We're Currently Working On

Newest items are at the top of the list.




Getting Started as an AD

An IESG Charter, RFC 3710 (2004)

There is a lot of useful information on how to utilize the tools. As a new AD you will work with the Secretariat for access.

Reference for All ADs on subjects such as basic AD responsibilities, using the datatracker, the document ballot process, and much more.

Useful Mailing Lists or Addresses

Email Address or Alias Recipient
<wg>-chairs @ mail the chairs of <wg>
<area>-chairs @ mail all the chairs of <area> ("<area>" is one of app, gen, int, ops, rai, rtg, sec, tsv)
<ad-name>-chairs @ mail all the chairs of WGs for which <ad-name> is responsible (john-smith-chairs, for example)
<wg>-ads @ mail the ADs of <wg>; note that this is the same as <area>-ads for the area in which <wg> resides... it does not send mail only to the AD responsible for <wg>
<area>-ads @ mail the ADs of <area> ("<area>" is one of app, gen, int, ops, rai, rtg, sec, tsv)
irtf-announce @ IRTF announcement list, including progress reports for the different reserach groups.
tools-discuss @ The mailing list for IETF Tools announcements and discussion.


The IESG has a private Wiki Site.

The IETF Chair has a demanding ChairTimeline to plan IETF meetings.

C code in I-Ds should do bound checking. The exception is when the code is a fragment and it's clear that it's a fragment. In that case a prominent note in the module needs to say "this is a code fragment, when this fragment is implemented as part of [insert_protocol_name] implement bound checking".

Wiki page for HandlingChangesWhenIDIsInQueue, LegacyErrataHandling, SpeakingForIetf, DealingWithPrivateFeedbackInIetfProcess, EnsuringAppropriateDiscussionOnIetfAtIetfList.

Dealing with some complicate IANA Registries: MediaTypes (a.k.a. MIME Types)

Some abandoned or obsolete stuff that's nonetheless useful to save

  • Wiki page for DocumentLanguageEditing session in London.
  • DraftShepherdWriteupWgAlternate - A new proposal for a radical change to the shepherd writeup, as discussed at IETF 84. This is a version that strips out all the yes/no sorts of things and instead asks for a paragraph or two of information in each of five categories. (This is now part of the normal shepherd writeup documentation.)
  • DownrefRegistry - The former Down Ref Registry - which documents have been Last Called as Downrefs following RFC 3967 (BCP 97) procedure (The Downref Registry has been moved into the ​datatracker as of 14 April 2017.)
  • DraftNoteWellSummary - A draft version of a very short Note Well summary. (This is now dead.)
  • DraftBoilerplateChange - A draft of a change to the boilerplate for cases where we are publishing something (such as documentation of a vendor-specific mechanism) where the community has consensus to publish, but consensus on the content doesn't make sense. (The IAB has chosen not to approve this, but the text is still useful as an IESG note in such documents.)

Can't Find It? You can access the former IESG Wiki Page here

Last modified 4 months ago Last modified on 08/06/22 15:47:43

Attachments (1)

Download all attachments as: .zip