From ieprep-bounces@ietf.org  Wed Apr 20 17:46:25 2005
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 RAA24916
	for <ieprep-archive@ietf.org>; Wed, 20 Apr 2005 17:46:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DONCy-0001N3-GV
	for ieprep-archive@ietf.org; Wed, 20 Apr 2005 17:58:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOMzr-0007xA-Fh; Wed, 20 Apr 2005 17:44:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOMzk-0007vp-3e
	for ieprep@megatron.ietf.org; Wed, 20 Apr 2005 17:44:28 -0400
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 RAA24596
	for <ieprep@ietf.org>; Wed, 20 Apr 2005 17:44:25 -0400 (EDT)
Message-Id: <200504202144.RAA24596@ietf.org>
Received: from athena.hosts.co.uk ([212.84.175.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DONB1-0001FQ-K5
	for ieprep@ietf.org; Wed, 20 Apr 2005 17:56:08 -0400
Received: from [69.138.71.61] (helo=albers)
	by athena.hosts.co.uk with esmtpa (Exim 4.44) id 1DOMzZ-0005Kk-Pk
	for ieprep@ietf.org; Wed, 20 Apr 2005 22:44:19 +0100
From: "Ken Carlberg" <carlberg@g11.org.uk>
To: <ieprep@ietf.org>
Date: Wed, 20 Apr 2005 17:43:21 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcVF8fjVwcgLHvE3SI2sBiERHLKOjw==
X-Spam-Score: 0.1 (/)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] re-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.9 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

<warning: this is a bit lengthy and kind of resembles a noel-gram :) >

a couple of months ago there was a brief thread on this list that
discussed the possibility of rechartering IEPREP.  currently, the
charter focuses the attention of IEPREP to requirements and
framework documents.  

however, it had been pointed out in that re-chartering thread that 
there are several individual drafts floating in the I-D ether that 
have varying degrees of relevance to the subject of emergency 
communications, and yet don't seem to have a home.  at both the 
washington-ietf and the minneapolis-ietf (and actually earlier 
meetings if one wants to include some of the rsvp extention work) 
there were attempts to discuss these drafts at the TSVWG meetings, 
but there wasn't much reaction.   Joe Touch's comment at each 
meeting (my paraphrasing) that the "silence was deafening" seemed 
to capture the moment.  on the other hand, it also seemed that a 
considerable chunk of the material that Fred Baker discussed 
(ie, the MLPP drafts) was quite outside of the interest of the 
usual suspects that attend TSVWG.  there seemed to be considerably 
more discussion on Fred's and James's material at the San Diego 
IETF meeting than at the DC and Minneapolis combined -- the 
minutes of each meeting may bear this out, but then that is also 
dependent on who takes the minutes.

while I can't speak for Fred or James as to the reason their MLPP
drafts have been forwarded to TSVWG (one assumes because it is the
catch-all for transport area drafts that have no other home), I can
certainly see that the current charter of IEPREP prevented their
inclusion in IEPREP (because it only deals with requirements and
frameworks).

so that takes us to the subject of this long winded email.  

In the old charter thread, James suggested (words to the effect of) 
we should explore rechartering IEPREP so that it can now address the 
subject of solutions.  its my understanding that some folks at the 
Minneapolis IETF discussed this topic in the hallways, but I am in the 
dark as to the ultimate conclusions.  soooooo, I'd like to revisit this
discussion on the list.  specifially, 

   - what are the objections (if any) to expanding the charter?
     (and if the chairs/ADs have objections, now is the time to
	chime in :-)
   - assuming we have rough consensus of exploring the subject of
     re-chartering, what should the new charter say?

Note, and this is a whopper of a caveat!  All of us need to be in
agreement that *proposed solutions* could only be considered in 
IEPREP where no other *applicable* active working group exists.

Note #2...Perhaps a starting point for any discussion of a proposed
new charter is agreeing on what is considered a solution :-)

comments?

-ken


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


From ieprep-bounces@ietf.org  Thu Apr 21 00:09:20 2005
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 AAA28274
	for <ieprep-archive@ietf.org>; Thu, 21 Apr 2005 00:09:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DOTBa-0002Ow-31
	for ieprep-archive@ietf.org; Thu, 21 Apr 2005 00:21:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOSyZ-00062l-JW; Thu, 21 Apr 2005 00:07:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOSyY-00062g-GH
	for ieprep@megatron.ietf.org; Thu, 21 Apr 2005 00:07:38 -0400
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 AAA28123
	for <ieprep@ietf.org>; Thu, 21 Apr 2005 00:07:36 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DOT9t-0002Mj-IR
	for ieprep@ietf.org; Thu, 21 Apr 2005 00:19:22 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 20 Apr 2005 21:07:28 -0700
X-IronPort-AV: i="3.92,118,1112598000"; 
	d="scan'208"; a="630959219:sNHT39353998"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j3L47Phu000823;
	Wed, 20 Apr 2005 21:07:25 -0700 (PDT)
Received: from [10.32.244.219] (stealth-10-32-244-219.cisco.com
	[10.32.244.219])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j3L3wPE8005873;
	Wed, 20 Apr 2005 20:58:25 -0700
In-Reply-To: <200504202144.RAA24596@ietf.org>
References: <200504202144.RAA24596@ietf.org>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <e37f9f9146639f675fc1321110a55d4e@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] re-charter?
Date: Wed, 20 Apr 2005 21:07:23 -0700
To: "Ken Carlberg" <carlberg@g11.org.uk>
X-Mailer: Apple Mail (2.622)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1114055905.360984"; x:"432200"; a:"rsa-sha1"; b:"nofws:350";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"WohzcjL2vtup21o/ZlY6b1nM5lzD4/ZXXVAlMZEY2H9I2DSuUod8boyHYzbyF4KWar3Mi3G+"
	"YEMM4C/iU2oN3ift0nzgOXk0FTwGa3lTR3n6bGHwfdOHt+pgYwm8oOu/oOnfZa1Rtg4AXLrLTdz"
	"IJ2aPD7Ve4VNB1h53QTrzfE4="; c:"From: Fred Baker <fred@cisco.com>";
	c:"Subject: Re: [Ieprep] re-charter?";
	c:"Date: Wed, 20 Apr 2005 21:07:23 -0700"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
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: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

On Apr 20, 2005, at 2:43 PM, Ken Carlberg wrote:
> while I can't speak for Fred or James as to the reason their MLPP 
> drafts have been forwarded to TSVWG (one assumes because it is the 
> catch-all for transport area drafts that have no other home), I can 
> certainly see that the current charter of IEPREP prevented their 
> inclusion in IEPREP (because it only deals with requirements and 
> frameworks).

That is it in a nutshell.

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


From ieprep-bounces@ietf.org  Thu Apr 21 18:16:14 2005
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 SAA22757
	for <ieprep-archive@ietf.org>; Thu, 21 Apr 2005 18:16:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DOk9a-00073h-ER
	for ieprep-archive@ietf.org; Thu, 21 Apr 2005 18:28:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOjwB-0002S1-P3; Thu, 21 Apr 2005 18:14:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOjw9-0002Rw-TX
	for ieprep@megatron.ietf.org; Thu, 21 Apr 2005 18:14:18 -0400
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 SAA22544
	for <ieprep@ietf.org>; Thu, 21 Apr 2005 18:14:14 -0400 (EDT)
Received: from ellis.ad.nps.navy.mil ([131.120.18.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOk7d-00071Z-UF
	for ieprep@ietf.org; Thu, 21 Apr 2005 18:26:10 -0400
Received: from antony ([131.120.179.249]) by ellis.ad.nps.navy.mil with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Apr 2005 15:14:12 -0700
Subject: Re: [Ieprep] re-charter?
From: Rex Buddenberg <budden@nps.navy.mil>
To: Ken Carlberg <carlberg@g11.org.uk>
In-Reply-To: <200504202144.RAA24596@ietf.org>
References: <200504202144.RAA24596@ietf.org>
Content-Type: text/plain
Date: Thu, 21 Apr 2005 15:14:12 -0700
Message-Id: <1114121653.13043.45.camel@antony>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Apr 2005 22:14:12.0974 (UTC)
	FILETIME=[72DD70E0:01C546BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
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: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit

Ken,

Thanks for a thoughtful note ... and not too long.

When you apply any technology, and certainly internet technology, to the
problem of emergency services, a bunch of things pertain, not just the
technology ... or the protocols.

In my experience, the internet protocols are pretty good for emergency
services.  The critical issues are things like provisioning -- ensuring
enough elimination of single points of failure that the system doesn't
conk out under stress.  Is not a protocol issue at all -- indeed, the
very design of IP waaaay back when v4 was first set down did the
trick.  

To put this in academic terms, there are three principles of high
availability engineering:
	- elimination of single points of failure
	- reliable crossover
	- prompt detection of failures as they occur.

The first is a provisioning problem, not a protocol one.  The second is
a protocol design one, but been done for years.  The third is solved at
the protocol level by SNMP, but is also a provisioning one (ya gotta
implement it, and at appropriate levels of granularity).

So if an emergency services planner (no, not always an oxymoron) is
looking for a one-stop shop, he won't find it in the RFCs and won't find
it in the current IEPREP charter.  Same problem turned around to a
slightly different view: if the only thing we concentrate on is
protocols (my understanding of the current charter), then we miss some
really important parts of the problem and ones that are not very
susceptible to protocol solutions.  


I'd like to see the charter broadened to include best practices -- a
one-stop how-to kit for planners working emergency services comms (which
should include just about every municipality in the land -- yours too,
Ken).  


On Wed, 2005-04-20 at 17:43 -0400, Ken Carlberg wrote:
> <warning: this is a bit lengthy and kind of resembles a noel-gram :) >
> 
> a couple of months ago there was a brief thread on this list that
> discussed the possibility of rechartering IEPREP.  currently, the
> charter focuses the attention of IEPREP to requirements and
> framework documents.  
> 
> however, it had been pointed out in that re-chartering thread that 
> there are several individual drafts floating in the I-D ether that 
> have varying degrees of relevance to the subject of emergency 
> communications, and yet don't seem to have a home.  at both the 
> washington-ietf and the minneapolis-ietf (and actually earlier 
> meetings if one wants to include some of the rsvp extention work) 
> there were attempts to discuss these drafts at the TSVWG meetings, 
> but there wasn't much reaction.   Joe Touch's comment at each 
> meeting (my paraphrasing) that the "silence was deafening" seemed 
> to capture the moment.  on the other hand, it also seemed that a 
> considerable chunk of the material that Fred Baker discussed 
> (ie, the MLPP drafts) was quite outside of the interest of the 
> usual suspects that attend TSVWG.  there seemed to be considerably 
> more discussion on Fred's and James's material at the San Diego 
> IETF meeting than at the DC and Minneapolis combined -- the 
> minutes of each meeting may bear this out, but then that is also 
> dependent on who takes the minutes.
> 
> while I can't speak for Fred or James as to the reason their MLPP
> drafts have been forwarded to TSVWG (one assumes because it is the
> catch-all for transport area drafts that have no other home), I can
> certainly see that the current charter of IEPREP prevented their
> inclusion in IEPREP (because it only deals with requirements and
> frameworks).
> 
> so that takes us to the subject of this long winded email.  
> 
> In the old charter thread, James suggested (words to the effect of) 
> we should explore rechartering IEPREP so that it can now address the 
> subject of solutions.  its my understanding that some folks at the 
> Minneapolis IETF discussed this topic in the hallways, but I am in the 
> dark as to the ultimate conclusions.  soooooo, I'd like to revisit this
> discussion on the list.  specifially, 
> 
>    - what are the objections (if any) to expanding the charter?
>      (and if the chairs/ADs have objections, now is the time to
> 	chime in :-)
>    - assuming we have rough consensus of exploring the subject of
>      re-chartering, what should the new charter say?
> 
> Note, and this is a whopper of a caveat!  All of us need to be in
> agreement that *proposed solutions* could only be considered in 
> IEPREP where no other *applicable* active working group exists.
> 
> Note #2...Perhaps a starting point for any discussion of a proposed
> new charter is agreeing on what is considered a solution :-)
> 
> comments?
> 
> -ken
> 
> 
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
-- 
b


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


From ieprep-bounces@ietf.org  Fri Apr 22 07:40:55 2005
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 HAA08238
	for <ieprep-archive@ietf.org>; Fri, 22 Apr 2005 07:40:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DOwiN-0008Ia-NN
	for ieprep-archive@ietf.org; Fri, 22 Apr 2005 07:52:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOwVn-0006jl-KY; Fri, 22 Apr 2005 07:39:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOwVm-0006jg-Hy
	for ieprep@megatron.ietf.org; Fri, 22 Apr 2005 07:39:54 -0400
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 HAA08118
	for <ieprep@ietf.org>; Fri, 22 Apr 2005 07:39:53 -0400 (EDT)
Message-Id: <200504221139.HAA08118@ietf.org>
Received: from hermes.hosts.co.uk ([212.84.175.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOwhO-0008Fe-9q
	for ieprep@ietf.org; Fri, 22 Apr 2005 07:51:55 -0400
Received: from [69.138.71.61] (helo=albers)
	by hermes.hosts.co.uk with esmtpa (Exim 4.44)
	id 1DOwVT-0000Jm-4Q; Fri, 22 Apr 2005 12:39:36 +0100
From: "Ken Carlberg" <carlberg@g11.org.uk>
To: "'Rex Buddenberg'" <budden@nps.navy.mil>
Subject: RE: [Ieprep] re-charter?
Date: Fri, 22 Apr 2005 07:39:18 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcVGv7wxj2cXcmffR5Gj3xinzqPmkAAb9F9g
In-Reply-To: <1114121653.13043.45.camel@antony>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 2.0 (++)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
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.9 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

 
> I'd like to see the charter broadened to include best practices -- a
> one-stop how-to kit for planners working emergency services comms (which
> should include just about every municipality in the land -- yours too,
> Ken).  

another perspective beyond best common practices would be one of
an architectural document -- something not very common within the
IETF in the past, but now more commonly seen over the past couple of
years.

-ken


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


From mailman-bounces@ietf.org  Sun May  1 05:20:46 2005
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 FAA06905
	for <ieprep-archive@ietf.org>; Sun, 1 May 2005 05:20:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DSAqY-0001Xi-C0
	for ieprep-archive@ietf.org; Sun, 01 May 2005 05:34:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DSAcx-0000zH-JC
	for ieprep-archive@ietf.org; Sun, 01 May 2005 05:20:39 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: ieprep-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.4248.1114938205.21866.mailman@lists.ietf.org>
Date: Sun, 01 May 2005 05:03:25 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for ieprep-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ieprep@ietf.org                          totuar    
https://www1.ietf.org/mailman/options/ieprep/ieprep-archive%40ietf.org


From ieprep-bounces@ietf.org  Thu May  5 17:30:38 2005
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 RAA20994
	for <ieprep-archive@ietf.org>; Thu, 5 May 2005 17:30:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DToA0-0002Og-Te
	for ieprep-archive@ietf.org; Thu, 05 May 2005 17:45:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTnlK-0001bV-Cz; Thu, 05 May 2005 17:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DTnlF-0001Zy-AU; Thu, 05 May 2005 17:19:57 -0400
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 RAA18911;
	Thu, 5 May 2005 17:19:54 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DTnzc-0001UV-Be; Thu, 05 May 2005 17:34:48 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DTnlE-0007OZ-DH; Thu, 05 May 2005 17:19:56 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1DTnlE-0007OZ-DH@newodin.ietf.org>
Date: Thu, 05 May 2005 17:19:56 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ieprep chair <kimberly.s.king@saic.com>,
        Internet Architecture Board <iab@iab.org>,
        ieprep chair <sob@harvard.edu>, ieprep mailing list <ieprep@ietf.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Ieprep] Document Action: 'Framework for Supporting Emergency 
 Telecommunications Service (ETS) in IP Telephony' to Informational RFC 
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: b19722fc8d3865b147c75ae2495625f2

The IESG has approved the following document:

- 'Framework for Supporting Emergency Telecommunications Service (ETS) in IP 
   Telephony '
   <draft-ietf-ieprep-framework-10.txt> as an Informational RFC

This document is the product of the Internet Emergency Preparedness Working 
Group. 

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary
 
This document presents a framework for authorized emergency-related 
communication, specifically within the context of IP telephony. It is a genera
survey of existing prioritization technologies used in PSTN emergency calling 
systems and Internet-based quality-of-service mechanisms. In particular, it 
analyzes the capabilities of these technologies with respect to a few key 
scenarios for emergency-related communications.
 
Working Group Summary
 
The IEPREP WG supports the advancement of this document.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.


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


