[Ieprep] Re: WG Review: Recharter of Internet Emergency Preparedness (ieprep)

Fred Baker <fred@cisco.com> Thu, 09 November 2006 21:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiHJS-00082M-8a; Thu, 09 Nov 2006 16:19:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiHJQ-0007yU-64; Thu, 09 Nov 2006 16:19:52 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiHJO-0004yA-5h; Thu, 09 Nov 2006 16:19:52 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 09 Nov 2006 13:19:48 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kA9LJl7b004406; Thu, 9 Nov 2006 13:19:47 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA9LJlin018615; Thu, 9 Nov 2006 13:19:47 -0800 (PST)
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.1830); Thu, 9 Nov 2006 13:19:47 -0800
Received: from [12.105.242.217] ([10.21.121.241]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Nov 2006 13:19:46 -0800
In-Reply-To: <tslu01dfuvu.fsf@cz.mit.edu>
References: <tslhcxihmw3.fsf@cz.mit.edu> <E1GfLJY-0003B5-Pg@ietf.org> <tslhcxihmw3.fsf@cz.mit.edu> <4.3.2.7.2.20061102124821.03caff08@email.cisco.com> <Pine.LNX.4.64.0611022301130.25516@netcore.fi> <454CEAA2.1040204@zurich.ibm.com> <6A5DDA18-6F3A-4AC2-A2D2-7FF8718404AB@cisco.com> <tslu01dfuvu.fsf@cz.mit.edu>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <886A0864-E3CF-426E-B907-E8CE7064E65F@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Thu, 9 Nov 2006 13:19:43 -0800
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 09 Nov 2006 21:19:46.0839 (UTC) FILETIME=[C8510A70:01C70444]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1566; t=1163107187; x=1163971187; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20WG=20Review=3A=20Recharter=20of=20Internet=20Emergenc y=20Preparedness=20(ieprep) |Sender:=20; bh=F+Pr7Gwj2mKk6e4Z+FLwpAmAPUs0ZENKHIaV4U5g4G0=; b=FrZ57s0GZlI+EiORAnTWafsANp+K0V/DCEaeGyriSGusi84SpWAmlrkF2038bjzvXXnmiFns zRyj/PiVPI0h7pJcyF20yAh6dz8Sz3b5kCGm/QY5pLObNkwG9jolzDjg;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (si g from cisco.com/sjdkim1002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Pekka Savola <pekkas@netcore.fi>, ieprep@ietf.org, Kimberly King <kimberly.s.king@saic.com>, Brian E Carpenter <brc@zurich.ibm.com>, Scott Bradner <sob@harvard.edu>, ietf@ietf.org
Subject: [Ieprep] Re: WG Review: Recharter of Internet Emergency Preparedness (ieprep)
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

I didn't write the proposed charter, and I don't intend to manage the  
next instance of the working group either. I will collaborate with  
the chairs on a charter if you like.

The key thing, though, is actually not this charter, as important as  
it is. It is the IETF leadership taking it upon itself to enable the  
work to progress in a timely fashion rather than having an infinite  
series of hurdles and road-blocks thrown in the way. Can you help us  
with that?

On Nov 5, 2006, at 1:25 PM, Sam Hartman wrote:

>>>>>> "Fred" == Fred Baker <fred@cisco.com> writes:
>
>     Fred> I have to say that my discussions with US DoD and DHS/NCS,
>     Fred> and with their counterparts in other countries, doesn't
>     Fred> suggest that the set of technical mechanisms is all
>     Fred> specified. If we're looking only at voice, it is maybe so,
>     Fred> but they're not looking only at voice.  Questions abound
>     Fred> around the mechanisms for sending an email and ensuring that
>     Fred> it is delivered in a stated time interval on the order of
>     Fred> minutes or that an indication of failure is returned to the
>     Fred> sender, and other things.
>
> Fred, if there are parts of the problem that clearly fall within the
> IETF, can you work on a narrowly focused charter that clearly says
> what you're going to work on and shows:
>
> 1) Why it is within the IETF's scope
>
> 2) What you plan to do?
>
> From the current charter I would have no idea at all that you were
> talking about email.
>
> --Sam

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