From ieprep-bounces@ietf.org Tue Aug 01 12:51:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G7xSn-0006Kl-Cy; Tue, 01 Aug 2006 12:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G7xSl-0006Io-H9
	for ieprep@ietf.org; Tue, 01 Aug 2006 12:51:23 -0400
Received: from hermes.hosts.co.uk ([212.84.175.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7xSk-0001U9-8D
	for ieprep@ietf.org; Tue, 01 Aug 2006 12:51:23 -0400
Received: from [69.138.71.89] (helo=[192.168.1.2])
	by hermes.hosts.co.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.60)
	(envelope-from <carlberg@g11.org.uk>)
	id 1G7xSS-0005Sm-8t; Tue, 01 Aug 2006 17:51:04 +0100
In-Reply-To: <72EC7AFD-0960-4EF0-B628-B8972D80C927@cisco.com>
References: <72EC7AFD-0960-4EF0-B628-B8972D80C927@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BCC2E852-AC85-4870-8891-894FA2C9308D@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Ieprep] Preferential Services
Date: Tue, 1 Aug 2006 12:51:14 -0400
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: -1.4 (-)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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>
Errors-To: ieprep-bounces@ietf.org

> You know, I think one thing that trips this group up is in the  
> title. The issue this Working Group is thinking about is not so  
> much "Emergency use of the Internet", which is often about  
> deploying a new network when the usual one has been smashed by a  
> hurricane or an airplane crash, but "Precedence-related Services in  
> the Internet".
>
> Would it make sense, in this recharter, to call it "Preferential  
> Services" or some such thing?


I would agree with Fred.  whether we use the term Preferential or  
Prioritized (my personal favorite :), I believe we gain something by  
focusing on the core of what one wants to accomplish.

Emergency/disaster can then used to provide further context on what  
some interested parties wish to address given an ability to provide  
or use preferential/prioritized service.

my 2 cents,

-ken


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



From ieprep-bounces@ietf.org Tue Aug 01 13:13:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G7xoW-0006CY-K8; Tue, 01 Aug 2006 13:13:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G7xoV-0006As-8s
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:13:51 -0400
Received: from mail.manske.org ([65.127.251.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7xoT-0004BG-Qq
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:13:51 -0400
Received: from mail.manske.org (localhost.manske.org [127.0.0.1])
	by mail.manske.org (8.13.6/8.13.4) with ESMTP id k71HDkga060187
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ieprep@ietf.org>; Tue, 1 Aug 2006 12:13:46 -0500 (CDT)
	(envelope-from hcb@layer3arts.com)
Received: (from nobody@localhost)
	by mail.manske.org (8.13.6/8.13.4/Submit) id k71HDkoM060186
	for ieprep@ietf.org; Tue, 1 Aug 2006 12:13:46 -0500 (CDT)
	(envelope-from hcb@layer3arts.com)
X-Authentication-Warning: mail.manske.org: nobody set sender to
	hcb@layer3arts.com using -f
Received: from 24-182-173-239.dhcp.stls.mo.charter.com
	(24-182-173-239.dhcp.stls.mo.charter.com [24.182.173.239]) 
	by webmail.layer3arts.com (IMP) with HTTP 
	for <howard@localhost>; Tue, 01 Aug 2006 12:13:46 -0500
Message-ID: <1154452426.44cf8bcab5463@webmail.layer3arts.com>
Date: Tue, 01 Aug 2006 12:13:46 -0500
From: "Howard C. Berkowitz" <hcb@layer3arts.com>
To: ieprep@ietf.org
Subject: Re: [Ieprep] Preferential Services
References: <72EC7AFD-0960-4EF0-B628-B8972D80C927@cisco.com>
	<BCC2E852-AC85-4870-8891-894FA2C9308D@g11.org.uk>
In-Reply-To: <BCC2E852-AC85-4870-8891-894FA2C9308D@g11.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1
X-Originating-IP: 24.182.173.239
X-manske.org-MailScanner-Information: Please contact the ISP for more
	information
X-manske.org-MailScanner: Found to be clean
X-manske.org-MailScanner-From: hcb@layer3arts.com
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

Quoting ken carlberg <carlberg@g11.org.uk>:

> > You know, I think one thing that trips this group up is in the  
> > title. The issue this Working Group is thinking about is not so  
> > much "Emergency use of the Internet", which is often about  
> > deploying a new network when the usual one has been smashed by a  
> > hurricane or an airplane crash, but "Precedence-related Services in  
> > the Internet".
> >
> > Would it make sense, in this recharter, to call it "Preferential  
> > Services" or some such thing?
> 
> 
> I would agree with Fred.  whether we use the term Preferential or  
> Prioritized (my personal favorite :), I believe we gain something by  
> focusing on the core of what one wants to accomplish.
> 
> Emergency/disaster can then used to provide further context on what  
> some interested parties wish to address given an ability to provide  
> or use preferential/prioritized service.
> 
> my 2 cents,
> 
Your 2 cents are worth more than that, if you've provided an insight into
bounding two problems. One problem is prioritized/preferential communications,
which is an end-to-end service assuming the network can carry it.

"To provide" is the other part, which involves creating/preempting facilities or
ad hoc communications (not quite MANET, but MANET is worth reviewing) in not
just generic emergencies, but emergencies that involve significant damage to
network faciities, traffic overloads, or both.

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



From ieprep-bounces@ietf.org Tue Aug 01 13:33:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G7y7L-0003ch-Is; Tue, 01 Aug 2006 13:33:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G7y7K-0003cc-7M
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:33:18 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7y7I-0005aP-TS
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:33:18 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 01 Aug 2006 10:33:16 -0700
X-IronPort-AV: i="4.07,203,1151910000"; 
	d="scan'208"; a="309152699:sNHT55739550"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k71HXGRb032539; Tue, 1 Aug 2006 10:33:16 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k71HXGmS021261;
	Tue, 1 Aug 2006 10:33:16 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 Aug 2006 10:33:15 -0700
Received: from [10.32.244.220] ([10.32.244.220]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 Aug 2006 10:33:15 -0700
In-Reply-To: <1154452426.44cf8bcab5463@webmail.layer3arts.com>
References: <72EC7AFD-0960-4EF0-B628-B8972D80C927@cisco.com>
	<BCC2E852-AC85-4870-8891-894FA2C9308D@g11.org.uk>
	<1154452426.44cf8bcab5463@webmail.layer3arts.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C0807170-9885-4DA7-9C66-C8AC4D15B5DE@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Preferential Services
Date: Tue, 1 Aug 2006 10:33:14 -0700
To: "Howard C. Berkowitz" <hcb@layer3arts.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 01 Aug 2006 17:33:15.0815 (UTC)
	FILETIME=[92205B70:01C6B590]
DKIM-Signature: a=rsa-sha1; q=dns; l=1335; t=1154453596; x=1155317596;
	c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[Ieprep]=20Preferential=20Services;
	X=v=3Dcisco.com=3B=20h=3DWPtY3TxBz/+SSQoqA/q0EM4IutA=3D;
	b=Cuc+5SL96iIjkAP0kVUmmyknDPRhflHFz3YZUfkXKSg9kJESk122QAF0/5XUz0f+Qn2cUnhd
	xD3p6OF1ysyKuISzFsaO8Ti26mOwMMkxciiwjAwsE3d4Cbtiqp1kqMSx;
Authentication-Results: sj-dkim-8.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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>
Errors-To: ieprep-bounces@ietf.org

I think he is indeed getting at what I was getting at. The obvious  
use of preferential services is during emergencies, but this isn't  
actually about emergencies, it is about a preferential service.

Yes, emergency responders use manet networks among other things. I'm  
at a complete loss to say how the two issues became companded. 9/11  
was an instance in which telecommunications facilities were damaged,  
and that happened in Katrina as well. It didn't happen when that  
nutcase threw Sarin Gas into a subway in Tokyo, though, but I  
guarantee that the GETS-equivalent was used that day to punch calls  
through busy lines. Ditto recent bombings in London, Spain, and  
elsewhere.

Let's not add noise where we don't need it.

On Aug 1, 2006, at 10:13 AM, Howard C. Berkowitz wrote:

> Your 2 cents are worth more than that, if you've provided an  
> insight into
> bounding two problems. One problem is prioritized/preferential  
> communications,
> which is an end-to-end service assuming the network can carry it.
>
> "To provide" is the other part, which involves creating/preempting  
> facilities or
> ad hoc communications (not quite MANET, but MANET is worth  
> reviewing) in not
> just generic emergencies, but emergencies that involve significant  
> damage to
> network faciities, traffic overloads, or both.

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



From ieprep-bounces@ietf.org Tue Aug 01 13:44:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G7yHs-0006hD-M8; Tue, 01 Aug 2006 13:44:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G7yHs-0006fq-Cv
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:44:12 -0400
Received: from mail.manske.org ([65.127.251.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7yHq-0007zf-W3
	for ieprep@ietf.org; Tue, 01 Aug 2006 13:44:12 -0400
Received: from mail.manske.org (localhost.manske.org [127.0.0.1])
	by mail.manske.org (8.13.6/8.13.4) with ESMTP id k71Hi8VL061799
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ieprep@ietf.org>; Tue, 1 Aug 2006 12:44:08 -0500 (CDT)
	(envelope-from hcb@layer3arts.com)
Received: (from nobody@localhost)
	by mail.manske.org (8.13.6/8.13.4/Submit) id k71Hi8IV061798
	for ieprep@ietf.org; Tue, 1 Aug 2006 12:44:08 -0500 (CDT)
	(envelope-from hcb@layer3arts.com)
X-Authentication-Warning: mail.manske.org: nobody set sender to
	hcb@layer3arts.com using -f
Received: from 24-182-173-239.dhcp.stls.mo.charter.com
	(24-182-173-239.dhcp.stls.mo.charter.com [24.182.173.239]) 
	by webmail.layer3arts.com (IMP) with HTTP 
	for <howard@localhost>; Tue, 01 Aug 2006 12:44:08 -0500
Message-ID: <1154454248.44cf92e840d42@webmail.layer3arts.com>
Date: Tue, 01 Aug 2006 12:44:08 -0500
From: "Howard C. Berkowitz" <hcb@layer3arts.com>
To: ieprep@ietf.org
Subject: Re: [Ieprep] Preferential Services
References: <72EC7AFD-0960-4EF0-B628-B8972D80C927@cisco.com>
	<BCC2E852-AC85-4870-8891-894FA2C9308D@g11.org.uk>
	<1154452426.44cf8bcab5463@webmail.layer3arts.com>
	<C0807170-9885-4DA7-9C66-C8AC4D15B5DE@cisco.com>
In-Reply-To: <C0807170-9885-4DA7-9C66-C8AC4D15B5DE@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1
X-Originating-IP: 24.182.173.239
X-manske.org-MailScanner-Information: Please contact the ISP for more
	information
X-manske.org-MailScanner: Found to be clean
X-manske.org-MailScanner-From: hcb@layer3arts.com
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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

Quoting Fred Baker <fred@cisco.com>:

> I think he is indeed getting at what I was getting at. The obvious  
> use of preferential services is during emergencies, but this isn't  
> actually about emergencies, it is about a preferential service.
> 
> Yes, emergency responders use manet networks among other things. I'm  
> at a complete loss to say how the two issues became companded. 

They don't have to be, as long as the Wise Advisors make sure that 
  (1) standards-track mechanisms both support preferential service, which
      may require precedence, admission control, or preemption. All of these
      functions may be required in emergencies, but have nonemergency uses.
  (2) new interconnection protocols (e.g., VoIP peering) are not as purist
      as Official Standards Bodies might like, recognizing that sometimes
      a U does need to connect to the N if only a NNI is available, or
      vice versa.

>9/11  
> was an instance in which telecommunications facilities were damaged,  
> and that happened in Katrina as well. It didn't happen when that  
> nutcase threw Sarin Gas into a subway in Tokyo, though, but I  
> guarantee that the GETS-equivalent was used that day to punch calls  
> through busy lines. Ditto recent bombings in London, Spain, and  
> elsewhere.
> 
> Let's not add noise where we don't need it.
> 
> On Aug 1, 2006, at 10:13 AM, Howard C. Berkowitz wrote:
> 
> > Your 2 cents are worth more than that, if you've provided an  
> > insight into
> > bounding two problems. One problem is prioritized/preferential  
> > communications,
> > which is an end-to-end service assuming the network can carry it.
> >
> > "To provide" is the other part, which involves creating/preempting  
> > facilities or
> > ad hoc communications (not quite MANET, but MANET is worth  
> > reviewing) in not
> > just generic emergencies, but emergencies that involve significant  
> > damage to
> > network faciities, traffic overloads, or both.
> 



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



From ieprep-bounces@ietf.org Thu Aug 10 15:50:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBGYD-0003gZ-7b; Thu, 10 Aug 2006 15:50:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBGY6-0003F9-Li; Thu, 10 Aug 2006 15:50:34 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GBGY6-0003ke-JF; Thu, 10 Aug 2006 15:50:34 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GBGY4-0008M5-Dy; Thu, 10 Aug 2006 15:50:34 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 2ECF417592;
	Thu, 10 Aug 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GBGXZ-0002N4-IJ; Thu, 10 Aug 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GBGXZ-0002N4-IJ@stiedprstage1.ietf.org>
Date: Thu, 10 Aug 2006 15:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: ieprep@ietf.org
Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-domain-frame-07.txt 
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Emergency Preparedness Working Group of the IETF.

	Title		: A Framework for Supporting Emergency Telecommunications Services (ETS) Within a Single Administrative Domain
	Author(s)	: K. Carlberg
	Filename	: draft-ietf-ieprep-domain-frame-07.txt
	Pages		: 18
	Date		: 2006-8-10
	
This document presents a framework discussing the role of various
protocols and mechanisms that could be considered candidates for
supporting Emergency Telecommunication Services (ETS) within a single
administrative domain.  Comments about their potential usage as well
as their current deployment are provided to the reader.  Specific
solutions are not presented.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-domain-frame-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ieprep-domain-frame-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ieprep-domain-frame-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--





From ieprep-bounces@ietf.org Fri Aug 18 12:07:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GE6rE-0004kr-CO; Fri, 18 Aug 2006 12:06:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GE6rC-0004gb-Rp
	for ieprep@ietf.org; Fri, 18 Aug 2006 12:06:02 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GE6rB-00058S-L9
	for ieprep@ietf.org; Fri, 18 Aug 2006 12:06:02 -0400
Received: from ([128.244.97.181])
	by pilot.jhuapl.edu with ESMTP  id 5502123.3880333;
	Fri, 18 Aug 2006 12:05:37 -0400
Message-ID: <44E5E69E.7040403@jhuapl.edu>
Date: Fri, 18 Aug 2006 12:11:10 -0400
From: "Robert G. Cole" <robert.cole@jhuapl.edu>
User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sob@harvard.edu,  kimberly.s.king@saic.com, 
	jon.peterson@neustar.biz,  fluffy@cisco.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ieprep@ietf.org
Subject: [Ieprep] IEPREP WG recharter status request?
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

Scott,
Kimberly,
Jon,
Cullen,

Would you all please provide us with a status update with respect to the 
IEPREP WG rechartering activity?  What are the sticking points?  When 
and how is a decision going to be reached?

Thanks,

Bob Cole



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



