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

Janet P Gunn <jgunn6@csc.com> Thu, 02 November 2006 21:50 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfkRl-0006i9-Nm; Thu, 02 Nov 2006 16:50:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfkRk-0006f8-QA for ieprep@ietf.org; Thu, 02 Nov 2006 16:50:00 -0500
Received: from amer-mta08.csc.com ([20.137.52.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GfkRj-0002Q1-Fd for ieprep@ietf.org; Thu, 02 Nov 2006 16:50:00 -0500
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta08.csc.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id kA2LnvSA018397 for <ieprep@ietf.org>; Thu, 2 Nov 2006 16:49:57 -0500 (EST)
To: ieprep@ietf.org
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OF19ECFF28.55513735-ON8525721A.0077DF80-8525721A.0077ECC8@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Thu, 2 Nov 2006 16:49:54 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 6.5.3|September 14, 2004) at 11/02/2006 04:48:50 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Subject: [Ieprep] Fw: 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








----- Forwarded by Janet P Gunn/FED/CSC on 11/02/2006 04:49 PM -----

Sam Hartman <hartmans@mit.edu> wrote on 11/02/2006 02:30:43 PM:

> >>>>> "James" == James M Polk <jmpolk@cisco.com> writes:
>
>     James> At 12:41 PM 11/2/2006 +0200, Pekka Savola wrote:
>     >> On Wed, 1 Nov 2006, Sam Hartman wrote: > I don't believe the
>     >> new charter of ieprep working group belongs in the > IETF.  I
>     >> understand why we chartered it here, and I believe that by >
>     >> doing as much work as we have done so far in the IETF, we have
>     >> done > something useful.  We've described the broad problem and
>     >> have helped > to explain how it fits in the Internet context.
>     >> That was an important > thing for us to do.
>     >>
>     >> I think I'll agree with Sam.
>
>     James> I do not agree with Sam
>
>     >> Having looked at the output of the WG, it already seems to
>     >> include a couple of useful framework documents and about 4
>     >> requirements documents.
>
>     James> the framework RFCs are for within a single public domain.
>     James> The other RFCs are requirements based.
>
>     James> There is no architecture guidelines docs or peering
>     James> guidelines or the like.
>
> Why does that belong in the IETF?  RFC 2418 gives a good set of things
> to consider for determining whether work belongs in the IETF.  I will
> try to write up a guideline by guideline analysis of this work,
> although when I briefly examine the guidelines my continuing reaction
> is that the work probably does not belong in the IETF.  If you have
> time to write up such an analysis I'd be interested in what you come
> up with.
>
>     >> This should already provide sufficient information how to
>     >> continue the work.
>
>     James> continue the work.... where? by who? by another SDO?  Why?
>
>
> My proposal is ITU-T--probably SG 13, although I don't understand ITU
> internals enough to know for sure that's the right place.
>
> Obviously, this assumes they want to do the work.
>
> To propose concrete action, I think the IETF should draft a liaison
> statement for action to the ITU asking for them to comment on whether
> they see any current conflicts and on whether there are parts of this
> work they would be interested in picking up.  Such liaisons are not
> uncommon when appropriate; we had such an exchange with IEEE when the
> trill working group was formed.
>
>
> If the ITU says that they're not interested in these aspects of the
> work, and no one else makes an alternative proposal, then I would not
> object to the work being chartered in the IETF.  However if the ITU
> would be interested in working on this problem space (or especially is
> already work on this problem space), we need to carefully ask
> ourselves why each aspect of the work being done in the IETF belongs
> here.
>
>
> --Sam
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


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