Rechartering the IETF Discussion List
draft-nottingham-discussion-recharter-00

Document Type Active Internet-Draft (individual)
Last updated 2020-08-16
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
GENDISPATCH                                                M. Nottingham
Internet-Draft                                           August 17, 2020
Updates: 3005 (if approved)
Intended status: Informational
Expires: February 18, 2021

                 Rechartering the IETF Discussion List
                draft-nottingham-discussion-recharter-00

Abstract

   This document updates RFC3005, the charter of the IETF discussion
   list.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   The issues list for this draft can be found at
   https://github.com/mnot/I-D/labels/discussion-recharter [1].

   The most recent (often, unpublished) draft is at
   https://mnot.github.io/I-D/discussion-recharter/ [2].

   Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
   pages/discussion-recharter [3].

   See also the draft's current status in the IETF datatracker, at
   https://datatracker.ietf.org/doc/draft-nottingham-discussion-
   recharter/ [4].

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 February 18, 2021.

Nottingham              Expires February 18, 2021               [Page 1]
Internet-Draft    Rechartering the IETF Discussion List      August 2020

Copyright Notice

   Copyright (c) 2020 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  The IETF discussion list is not representative  . . . . .   3
     1.2.  The IETF discussion list is unproductive  . . . . . . . .   4
   2.  Re-Scoping the IETF discussion list . . . . . . . . . . . . .   5
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     4.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The IETF discussion list was chartered to '[further] the development
   and specification of Internet technology through discussion of
   technical issues, and [host] discussions of IETF direction, policy,
   meetings and procedures.'[RFC3005] It is thus considered the primary
   venue where the operation of the IETF is discussed, as well as the
   default home for technical discussions that don't have a more focused
   venue.

   Over time, it has become the favoured venue for the IESG to 'take the
   temperature' of the IETF as a whole, especially for proposals that
   affect many either administratively or technically.  Support on the
   list is taken as a sign that there is support within the IETF
   overall; objections on the list can stop a proposal from being
   enacted.

   This draft contends that the IETF discussion list is not an
   appropriate venue for that, because it is not representative of the
   IETF community Section 1.1, and because it is not productive

Nottingham              Expires February 18, 2021               [Page 2]
Internet-Draft    Rechartering the IETF Discussion List      August 2020

   Section 1.2.  Section 2 recommends re-scoping the charter of the IETF
   discussion list to reflect this.

1.1.  The IETF discussion list is not representative

   The IETF discussion list is often said to be the place where the IETF
   community comes together.  Discussion there often influences
   decisions made about the direction of the organisation, as well as
   specific technology choices.  However, measuring how representative
   it is of the IETF community is difficult.

   One way to approximate is to compare its membership with other IETF
   lists.  Although this has many limitations (e.g., some may use
Show full document text