[secdir] [New-work] WG Review: Dispatch (dispatch)

IESG Secretary <iesg-secretary@ietf.org> Wed, 18 March 2009 14:37 UTC

Return-Path: <secdir-bounces@mit.edu>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8A9628C17E for <secdir@core3.amsl.com>; Wed, 18 Mar 2009 07:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level:
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-OSiBclVSrh for <secdir@core3.amsl.com>; Wed, 18 Mar 2009 07:37:06 -0700 (PDT)
Received: from pch.mit.edu (PCH.MIT.EDU [18.7.21.90]) by core3.amsl.com (Postfix) with ESMTP id 98AEB28C1FF for <secdir@ietf.org>; Wed, 18 Mar 2009 07:37:02 -0700 (PDT)
Received: from pch.mit.edu (pch.mit.edu [127.0.0.1]) by pch.mit.edu (8.13.6/8.12.8) with ESMTP id n2IEbkG3003584 for <secdir@ietf.org>; Wed, 18 Mar 2009 10:37:46 -0400
Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.13.6/8.12.8) with ESMTP id n2IEbiZr003571 for <secdir@PCH.mit.edu>; Wed, 18 Mar 2009 10:37:45 -0400
Received: from mit.edu (M24-004-BARRACUDA-2.MIT.EDU [18.7.7.112]) by pacific-carrier-annex.mit.edu (8.13.6/8.9.2) with ESMTP id n2IEbZne007811 for <secdir@mit.edu>; Wed, 18 Mar 2009 10:37:35 -0400 (EDT)
Received: from mail.ietf.org (localhost [127.0.0.1]) by mit.edu (Spam Firewall) with ESMTP id 9728715F57DA for <secdir@mit.edu>; Wed, 18 Mar 2009 10:37:34 -0400 (EDT)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by mit.edu with ESMTP id yfWEt8DX2N6AzLD9 for <secdir@mit.edu>; Wed, 18 Mar 2009 10:37:34 -0400 (EDT)
Received-SPF: pass (mit.edu: domain of new-work-bounces@ietf.org designates 64.170.98.32 as permitted sender) receiver=mit.edu; client_ip=64.170.98.32; envelope-from=new-work-bounces@ietf.org;
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 062F828C202; Wed, 18 Mar 2009 07:36:40 -0700 (PDT)
X-Original-To: new-work@ietf.org
Delivered-To: new-work@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 846FD28C0E6; Wed, 18 Mar 2009 07:36:38 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: new-work@ietf.org
Mime-Version: 1.0
Message-Id: <20090318143638.846FD28C0E6@core3.amsl.com>
Date: Wed, 18 Mar 2009 07:36:38 -0700
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
X-Scanned-By: MIMEDefang 2.42
X-BeenThere: secdir@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: secdir-bounces@mit.edu
Errors-To: secdir-bounces@mit.edu
X-Mailman-Approved-At: Thu, 19 Mar 2009 03:14:08 -0700
Subject: [secdir] [New-work] WG Review: Dispatch (dispatch)
X-BeenThere: secdir@ietf.org
Reply-To: iesg@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Mar 2009 14:37:07 -0000

A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area.  The IESG has not made any determination as 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 Wednesday, March 25, 2009.

Dispatch (dispatch)
-------------------------------------------------- 
Last Modified: 2009-03-12

Current Status: Proposed Working Group

Group Description: 

The Dispatch working group is chartered to consider proposals for
  new work in the RAI area and identify, or help create, an appropriate
  venue for the work. Options for handling new work include:

  - Assigning the work to an existing WG.
  - Developing a proposal for a BOF.
  - Developing a charter and establishing consensus for a new WG
    or Exploratory Group. This option will primarily be used with
    fairly mature and well-defined efforts.
  - Rejecting and deferring work.

  A major objective of the DISPATCH WG is to provide timely, clear
  dispositions of new efforts. Where there is consensus to take
  on new work, the WG will strive to quickly find a home for it.
  Reconsideration of proposals which have failed to gather consensus
  will be prioritized behind proposals for new work which have not
  yet been considered. In general, requests for reconsideration
  should only be made once a proposal has been significantly
  revised.

  The DISPATCH WG will also operate as an area wide WG where ideas can
  be discussed that do not currently have a logical venue for the work
  to be done. As part of this function, the WG will evaluate SIP Event
  Packages that were not developed inside some other area working group.

  Guiding principles will include:

  1. Providing a clear problem statement for proposed new work.

  2. Prioritizing new efforts so that RAI does not take on more work
     than it can effectively complete.

  3. Looking for commonalities among ongoing development efforts.
     Such commonalities may indicate the need to develop more
     general, reusable components.

  4. Protecting the architectural integrity of RAI protocols and  
ensuring that work has general applicability.

  The WG may take on some of the previous work items from the SIPPING
working group to allow a smooth transition. If the group decides  
that a particular topic needs to be addressed by a new or existing WG,
this is still followed by the usual IETF chartering process, including,
for instance, IETF-wide review of the proposed changes. Proposal for large
work efforts SHOULD lead to a BOF where the topic can be discussed in
front of the entire IETF community.


Milestones:
    TBD
_______________________________________________
New-work mailing list
New-work@ietf.org
https://www.ietf.org/mailman/listinfo/new-work
_______________________________________________
secdir mailing list
secdir@mit.edu
https://mailman.mit.edu/mailman/listinfo/secdir