[Ieprep] Discussion on Charter

"Bose, Pratik" <pratik.bose@lmco.com> Wed, 23 February 2005 04:01 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 XAA27140 for <ieprep-web-archive@ietf.org>; Tue, 22 Feb 2005 23:01:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3o5H-0007HB-VO for ieprep-web-archive@ietf.org; Tue, 22 Feb 2005 23:25:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3UEo-0002iE-BR; Tue, 22 Feb 2005 02:13:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3MDA-0001xD-0R for ieprep@megatron.ietf.org; Mon, 21 Feb 2005 17:39: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 RAA23563 for <ieprep@ietf.org>; Mon, 21 Feb 2005 17:39:20 -0500 (EST)
Received: from mailgw3a.lmco.com ([192.35.35.7]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3MZQ-0007Fq-OR for ieprep@ietf.org; Mon, 21 Feb 2005 18:02:30 -0500
Received: from emss04g01.ems.lmco.com (relay4.ems.lmco.com [166.17.13.122]) by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id j1LMdKrx021919 for <ieprep@ietf.org>; Mon, 21 Feb 2005 17:39:20 -0500 (EST)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30884) id <0ICA00K019LKIY@lmco.com> for ieprep@ietf.org; Mon, 21 Feb 2005 17:39:20 -0500 (EST)
Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF V6.1-1X6 #30884) with ESMTP id <0ICA00F279LKMQ@lmco.com> for ieprep@ietf.org; Mon, 21 Feb 2005 17:39:20 -0500 (EST)
Received: from EMSS04M14.us.lmco.com ([162.16.20.50]) by EMSS04I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 21 Feb 2005 17:39:19 -0500
Date: Mon, 21 Feb 2005 17:39:19 -0500
From: "Bose, Pratik" <pratik.bose@lmco.com>
To: ieprep@ietf.org
Message-id: <37B6F612D86CA143B5F965E9EE8BD7AA05A1E111@emss04m14.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: Discussion on Charter
Thread-Index: AcUYZi2+2xlbyeqhRbC5NNL9/Gjh4w==
content-class: urn:content-classes:message
X-OriginalArrivalTime: 21 Feb 2005 22:39:19.0824 (UTC) FILETIME=[2EA54100:01C51866]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: [Ieprep] Discussion on Charter
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.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

To the IEPREP List Members and WG Chairs, 

In the past few IETFs, there has been a growing movement to standardize
the following capabilities via updates to existing standards or new
internet drafts: 

- 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. 

targeting the emergency preparedness of standards based civilian and
military networks. However, there is a no single home for this effort
till date and any activity currently has been following the route of
vetting at IEPREP and then WG acceptance in different WGs (for ex,
SIPPING, TSVWG etc.)

In the interest of various vendors, system integrators (for ex. like my
employer Lockheed Martin), as well as end customers (usually various
governments) who are developing these solutions, it would be efficient
to either recharter IEPREP so that it itself  can standardize such
capabilities or consider the formation of a new WG which can address
this particular area. 

It would be good if we can broach the above topic in mailing list
discussions and at the next WG meeting. 

Thanks, 

Pratik






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