Notice an omission or error? Please work with the IESG and edit this page.
|Éric V.||Tools Team|
|Warren, Ben, Martin D., Roman, John, Zahed||Comms Review|
Newest items are at the top of the list.
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.
|Email Address or Alias||Recipient|
|[wg]-chairs @ ietf.org||mail the chairs of [wg]|
|[area]-chairs @ ietf.org||mail all the chairs of [area] ("[area]" is one of art, gen, int, ops, rtg, sec, tsv)|
|[ad-name]-chairs @ ietf.org||mail all the chairs of WGs for which [ad-name] is responsible (john-smith-chairs, for example)|
|[wg]-ads @ ietf.org||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 @ ietf.org||mail the ADs of [area] ("[area]" is one of art, gen, int, ops, rtg, sec, tsv)|
|irtf-announce @ irtf.org||IRTF announcement list, including progress reports for the different reserach groups. https://www.ietf.org/mailman/listinfo/irtf-announce|
|tools-discuss @ ietf.org||The mailing list for IETF Tools announcements and discussion. https://www.ietf.org/mailman/listinfo/tools-discuss|
The IESG has a private Wiki Site.
The IETF Chair has a demanding Chair Timeline 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".
Dealing with some complicate IANA Registries: Media Types (a.k.a. MIME Types)
Wiki page for Document Language Editing session at IETF 89 (2014) in London.
Draft Shepherd Writeup WG Alternate - A new proposal for a radical change to the shepherd writeup, as discussed at IETF 84 (2012). 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.)
Downref Registry - 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.)
Draft NoteWell Summary - A draft version of a very short Note Well summary. (This is now dead.)
Draft Boilerplate Change - 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.)
Off Duty - This has been moved to the IESG Private Wiki Site.