IESG Statements on Procedures

These messages represent the IESG's best effort to deal with specific issues that have come up from time to time and are not meant to be a way for the IESG to revise the established IETF processes. If at any time someone feels that one or more of these messages represents a misunderstanding of the intent of the relevant RFCs the issue should be taken to the IESG mailing list for discussion.

Date Posted IESG Statement
2012-10-25 IESG Statement on Removal of an Internet-Draft from the IETF Web Site
2012-10-25 IESG Statement on Ethertypes
2011-10-20 IESG Statement on Designating RFCs as Historic
2011-06-27

IESG Statement on Designating RFCs as Historic

NOTE: This IESG Statement is superseded by the IESG Statement "IESG Statement on Designating RFCs as Historic" dated 20 October 2011.

2011-06-13 IESG Statement on IESG Processing of RFC Errata concerning RFC Metadata
2010-10-11 IESG Statement on Document Shepherds
2010-05-24 IESG Statement on the Usage of Assignable Codepoints, Addresses and Names in Specification Examples
2009-09-08 IESG Statement on Copyright
2009-01-20 IESG Statement on Proposed Status for IETF Documents Reserving Resources for Example Purposes
2008-07-30 IESG Processing of RFC Errata for the IETF Stream
2007-10-04 On Appeals of IESG and Area Director Actions and Decisions
2007-07-05 DISCUSS Criteria in IESG Review
2007-03-20 Guidance on Area Director Sponsoring of Documents
2007-01-15 Last Call Guidance to the Community
2006-04-19 IESG Statement: Normative and Informative References
2006-01-05 IESG Statement on AUTH48 State
2005-05-12 Syntax for Format Definitions
2002-11-27

Copyright Statement in MIB and PIB Modules

NOTE: This IESG Statement is superseded by the IESG Statement "IESG Statement on Copyright" dated 8 September 2009.

2001-12-21 On Design Teams
2001-10-01 Guidelines for the Use of Formal Languages in IETF Specifications

Return to All IESG Statements