[secdir] [new-work] WG Review: General Area Dispatch (gendispatch)

The IESG <iesg@ietf.org> Thu, 26 September 2019 22:44 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0EC120ABC; Thu, 26 Sep 2019 15:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1569537887; bh=LpRkKPeX5Z7MUM5Pe56ygqh0ChTnB7c7C/+gdhLvyBQ=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=Dyv5WeugP/ftsCo93F2peZAMHJuEPXdVsy8+6TMeyIjGhFVt/tfcfFgI20utMsJKk 7edtsr4Hn70D1oMA2+LGR1+xvgUwsgovkDTVvxQoPZSuLbM8w+qQ3TSUyaISaxBnkA jAJNrlNYVEVWDvWbPu/1dSQajZ+dEg9fdiIkXRQ0=
X-Mailbox-Line: From new-work-bounces@ietf.org Thu Sep 26 15:44:42 2019
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B625D120AA6; Thu, 26 Sep 2019 15:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1569537881; bh=LpRkKPeX5Z7MUM5Pe56ygqh0ChTnB7c7C/+gdhLvyBQ=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=qu/V10+N4KPG7ZzZ7kaYGOsICViAMrLFaWOZcvcry9/FduX5xSkeV3dqgvFKfWRv5 oV62O9iA8m/UfUQHC3MX29KIhICc32M8Lrt3JzRsItniEycOeLRwGEy9u0WV/vMP+c iooL4Rl9vrHEtkV4ICvBKpOc+/lV0ExvK+tUZ3u4=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B60120018 for <new-work@ietf.org>; Thu, 26 Sep 2019 15:44:25 -0700 (PDT)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: <new-work@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply_to: <iesg@ietf.org>
MIME-Version: 1.0
Message-ID: <156953786533.31837.10722928868596206978.idtracker@ietfa.amsl.com>
Date: Thu, 26 Sep 2019 15:44:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/E4h8QE2l_VUzwkiAEeoeCAiZNfQ>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.29
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/6Hd1INFQB5Ni1XMM_Az9wqIpYNA>
X-Mailman-Approved-At: Thu, 26 Sep 2019 15:54:22 -0700
Subject: [secdir] [new-work] WG Review: General Area Dispatch (gendispatch)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 22:44:53 -0000

A new IETF WG has been proposed in the General Area. The IESG has not made
any determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to the
IESG mailing list (iesg@ietf.org) by 2019-10-11.

General Area Dispatch (gendispatch)
Current status: Proposed WG

  Francesca Palombini <francesca.palombini@ericsson.com>
  Pete Resnick <resnick@episteme.net>

Assigned Area Director:
  Alissa Cooper <alissa@cooperw.in>

General Area Directors:
  Alissa Cooper <alissa@cooperw.in>

Mailing list:
  Address: gendispatch@ietf.org
  To subscribe:

Group page: https://datatracker.ietf.org/group/gendispatch/

Charter: https://datatracker.ietf.org/doc/charter-ietf-gendispatch/

The GENDISPATCH working group is a DISPATCH-style working group (see RFC
7957) chartered to consider proposals for new work in the GEN area, including
proposals for changes or improvements to the IETF process and process
documents. The working group is chartered to identify, or help create, an
appropriate venue for the work. The working group will not consider any
technical standardization work.

Guiding principles for the proposed new work include:

1. Providing a clear problem statement, historical context, motivation, and
deliverables for the proposed new work.

2. Ensuring there has been adequate mailing list discussion reflecting
sufficient interest, individuals have expressed a willingness to contribute
(if appropriate given the subject matter of the proposal) and there is WG
consensus before new work is dispatched.

3. Looking for and identifying commonalities and overlap amongst published or
ongoing work in the GEN area, within the IESG, or within the IETF LLC.

Options for handling new work include:

- Directing the work to an existing WG.

- Developing a proposal for a BOF.

- Developing a charter for a new WG.

- Making recommendations that documents be AD-sponsored (which ADs may or may
not choose to follow).

- Requesting that the the IESG or the IETF LLC consider taking up the work.

- Deferring the decision for the new work.

- Rejecting the new work.

If the group decides that a particular topic needs to be addressed by a new
WG, the normal IETF chartering process will be followed, including, for
instance, IETF-wide review of the proposed charter. Proposals for large work
efforts SHOULD lead to a BOF where the topic can be discussed in front of the
entire IETF community. Documents progressed as AD-sponsored would typically
include those that are extremely simple or make minor updates to existing
process documents.

Proposed new work may be deferred in cases where the WG does not have enough
information for the chairs to determine consensus. New work may be rejected
in cases where there is not sufficient WG interest or the proposal has been
considered and rejected in the past, unless a substantially revised proposal
is put forth, including compelling new reasons for accepting the work.

A major objective of the GENDISPATCH WG is to provide timely, clear
dispositions of new efforts. Thus, where there is consensus to take on new
work, the WG will strive to quickly find a home for it. While most new work
in the GEN area is expected to be considered in the GENDISPATCH working
group, there may be times where that is not appropriate. At the discretion of
the GEN AD, new efforts may follow other paths. For example, work may go
directly to a BOF, may be initiated in other working groups when it clearly
belongs in that group, or may be directly AD-sponsored.

Another major objective of the GENDISPATCH WG is to streamline how the IETF
community considers process improvements. Community discussions about process
suggestions that begin on other mailing lists, including ietf@ietf.org, will
be redirected to the GENDISPATCH mailing list where they will be facilitated
by the WG chairs. Proponents of process improvements will be encouraged to
craft concrete proposals for discussion on the GENDISPATCH mailing list, with
the goal of producing a concrete outcome in bounded time. Direct requests to
the IESG may also, after proper consideration, be redirected to the WG. For
proposals to be considered by the WG they will be expected to meet guiding
principle #1 above.

The existence of this working group does not change the IESG's
responsibilities as described in RFC 3710. Work related to the IAB, IRTF, and
RFC Editor processes is out of scope.

new-work mailing list