Notice an omission or error? Please work with the IESG and edit this page.
|Éric V. and Warren K.||Tools Team|
|Warren K. and Paul W.||EODIR|
|Warren, Martin, Roman, John, Zahed||Comms Review|
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.
IESG Lore for New Area Directors slide deck, put together by the Secretariat
|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)
Which is nonetheless useful to save