Some Thoughts on IETF Community Leadership
draft-carpenter-community-leaders-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       B. Carpenter
Internet-Draft                                         Univ. of Auckland
Intended status: Informational                         September 8, 2018
Expires: March 12, 2019

               Some Thoughts on IETF Community Leadership
                  draft-carpenter-community-leaders-00

Abstract

   This is a personal view of what the IETF community might expect of
   its members who serve in leadership positions such as Area Directors
   and IAB members.  It is intended as personal input to the Nominating
   Committee, but posted as a draft since there is nothing private about
   it.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on March 12, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Carpenter                Expires March 12, 2019                 [Page 1]
Internet-Draft            Community Leadership            September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Expectations  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change log . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The IETF has a relatively open but not exactly democratic way of
   choosing those who serve the community as Area Directors, members of
   the Internet Architecture Board, and as IETF Chair.  Job descriptions
   are open and candidate lists are open.  Feedback on individuals is
   intentionally confidential to the NomCom, which in my opinion is
   correct.  We shouldn't be in the business of naming and shaming those
   who are willing to serve us.  As a community, we must not hesitate to
   make a fuss about decisions we don't like, or to insist when we see a
   technical error going uncorrected.  We do have a formal appeals
   mechanism, we do have the opportunity to send frank feedback to the
   NomCom every year, and we do in theory have the ultimate weapon of a
   recall procedure.

   However, there's a gap in the above mechanisms.  The job descriptions
   mentioned above are written by the body where there is a vacancy: by
   the IESG for Area Directors and the IETF Chair, and by the IAB for
   its own membership.  That's logical as far as it goes, but it doesn't
   give the community as a whole the chance to say what we think we
   expect of those who serve in leadership positions, beyond their
   obligations to the IETF process rules and their technical expertise.
   Also, even with the best of intentions, those bodies write job
   descriptions to replicate themselves and what they see as a smooth-
   running operation.  There is little scope in the job descriptions for
   describing desirable changes in the status quo.

   To some extent this gap is filled by the formal documents that
   describe the IETF process, in the IESG and IAB charters, and in the
   Tao of the IETF.  But there is little explicit description of how the
   leadership is expected to behave.  This draft is a personal version
   of a more explicit approach.  It's by no means definitive and has no
   authority.  Discussion (on ietf@ietf.org?) is welcome.

   A personal note: I have served in the past on the IAB (including a
   spell as Chair), and on the IESG as IETF Chair.  I'm quite sure that
Show full document text