From mailnull@www1.ietf.org  Mon Mar  3 17:01:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14546
	for <ieprep-archive@odin.ietf.org>; Mon, 3 Mar 2003 17:01:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h23MC6h31341
	for ieprep-archive@odin.ietf.org; Mon, 3 Mar 2003 17:12:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23MC5p31338
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 3 Mar 2003 17:12:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14520
	for <ieprep-web-archive@ietf.org>; Mon, 3 Mar 2003 17:01:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23M7Dp30828;
	Mon, 3 Mar 2003 17:07:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23M6Fp30403
	for <ieprep@optimus.ietf.org>; Mon, 3 Mar 2003 17:06:15 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14348
	for <ieprep@ietf.org>; Mon, 3 Mar 2003 16:55:33 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z0Z726>; Mon, 3 Mar 2003 16:55:43 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410A414B75@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Folts, Harold'" <foltsh@ncs.gov>,
        "ieprep List (E-mail)"
	 <ieprep@ietf.org>
Subject: RE: [Ieprep] ITU-T Workshop on Telecommunications for Disaster Re
	lief
Date: Mon, 3 Mar 2003 16:53:57 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

Could someone who attended this please give us a summary, especially
anything relevant to ieprep.

Thanks


-----Original Message-----
From: Folts, Harold [mailto:foltsh@ncs.gov]
Sent: Monday, February 03, 2003 8:41 AM
To: ieprep List (E-mail)
Subject: [Ieprep] ITU-T Workshop on Telecommunications for Disaster
Relief


The ITU-T has organized a three-day workshop in Emergency Telecommunications
in Geneva, Switzerland, February 17-19, 2003. You can find more information
at http://www.itu.int/ITU-T/worksem/ets/. The event has a close relationship
with the considerations being addressed by ieprep. It is a fully open event
and ieprep participants will be most welcome to participate.

Hal


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



From mailnull@www1.ietf.org  Wed Mar  5 09:49:11 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01983
	for <ieprep-archive@odin.ietf.org>; Wed, 5 Mar 2003 09:49:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25F0Aa31624
	for ieprep-archive@odin.ietf.org; Wed, 5 Mar 2003 10:00:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25F0A531621
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 10:00:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01967
	for <ieprep-web-archive@ietf.org>; Wed, 5 Mar 2003 09:48:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Ewb531457;
	Wed, 5 Mar 2003 09:58:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Npi524879
	for <ieprep@optimus.ietf.org>; Tue, 4 Mar 2003 18:51:44 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15542;
	Tue, 4 Mar 2003 18:40:30 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h24NgXZ09182;
	Tue, 4 Mar 2003 15:42:33 -0800 (PST)
Message-Id: <200303042342.h24NgXZ09182@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, ieprep@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 04 Mar 2003 15:42:33 -0800
Subject: [Ieprep] RFC 3487 on Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP)
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3487

        Title:      Requirements for Resource Priority Mechanisms for
                    the Session Initiation Protocol (SIP)
        Author(s):  H. Schulzrinne
        Status:     Informational
        Date:       February 2003
        Mailbox:    schulzrinne@cs.columbia.edu
        Pages:      17
        Characters: 39615
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ieprep-sip-reqs-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3487.txt


This document summarizes requirements for prioritizing access to
circuit-switched network, end system and proxy resources for
emergency preparedness communications using the Session Initiation
Protocol (SIP).

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <030304154049.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3487

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3487.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <030304154049.RFC@RFC-EDITOR.ORG>

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



From mailnull@www1.ietf.org  Wed Mar  5 11:09:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09406
	for <ieprep-archive@odin.ietf.org>; Wed, 5 Mar 2003 11:09:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h25GKhc08727
	for ieprep-archive@odin.ietf.org; Wed, 5 Mar 2003 11:20:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25GKh508724
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 11:20:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09389
	for <ieprep-web-archive@ietf.org>; Wed, 5 Mar 2003 11:09:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25GJ8508542;
	Wed, 5 Mar 2003 11:19:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25GId508478
	for <ieprep@optimus.ietf.org>; Wed, 5 Mar 2003 11:18:39 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09308
	for <ieprep@ietf.org>; Wed, 5 Mar 2003 11:07:04 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (8.12.8/8.12.6) with ESMTP id h25G8hJp023348
	for <ieprep@ietf.org>; Wed, 5 Mar 2003 09:08:43 -0700 (MST)
Received: from USAZ107115SVR20 ([130.131.166.68]) by
          pxmail1.agcs.com (Netscape Messaging Server 4.15 pxmail1 Mar  5
          2002 15:11:07) with SMTP id HBAA7600.LW0 for <ieprep@ietf.org>;
          Wed, 5 Mar 2003 09:09:06 -0700 
Received: FROM agcs.com BY USAZ107115SVR20 ; Wed Mar 05 09:09:05 2003 -0700
Message-ID: <3E662120.7CB75989@agcs.com>
Date: Wed, 05 Mar 2003 09:09:04 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Gunn Janet" <Janet.Gunn@dyncorp.com>
CC: "ieprep List (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] ITU-T Workshop on Telecommunications for Disaster Relief
References: <CBED705A7FD2D311865500508B1089410A414B75@chntex02.is.dyncorp.com>
Content-Type: multipart/mixed;
 boundary="------------3BA4D518C6723A1C499C5897"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

This is a multi-part message in MIME format.
--------------3BA4D518C6723A1C499C5897
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


Janet,

I was fortunate enough to have attended, and spoke at, the ITU-T Workshop on
Telecommunications for Disaster Relief (TDR), and I am happy to respond to your
request by sharing my personal observations.  The presentations may be found at:

http://www.itu.int/ITU-T/worksem/ets/program.html

This is my  attempt to distill a few "take aways" from three full days of
presentations.

I found that the workshop accomplished the goal of the organizers by
communicating information between a diverse collection of experts involved in
different aspects of TDR. In addition to ITU-T members, T1, ETSI, and IETF were
invited to attend. We had a bit over 100 people register for the workshop.

The purpose of the workshop was to improve everybody’s understanding of the
telecommunication requirements. Need to have a common understanding if we hope
to agree on solutions. We need to recognize the different national policies. TDR
provides preferential treatment for government authorized users. Funding and
regulatory factors are major issues that need to be resolved. The current
infrastructure will be converting to multimedia, broadband, etc. We must address
the interworking with the legacy networks as well as with the new technology.
Availability, quality, and security are needed for communications during times
of disaster.

Almost every speaker from the user committee mentioned Cyber war, and the USA
ranked its adverse impact on telecommunications as being exceeded only by
nuclear war!

The speakers reconfirmed during a Q & A session that SIP based networks do not
recognize national boundaries. The DTR mechanisms that eventually emerge must be
sufficiently secure so that a country's national ETS is not compromised by
preference communication attacks.

Keep it simple. Keep it reliable. Make it affordable. Make it interconnect. Make
it backward compatible. Need it now.  Some degraded QoS is better than no
communication.

Disasters have a pre, during, and post life. Disasters cause billions and
billions of dollars of loss and loss of life. We need to shift from disaster
relief to disaster prevention.

Emphasis is on decentralized communication facilities. Emphasis is on mobile
technologies. ITU-R is addressing spectrum issues.

Affected countries have tended to have very poor infrastructure to start with
prior to the disaster. Going toward TCP/IP over satellite links. Last mile is
still a problem, which may be addressed by WiFi.

Tools used by different agencies are very different and do not interwork. Need
standardization to be able to coordinate.

Try to use the local facilities and a combination of them for backup should
infrastructure be destroyed. Want something simple to use (5 minutes training),
low cost, world wide cross boarder.

Network saturation and unavailability when disaster strikes is a problem. They
need to be given priority when there is congestion. Mobility, interoperability,
and universal conductivity are required. The network needs different levels of
QoS depending on user and application. Voice is (or shortly will) no longer the
primary communication tool.

Users need simple and cheap systems. The biggest problem is often the power
supply. Voice is needed first and the e-mail, Internet and fax. Survivors also
need access to telephones (mobile stations) to contact relatives. Third world
often is not able to use the existing technology, and does not need even more
complicated systems.

Put the needed capability in the NGN now rather than having to retrofit later!

ETS requirements are not market driven. Needs regulator backing. If the private
sector does not voluntarily respond accordingly, then the requirements may
become mandatory.

Interworking Public Safety Organizations with Different Technologies: Key
problems are more operational than technical. Most of the problems are
communication to remote sites.

VoIP needs extendable labels to indicate that it is a emergency call.

Need to map the PSTN indicator to SIP and back

Voice is the minimum service. Local access and conductivity are essential. SMS,
reliable E-mail with attachments, high-resolution graphics, video needs are
coming. Seemed to indicate that much use of the public Internet will be made use
of rather than a managed Intranet. Some service is better than no service. Multi
media, especially over wireless, is the direction to go in.

Minimize DoS attacks by authenticating user is truly authorized for TDR. In
packet networks the flow of packets also needs to be confirmed as being TDR. In
the Internet the concept of trusted network, as used in the PSTN, is absence.

Cannot obsolete existing facilities are now in use.  Establish technical
standards that are RESPONSIVE to disaster relief requirements. Authentication is
essential to prevent abuse of preferential service. It is better to communicate
with difficulty than to not communicate at all. Keep the local interfaces as
simple as possible and keep the additional costs down. Harmonize the different
levels of priority in the different protocols.  Discussed steering committee
terms of reference to keep the work going and to harmonize the various efforts.

Second workshop mid 2004. Work is contribution driven.  Need more input from the
people with real experience in dealing with disasters.

"Gunn, Janet" wrote:

> Could someone who attended this please give us a summary, especially
> anything relevant to ieprep.
>
> Thanks
>
> -----Original Message-----
> From: Folts, Harold [mailto:foltsh@ncs.gov]
> Sent: Monday, February 03, 2003 8:41 AM
> To: ieprep List (E-mail)
> Subject: [Ieprep] ITU-T Workshop on Telecommunications for Disaster
> Relief
>
> The ITU-T has organized a three-day workshop in Emergency Telecommunications
> in Geneva, Switzerland, February 17-19, 2003. You can find more information
> at http://www.itu.int/ITU-T/worksem/ets/. The event has a close relationship
> with the considerations being addressed by ieprep. It is a fully open event
> and ieprep participants will be most welcome to participate.
>
> Hal
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

--------------3BA4D518C6723A1C499C5897
Content-Type: text/x-vcard; charset=us-ascii;
 name="goldmans.vcf"
Content-Description: Card for Stuart (Stu) Goldman
Content-Disposition: attachment;
 filename="goldmans.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Goldman;-Stuart
tel;cell:623 582 7136
tel;fax:623 582 7111
tel;home:602 493 8438  
tel;work:623 582 7136
x-mozilla-html:TRUE
org:AG Communication Systems
adr:;;P.O. Box 52179;Phoenix;AZ;85072-2179;USA
version:2.1
email;internet:sgoldman@lucent.com
x-mozilla-cpt:;-23496
fn:Stuart Goldman
end:vcard

--------------3BA4D518C6723A1C499C5897--

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



From mailnull@www1.ietf.org  Thu Mar  6 06:35:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04461
	for <ieprep-archive@odin.ietf.org>; Thu, 6 Mar 2003 06:35:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h26BkvG27285
	for ieprep-archive@odin.ietf.org; Thu, 6 Mar 2003 06:46:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BkvO27282
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 6 Mar 2003 06:46:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04392
	for <ieprep-web-archive@ietf.org>; Thu, 6 Mar 2003 06:35:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BijO27134;
	Thu, 6 Mar 2003 06:44:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BcTO26424
	for <ieprep@optimus.ietf.org>; Thu, 6 Mar 2003 06:38:29 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02819;
	Thu, 6 Mar 2003 06:26:59 -0500 (EST)
Message-Id: <200303061126.GAA02819@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ieprep@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 06 Mar 2003 06:26:58 -0500
Subject: [Ieprep] I-D ACTION:draft-polk-ieprep-scenarios-03.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

--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		: IEPREP Telephony Topology Terminology
	Author(s)	: J. Polk
	Filename	: draft-polk-ieprep-scenarios-03.txt
	Pages		: 6
	Date		: 2003-3-5
	
This memo conveys simplistically the likely topological scenarios that may be encountered in reference to IEPREP phone calls.  These scenarios should be used to focus the IEPREP Working Group during discussions and when writing requirements, gap analysis and other solutions documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-polk-ieprep-scenarios-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-polk-ieprep-scenarios-03.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-polk-ieprep-scenarios-03.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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-5140721.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-polk-ieprep-scenarios-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-polk-ieprep-scenarios-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-5140721.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Fri Mar  7 07:02:19 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23064
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:02:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CDmt17309
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 07:13:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CDmO17306
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:13:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23006
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 07:01:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CBPO17093;
	Fri, 7 Mar 2003 07:11:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C4jO15705
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 07:04:45 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21141;
	Fri, 7 Mar 2003 06:52:46 -0500 (EST)
Message-Id: <200303071152.GAA21141@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ieprep@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:52:45 -0500
Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-ets-telephony-02.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

--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		: IP Telephony Requirements for Emergency 
                          Telecommunication Service
	Author(s)	: K. Carlberg, R. Atkinson
	Filename	: draft-ietf-ieprep-ets-telephony-02.txt
	Pages		: 6
	Date		: 2003-3-6
	
This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within the context of IP telephony.
It is an extension to the general requirements presented in [3].
Solutions to these requirements are not presented in this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-ets-telephony-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ets-telephony-02.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-ets-telephony-02.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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-6125120.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ieprep-ets-telephony-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ieprep-ets-telephony-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6125120.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Fri Mar  7 07:02:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23077
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:02:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CDoX17325
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 07:13:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CDoO17322
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:13:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23012
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 07:01:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CBKO17041;
	Fri, 7 Mar 2003 07:11:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C4aO15686
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 07:04:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21102;
	Fri, 7 Mar 2003 06:52:36 -0500 (EST)
Message-Id: <200303071152.GAA21102@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ieprep@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:52:36 -0500
Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-04.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

--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		: Framework for Supporting IEPS in IP Telephony
	Author(s)	: K. Carlberg, I. Brown, C. Beard
	Filename	: draft-ietf-ieprep-framework-04.txt
	Pages		: 29
	Date		: 2003-3-6
	
This document presents a framework for supporting authorized
emergency related communication within the context of IP telephony.
We present a series of objectives that reflect a general view of how
authorized emergency service, in line with the Emergency
Telecommunications Service (ETS), should be realized within today's
IP architecture and service models.  From these objectives, we
present a corresponding set of protocols and capabilities, which
provide a more specific set of recommendations regarding existing
IETF protocols.  Finally, we present two scenarios that act as
guiding models for the objectives and functions listed in this
document.  These, models, coupled with an example of an existing
service in the PSTN, contribute to a constrained solution space.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-framework-04.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-framework-04.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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-6125103.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ieprep-framework-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ieprep-framework-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6125103.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Fri Mar  7 07:02:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23079
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:02:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27CDo817341
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 07:13:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CDoO17338
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 07:13:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23014
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 07:01:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27CBOO17077;
	Fri, 7 Mar 2003 07:11:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27C4eO15697
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 07:04:41 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21123;
	Fri, 7 Mar 2003 06:52:41 -0500 (EST)
Message-Id: <200303071152.GAA21123@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ieprep@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 07 Mar 2003 06:52:41 -0500
Subject: [Ieprep] I-D ACTION:draft-ietf-ieprep-ets-general-02.txt
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

--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		: General Requirements for Emergency Telecommunication 
                          Service
	Author(s)	: K. Carlberg, R. Atkinson
	Filename	: draft-ietf-ieprep-ets-general-02.txt
	Pages		: 9
	Date		: 2003-3-6
	
This document presents a list of general requirements in support of
Emergency Telecommunications Service (ETS). Solutions to these
requirements are not presented in this document.  Additional
requirements pertaining to specific applications, or types of
applications, are to be specified in separate document(s).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-ets-general-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ets-general-02.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-ets-general-02.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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-3-6125112.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ieprep-ets-general-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ieprep-ets-general-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-3-6125112.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Fri Mar  7 10:55:23 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12128
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 10:55:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27G6uh06819
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 11:06:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27G6uO06816
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 11:06:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12059
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 10:54:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27G3QO06504;
	Fri, 7 Mar 2003 11:03:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27G2pO06463
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 11:02:51 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11778
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 10:50:47 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h27Fqoe3007069
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 10:52:50 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h27FqoH2007068
	for ieprep@ietf.org; Fri, 7 Mar 2003 10:52:50 -0500 (EST)
Date: Fri, 7 Mar 2003 10:52:50 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200303071552.h27FqoH2007068@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] not an ad but maybe useful background info
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


if anyone gets this please let the list know if it is worth buying

tnx

Scott

http://www.usta.org/publications/emergency_preparedness.html
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Mar  7 11:12:42 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13228
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 11:12:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27GOFx08702
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 11:24:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GOFO08699
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 11:24:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13125
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 11:12:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GM1O08608;
	Fri, 7 Mar 2003 11:22:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27GLqO08585
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 11:21:52 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12829
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 11:09:47 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 7 Mar 2003 11:10:37 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003030711113706533
 ; Fri, 07 Mar 2003 11:11:37 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPL29TW>; Fri, 7 Mar 2003 11:13:43 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77D2B@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Scott Bradner'" <sob@harvard.edu>, ieprep@ietf.org
Subject: RE: [Ieprep] not an ad but maybe useful background info
Date: Fri, 7 Mar 2003 11:11:36 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


This may also shed light some light on today's state of the art.

"Representative David Blumenthal said that on April 1 EarthLink will begin
offering BlackBerry pagers loaded with software that lets emergency-services
workers tap a database of private information on 98 percent of the U.S.
adult population. The database, run by LocatePlus, includes names,
addresses, phone numbers, prior addresses, dates of birth, social security
numbers, real estate holdings, bankruptcies and criminal records. "

http://news.com.com/2100-1039-991409.html


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



From mailnull@www1.ietf.org  Fri Mar  7 15:11:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26890
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 15:11:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27KMhI02865
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 15:22:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KMhO02862
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 15:22:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26811
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 15:10:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KJKO02621;
	Fri, 7 Mar 2003 15:19:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KIEO02508
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 15:18:14 -0500
Received: from seahorse.shentel.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26128
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 15:06:03 -0500 (EST)
Received: from Steve (ha96s701.d.shentel.net [204.111.98.189])
	by seahorse.shentel.net (8.11.6/8.11.6) with SMTP id h27K7sJ23250;
	Fri, 7 Mar 2003 15:07:54 -0500
From: "Steve Silverman" <steves@shentel.net>
To: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Scott Bradner'" <sob@harvard.edu>, <ieprep@ietf.org>
Subject: RE: [Ieprep] not an ad but maybe useful background info
Date: Fri, 7 Mar 2003 15:09:29 -0500
Message-ID: <CIEELMKPOOAMCIAKANLBAEAKCDAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77D2B@mcl-its-exs01.mail.saic.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

So much for privacy in the USA.  If emergency workers can access this,
so can anyone else
with an interest.  Sounds great for assisting identity theft.
Steve Silverman

> -----Original Message-----
> From: ieprep-admin@ietf.org
> [mailto:ieprep-admin@ietf.org]On Behalf Of
> King, Kimberly S.
> Sent: Friday, March 07, 2003 11:12 AM
> To: 'Scott Bradner'; ieprep@ietf.org
> Subject: RE: [Ieprep] not an ad but maybe useful background info
>
>
>
> This may also shed light some light on today's state of the art.
>
> "Representative David Blumenthal said that on April 1
> EarthLink will begin
> offering BlackBerry pagers loaded with software that lets
> emergency-services
> workers tap a database of private information on 98 percent
> of the U.S.
> adult population. The database, run by LocatePlus, includes names,
> addresses, phone numbers, prior addresses, dates of birth,
> social security
> numbers, real estate holdings, bankruptcies and criminal records. "
>
> http://news.com.com/2100-1039-991409.html
>
>
> - Kimberly
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>
>


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



From mailnull@www1.ietf.org  Fri Mar  7 15:16:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27236
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 15:16:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27KSXp03381
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 15:28:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KSXO03378
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 15:28:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27177
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 15:16:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KR3O03180;
	Fri, 7 Mar 2003 15:27:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KQSO03124
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 15:26:28 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27075
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 15:14:18 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 7 Mar 2003 15:15:16 -0500
Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003030715161518084
 ; Fri, 07 Mar 2003 15:16:15 -0500
Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPLJFZF>; Fri, 7 Mar 2003 15:18:22 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77D34@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Steve Silverman'" <steves@shentel.net>,
        "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "'Scott Bradner'" <sob@harvard.edu>, ieprep@ietf.org
Subject: RE: [Ieprep] not an ad but maybe useful background info
Date: Fri, 7 Mar 2003 15:16:14 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

Steve,

>So much for privacy in the USA.  If emergency workers can access this,
>so can anyone else
>with an interest.  Sounds great for assisting identity theft.

I understand your concerns.

It seems any technology with the potential for great good also has the
potential for grave misuse.  It's always a matter of managing risks and
using solid engineering to "increase the probability" that the good
outweighs the bad.  

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



From mailnull@www1.ietf.org  Fri Mar  7 15:18:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27326
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 15:18:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27KUYg03561
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 15:30:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KUXO03557
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 15:30:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27301
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 15:18:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KT2O03440;
	Fri, 7 Mar 2003 15:29:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KSYO03394
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 15:28:34 -0500
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27182
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 15:16:24 -0500 (EST)
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h27KITe3008785;
	Fri, 7 Mar 2003 15:18:29 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h27KITDj008781;
	Fri, 7 Mar 2003 15:18:29 -0500 (EST)
Date: Fri, 7 Mar 2003 15:18:29 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200303072018.h27KITDj008781@newdev.harvard.edu>
To: ieprep@ietf.org, KIMBERLY.S.KING@saic.com, sob@harvard.edu,
        steves@shentel.net
Subject: RE: [Ieprep] not an ad but maybe useful background info
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77D34@mcl-its-exs01.mail.saic.com>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

> It's always a matter of managing risks and
> using solid engineering to "increase the probability" that the good
> outweighs the bad.  


it helps to use logic as well - what emergency use can there be for 
SSNs? - if there is no compelling use why should they be exposed to
emergency workers (or whoever runs of with the emergency worker's PDA)?

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



From mailnull@www1.ietf.org  Fri Mar  7 15:24:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27583
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 15:24:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27KZeB03942
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 15:35:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KZeO03939
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 15:35:40 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27557
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 15:23:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KY7O03810;
	Fri, 7 Mar 2003 15:34:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27KVuO03639
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 15:31:56 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27355
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 15:19:45 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 7 Mar 2003 15:20:35 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003030715213507606
 ; Fri, 07 Mar 2003 15:21:35 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPL2QJ3>; Fri, 7 Mar 2003 15:21:15 -0500
Message-Id: <B8030EB94AF1D51196D70002A589D64207E77D35@mcl-its-exs01.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Scott Bradner'" <sob@harvard.edu>, ieprep@ietf.org,
        KIMBERLY.S.KING@saic.com, steves@shentel.net
Subject: RE: [Ieprep] not an ad but maybe useful background info
Date: Fri, 7 Mar 2003 15:21:34 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

Scott,

>it helps to use logic as well - what emergency use can there be for 
>SSNs? - if there is no compelling use why should they be exposed to
>emergency workers (or whoever runs of with the emergency worker's PDA)?

I assume SSN's could be used in association with medical records but I tend
to strongly agree with your position.

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



From mailnull@www1.ietf.org  Fri Mar  7 18:14:00 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13413
	for <ieprep-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:14:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h27NPhK24517
	for ieprep-archive@odin.ietf.org; Fri, 7 Mar 2003 18:25:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NPhO24514
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 7 Mar 2003 18:25:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13395
	for <ieprep-web-archive@ietf.org>; Fri, 7 Mar 2003 18:13:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NO6O24354;
	Fri, 7 Mar 2003 18:24:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NMSO24186
	for <ieprep@optimus.ietf.org>; Fri, 7 Mar 2003 18:22:28 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13059
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 18:10:14 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (8.12.8/8.12.6) with ESMTP id h27NBsJp008554
	for <ieprep@ietf.org>; Fri, 7 Mar 2003 16:11:54 -0700 (MST)
Received: from USAZ107115SVR20 ([130.131.166.68]) by
          pxmail1.agcs.com (Netscape Messaging Server 4.15 pxmail1 Mar  5
          2002 15:11:07) with SMTP id HBEJ4I00.KG0 for <ieprep@ietf.org>;
          Fri, 7 Mar 2003 16:12:18 -0700 
Received: FROM agcs.com BY USAZ107115SVR20 ; Fri Mar 07 16:12:17 2003 -0700
Message-ID: <3E692750.9264F7B5@agcs.com>
Date: Fri, 07 Mar 2003 16:12:17 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "King Kimberly S." <KIMBERLY.S.KING@saic.com>
CC: ieprep@ietf.org
Subject: Re: [Ieprep] not an ad but maybe useful background info
References: <B8030EB94AF1D51196D70002A589D64207E77D35@mcl-its-exs01.mail.saic.com>
Content-Type: multipart/mixed;
 boundary="------------E78D9D128AEAD0D5FA5C8569"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

This is a multi-part message in MIME format.
--------------E78D9D128AEAD0D5FA5C8569
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Folks,

I would hope that there are different classes of information that would be
displayed based on the type of emergency worker. The article mentioned
bankruptcies for instance. Does the EMT need to know if I can afford to pay the
bill before he bothers to restart my heart?

I would also hope that an audit trail would be generated requiring some
confirmation regarding the inquiry.

Since it is a service being marketed, I suspect that neither hope has been
addressed,

"King, Kimberly S." wrote:

> Scott,
>
> >it helps to use logic as well - what emergency use can there be for
> >SSNs? - if there is no compelling use why should they be exposed to
> >emergency workers (or whoever runs of with the emergency worker's PDA)?
>
> I assume SSN's could be used in association with medical records but I tend
> to strongly agree with your position.
>
> Kimberly
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

--------------E78D9D128AEAD0D5FA5C8569
Content-Type: text/x-vcard; charset=us-ascii;
 name="goldmans.vcf"
Content-Description: Card for Stuart (Stu) Goldman
Content-Disposition: attachment;
 filename="goldmans.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Goldman;-Stuart
tel;cell:623 582 7136
tel;fax:623 582 7111
tel;home:602 493 8438  
tel;work:623 582 7136
x-mozilla-html:TRUE
org:AG Communication Systems
adr:;;P.O. Box 52179;Phoenix;AZ;85072-2179;USA
version:2.1
email;internet:sgoldman@lucent.com
x-mozilla-cpt:;-23496
fn:Stuart Goldman
end:vcard

--------------E78D9D128AEAD0D5FA5C8569--

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



From mailnull@www1.ietf.org  Sat Mar  8 15:19:57 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00044
	for <ieprep-archive@odin.ietf.org>; Sat, 8 Mar 2003 15:19:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h28KW6900571
	for ieprep-archive@odin.ietf.org; Sat, 8 Mar 2003 15:32:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28KW5O00568
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 15:32:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29939
	for <ieprep-web-archive@ietf.org>; Sat, 8 Mar 2003 15:19:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28KUJO00449;
	Sat, 8 Mar 2003 15:30:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h28KR8O00333
	for <ieprep@optimus.ietf.org>; Sat, 8 Mar 2003 15:27:08 -0500
Received: from clifden.donelan.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28909
	for <ieprep@ietf.org>; Sat, 8 Mar 2003 15:14:28 -0500 (EST)
Received: from sean (helo=localhost)
	by clifden.donelan.com with local-esmtp (Exim 3.34 #3)
	id 18rkkE-0007VB-00
	for ieprep@ietf.org; Sat, 08 Mar 2003 15:16:34 -0500
Date: Sat, 8 Mar 2003 15:16:34 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: ieprep@ietf.org
In-Reply-To: <3E692750.9264F7B5@agcs.com>
Message-ID: <Pine.GSO.4.44.0303081512470.28818-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ieprep] GETS or Blackberries
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


Personal opinion, not representative of any organization or company

I wonder if members of congress would give up their GETS cards or their
Blackberries first?


http://www.nytimes.com/2003/03/08/politics/08PREP.html

On Capitol Hill, lawmakers prowl the halls with new BlackBerry handheld
digital pagers that are to notify them instantly in case of an attack.
Security officials regularly use the devices to warn lawmakers of breaches
and tell them where to gather in an emergency.

Representative Bob Ney, Republican of Ohio, distributed the devices to all
House members after he found that on Sept. 11, 2001, telephone lines were
clogged and his BlackBerry was his sole effective means of communication.

"It's the only thing that worked that day," said Mr. Ney, chairman of the
committee responsible for House security.

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



From mailnull@www1.ietf.org  Sat Mar  8 21:56:35 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14329
	for <ieprep-archive@odin.ietf.org>; Sat, 8 Mar 2003 21:56:34 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2938p926899
	for ieprep-archive@odin.ietf.org; Sat, 8 Mar 2003 22:08:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2938pO26896
	for <ieprep-web-archive@optimus.ietf.org>; Sat, 8 Mar 2003 22:08:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14227
	for <ieprep-web-archive@ietf.org>; Sat, 8 Mar 2003 21:56:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2937PO26710;
	Sat, 8 Mar 2003 22:07:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h292s6O25472
	for <ieprep@optimus.ietf.org>; Sat, 8 Mar 2003 21:54:06 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA11432
	for <ieprep@ietf.org>; Sat, 8 Mar 2003 21:41:17 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.16230-0@bells.cs.ucl.ac.uk>; Sun, 9 Mar 2003 02:40:15 +0000
To: Sean Donelan <sean@donelan.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] GETS or Blackberries
In-reply-to: Your message of "Sat, 08 Mar 2003 15:16:34 EST." <Pine.GSO.4.44.0303081512470.28818-100000@clifden.donelan.com>
Date: Sun, 09 Mar 2003 02:40:14 +0000
Message-ID: <1670.1047177614@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


> I wonder if members of congress would give up their GETS cards or their
> Blackberries first?

agreed, an interesting question.  assuming members of congress had a
GETS card, I would be interested in the response of the members from
Utah.  Particularly if one told them that if they were vacationing in
Park City, they would not have Blackberry service (according to
http://www.motient.com/find/), but rather would have to drive to Salt
Lake City, Provo, Ogden, or Layton to get it.  Further, that if they
were in the cities of Delta, Nephi, Ephraim, Huntington, Price,
Richfield, Circleville, Loa, Moab, St. George, Cedar City, Panguitch,
Kanab, Beaver, Heber, Brigham City, Evanston, Randolph, Logan, Blanding,
or Roosevelt they would not have Blackberry service.

-ken


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



From mailnull@www1.ietf.org  Mon Mar 10 12:04:01 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03192
	for <ieprep-archive@odin.ietf.org>; Mon, 10 Mar 2003 12:04:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AHH5W28787
	for ieprep-archive@odin.ietf.org; Mon, 10 Mar 2003 12:17:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHH5O28784
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 12:17:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03145
	for <ieprep-web-archive@ietf.org>; Mon, 10 Mar 2003 12:03:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHF9O28594;
	Mon, 10 Mar 2003 12:15:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHA8O28338
	for <ieprep@optimus.ietf.org>; Mon, 10 Mar 2003 12:10:08 -0500
Received: from bootstrap.agcs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02851
	for <ieprep@ietf.org>; Mon, 10 Mar 2003 11:56:33 -0500 (EST)
Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.52.9])
	by bootstrap.agcs.com (8.12.8/8.12.6) with ESMTP id h2AGwFJp027815
	for <ieprep@ietf.org>; Mon, 10 Mar 2003 09:58:15 -0700 (MST)
Received: from USAZ107115SVR20 ([130.131.166.68]) by
          pxmail1.agcs.com (Netscape Messaging Server 4.15 pxmail1 Mar  5
          2002 15:11:07) with SMTP id HBJLTS00.Q8D for <ieprep@ietf.org>;
          Mon, 10 Mar 2003 09:58:40 -0700 
Received: FROM agcs.com BY USAZ107115SVR20 ; Mon Mar 10 09:58:39 2003 -0700
Message-ID: <3E6CC43F.7BE37A03@agcs.com>
Date: Mon, 10 Mar 2003 09:58:39 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
CC: Sean Donelan <sean@donelan.com>, ieprep@ietf.org
Subject: Re: [Ieprep] GETS or Blackberries
References: <1670.1047177614@cs.ucl.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ken,

Would it not be the wisest course of action for them to have have both?

Since I don't know what facilities might be lost during a disaster, having as
many tools (using different technologies) as possible would seem to give me the
best chance of at least one tool remaining viable.

Ken Carlberg wrote:

> > I wonder if members of congress would give up their GETS cards or their
> > Blackberries first?
>
> agreed, an interesting question.  assuming members of congress had a
> GETS card, I would be interested in the response of the members from
> Utah.  Particularly if one told them that if they were vacationing in
> Park City, they would not have Blackberry service (according to
> http://www.motient.com/find/), but rather would have to drive to Salt
> Lake City, Provo, Ogden, or Layton to get it.  Further, that if they
> were in the cities of Delta, Nephi, Ephraim, Huntington, Price,
> Richfield, Circleville, Loa, Moab, St. George, Cedar City, Panguitch,
> Kanab, Beaver, Heber, Brigham City, Evanston, Randolph, Logan, Blanding,
> or Roosevelt they would not have Blackberry service.
>
> -ken
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep

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



From mailnull@www1.ietf.org  Mon Mar 10 12:21:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04314
	for <ieprep-archive@odin.ietf.org>; Mon, 10 Mar 2003 12:21:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2AHYWn30440
	for ieprep-archive@odin.ietf.org; Mon, 10 Mar 2003 12:34:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHYWO30437
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 10 Mar 2003 12:34:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04284
	for <ieprep-web-archive@ietf.org>; Mon, 10 Mar 2003 12:20:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHX2O30326;
	Mon, 10 Mar 2003 12:33:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2AHWKO30261
	for <ieprep@optimus.ietf.org>; Mon, 10 Mar 2003 12:32:20 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04154
	for <ieprep@ietf.org>; Mon, 10 Mar 2003 12:18:45 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.11351-0@bells.cs.ucl.ac.uk>; Mon, 10 Mar 2003 17:20:43 +0000
To: "Stuart (Stu) Goldman" <goldmans@agcs.com>
cc: Sean Donelan <sean@donelan.com>, ieprep@ietf.org
Subject: Re: [Ieprep] GETS or Blackberries
In-reply-to: Your message of "Mon, 10 Mar 2003 09:58:39 MST." <3E6CC43F.7BE37A03@agcs.com>
Date: Mon, 10 Mar 2003 17:20:43 +0000
Message-ID: <22997.1047316843@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


> Would it not be the wisest course of action for them to have have both?

absolutely, and more the merrier.  the original question was placed as
an either/or proposition.  I'm not sure I see the utility of such a
position, but the question of the tradeoff of perceived coverage
versus new technology and architecture is a fair one -- this includes
handwaving over various factors.  I personally go for coverage if i 
know I'll travel and my "home" is distributed.

-ken

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



From mailnull@www1.ietf.org  Tue Mar 11 16:47:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13618
	for <ieprep-archive@odin.ietf.org>; Tue, 11 Mar 2003 16:47:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BM19N04033
	for ieprep-archive@odin.ietf.org; Tue, 11 Mar 2003 17:01:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BM19O04030
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 17:01:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13577
	for <ieprep-web-archive@ietf.org>; Tue, 11 Mar 2003 16:47:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BLxLO03295;
	Tue, 11 Mar 2003 16:59:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BLwCO03212
	for <ieprep@optimus.ietf.org>; Tue, 11 Mar 2003 16:58:12 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13368;
	Tue, 11 Mar 2003 16:44:02 -0500 (EST)
Message-Id: <200303112144.QAA13368@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>,
        ieprep@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Date: Tue, 11 Mar 2003 16:44:02 -0500
Subject: [Ieprep] Document Action: IEPREP Telephony Topology Terminology to
 Informational
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>



The IESG has approved the Internet-Draft 'IEPREP Telephony Topology 
Terminology' <draft-polk-ieprep-scenarios-03.txt> as an Informational 
RFC.  This document is the product of the Internet Emergency 
Preparedness Working Group.  The IESG contact persons are Allison Mankin 
and Scott Bradner.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Tue Mar 11 18:28:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18399
	for <ieprep-archive@odin.ietf.org>; Tue, 11 Mar 2003 18:28:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2BNgZA11747
	for ieprep-archive@odin.ietf.org; Tue, 11 Mar 2003 18:42:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNgYO11744
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 18:42:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18389
	for <ieprep-web-archive@ietf.org>; Tue, 11 Mar 2003 18:28:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNfEO11715;
	Tue, 11 Mar 2003 18:41:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BNeYO11689
	for <ieprep@optimus.ietf.org>; Tue, 11 Mar 2003 18:40:35 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18338
	for <ieprep@ietf.org>; Tue, 11 Mar 2003 18:26:22 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z05YQB>; Tue, 11 Mar 2003 18:26:37 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BDD@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "Ieprep (E-mail)"
	 <ieprep@ietf.org>
Cc: "Allison Mankin (E-mail)" <mankin@psg.com>,
        "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
Subject: RE: [Ieprep] Considerations on the IEPREP requirements for SIP
Date: Tue, 11 Mar 2003 18:24:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

I have posted my initial comments on the sipping list.

-----Original Message-----
From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
Sent: Thursday, February 27, 2003 10:41 AM
To: 'King, Kimberly S.'; Ieprep (E-mail)
Cc: Allison Mankin (E-mail); 'Scott Bradner ' (E-mail)
Subject: RE: [Ieprep] Considerations on the IEPREP requirements for SIP


Also,  the discussion of Jon's ieprep-sipping
draft should take place just on the sipping list.


- Kimberly

>-----Original Message-----
>From: King, Kimberly S. [mailto:KIMBERLY.S.KING@saic.com]
>Sent: Thursday, February 27, 2003 10:00 AM
>To: Ieprep (E-mail)
>Subject: [Ieprep] Considerations on the IEPREP requirements for SIP
>
>
>
>FYI:  The following draft came out today on the SIPPING mailing list.
>
>
>"A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
>	Title		: Considerations on the IEPREP 
>requirements for SIP
>	Author(s)	: J. Peterson
>	Filename	: draft-peterson-sipping-ieprep-00.txt
>	Pages		: 10
>	Date		: 2003-2-26
>	
>The IEPREP working group has provided the SIPPING WG with a framework
>and requirements draft for prioritized communications services in
>SIP.  The considerations raised in that draft are examined here, and
>some feedback and implementation recommendations based on its
>requirements are provided.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-peterson-sipping-iepr
ep-00.txt "

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



From mailnull@www1.ietf.org  Mon Mar 17 19:00:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08942
	for <ieprep-archive@odin.ietf.org>; Mon, 17 Mar 2003 19:00:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I0Gvq17265
	for ieprep-archive@odin.ietf.org; Mon, 17 Mar 2003 19:16:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0GuO17262
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 17 Mar 2003 19:16:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08914
	for <ieprep-web-archive@ietf.org>; Mon, 17 Mar 2003 18:59:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0FLO17198;
	Mon, 17 Mar 2003 19:15:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I0EiO17153
	for <ieprep@optimus.ietf.org>; Mon, 17 Mar 2003 19:14:44 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08853
	for <ieprep@ietf.org>; Mon, 17 Mar 2003 18:57:36 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z06F44>; Mon, 17 Mar 2003 18:57:57 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995BFA@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'King, Kimberly  S.'" <KIMBERLY.S.KING@saic.com>,
        "James Polk (E-mail)" <jmpolk@cisco.com>
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: RE: [Ieprep] draft-polk-ieprep-flow-model-considerations-00.txt
Date: Mon, 17 Mar 2003 18:56:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

A few (mostly editorial) comments.

pg 2 (grammar nit) out-of-band signaling.  It should be "different from the
data path" rather than "different than the data path".  Also it should be
"port numbers ... are different"  rather than "is different."

It is a little bit confusing that on pg 3 you use Magaco and H.234 as
examples, but then on page 5 you say they are "not categorized".

The text in 3.0 looks as if it belongs in 3.1.

Like Kimberly, I was confused by the categorization of FTP.  Because the
diagram for 3.3 shows the signaling path going through an "intermediate
server", it really looks as if you are saying FTP goes through an
intermediate server.  Maybe you need two diagrams in section 3.3.  Or maybe
you need separate sections for "Out-of-Band Signaling via a Server", and
Out-of-Band Signaling with Direct Connections."

While it can't be exhaustive, I would like to see a few more protocols
categorized, or otherwise referenced.  For instance, I assume that RSVP and
Diffserve are protocols that could be APPLIED to the data or signaling path,
not protocols to be categorized.  But it would be nice to say that
explicitly.  You list POP3, but not SMTP.  You list http but not https.
What about SNMP (not that I can immediately come up with a reason ETS would
need to use SNMP)?


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



From mailnull@www1.ietf.org  Tue Mar 18 02:51:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03716
	for <ieprep-archive@odin.ietf.org>; Tue, 18 Mar 2003 02:51:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2I88Rw27528
	for ieprep-archive@odin.ietf.org; Tue, 18 Mar 2003 03:08:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I88RO27523
	for <ieprep-web-archive@optimus.ietf.org>; Tue, 18 Mar 2003 03:08:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03711
	for <ieprep-web-archive@ietf.org>; Tue, 18 Mar 2003 02:51:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I87DO26937;
	Tue, 18 Mar 2003 03:07:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2I86BO26682
	for <ieprep@optimus.ietf.org>; Tue, 18 Mar 2003 03:06:11 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03697
	for <ieprep@ietf.org>; Tue, 18 Mar 2003 02:48:53 -0500 (EST)
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 18 Mar 2003 01:51:06 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Ieprep] draft-polk-ieprep-flow-model-considerations-00.txt
Date: Tue, 18 Mar 2003 01:51:06 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02D042@KC-MAIL4.kc.umkc.edu>
Thread-Topic: [Ieprep] draft-polk-ieprep-flow-model-considerations-00.txt
Thread-Index: AcLs4WXhge++xSbLQMWr2zzepFtrMgAP9JFQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>,
        "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>,
        "James Polk (E-mail)" <jmpolk@cisco.com>
Cc: "Ieprep (E-mail)" <ieprep@ietf.org>
X-OriginalArrivalTime: 18 Mar 2003 07:51:06.0947 (UTC) FILETIME=[21FA1130:01C2ED23]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2I86BO26683
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> While it can't be exhaustive, I would like to see a few more protocols
> categorized, or otherwise referenced.  

Yes. If standardized, it will be assumed that these are the only protocols 
applicable for ieprep. Atleast, reference to other application level 
protocols should be included (but, not a laundry list !!!) 


> For instance, I assume that RSVP and Diffserve are protocols that could 
> be APPLIED to the data or signaling path,

well, yes. But, I presume, the draft exclusively lists only application 
level stuff. So, rsvp cannot be accounted (might be, but lot of other 
interaction cases have to be addressed.)


> What about SNMP (not that I can immediately come up with a 
> reason ETS would need to use SNMP)?

As sean mentioned once, NM control relaxing will act counter intuitive at 
times for ieprep.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Mar 19 16:58:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11417
	for <ieprep-archive@odin.ietf.org>; Wed, 19 Mar 2003 16:58:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2JMFko11983
	for ieprep-archive@odin.ietf.org; Wed, 19 Mar 2003 17:15:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JMFkO11980
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 17:15:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11390
	for <ieprep-web-archive@ietf.org>; Wed, 19 Mar 2003 16:57:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JMBGO11701;
	Wed, 19 Mar 2003 17:11:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JMAfO11672
	for <ieprep@optimus.ietf.org>; Wed, 19 Mar 2003 17:10:41 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11204
	for <ieprep@ietf.org>; Wed, 19 Mar 2003 16:52:36 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z06MFL>; Wed, 19 Mar 2003 16:52:55 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995C0B@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'Ken Carlberg'" <K.Carlberg@cs.ucl.ac.uk>
Cc: ieprep@ietf.org, "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Subject: RE: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt
Date: Wed, 19 Mar 2003 16:51:06 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

What Henning didn't say is that he and James have ANOTHER document
(currently in the SIP working group) which DOES address the Resource
Priority Header, and should probably be referenced in the document.

http://www.ietf.org/internet-drafts/draft-polk-sip-resource-02.txt

 Communications Resource Priority for the Session Initiation
                             Protocol (SIP)

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
Sent: Monday, February 17, 2003 1:51 PM
To: Gunn, Janet
Cc: 'Ken Carlberg'; ieprep@ietf.org
Subject: Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt


Indeed. The requirements draft takes great pains to be solution-neutral 
and thus does not address a specific mechanism. In reality, the number 
of possibilities aren't infinite, given the constraints of the protocol. 
There will shortly be a solution-oriented draft that does indeed propose 
a new header field, after trying to exhaustively go through all the 
design options and identifying why no other solution satisfies the 
requirements stated. As always, I might have missed possibilities or 
solutions, but I'm sure that participants in this and SIP-related 
working groups won't be shy in pointing out any such omission.

In short, Janet is correct.

Gunn, Janet wrote:
> Maybe Henning can clarify, but the current version of
> draft-ietf-ieprep-sip-reqs-03.txt says
> "This document describes requirements rather than possible existing or
>    new protocol features. Although it is scoped to deal with SIP-based
>    applications, this should not be taken to imply that mechanisms have
>    to be SIP protocol features such as header fields, methods or URI
>    parameters."
> 
> It presents requirements for which a new header field is the "obvious"
> solution, but no longer states it as a requirement FRO a header field.
> 
> -----Original Message-----
> From: Ken Carlberg [mailto:K.Carlberg@cs.ucl.ac.uk]
> 
> 
>>Pg 11 reference to Henning's document - it no longer refers explicitly
>>to headers.
> 
> 
> the original passage is:
> 
>    [15] is a (soon to be) RFC that defines the requirements for a new
>    header field for SIP in reference to resource priority.  This new
>    header field is meant to provide an additional measure of distinction
>    that can influence the behavior of gateways and SIP proxies.
> 
> my understanding is that it pertains to requirements for a header *field*.

> so yes, we are in agreement.
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Mar 19 18:53:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16529
	for <ieprep-archive@odin.ietf.org>; Wed, 19 Mar 2003 18:53:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K0BPS21313
	for ieprep-archive@odin.ietf.org; Wed, 19 Mar 2003 19:11:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0BPO21310
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 19:11:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16520
	for <ieprep-web-archive@ietf.org>; Wed, 19 Mar 2003 18:53:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0A9O21237;
	Wed, 19 Mar 2003 19:10:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K09UO21191
	for <ieprep@optimus.ietf.org>; Wed, 19 Mar 2003 19:09:30 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16477
	for <ieprep@ietf.org>; Wed, 19 Mar 2003 18:51:23 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.19290-0@bells.cs.ucl.ac.uk>; Wed, 19 Mar 2003 23:53:34 +0000
To: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
cc: ieprep@ietf.org
Subject: Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt
In-reply-to: Your message of "Wed, 19 Mar 2003 16:51:06 EST." <CBED705A7FD2D311865500508B1089410D995C0B@chntex02.is.dyncorp.com>
Date: Wed, 19 Mar 2003 23:53:34 +0000
Message-ID: <11579.1048118014@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


> What Henning didn't say is that he and James have ANOTHER document
> (currently in the SIP working group) which DOES address the Resource
> Priority Header, and should probably be referenced in the document.
>
> http://www.ietf.org/internet-drafts/draft-polk-sip-resource-02.txt

we don't want to reference the above draft because its still a work in
progress.  its best to focus on RFC3487, "Requirements for Resource
Priority Mechanisms for the Session Initiation Protocol (SIP)"

-ken

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



From mailnull@www1.ietf.org  Wed Mar 19 19:00:37 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16705
	for <ieprep-archive@odin.ietf.org>; Wed, 19 Mar 2003 19:00:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K0IDV21578
	for ieprep-archive@odin.ietf.org; Wed, 19 Mar 2003 19:18:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0IDO21575
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 19:18:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16698
	for <ieprep-web-archive@ietf.org>; Wed, 19 Mar 2003 19:00:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0H4O21543;
	Wed, 19 Mar 2003 19:17:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0GWO21514
	for <ieprep@optimus.ietf.org>; Wed, 19 Mar 2003 19:16:32 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16662
	for <ieprep@ietf.org>; Wed, 19 Mar 2003 18:58:24 -0500 (EST)
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.211] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 19 Mar 2003 18:00:40 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt
Date: Wed, 19 Mar 2003 18:00:39 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02D044@KC-MAIL4.kc.umkc.edu>
Thread-Topic: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt
Thread-Index: AcLucuJJrPjIfB/JQiOhp59TxM2l1wAAFHVA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Ken Carlberg" <K.Carlberg@cs.ucl.ac.uk>,
        "Gunn, Janet" <Janet.Gunn@DynCorp.com>
Cc: <ieprep@ietf.org>
X-OriginalArrivalTime: 20 Mar 2003 00:00:40.0741 (UTC) FILETIME=[BEAC5550:01C2EE73]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2K0GWO21515
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> > What Henning didn't say is that he and James have ANOTHER document
> > (currently in the SIP working group) which DOES address the Resource
> > Priority Header, and should probably be referenced in the document.
> >
> > http://www.ietf.org/internet-drafts/draft-polk-sip-resource-02.txt
> 
> we don't want to reference the above draft because its still a work in
> progress.  

but, your reference cites many other work-in-progress drafts ( some even
expired.) For example, the Classifier Extension Header for RTP. I don't 
know which WG is discussing that draft. So, I see no harm in referring
both the requirements (RFC3487) and the actual priority header draft.
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Wed Mar 19 19:34:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17828
	for <ieprep-archive@odin.ietf.org>; Wed, 19 Mar 2003 19:34:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2K0qIA24362
	for ieprep-archive@odin.ietf.org; Wed, 19 Mar 2003 19:52:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0qIO24359
	for <ieprep-web-archive@optimus.ietf.org>; Wed, 19 Mar 2003 19:52:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17825
	for <ieprep-web-archive@ietf.org>; Wed, 19 Mar 2003 19:34:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0p7O24318;
	Wed, 19 Mar 2003 19:51:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K0oCO24254
	for <ieprep@optimus.ietf.org>; Wed, 19 Mar 2003 19:50:12 -0500
Received: from bells.cs.ucl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17782
	for <ieprep@ietf.org>; Wed, 19 Mar 2003 19:32:05 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.24182-0@bells.cs.ucl.ac.uk>; Thu, 20 Mar 2003 00:34:03 +0000
To: "Ayyasamy, Senthilkumar (UMKC-Student)" <saq66@umkc.edu>
cc: ieprep <ieprep@ietf.org>
Subject: Re: [Ieprep] I-D ACTION:draft-ietf-ieprep-framework-03.txt
In-reply-to: Your message of "Wed, 19 Mar 2003 18:00:39 CST." <5EF7D95E17BDAD4A968C812E5ABC390B02D044@KC-MAIL4.kc.umkc.edu>
Date: Thu, 20 Mar 2003 00:34:03 +0000
Message-ID: <14420.1048120443@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


> > we don't want to reference the above draft because its still a work in
> > progress.
> 
> but, your reference cites many other work-in-progress drafts ( some even
> expired.) For example, the Classifier Extension Header for RTP. I don't
> know which WG is discussing that draft. So, I see no harm in referring
> both the requirements (RFC3487) and the actual priority header draft.

my mistake for not finishing the original sentence above.  I should have
added that RFC-3487 is a sufficient reference for the original passage
in the Framework document (though i'll probably slightly alter that
passage shortly to make sure of this).  given a choice between a draft
and an RFC as a reference point, its best to choose the RFC.

as for the other drafts referenced, one is allowed to cite them within
constraints.  I'd like to replace those in the draft where possible, and
in fact two will be replaced by new RFCs (eg, 3487 :-) that came out
right after I submitted version of the Framework draft.  hopefully, in
short period, two others will also be replaced by RFCs.

-ken

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



From mailnull@www1.ietf.org  Thu Mar 20 18:44:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14421
	for <ieprep-archive@odin.ietf.org>; Thu, 20 Mar 2003 18:44:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2L02Nn08868
	for ieprep-archive@odin.ietf.org; Thu, 20 Mar 2003 19:02:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L02NO08865
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 19:02:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14408
	for <ieprep-web-archive@ietf.org>; Thu, 20 Mar 2003 18:43:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KNupO08569;
	Thu, 20 Mar 2003 18:56:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2KNoGO08318
	for <ieprep@optimus.ietf.org>; Thu, 20 Mar 2003 18:50:16 -0500
Received: from post.webmailer.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14107
	for <ieprep@ietf.org>; Thu, 20 Mar 2003 18:31:38 -0500 (EST)
Received: from barytde (wl-139-253.wireless.ietf56.ietf.org [130.129.139.253])
	by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h2KNXg6g011198
	for <ieprep@ietf.org>; Fri, 21 Mar 2003 00:33:53 +0100 (MET)
Reply-To: <tc@baryt.de>
From: "Thorsten Claus" <tc@baryt.de>
To: "ieprep" <ieprep@ietf.org>
Date: Thu, 20 Mar 2003 15:33:41 -0800
Organization: baryt.de
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAfYJY/xPfTEyX+A9jdGgJDcKAAAAQAAAAhSpwYPNKjUewEjG6KX1ceQEAAAAA@baryt.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C2EEF6.1A8E3CD0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Subject: [Ieprep] Slides and Docs from WG meeting?
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C2EEF6.1A8E3CD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

Are the Slides and Docs from the WG meeting yesterday somewhere available?

 

:: tc ::

 


------=_NextPart_000_0000_01C2EEF6.1A8E3CD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tele-GroteskNor;
	panose-1:0 0 5 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tele-Antiqua;
	panose-1:0 0 5 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tele-GroteskUlt;
	panose-1:0 0 5 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tele-GroteskFet;
	panose-1:0 0 5 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tele-GroteskHal;
	panose-1:0 0 5 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
h1
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:1.5in;
	margin-left:0in;
	text-align:justify;
	text-indent:0in;
	page-break-before:always;
	page-break-after:avoid;
	font-size:26.0pt;
	font-family:Tele-Antiqua;
	font-weight:normal;}
h2
	{margin-top:.25in;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:0in;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Tele-GroteskUlt;
	font-weight:normal;}
h3
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Tele-GroteskFet;
	font-weight:normal;}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskFet;
	font-weight:normal;}
h5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskHal;
	font-weight:normal;}
h6
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;
	font-weight:normal;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:0in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin-top:.25in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:12.0pt;
	font-family:Tele-GroteskUlt;}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.45in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.3in;
	font-size:10.0pt;
	font-family:Tele-GroteskHal;}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.6in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.3in;
	font-size:10.0pt;
	font-family:Tele-GroteskNor;}
p.MsoToc4, li.MsoToc4, div.MsoToc4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.75in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.3in;
	font-size:10.0pt;
	font-family:Tele-GroteskNor;}
p.MsoToc5, li.MsoToc5, div.MsoToc5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:33.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc6, li.MsoToc6, div.MsoToc6
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:44.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc7, li.MsoToc7, div.MsoToc7
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:55.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc8, li.MsoToc8, div.MsoToc8
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:66.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc9, li.MsoToc9, div.MsoToc9
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:77.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:9.0pt;
	font-size:9.0pt;
	font-family:Tele-GroteskNor;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:9.0pt;
	font-size:9.0pt;
	font-family:Tele-GroteskNor;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:9.0pt;
	font-size:9.0pt;
	font-family:Tele-GroteskNor;}
p.MsoCaption, li.MsoCaption, div.MsoCaption
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	line-height:11.0pt;
	font-size:10.0pt;
	font-family:Tele-GroteskNor;
	font-weight:bold;}
span.MsoFootnoteReference
	{font-family:Tele-GroteskNor;
	vertical-align:super;}
span.MsoPageNumber
	{font-family:Tele-GroteskNor;}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:11.0pt;
	margin-left:21.25pt;
	text-align:justify;
	text-indent:-21.25pt;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:128.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.8in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListBullet2, li.MsoListBullet2, div.MsoListBullet2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:128.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.8in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:128.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.8in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListBullet4, li.MsoListBullet4, div.MsoListBullet4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.25in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.25in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListBullet5, li.MsoListBullet5, div.MsoListBullet5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.25in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.25in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListNumber2, li.MsoListNumber2, div.MsoListNumber2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:128.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.8in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListNumber3, li.MsoListNumber3, div.MsoListNumber3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.25in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoListNumber4, li.MsoListNumber4, div.MsoListNumber4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.25in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.25in;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.MsoTitle, li.MsoTitle, div.MsoTitle
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:21.0pt;
	font-size:22.0pt;
	font-family:Tele-Antiqua;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.Text, li.Text, div.Text
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.TextIndent1, li.TextIndent1, div.TextIndent1
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:35.4pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.TextIndent2, li.TextIndent2, div.TextIndent2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:70.8pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.Aufzhlungmagenta, li.Aufzhlungmagenta, div.Aufzhlungmagenta
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:20.15pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-20.15pt;
	line-height:14.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.Aufzhlungschwarz, li.Aufzhlungschwarz, div.Aufzhlungschwarz
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:128.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-indent:-.8in;
	line-height:14.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;
	layout-grid-mode:line;}
p.Grafik1, li.Grafik1, div.Grafik1
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.Grafik2, li.Grafik2, div.Grafik2
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.Grafiken, li.Grafiken, div.Grafiken
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.Headline1, li.Headline1, div.Headline1
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:20.0pt;
	font-family:Tele-Antiqua;
	color:fuchsia;}
p.Headline2, li.Headline2, div.Headline2
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:20.0pt;
	font-family:Tele-Antiqua;
	color:gray;}
p.Kopfzeile1, li.Kopfzeile1, div.Kopfzeile1
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:9.0pt;
	font-size:9.0pt;
	font-family:Tele-GroteskUlt;}
p.KopfzeileZusatz, li.KopfzeileZusatz, div.KopfzeileZusatz
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskNor;}
p.KopfzeileZusatz1, li.KopfzeileZusatz1, div.KopfzeileZusatz1
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskUlt;}
p.Kurzberschrift, li.Kurzberschrift, div.Kurzberschrift
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	text-align:justify;
	font-size:9.0pt;
	font-family:Arial;}
p.Tabtextff, li.Tabtextff, div.Tabtextff
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:8.0pt;
	font-family:Arial;}
p.Tabtext1, li.Tabtext1, div.Tabtext1
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	text-align:center;
	font-size:8.0pt;
	font-family:Arial;
	font-weight:bold;
	font-style:italic;}
p.Tabeintrag, li.Tabeintrag, div.Tabeintrag
	{margin-top:2.0pt;
	margin-right:0in;
	margin-bottom:2.0pt;
	margin-left:0in;
	text-align:justify;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:bold;}
p.Tabelle, li.Tabelle, div.Tabelle
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:10.0pt;
	font-family:Tele-GroteskNor;}
p.Tabelle2, li.Tabelle2, div.Tabelle2
	{margin:0in;
	margin-bottom:.0001pt;
	line-height:12.0pt;
	font-size:8.0pt;
	font-family:Helvetica;}
p.Tabellenberschrift, li.Tabellenberschrift, div.Tabellenberschrift
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:14.0pt;
	font-size:12.0pt;
	font-family:Tele-GroteskFet;
	color:white;
	layout-grid-mode:line;}
p.Tabellen-Inhalt, li.Tabellen-Inhalt, div.Tabellen-Inhalt
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.Tabellenberschrift0, li.Tabellenberschrift0, div.Tabellenberschrift0
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:bold;}
p.TitelCharts, li.TitelCharts, div.TitelCharts
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:14.0pt;
	font-family:Tele-GroteskFet;
	color:white;
	layout-grid-mode:line;}
p.Titelgrafik, li.Titelgrafik, div.Titelgrafik
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	background:#CCCCCC;
	font-size:9.0pt;
	font-family:Tele-GroteskNor;}
p.GrafikMitUntertitel, li.GrafikMitUntertitel, div.GrafikMitUntertitel
	{margin-top:0in;
	margin-right:-.1in;
	margin-bottom:3.0pt;
	margin-left:-.1in;
	line-height:12.0pt;
	page-break-after:avoid;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:Tele-GroteskNor;}
p.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige, =
li.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige, =
div.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige
	{margin-top:0in;
	margin-right:-.1in;
	margin-bottom:3.0pt;
	margin-left:-.1in;
	line-height:12.0pt;
	page-break-after:avoid;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:Tele-GroteskNor;}
p.Begriff, li.Begriff, div.Begriff
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	line-height:11.0pt;
	font-size:11.0pt;
	font-family:Tele-GroteskHal;}
p.ersteUeberschriftohneNummer, li.ersteUeberschriftohneNummer, =
div.ersteUeberschriftohneNummer
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:1.5in;
	margin-left:0in;
	text-align:justify;
	page-break-before:always;
	page-break-after:avoid;
	font-size:26.0pt;
	font-family:Tele-Antiqua;}
span.EmailFormatvorlage72
	{font-family:"Courier New";
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Hi,</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New"'>Are the Slides and Docs from the WG =
meeting
yesterday somewhere available?</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New"'>:: tc ::</span></font></p>

<p class=3DMsoNormal><font size=3D2 =
face=3DTele-GroteskNor>&nbsp;</font></p>

</div>

</body>

</html>

------=_NextPart_000_0000_01C2EEF6.1A8E3CD0--


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



From mailnull@www1.ietf.org  Thu Mar 20 19:29:49 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15694
	for <ieprep-archive@odin.ietf.org>; Thu, 20 Mar 2003 19:29:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2L0lt012475
	for ieprep-archive@odin.ietf.org; Thu, 20 Mar 2003 19:47:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0ltO12472
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 19:47:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15688
	for <ieprep-web-archive@ietf.org>; Thu, 20 Mar 2003 19:29:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0k4O12392;
	Thu, 20 Mar 2003 19:46:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0jjO12359
	for <ieprep@optimus.ietf.org>; Thu, 20 Mar 2003 19:45:45 -0500
Received: from chntex01.is.dyncorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15654
	for <ieprep@ietf.org>; Thu, 20 Mar 2003 19:27:05 -0500 (EST)
Received: by chntex01.is.dyncorp.com with Internet Mail Service (5.5.2653.19)
	id <F4Z06QAC>; Thu, 20 Mar 2003 19:27:29 -0500
Message-ID: <CBED705A7FD2D311865500508B1089410D995C10@chntex02.is.dyncorp.com>
From: "Gunn, Janet" <Janet.Gunn@DynCorp.com>
To: "'tc@baryt.de'" <tc@baryt.de>, ieprep <ieprep@ietf.org>
Subject: RE: [Ieprep] Slides and Docs from WG meeting?
Date: Thu, 20 Mar 2003 19:25:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2EF40.643C8B30"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2EF40.643C8B30
Content-Type: text/plain;
	charset="iso-8859-1"

The documents are all available here
http://www.ietf.org/ids.by.wg/ieprep.html
<http://www.ietf.org/ids.by.wg/ieprep.html> 
or here
http://www.ietf.org/ids.by.wg/none.html
<http://www.ietf.org/ids.by.wg/none.html> 
 
I expect the [resentations will be available later.
 

-----Original Message-----
From: Thorsten Claus [mailto:tc@baryt.de]
Sent: Thursday, March 20, 2003 6:34 PM
To: ieprep
Subject: [Ieprep] Slides and Docs from WG meeting?



Hi,

Are the Slides and Docs from the WG meeting yesterday somewhere available?

 

:: tc ::

 


------_=_NextPart_001_01C2EF40.643C8B30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4134.100" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Helvetica;
}
@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Tele-GroteskNor;
}
@font-face {
	font-family: Tele-Antiqua;
}
@font-face {
	font-family: Tele-GroteskUlt;
}
@font-face {
	font-family: Tele-GroteskFet;
}
@font-face {
	font-family: Tele-GroteskHal;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 56.7pt =
70.85pt; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
H1 {
	PAGE-BREAK-BEFORE: always; FONT-WEIGHT: normal; FONT-SIZE: 26pt; =
MARGIN: 0in 0in 1.5in; TEXT-INDENT: 0in; FONT-FAMILY: Tele-Antiqua; =
TEXT-ALIGN: justify
}
H2 {
	FONT-WEIGHT: normal; FONT-SIZE: 12pt; MARGIN: 0.25in 0in 9pt; =
TEXT-INDENT: 0in; FONT-FAMILY: Tele-GroteskUlt; TEXT-ALIGN: justify
}
H3 {
	FONT-WEIGHT: normal; FONT-SIZE: 12pt; MARGIN: 12pt 0in 3pt; =
TEXT-INDENT: 0in; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: justify
}
H4 {
	FONT-WEIGHT: normal; FONT-SIZE: 11pt; MARGIN: 12pt 0in 3pt; =
TEXT-INDENT: 0in; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: justify
}
H5 {
	FONT-WEIGHT: normal; FONT-SIZE: 11pt; MARGIN: 6pt 0in 0pt; =
TEXT-INDENT: 0in; FONT-FAMILY: Tele-GroteskHal; TEXT-ALIGN: justify
}
H6 {
	FONT-WEIGHT: normal; FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; =
TEXT-INDENT: 0in; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoHeading7 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoHeading7 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoHeading7 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoHeading8 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoHeading8 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoHeading8 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; TEXT-INDENT: 0in; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoToc1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: Tele-GroteskUlt; =
TEXT-ALIGN: justify
}
LI.MsoToc1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: Tele-GroteskUlt; =
TEXT-ALIGN: justify
}
DIV.MsoToc1 {
	FONT-SIZE: 12pt; MARGIN: 0.25in 0in 0pt; FONT-FAMILY: Tele-GroteskUlt; =
TEXT-ALIGN: justify
}
P.MsoToc2 {
	FONT-SIZE: 10pt; MARGIN: 12pt 0in 0pt 0.45in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskHal; TEXT-ALIGN: justify
}
LI.MsoToc2 {
	FONT-SIZE: 10pt; MARGIN: 12pt 0in 0pt 0.45in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskHal; TEXT-ALIGN: justify
}
DIV.MsoToc2 {
	FONT-SIZE: 10pt; MARGIN: 12pt 0in 0pt 0.45in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskHal; TEXT-ALIGN: justify
}
P.MsoToc3 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.6in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoToc3 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.6in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoToc3 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.6in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoToc4 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoToc4 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoToc4 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.3in; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoToc5 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 33pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
LI.MsoToc5 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 33pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
DIV.MsoToc5 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 33pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
P.MsoToc6 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 44pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
LI.MsoToc6 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 44pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
DIV.MsoToc6 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 44pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
P.MsoToc7 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 55pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
LI.MsoToc7 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 55pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
DIV.MsoToc7 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 55pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
P.MsoToc8 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 66pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
LI.MsoToc8 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 66pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
DIV.MsoToc8 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 66pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
P.MsoToc9 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 77pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
LI.MsoToc9 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 77pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
DIV.MsoToc9 {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 77pt; FONT-FAMILY: "Times New =
Roman"; TEXT-ALIGN: justify
}
P.MsoFootnoteText {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoFootnoteText {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoFootnoteText {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoHeader {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoHeader {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoHeader {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoCaption {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoCaption {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoCaption {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
SPAN.MsoFootnoteReference {
	VERTICAL-ALIGN: super; FONT-FAMILY: Tele-GroteskNor
}
SPAN.MsoPageNumber {
	FONT-FAMILY: Tele-GroteskNor
}
P.MsoListBullet {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 11pt 21.25pt; TEXT-INDENT: -21.25pt; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListBullet {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 11pt 21.25pt; TEXT-INDENT: -21.25pt; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListBullet {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 11pt 21.25pt; TEXT-INDENT: -21.25pt; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListNumber {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListNumber {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListNumber {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListBullet2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListBullet2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListBullet2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListBullet3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListBullet3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListBullet3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListBullet4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListBullet4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListBullet4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListBullet5 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListBullet5 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListBullet5 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListNumber2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListNumber2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListNumber2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; TEXT-INDENT: -0.8in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListNumber3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListNumber3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListNumber3 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoListNumber4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.MsoListNumber4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.MsoListNumber4 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.25in; TEXT-INDENT: -0.25in; =
LINE-HEIGHT: 11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.MsoTitle {
	FONT-SIZE: 22pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 21pt; FONT-FAMILY: =
Tele-Antiqua; TEXT-ALIGN: justify
}
LI.MsoTitle {
	FONT-SIZE: 22pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 21pt; FONT-FAMILY: =
Tele-Antiqua; TEXT-ALIGN: justify
}
DIV.MsoTitle {
	FONT-SIZE: 22pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 21pt; FONT-FAMILY: =
Tele-Antiqua; TEXT-ALIGN: justify
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
P.Text {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Text {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Text {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.TextIndent1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 35.4pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.TextIndent1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 35.4pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.TextIndent1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 35.4pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.TextIndent2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 70.8pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.TextIndent2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 70.8pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.TextIndent2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 6pt 70.8pt; LINE-HEIGHT: 11pt; =
FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Aufzhlungmagenta {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 20.15pt; TEXT-INDENT: -20.15pt; =
LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Aufzhlungmagenta {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 20.15pt; TEXT-INDENT: -20.15pt; =
LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Aufzhlungmagenta {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 20.15pt; TEXT-INDENT: -20.15pt; =
LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Aufzhlungschwarz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; LAYOUT-GRID-MODE: line; =
TEXT-INDENT: -0.8in; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; =
TEXT-ALIGN: justify
}
LI.Aufzhlungschwarz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; LAYOUT-GRID-MODE: line; =
TEXT-INDENT: -0.8in; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; =
TEXT-ALIGN: justify
}
DIV.Aufzhlungschwarz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 128.4pt; LAYOUT-GRID-MODE: line; =
TEXT-INDENT: -0.8in; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskNor; =
TEXT-ALIGN: justify
}
P.Grafik1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Grafik1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Grafik1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Grafik2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Grafik2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Grafik2 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Grafiken {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Grafiken {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Grafiken {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Headline1 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: fuchsia; FONT-FAMILY: =
Tele-Antiqua
}
LI.Headline1 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: fuchsia; FONT-FAMILY: =
Tele-Antiqua
}
DIV.Headline1 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: fuchsia; FONT-FAMILY: =
Tele-Antiqua
}
P.Headline2 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: gray; FONT-FAMILY: =
Tele-Antiqua
}
LI.Headline2 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: gray; FONT-FAMILY: =
Tele-Antiqua
}
DIV.Headline2 {
	FONT-SIZE: 20pt; MARGIN: 0in 0in 0pt; COLOR: gray; FONT-FAMILY: =
Tele-Antiqua
}
P.Kopfzeile1 {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
LI.Kopfzeile1 {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
DIV.Kopfzeile1 {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 9pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
P.KopfzeileZusatz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.KopfzeileZusatz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.KopfzeileZusatz {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.KopfzeileZusatz1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
LI.KopfzeileZusatz1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
DIV.KopfzeileZusatz1 {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskUlt; TEXT-ALIGN: justify
}
P.Kurzberschrift {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 3pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
LI.Kurzberschrift {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 3pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
DIV.Kurzberschrift {
	FONT-SIZE: 9pt; MARGIN: 0in 0in 3pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
P.Tabtextff {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
LI.Tabtextff {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
DIV.Tabtextff {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial; TEXT-ALIGN: =
justify
}
P.Tabtext1 {
	FONT-WEIGHT: bold; FONT-SIZE: 8pt; MARGIN: 6pt 0in; FONT-STYLE: =
italic; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.Tabtext1 {
	FONT-WEIGHT: bold; FONT-SIZE: 8pt; MARGIN: 6pt 0in; FONT-STYLE: =
italic; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.Tabtext1 {
	FONT-WEIGHT: bold; FONT-SIZE: 8pt; MARGIN: 6pt 0in; FONT-STYLE: =
italic; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.Tabeintrag {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 2pt 0in; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
LI.Tabeintrag {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 2pt 0in; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
DIV.Tabeintrag {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 2pt 0in; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
P.Tabelle {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Tabelle {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Tabelle {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskNor; TEXT-ALIGN: justify
}
P.Tabelle2 {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 12pt; FONT-FAMILY: =
Helvetica
}
LI.Tabelle2 {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 12pt; FONT-FAMILY: =
Helvetica
}
DIV.Tabelle2 {
	FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 12pt; FONT-FAMILY: =
Helvetica
}
P.Tabellenberschrift {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: =
justify
}
LI.Tabellenberschrift {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: =
justify
}
DIV.Tabellenberschrift {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; LINE-HEIGHT: 14pt; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: =
justify
}
P.Tabellen-Inhalt {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Times New Roman"; TEXT-ALIGN: justify
}
LI.Tabellen-Inhalt {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Times New Roman"; TEXT-ALIGN: justify
}
DIV.Tabellen-Inhalt {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: =
"Times New Roman"; TEXT-ALIGN: justify
}
P.Tabellenberschrift0 {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
LI.Tabellenberschrift0 {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
DIV.Tabellenberschrift0 {
	FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 6pt 0in 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: justify
}
P.TitelCharts {
	FONT-SIZE: 14pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: center
}
LI.TitelCharts {
	FONT-SIZE: 14pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: center
}
DIV.TitelCharts {
	FONT-SIZE: 14pt; MARGIN: 0in 0in 0pt; LAYOUT-GRID-MODE: line; COLOR: =
white; FONT-FAMILY: Tele-GroteskFet; TEXT-ALIGN: center
}
P.Titelgrafik {
	FONT-SIZE: 9pt; BACKGROUND: #cccccc; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
LI.Titelgrafik {
	FONT-SIZE: 9pt; BACKGROUND: #cccccc; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
DIV.Titelgrafik {
	FONT-SIZE: 9pt; BACKGROUND: #cccccc; MARGIN: 0in 0in 0pt; LINE-HEIGHT: =
11pt; FONT-FAMILY: Tele-GroteskNor; TEXT-ALIGN: justify
}
P.GrafikMitUntertitel {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
LI.GrafikMitUntertitel {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
DIV.GrafikMitUntertitel {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
P.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
LI.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
DIV.FormatvorlageGrafikMitUntertitelRechtsSchattiertEinfacheeinfarbige =
{
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium =
none; PADDING-LEFT: 0in; FONT-SIZE: 12pt; PADDING-BOTTOM: 0in; MARGIN: =
0in -0.1in 3pt; BORDER-LEFT: medium none; LINE-HEIGHT: 12pt; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none; FONT-FAMILY: =
Tele-GroteskNor
}
P.Begriff {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskHal; TEXT-ALIGN: justify
}
LI.Begriff {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskHal; TEXT-ALIGN: justify
}
DIV.Begriff {
	FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; LINE-HEIGHT: 11pt; FONT-FAMILY: =
Tele-GroteskHal; TEXT-ALIGN: justify
}
P.ersteUeberschriftohneNummer {
	PAGE-BREAK-BEFORE: always; FONT-SIZE: 26pt; MARGIN: 0in 0in 1.5in; =
FONT-FAMILY: Tele-Antiqua; TEXT-ALIGN: justify
}
LI.ersteUeberschriftohneNummer {
	PAGE-BREAK-BEFORE: always; FONT-SIZE: 26pt; MARGIN: 0in 0in 1.5in; =
FONT-FAMILY: Tele-Antiqua; TEXT-ALIGN: justify
}
DIV.ersteUeberschriftohneNummer {
	PAGE-BREAK-BEFORE: always; FONT-SIZE: 26pt; MARGIN: 0in 0in 1.5in; =
FONT-FAMILY: Tele-Antiqua; TEXT-ALIGN: justify
}
SPAN.EmailFormatvorlage72 {
	COLOR: windowtext; FONT-FAMILY: "Courier New"
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
documents are all available here</FONT></SPAN></DIV>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/ids.by.wg/ieprep.html">http://www.ietf.org/i=
ds.by.wg/ieprep.html</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff size=3D2>or=20
here</FONT></SPAN></DIV>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/ids.by.wg/none.html">http://www.ietf.org/ids=
.by.wg/none.html</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D010532700-21032003><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
expect the [resentations will be available later.</FONT></SPAN></DIV>
<DIV><SPAN class=3D010532700-21032003></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Thorsten Claus=20
  [mailto:tc@baryt.de]<BR><B>Sent:</B> Thursday, March 20, 2003 6:34=20
  PM<BR><B>To:</B> ieprep<BR><B>Subject:</B> [Ieprep] Slides and Docs =
from WG=20
  meeting?<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Hi,</SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Are the Slides =
and Docs=20
  from the WG meeting yesterday somewhere available?</SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoAutoSig><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">:: tc =
::</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DTele-GroteskNor=20
size=3D2></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2EF40.643C8B30--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Thu Mar 20 19:37:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15858
	for <ieprep-archive@odin.ietf.org>; Thu, 20 Mar 2003 19:37:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2L0tdN12748
	for ieprep-archive@odin.ietf.org; Thu, 20 Mar 2003 19:55:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0tcO12745
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 20 Mar 2003 19:55:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15846
	for <ieprep-web-archive@ietf.org>; Thu, 20 Mar 2003 19:37:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0sEO12691;
	Thu, 20 Mar 2003 19:54:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2L0rXO12645
	for <ieprep@optimus.ietf.org>; Thu, 20 Mar 2003 19:53:33 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15817
	for <ieprep@ietf.org>; Thu, 20 Mar 2003 19:34:55 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Thu, 20 Mar 2003 19:35:49 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003032019365621879
 ; Thu, 20 Mar 2003 19:36:56 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPM2CAT>; Thu, 20 Mar 2003 19:36:35 -0500
Message-Id: <D24D16A6707B0A4B9EF084299CE99B393646AD@mcl-its-exs02.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "'Thorsten Claus '" <tc@baryt.de>, "'ieprep '" <ieprep@ietf.org>
Subject: RE: [Ieprep] Slides and Docs from WG meeting?
Date: Thu, 20 Mar 2003 19:36:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

Hello,

I submitted the presentation materials this morning.  They will be at
http://www.ietf.org/proceedings/03mar/ in about a day or two.

I'll submit the minutes as soon as I get rough consensus on what happened.
:-)

Kimberly


-----Original Message-----
From: Thorsten Claus
To: ieprep
Sent: 3/20/2003 6:33 PM
Subject: [Ieprep] Slides and Docs from WG meeting?

Hi,

Are the Slides and Docs from the WG meeting yesterday somewhere
available?

 

:: tc ::

 

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



From mailnull@www1.ietf.org  Thu Mar 27 11:13:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05353
	for <ieprep-archive@odin.ietf.org>; Thu, 27 Mar 2003 11:13:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2RGYLx28957
	for ieprep-archive@odin.ietf.org; Thu, 27 Mar 2003 11:34:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RGYLO28954
	for <ieprep-web-archive@optimus.ietf.org>; Thu, 27 Mar 2003 11:34:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05332
	for <ieprep-web-archive@ietf.org>; Thu, 27 Mar 2003 11:12:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RGW8O28826;
	Thu, 27 Mar 2003 11:32:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RGH6O28089
	for <ieprep@optimus.ietf.org>; Thu, 27 Mar 2003 11:17:06 -0500
Received: from web14802.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA04718
	for <ieprep@ietf.org>; Thu, 27 Mar 2003 10:55:15 -0500 (EST)
Message-ID: <20030327155736.94380.qmail@web14802.mail.yahoo.com>
Received: from [65.213.193.49] by web14802.mail.yahoo.com via HTTP; Thu, 27 Mar 2003 07:57:36 PST
Date: Thu, 27 Mar 2003 07:57:36 -0800 (PST)
From: CAITR <info@caitr.org>
Reply-To: info@caitr.org
To: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1029449120-1048780656=:93961"
Subject: [Ieprep] Internetworking 2003: Call for Papers
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

--0-1029449120-1048780656=:93961
Content-Type: text/plain; charset=us-ascii


Dear Colleagues:

Our sincere apologies if you receive multiple copies of this announcement.

     CONFERENCE ANNOUNCEMENT AND CALL FOR PRESENTATIONS

                   Internetworking 2003
                      June 22-24, 2003
                   San Jose, California
      In technical cooperation with IEEE, IFIP, and ACM (Pending)


Internetworking 2003 Program Committee cordially invites you to submit proposals for original, unpublished presentations focusing on internetworking technologies in the IP, optical, and wireless domains. Summaries not exceeding 250 words can be submitted to submissions@caitr.org for review and possible inclusion in the program, no later than April 11, 2003. Topics of interest include, but are not limited to the following:

- Voice over IP (VoIP)
- IP Video Conferencing
- Storage Area Networks (SANs)
- Unicast and Multicast Routing and Convergence
- QoS Routing
- Network Security and Service Integration
- Operational Support Systems
- Virtual Private Networks
- Internetworking Wireless LANs and 3G Wireless Networks
- IP-based Infrastructure for Wireless Networks
- Internetworking IP and Optical Networks
- Internetworking MPLS with Legacy ATM and Frame Relay Networks
- Transition from IPv4 to IPv6 and interworking
- Pervasive Computing
- High Speed Transport Layer Protocols
- Peer to Peer Networking and Grid Computing
- Video Teleconferencing (VTC) 
- 802.11 Hotspots


The Internetworking 2003 event in June will include participation from industry, government agencies, and academia. If you need additional technical information, please contact the Technical Cochairs Professor Maurice GAGNAIRE <gagnaire@enst.fr>, or Daniel Awduche <Awduche@awduche.com>.


--0-1029449120-1048780656=:93961
Content-Type: text/html; charset=us-ascii

<DIV id=message>
<P>Dear Colleagues:</P>
<P>Our sincere apologies if you receive multiple copies of this announcement.</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp; CONFERENCE ANNOUNCEMENT AND CALL FOR PRESENTATIONS</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internetworking 2003<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; June 22-24, 2003<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; San Jose, California<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In technical cooperation with IEEE, IFIP, and ACM (Pending)</P>
<P><BR>Internetworking 2003 Program Committee cordially invites you to submit proposals for original, unpublished presentations focusing on internetworking technologies in the IP, optical, and wireless domains. Summaries not exceeding 250 words can be submitted to <A href="http://mail.yahoo.com/config/login?/ym/Compose?To=submissions@caitr.org" target=_blank>submissions@caitr.org</A> for review and possible inclusion in the program, no later than April 11, 2003. Topics of interest include, but are not limited to the following:</P>
<P>- Voice over IP (VoIP)<BR>- IP Video Conferencing<BR>- Storage Area Networks (SANs)<BR>- Unicast and Multicast Routing and Convergence<BR>- QoS Routing<BR>- Network Security and Service Integration<BR>- Operational Support Systems<BR>- Virtual Private Networks<BR>- Internetworking Wireless LANs and 3G Wireless Networks<BR>- IP-based Infrastructure for Wireless Networks<BR>- Internetworking IP and Optical Networks<BR>- Internetworking MPLS with Legacy ATM and Frame Relay Networks<BR>- Transition from IPv4 to IPv6 and interworking<BR>- Pervasive Computing<BR>- High Speed Transport Layer Protocols<BR>- Peer to Peer Networking and Grid Computing<BR>- Video Teleconferencing (VTC) <BR>- 802.11 Hotspots</P>
<P><BR>The Internetworking 2003 event in June will include participation from industry, government agencies, and academia. If you need additional technical information, please contact the Technical Cochairs Professor Maurice GAGNAIRE &lt;<A href="http://mail.yahoo.com/config/login?/ym/Compose?To=gagnaire@enst.fr" target=_blank>gagnaire@enst.fr</A>&gt;, or Daniel Awduche &lt;<A href="http://mail.yahoo.com/config/login?/ym/Compose?To=Awduche@awduche.com" target=_blank>Awduche@awduche.com</A>&gt;.<BR></P></DIV>
--0-1029449120-1048780656=:93961--
_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep



From mailnull@www1.ietf.org  Fri Mar 28 09:52:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00243
	for <ieprep-archive@odin.ietf.org>; Fri, 28 Mar 2003 09:52:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2SFDoI10596
	for ieprep-archive@odin.ietf.org; Fri, 28 Mar 2003 10:13:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SFDoO10593
	for <ieprep-web-archive@optimus.ietf.org>; Fri, 28 Mar 2003 10:13:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00218
	for <ieprep-web-archive@ietf.org>; Fri, 28 Mar 2003 09:51:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SFC8O10531;
	Fri, 28 Mar 2003 10:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SFBrO10508
	for <ieprep@optimus.ietf.org>; Fri, 28 Mar 2003 10:11:53 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00153
	for <ieprep@ietf.org>; Fri, 28 Mar 2003 09:49:32 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Fri, 28 Mar 2003 09:50:20 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003032809513018873
 ; Fri, 28 Mar 2003 09:51:30 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <FSPM5JVN>; Fri, 28 Mar 2003 09:51:09 -0500
Message-Id: <D24D16A6707B0A4B9EF084299CE99B393646D2@mcl-its-exs02.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>,
        "'Scott Bradner ' (E-mail)" <sob@harvard.edu>
Date: Fri, 28 Mar 2003 09:51:30 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] ieprep minutes San Francisco
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>

IEPREP Meeting Notes

Internet Emergency Preparedness WG (ieprep)

Wednesday, March 19 at 1300-1500 
================================

CHAIRS: Scott Bradner   <sob@harvard.edu> 
        Kimberly King   <kimberly.s.king@saic.com>

AGENDA:

		agenda bashing	
                Chairs
5 minutes

		draft-polk-ieprep-flow-model-considerations-00.txt
                James Polk
10 minutes

                draft-ietf-ieprep-framework-04.txt 
                draft-ietf-ieprep-ets-telephony-02.txt
                draft-ietf-ieprep-ets-general-02.txt                     
                Ken Carlberg
20 minutes

                ETS progress at the ITU 
                Stephen Perschau
10 minutes

                ieprep next steps
                Group discussion
25 minutes
----------
70 minutes

James Polk -> flow model considerations
Informative document on an information track

Delineate the control plane from the data plane
Signaling/Control Plane between the responder and initiator
Data plane between the responder and initiator
	
Major change will be to add a new diagram

And change wording around QoS

Questions:
An email suggestion to add SAP, but unsure of its relevance.

Ken Carlberg -> ETS General Requirements
Changing IPprep to IPPREP

Changing "better than best effort" around application layer mechanisms to
"other than best effort".

Changing:

	don't refer to VoIP as "other elastic application"

	change "carriers" to "telephony carriers"

expand the reference of "higher probability" to refer to call completion

	removed term "centralized authentication" in reference 
	to PSTN security model

TBD: 
	refer to Genuity and Sprint Traffic Engineering in Atlanta IETF

request for discussion of service that makes a positive difference

	original comments aimed at general requirements

More to be added (but perhaps premature):
	DCCP -> spec due on Dec' 03
	NSIS
	UDP-Lite

Questions:
Dennis Berg: I am trying to understand the character of a framework document
vs. a best practices document, etc. It seems to not go all the way in coming
out with a set of requirements

Scott Bradner: This is an IETF meta-question, frameworks are not meant to be
specific.  Frameworks describe the environment in which we are playing.  The
requirements are how to build the swing set.  Frameworks are not
descriptions of what you must do but describe the environment.  

Dennis Berg: Are we going to move forward with a requirements documents? Not
quite clear: high probability of completion and guarantee of completion
objective of not expecting every network or portion of a call path to be
enhanced with this work.  In other words, partial deployment is a
compromise, not a goal.

Scott Bradner: An absolute requirement for absolute reliability would imply
more resources, i.e. more bandwidth.

Dennis Berg: should just say to do a little bit better (perfect would be the
panacea, but...) at least.

Janet Gunn: One of the requirements that I would like to see is if there is
a call admission process, that there is priority in the call admission
process (call setup), even if it means simply trying again (and this goes in
the telephony requirements doc).

Ken Carlberg: That type of requirement would be in ip tel requirement
document.  He asks Janet to sent some potential text for the document.

Bill Woodcock: These problems aren't network related the network is already
doing better than PSTN call completion, so the expectation between
circuit-switched network and packet-switched network folks is completely at
odds.

Scott Bradner: We postulate that the backbone isn't the issue, but problems
are more in the access networks such as cable networks or enterprise
networks.

Bill Woodcock: We keep requiring methods, not service requirements, and no
one has demonstrated that calls are not being completed, so is there really
a problem?

Scott Bradner:  Some people want it and will pay for it so let them do so.

Bill Woodcock: That is not what IETF is here for.  No one has demonstrated
that there is a problem.

Scott Bradner: If there is no need then it will die its death and we don't
need lots of protocol development anyway.

James Polk: Just because there hasn't been an issue doesn't mean there won't
be one

Dick Knight: I am agreeing that the problem is in the access network, not
the backbone.

Scott Bradner: also the gateway

Dick Knight: How does one do authentication, massive processing, etc. in a
congested environment?  There isn't enough information about this in the
drafts.

Scott Bradner: and authorization

Eric Rescorla : If we cannot simulate the problem, how can we test a
solution?

Janet Gunn: There aren't a great deal of SIP phones at this point, and there
will be critical mass at some point

Dave Crocker: Theoretical possibility of the infrastructure being a problem
is real, and the potential damage is significant, so placing concern is
good. The question is resources, and this working group has yet to produce
so focus on the backbone should only be done after other issues have been
solved.

Peter Lothberg: Who is the operator that is the problem here? There is
decoupling between the access point and the backbone provider.

Dennis Berg: I have a procedural question.  What is the relationship between
your documents and Henning's RFC 3487, is there order of precedence and
overlap? Or a contradiction? 

Greg Woodhouse: In D.C. on 9/11, and the cell phone was his only means of
communication.  

Stephen Perschau -> ITU-T progress
E.106 description of an International Emergency Preference Scheme for
Disaster Relief Operations adding support for packet networks

Supplement to J.160 architectural framework for the delivery of
time-critical services over cable data networks

J.ETS new recommendation addressing emergency telecom over cable data
networks

Study Group 11
including support for an international codepoint for ETS

Study Group 16
Question I use of public telecom services for emergency and disaster relief
operations

Study Items
identify organizations addressing the various aspects related to telecom for
emergency and disaster relief operations

	working on security aspects for authentication of users and
prevention of interference

	TDR standardization (British Telco's might not be reimbursed if ETS
term was used in place of TDR so the name was changed)
	
Questions:
Brian Rosen: The codepoint in SG 11 is an ISUP codepoint right?

IEPREP Next Steps:
Scott Bradner: We should not assume that the backbone is a part of the
problem at the moment.

Comments:
Janet Gunn: The one thing in the charter that we haven't played with is the
BCP

John Gilmore: To what extent is the discussion here to deny service to
non-authorized users? Will non-authorized traffic simply be dropped?

Scott Bradner:  I'm reluctant to support turning off everyone.  I think
civilian should communicate just as much as government.  I suggest few ISPs
to convert to ETS only as their customers wouldn't stand for it.  

John Gilmore: Some governments declare "emergency" to curb communications.

Steve Silverman: if the prioritized traffic is less than 10% of the rest,
the impact is small.

Dan Romascanu: The issue of E911 traffic hasn't been addressed here.

Thorsten Claus (?): from a SP perspective, how can I invest money in
building my network for working with the government?  Are there any business
cases?

Janet Gunn: Money is paid for service provider and to the vendor for
software changes for GETS capability, maybe that will happen here... I  have
never seen any desire to block non-authorized traffic for any reason other
than call completion. There has never been any intention to make this only
available to government workers. There is a precedence for putting in
mechanisms for limiting the GETS type traffic.

Brian Rosen: One should not assume that this is only for voice.

Dave Knight: Globally, the US is not paying other countries to put this
stuff in (applause).

Dennis Berg: Service Providers are paranoid about E911 traffic. Should make
a note about the position about IEPREP capabilities vs. E911 support.

Janet Gunn: working on 911 issues for WPS, the PSAPS do not want
preferential treatment.  Human resources are the constrained resource.

Keith Dredge: can E911 be out of the scope for this group?

Scott Bradner:  E911 is being worked in SIPPING.  E911 is out of scope for
IEPREP.

Jon Peterson: believes that working on the access points, links, and
enterprise networks is going to be time consuming and difficult but says
okay if IEPREP has the stomach for it.

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



From mailnull@www1.ietf.org  Mon Mar 31 12:15:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15082
	for <ieprep-archive@odin.ietf.org>; Mon, 31 Mar 2003 12:15:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h2VHcxN21925
	for ieprep-archive@odin.ietf.org; Mon, 31 Mar 2003 12:38:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VHcwT21922
	for <ieprep-web-archive@optimus.ietf.org>; Mon, 31 Mar 2003 12:38:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15066
	for <ieprep-web-archive@ietf.org>; Mon, 31 Mar 2003 12:15:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VHSOT20633;
	Mon, 31 Mar 2003 12:28:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2VHRbT20542
	for <ieprep@optimus.ietf.org>; Mon, 31 Mar 2003 12:27:37 -0500
Received: from mclmx.mail.saic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14611
	for <ieprep@ietf.org>; Mon, 31 Mar 2003 12:03:47 -0500 (EST)
Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com for ieprep@ietf.org; Mon, 31 Mar 2003 11:55:47 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
 by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.17) with SMTP id M2003033111565805584
 for <ieprep@ietf.org>; Mon, 31 Mar 2003 11:56:58 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19)
	id <2AXFCPD6>; Mon, 31 Mar 2003 11:56:36 -0500
Message-Id: <D24D16A6707B0A4B9EF084299CE99B393646EF@mcl-its-exs02.mail.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: "Ieprep (E-mail)" <ieprep@ietf.org>
Date: Mon, 31 Mar 2003 11:56:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Ieprep] access and enterprise networks
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
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>


At the last meeting, people expressed an interest in addressing access and
enterprise networks.  As frustrating as it might seem, if there is to be any
progress, the problem still has to be precisely defined.  

Let's consider defining the problem and it would be nice to factor in some
practical realities too.  

Here are some assumptions: 

A) ETS locations are known in advance of any emergency. When an emergency
occurs, each will already be connected to a network (unless the emergency
damaged the connection in which case that situation is out of scope).

B) Generally, we aren't trying to simultaneously solve the problem for every
ETS location in the entire world at the same time.  Rather, subsets of ETS
locations are affiliated with each other and some policy decision (and
likely funding scenario) is made for that subset.  An example, say all fire
stations in particular county want to procure IP connections for their use.
Meanwhile, a city's hospitals might be under completely different policy and
funding and aren't particularly interested in paying for enhanced
communications via some fancy IP network with the fire stations.  

So, what is it that we want to ensure?  Would ieprep like a service that
provided some minimum bandwidth guarantee (like gold service) over the
access link and that's sufficient to make everyone reasonably happy?  If
that kind of service just isn't acceptable, then please provide some text
and details about the problem you believe we need to address.

Kimberly


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