Re: [Ieprep] proposed charter

"James M. Polk" <jmpolk@cisco.com> Tue, 26 September 2006 05:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GS5bD-0003TA-TD; Tue, 26 Sep 2006 01:35:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GS5bC-0003T5-FI for ieprep@ietf.org; Tue, 26 Sep 2006 01:35:18 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GS5bB-0000hz-4y for ieprep@ietf.org; Tue, 26 Sep 2006 01:35:18 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 25 Sep 2006 22:35:17 -0700
X-IronPort-AV: i="4.09,217,1157353200"; d="scan'208"; a="43573606:sNHT33849466"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k8Q5ZGqj008406; Tue, 26 Sep 2006 01:35:16 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k8Q5ZGuI011125; Tue, 26 Sep 2006 01:35:16 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Sep 2006 01:35:16 -0400
Received: from jmpolk-wxp.cisco.com ([10.89.16.53]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Sep 2006 01:35:15 -0400
Message-Id: <4.3.2.7.2.20060926002023.0357bed0@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 26 Sep 2006 00:35:14 -0500
To: curtis@occnc.com, ieprep@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] proposed charter
In-Reply-To: <200609260521.k8Q5LdcQ097727@workhorse.brookfield.occnc.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 26 Sep 2006 05:35:15.0940 (UTC) FILETIME=[8BA71A40:01C6E12D]
DKIM-Signature: a=rsa-sha1; q=dns; l=2717; t=1159248916; x=1160112916; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:Re=3A=20[Ieprep]=20proposed=20charter |To:curtis@occnc.com,=20ieprep@ietf.org; X=v=3Dcisco.com=3B=20h=3D6EtrC7P5eU6sA3JOAE7fXMnRud0=3D; b=KmZi4jx3CeZTdVgTLW1IaH1LXpnYzO+EzZT3lB1I/KEmB1cwBglpdlfVOPLR9jL0+wWY9Hsg rlMcR5OU2aCha7Z3ZyEju8ahz4Q7M8cu+EXdsoRj6usGAlnbDpw1B8r6;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc:
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>
Errors-To: ieprep-bounces@ietf.org

comments in-line

At 01:21 AM 9/26/2006 -0400, Curtis Villamizar wrote:

>Two people sent me private email pointing to the email message with
>the proposed charter.
>
>http://www1.ietf.org/mail-archive/web/ieprep/current/msg02421.html
>
>Thanks.
>
>Seems mostly reasonable to me.  One paragraph seems open ended and may
>be a source of trouble for other reasons.
>
>   If there is an existing group that can extend a protocol or
>   mechanism, IEPREP will generate only a requirements document for
>   those groups to evaluate. If there is not an existing group that can
>   extend a protocol or mechanism, IEPREP will prepare requirements and
>   discuss the extension of that protocol/mechanism or
>   protocols/mechanisms within IEPREP.
>
>This is a promise to liason with anybody and everbody that intends to
>work in this area and to step back and let that other group do the
>protocol work.

Correct, and this is what IEPREP has been limited to since its creation 
(i.e. it has only been able to do requirements, and no solutions)

>The IESG favors (with good reason) WG charters that
>propose to do work

ah, but IEPREP isn't allowed to *do* anything, only write requirements for 
other WGs to *do* something, and only *if* that WG decides to *do* anything 
with the requirement(s), which may get brushed asside as not interesting, 
or without significant WG interest (from that other WG).

RFC4412 took 6 years to get done due to lack of interest in another WG, yet 
the IEPREP WG could have done the work in 2.

>rather than WG charters that propose to sit back
>and watch the ITU do work in that area.

Well... the intention is to have IEPREP actually be able to extend 
protocols that don't currently have WGs chartered for said protocols, and 
it there are WGs for said protocols - to give those WGs merely the 
requirements.  This paragraph's intent is to state that IEPREP doesn't want 
to step on anyone's toes if a current WG charter elsewhere covers a desired 
piece of protocol work, and actually do the work if it isn't chartered 
anywhere else.

ITU-T is mentioned in a cooperative sense, but IEPREP isn't expecting to 
assign ITU-T work.

>A good example (and closely
>related to this sort of work) where the result coming from the ITU was
>not at all useful is the ITU QoS requirements work in the mid to late
>1990s.  This may be looking too much like more of the same.

<snip>

>Any effort which requires the whole world to agree before getting
>started will never get started.
>
>Curtis
>
>_______________________________________________
>Ieprep mailing list
>Ieprep@ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep

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