RE: [Ieprep] Discussion on Charter

"Ken Carlberg" <carlberg@g11.org.uk> Wed, 23 February 2005 23:16 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10601 for <ieprep-web-archive@ietf.org>; Wed, 23 Feb 2005 18:16:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D466r-0008EN-Cd for ieprep-web-archive@ietf.org; Wed, 23 Feb 2005 18:40:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3w7x-0006wV-9l; Wed, 23 Feb 2005 08:00:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3w7t-0006w1-Hs for ieprep@megatron.ietf.org; Wed, 23 Feb 2005 08:00:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13071 for <ieprep@ietf.org>; Wed, 23 Feb 2005 08:00:09 -0500 (EST)
Message-Id: <200502231300.IAA13071@ietf.org>
Received: from phobos.simply.net ([81.3.64.11]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D3wUI-0001fs-VD for ieprep@ietf.org; Wed, 23 Feb 2005 08:23:38 -0500
Received: (qmail 19430 invoked from network); 23 Feb 2005 12:59:34 -0000
Received: from pcp08471369pcs.towson01.md.comcast.net (HELO albers) (69.138.76.154) by phobos.simply.net with SMTP; 23 Feb 2005 12:59:34 -0000
From: Ken Carlberg <carlberg@g11.org.uk>
To: "'Bose, Pratik'" <pratik.bose@lmco.com>
Subject: RE: [Ieprep] Discussion on Charter
Date: Wed, 23 Feb 2005 07:59:26 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcUYZi2+2xlbyeqhRbC5NNL9/Gjh4wBP077Q
In-Reply-To: <37B6F612D86CA143B5F965E9EE8BD7AA05A1E111@emss04m14.us.lmco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

Traditionally, the strongest form of persuasion in the IETF is to have an
actual draft-RFC from which others can comment on, and in this case, decide
whether the document is a reasonable starting point to re-charter a group (or
if it should go into another group, remain an individual submission, or simply
expire).

the rare exception that comes to mind is the MANET wg, which recently migrated
its charter from experimental work to proposed standards.  But I doubt that the
exception will change the tradition.  If there are specific draft(s) that you'd
like to put forth that would cover the following, I'd encourage you or others
to submit them.

> - Preemption of Inelastic traffic sessions
> - Routing and QoS for nested VPNs
> - MLPP/GETS capabilities for application protocols like SIP, and
> signaling protocols like RSVP
> - etc. 

cheers,

-ken



_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep