[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 01 02 03 RFC 3710

Network Working Group                                      H. Alvestrand
Internet-Draft                                             Cisco Systems
Expires: June 6, 2003                                   December 6, 2002


                            An IESG charter
                         draft-iesg-charter-00

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 6, 2003.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This memo gives a charter for the Internet Engineering Steering Group
   (IESG), a management function of the Internet Engineering Task Force
   (IETF).












Alvestrand                Expires June 6, 2003                  [Page 1]


Internet-Draft              An IESG charter                December 2002


1. Introduction

   The role of the IESG in the IETF management structure has been
   largely constant since 1992, when the structure of the Internet
   standards process was defined by RFC 1310 (which was later updated by
   RFC 1602, RFC 1871 and RFC 2026).

   Some of the functions were also defined in RFC 1603 (which was later
   updated by RFC 2418).

   As the community has grown, and the IESG has gathered experience, the
   way in which the IESG approaches its tasks has varied considerably,
   but the tasks have remained relatively constant.

   This document describes the tasks assigned to the IESG.




































Alvestrand                Expires June 6, 2003                  [Page 2]


Internet-Draft              An IESG charter                December 2002


2. The composition of the IESG

   The IESG has the following members:

   o  The IETF Chair, who is also the General AD

   o  The Area Directors for the IETF Areas

   o  Liaisons

   The Chair and the Area Directors are selected by the IETF NomCom
   according to the procedures of RFC 2282 (Nomcom procedures).  The
   Liaisons are selected as appropriate by the liaising bodies.  At the
   time of this writing, the liaisons present are:

      The RFC Editor

      The IANA

      The IAB

   In addition, members of the IETF Secretariat are subscribed to the
   mailing list and present in the IESG meetings as needed in order to
   serve as a support function.



























Alvestrand                Expires June 6, 2003                  [Page 3]


Internet-Draft              An IESG charter                December 2002


3. The IESG role in working group management

3.1 Working group creation

   The formation of working groups is described in RFC 2418 section 2.
   Each area director is responsible for ensuring that a working group
   being chartered is relevant, has achievable goals and constitutes an
   acceptable risk, has sufficient interest and so on.  The charter is
   the result of a negotiation between the AD and the prospective
   chairs, with review by the IAB and approval by the IESG.  Normally,
   there will be communication with the community of interest for the
   working group too.

   The AD is also responsible for selecting chairs for the working group
   that he thinks will be up to the task.

   The BOF procedure described in RFC 2418 section 2.4 also requires
   approval from the relevant AD.  A BOF is not required to start a
   working group, and a BOF may be held without the purpose being to
   create a working group.  BOFs are also often discussed with the IESG
   and IAB.

   If an AD determines that it is needed, he can take the initiative to
   create a working group.

3.2 Working group management

   The role of the Area Director in WG management is described in RFC
   2418 section 6.7.  The AD is responsible for making sure the working
   groups stay focused on the charter tasks, make forward progress, are
   coordinated with the rest of the area, and (with the IESG)
   coordinated with the rest of the IETF.

   In a well functioning working group, main responsibility for these
   things rests with the chairs; the AD will normally be able to
   concentrate on supporting the working group chairs' work.

   When a WG finds that it is essential that work gets done which is not
   on its charter, the AD is responsible for figuring out whether to add
   it to their charter, add it to another group's charter, task someone
   outside the WG to work on it, or initiate creation of another WG.

   The Area Director is also responsible for picking and, when
   necessary, replacing working group chairs.  This is usually done in
   consultation with the IESG.






Alvestrand                Expires June 6, 2003                  [Page 4]


Internet-Draft              An IESG charter                December 2002


4. The IESG role