[Ieprep] About these recharter text suggestions... ?

"James M. Polk" <jmpolk@cisco.com> Fri, 07 July 2006 22:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyzDr-0002qI-7k; Fri, 07 Jul 2006 18:54:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyzDq-0002pi-Bt for ieprep@ietf.org; Fri, 07 Jul 2006 18:54:54 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyzDp-00028x-20 for ieprep@ietf.org; Fri, 07 Jul 2006 18:54:54 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 07 Jul 2006 15:54:52 -0700
X-IronPort-AV: i="4.06,219,1149490800"; d="scan'208"; a="327876038:sNHT51582430"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k67MsqZI029229 for <ieprep@ietf.org>; Fri, 7 Jul 2006 15:54:52 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k67MsqTQ008910 for <ieprep@ietf.org>; Fri, 7 Jul 2006 15:54:52 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jul 2006 15:54:52 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.120.207]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jul 2006 15:54:51 -0700
Message-Id: <4.3.2.7.2.20060707174632.03293c60@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 07 Jul 2006 17:54:51 -0500
To: ieprep@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 07 Jul 2006 22:54:52.0030 (UTC) FILETIME=[5B3D59E0:01C6A218]
DKIM-Signature: a=rsa-sha1; q=dns; l=1018; t=1152312892; x=1153176892; c=relaxed/simple; s=sjdkim2001; 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:About=20these=20recharter=20text=20suggestions...=20?; X=v=3Dcisco.com=3B=20h=3DZI2kdd+gtSE9IxNNOwwadMYqygo=3D; b=deQGOOme4LINUSmPnfqesH7CLAQ6fA8/EeqUf8inrEOqMGpvcYzXabu5mO1vOaCThS9xbWdM 1HjawngNeRUahoOFQmyYV6nZz02+W1ovnE8Vtsj+6zlRz4yzBfogos0J;
Authentication-Results: sj-dkim-2.cisco.com; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [Ieprep] About these recharter text suggestions... ?
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

All

It appears to me that some on our list want to move away from what ieprep 
was orignially founded upon - disaster related communications, and towards, 
seemingly exclusively, military communications.

I, for one, do not agree with this revolutionary shift.

I believe we need to shift from a generally informative WG to a standards 
track WG.

By this I mean to shift our focus on developing informative requirements 
documents that we, in ieprep, will be able to solve through standards 
track, or BCP, documents generated and discussed to the point of consensus, 
by us - in this WG.

I am reading lately offerings and suggestions to make this WG all about 
MLPP, and I don't believe we need to make it only about MLPP, rather, we 
need to add MLPP functionality to what we can standardize.

IEPREP can do a lot more in the area of disaster related communications, 
and we should not completely shift away from addressing that area, which is 
not fully addressed within our RFCs to date.

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