From ieprep-bounces@ietf.org Thu Oct 06 11:42:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENXsg-0007E0-7F; Thu, 06 Oct 2005 11:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENXsf-0007Dv-9m
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 11:42:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10955
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 11:41:58 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENY1j-0005Fj-5N
	for Ieprep@ietf.org; Thu, 06 Oct 2005 11:51:26 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j952dHE1017836
	for <Ieprep@ietf.org>; Tue, 4 Oct 2005 22:39:17 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510050239.j952dHE1017836@nic-naa.net>
To: Ieprep@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17834.1128479957.1@nic-naa.net>
Date: Tue, 04 Oct 2005 22:39:17 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: [Ieprep] IAA charter item query
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Oki all,

I've grovelled through the archives abck to the first charter and I haven't
found a satisfactory discussion of the IAA requirement, or non-requirement,
or operational experience(s) with any IAA specificiation or reference
implementation.

If anyone has some clue to throw my way, I'd appreciate it. The data is
anecdotal, but in the Katrina outage area IAA-like query and response
attempts (absent an actual IAA mechanism other than voice-to-voice w/o
any call routing or forwarding or logging, other than that incidental to
voice service, contributed to network load, responder tasking, dispatch
failure, and of course, end user stress, and no governmental or quango
involved in Katrina response operates a "missing persons" database, though
one quango has made an attempt in that area.

Cheers,
Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 12:18:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENYOd-00072t-80; Thu, 06 Oct 2005 12:15:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENYOb-00072S-D9
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 12:15:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12724
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 12:14:58 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENYXi-0006bd-Hn
	for Ieprep@ietf.org; Thu, 06 Oct 2005 12:24:27 -0400
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com
	[135.1.23.83])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j96GEnGc020570; 
	Thu, 6 Oct 2005 11:14:49 -0500 (CDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service
	(5.5.2657.72) id <RN67G2RH>; Thu, 6 Oct 2005 11:15:54 -0500
Message-ID: <17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
From: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
To: Eric Brunner-Williams at a VSAT somewhere <brunner@nic-naa.net>,
	Ieprep@ietf.org
Subject: RE: [Ieprep] IAA charter item query
Date: Thu, 6 Oct 2005 11:14:45 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Eric,

Like everyone else on the planet, I was glued to the TV during the resent disaster in New Orleans.

There were a number of occasions where the victim being interviewed said they had lost touch with family members and used the TV broadcast as an opportunity to send a message saying where they were now and how they could be contacted by the missing family members. As I watched this exchange a number of times, each time I was reminded of the ""I Am Alive" capability database that still is not in existence  in the US.

Having said that, it is my understanding that such a capability would entail the ability to post location/status type of data about individuals on a database that could be queried by the public. Perhaps the posting might need to be done by an agency such as the Red Cross in the US, to avoid malicious postings. (Mickey Mouse is OK, or worse, fraudulent information).

If that understanding is basically correct, then it would seem to me that neither the posting nor the querying of the database, while important to the participants, is of a nature that it would need preference over other traffic, such as the communications from First Responders require.  If it sufficient to support this capability with the same level of service as provided for ordinary communications, does the effort then fall on just developing the capability, which may not need any special accommodations in the IP space, or am I missing something?


Stu Goldman
Lucent Technologies
5531 E. Kelton LN
Scottsdale,AZ 85254
602 493 8438 home office
623-582-7136 voicemail  


-----Original Message-----
From: ieprep-bounces@ietf.org [mailto:ieprep-bounces@ietf.org]On Behalf
Of Eric Brunner-Williams at a VSAT somewhere
Sent: Tuesday, October 04, 2005 7:39 PM
To: Ieprep@ietf.org
Subject: [Ieprep] IAA charter item query


Oki all,

I've grovelled through the archives abck to the first charter and I haven't
found a satisfactory discussion of the IAA requirement, or non-requirement,
or operational experience(s) with any IAA specificiation or reference
implementation.

If anyone has some clue to throw my way, I'd appreciate it. The data is
anecdotal, but in the Katrina outage area IAA-like query and response
attempts (absent an actual IAA mechanism other than voice-to-voice w/o
any call routing or forwarding or logging, other than that incidental to
voice service, contributed to network load, responder tasking, dispatch
failure, and of course, end user stress, and no governmental or quango
involved in Katrina response operates a "missing persons" database, though
one quango has made an attempt in that area.

Cheers,
Eric

_______________________________________________
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 ieprep-bounces@ietf.org Thu Oct 06 12:35:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENYiS-0006cn-Cr; Thu, 06 Oct 2005 12:35:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENYiQ-0006ci-Ix
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 12:35:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13781
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 12:35:27 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENYrX-0007VU-3n
	for Ieprep@ietf.org; Thu, 06 Oct 2005 12:44:56 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j952kvHn017977;
	Tue, 4 Oct 2005 22:46:57 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510050246.j952kvHn017977@nic-naa.net>
To: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
Subject: Re: [Ieprep] IAA charter item query 
In-Reply-To: Your message of "Thu, 06 Oct 2005 11:14:45 CDT."
	<17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17975.1128480417.1@nic-naa.net>
Date: Tue, 04 Oct 2005 22:46:57 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Stu,


> ... post location/status type of data about individuals on a database th
> at could be queried by the public ...

Application schema and access models do not all degenrate to "all" and "any".

> If that understanding is basically correct ...

It doesn't match with mine, but that's OK.

Our experience providing SATV/wireless|phones/VoIP to the Gulf Coast prior
to RBOC|ILEC|wirelineISPs resotration of idata and voice is different from
yours, but milage varies, and ToS/QoS has always been a fun ride.

Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 12:43:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENYpi-0000cK-Bt; Thu, 06 Oct 2005 12:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENYpf-0000bl-Ms
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 12:42:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14290
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 12:42:56 -0400 (EDT)
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENYyn-0007rp-79
	for Ieprep@ietf.org; Thu, 06 Oct 2005 12:52:25 -0400
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j96GgiWk005386
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 6 Oct 2005 12:42:45 -0400 (EDT)
Message-ID: <434553D6.902@cs.columbia.edu>
Date: Thu, 06 Oct 2005 12:41:58 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
Subject: Re: [Ieprep] IAA charter item query
References: <17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
In-Reply-To: <17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0,
	__CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0,
	__USER_AGENT 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit
Cc: Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

I agree with Stu that this is somewhat beyond the traditional focus of 
IEPREP on prioritization of first-responder and emergency coordination 
network traffic.

However, this is clearly an area where lack of standards makes things 
far less efficient than they could be. Having hundreds of impromptu web 
sites pop up where people register (and try to find others) is not 
exactly a good use of time for volunteers or families trying to reunite.

In my view, this is less of a protocol problem than a data format 
problem. If you were to define a data format representing a "sighting" 
of a person, you could then use a variety of secured mechanisms to 
gather this information, from HTTP to SIP IM to SMTP and maybe even p2p 
protocols. In some cases, for example, a laptop in a shelter may not 
have network connectivity, so it makes more sense to collect those and 
then upload them in batch by carrying a disk or having a "circuit rider" 
virtually pick them up. (We have built a system, called 7DS, that does 
something like that, although emergency use was not among our envisioned 
set of applications.)

We have one such format already, namely the PIDF-LO + CIPID format. It 
contains location information ("where/when seen") and name/original 
address information.

Henning


GOLDMAN, STUART O (STUART) wrote:
> Eric,
> 
> Like everyone else on the planet, I was glued to the TV during the
> resent disaster in New Orleans.
> 
> There were a number of occasions where the victim being interviewed
> said they had lost touch with family members and used the TV
> broadcast as an opportunity to send a message saying where they were
> now and how they could be contacted by the missing family members. As
> I watched this exchange a number of times, each time I was reminded
> of the ""I Am Alive" capability database that still is not in
> existence  in the US.
> 
> Having said that, it is my understanding that such a capability would
> entail the ability to post location/status type of data about
> individuals on a database that could be queried by the public.
> Perhaps the posting might need to be done by an agency such as the
> Red Cross in the US, to avoid malicious postings. (Mickey Mouse is
> OK, or worse, fraudulent information).
> 
> If that understanding is basically correct, then it would seem to me
> that neither the posting nor the querying of the database, while
> important to the participants, is of a nature that it would need
> preference over other traffic, such as the communications from First
> Responders require.  If it sufficient to support this capability with
> the same level of service as provided for ordinary communications,
> does the effort then fall on just developing the capability, which
> may not need any special accommodations in the IP space, or am I
> missing something?
> 
> 
> Stu Goldman Lucent Technologies 5531 E. Kelton LN Scottsdale,AZ 85254
>  602 493 8438 home office 623-582-7136 voicemail
> 
> 
> -----Original Message----- From: ieprep-bounces@ietf.org
> [mailto:ieprep-bounces@ietf.org]On Behalf Of Eric Brunner-Williams at
> a VSAT somewhere Sent: Tuesday, October 04, 2005 7:39 PM To:
> Ieprep@ietf.org Subject: [Ieprep] IAA charter item query
> 
> 
> Oki all,
> 
> I've grovelled through the archives abck to the first charter and I
> haven't found a satisfactory discussion of the IAA requirement, or
> non-requirement, or operational experience(s) with any IAA
> specificiation or reference implementation.
> 
> If anyone has some clue to throw my way, I'd appreciate it. The data
> is anecdotal, but in the Katrina outage area IAA-like query and
> response attempts (absent an actual IAA mechanism other than
> voice-to-voice w/o any call routing or forwarding or logging, other
> than that incidental to voice service, contributed to network load,
> responder tasking, dispatch failure, and of course, end user stress,
> and no governmental or quango involved in Katrina response operates a
> "missing persons" database, though one quango has made an attempt in
> that area.
> 
> Cheers, Eric
> 
> _______________________________________________ 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 ieprep-bounces@ietf.org Thu Oct 06 12:57:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZ3m-0004HU-CA; Thu, 06 Oct 2005 12:57:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZ3k-0004HP-Gg
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 12:57:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14971
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 12:57:29 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZCr-0008U0-Dc
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:06:58 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j952o5ZR018023;
	Tue, 4 Oct 2005 22:50:05 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510050250.j952o5ZR018023@nic-naa.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Ieprep] IAA charter item query 
In-Reply-To: Your message of "Thu, 06 Oct 2005 12:41:58 EDT."
	<434553D6.902@cs.columbia.edu> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18021.1128480605.1@nic-naa.net>
Date: Tue, 04 Oct 2005 22:50:05 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: "GOLDMAN, STUART O \(STUART\)" <sgoldman@lucent.com>, Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Henning,

I'm not trying to convince you, or anyone, that any rather trivial application
is in-scope for any working group. Nor that the absnece of such a mechanism is
a cause for load upon first-responder and emergency coordination network
traffic, for weeks after the failure of the communications fabric.

If there is no further clue, I'll unsub and leave you all to the chartered
deliverables.
Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 13:11:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZH9-0007WS-HC; Thu, 06 Oct 2005 13:11:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZH6-0007Vd-In
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 13:11:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15653
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 13:11:17 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZQD-0000ai-Di
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:20:46 -0400
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com
	[135.1.23.83])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j96HAvtK010967; 
	Thu, 6 Oct 2005 12:10:57 -0500 (CDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service
	(5.5.2657.72) id <RN67GPSS>; Thu, 6 Oct 2005 12:12:02 -0500
Message-ID: <17D8724A2A8D9542B2B8AE546B9E5BBC0535089A@az4315exch001u.phx.lucent.com>
From: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
To: Eric Brunner-Williams at a VSAT somewhere <brunner@nic-naa.net>,
	Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: RE: [Ieprep] IAA charter item query 
Date: Thu, 6 Oct 2005 12:10:52 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: "GOLDMAN, STUART O \(STUART\)" <sgoldman@lucent.com>, Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Eric,

I may not have been clear in my original response. I was giving support for the need for such a service and using the protracted disruption of service in a large geographical area coupled with the mass migration of that population out of the area and dispersed across the country.

I was then trying to understand how such a service could coming into existence and what protocol enhancements, if any, would be needed. (example: is preference needed?)

Henning has an excellent point that a single, uniform service capability would be much preferred over a collection of diverse service points with different procedures, formats, etc.

Personally I would hate to see any supporter of the need for IAA drop themselves from the mailing list.




Stu Goldman
Lucent Technologies
5531 E. Kelton LN
Scottsdale,AZ 85254
602 493 8438 home office
623-582-7136 voicemail  


-----Original Message-----
From: Eric Brunner-Williams at a VSAT somewhere
[mailto:brunner@nic-naa.net]
Sent: Tuesday, October 04, 2005 7:50 PM
To: Henning Schulzrinne
Cc: GOLDMAN, STUART O (STUART); Eric Brunner-Williams at a VSAT
somewhere; Ieprep@ietf.org; brunner@nic-naa.net
Subject: Re: [Ieprep] IAA charter item query 


Henning,

I'm not trying to convince you, or anyone, that any rather trivial application
is in-scope for any working group. Nor that the absnece of such a mechanism is
a cause for load upon first-responder and emergency coordination network
traffic, for weeks after the failure of the communications fabric.

If there is no further clue, I'll unsub and leave you all to the chartered
deliverables.
Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 13:15:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZLO-00089r-GM; Thu, 06 Oct 2005 13:15:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZLI-00087t-DZ
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 13:15:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15855
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 13:15:37 -0400 (EDT)
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZUP-0000pf-Ab
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:25:06 -0400
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j96HFZWk007559
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 6 Oct 2005 13:15:36 -0400 (EDT)
Message-ID: <43455B88.7000506@cs.columbia.edu>
Date: Thu, 06 Oct 2005 13:14:48 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
Subject: Re: [Ieprep] IAA charter item query
References: <17D8724A2A8D9542B2B8AE546B9E5BBC0535089A@az4315exch001u.phx.lucent.com>
In-Reply-To: <17D8724A2A8D9542B2B8AE546B9E5BBC0535089A@az4315exch001u.phx.lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0,
	__CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc: Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

If this wasn't obvious from my previous note, I would certainly advocate 
that standardization activities in this area are undertaken. I'm less 
convinced that a transport-layer group is the right venue for that. 
Maybe a BOF should investigate whether this is a components or a systems 
issue, i.e., do we need more protocols or "just" somebody to put 
existing things together?

I also suspect that without participation by, say, the ICRC, FEMA and 
other bodies, that such activities will be largely ignored. The 
traditional model of translating IETF activities into practice via 
hardware and telecom systems vendors is not likely to work well here.

(Also, it might be worth noting that OASIS is working on data formats 
related to law enforcement and emergency alerting.)

Henning

GOLDMAN, STUART O (STUART) wrote:
> Eric,
> 
> I may not have been clear in my original response. I was giving support for the need for such a service and using the protracted disruption of service in a large geographical area coupled with the mass migration of that population out of the area and dispersed across the country.
> 
> I was then trying to understand how such a service could coming into existence and what protocol enhancements, if any, would be needed. (example: is preference needed?)
> 
> Henning has an excellent point that a single, uniform service capability would be much preferred over a collection of diverse service points with different procedures, formats, etc.
> 
> Personally I would hate to see any supporter of the need for IAA drop themselves from the mailing list.
> 
> 
> 
> 
> Stu Goldman
> Lucent Technologies
> 5531 E. Kelton LN
> Scottsdale,AZ 85254
> 602 493 8438 home office
> 623-582-7136 voicemail  
> 
> 
> -----Original Message-----
> From: Eric Brunner-Williams at a VSAT somewhere
> [mailto:brunner@nic-naa.net]
> Sent: Tuesday, October 04, 2005 7:50 PM
> To: Henning Schulzrinne
> Cc: GOLDMAN, STUART O (STUART); Eric Brunner-Williams at a VSAT
> somewhere; Ieprep@ietf.org; brunner@nic-naa.net
> Subject: Re: [Ieprep] IAA charter item query 
> 
> 
> Henning,
> 
> I'm not trying to convince you, or anyone, that any rather trivial application
> is in-scope for any working group. Nor that the absnece of such a mechanism is
> a cause for load upon first-responder and emergency coordination network
> traffic, for weeks after the failure of the communications fabric.
> 
> If there is no further clue, I'll unsub and leave you all to the chartered
> deliverables.
> Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 13:31:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZaf-0005sb-In; Thu, 06 Oct 2005 13:31:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZad-0005rO-5b
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 13:31:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16702
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 13:31:27 -0400 (EDT)
Received: from ellis.ad.nps.navy.mil ([131.120.18.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZjk-0001Vq-QV
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:40:57 -0400
Received: from antony ([131.120.179.249]) by ellis.ad.nps.navy.mil with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 6 Oct 2005 10:31:13 -0700
Subject: RE: [Ieprep] IAA charter item query
From: Rex Buddenberg <budden@nps.navy.mil>
To: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
In-Reply-To: <17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
References: <17D8724A2A8D9542B2B8AE546B9E5BBC05350815@az4315exch001u.phx.lucent.com>
Content-Type: text/plain
Date: Thu, 06 Oct 2005 10:31:13 -0700
Message-Id: <1128619873.5402.693.camel@antony>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-6) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Oct 2005 17:31:13.0658 (UTC)
	FILETIME=[BFCD6DA0:01C5CA9B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit
Cc: Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Eric, Stu, and ...

One of my colleagues has generated the nasty habit of raiding my lab and
heading off to disasters.  First the tsunami (Phuket, Thailand to be
specific) and most recently Katrina (Hancock County, Ms).  There's a
distinct pattern that shows here:

1.  In all cases, there's a multi-agency government/quasi government
command and control operation.  Often with ad hoc players that just sort
of appear on scene.  These need
	- instant internet to replace the wiped-out infrastructure
	- an interoperable set of applications (e-mail, instant messaging,
common operational picture, ...).  Your comment is right -- authenticity
is a core requirement that is lacking in may of the off-shelf apps and
certainly in the off-shelf configurations out there.  
	

2.  In some cases, there's a big family reunification problem.  It
didn't occur in, say, Northridge earthquake because the quake had the
manners to arrive at o-dark-thirty when the kids weren't in school, etc.
But there were hundreds of Europeans vacationing in Thailand when the
tsunami arrived -- a very large family reunification problem.
Northridge would have had this problem if it had happened at 1000
instead of middle of night.  Katrina had the family reunification
problem layered on top of 1. above; Rita tended not to because the
warnings were heeded much more seriously.
	In Thailand, my colleague set up an 802.16 backbone with a satellite
backhaul to the Internet and populated the fringes of the .16 network
with 802.11 APs.  The primary penetrations were into a refugee camp and
a Buddhist monastery that had been appropriated as a morgue (DNA
sampling for victim ID -- surprisingly data intensive).  When the crew
got the system up and running, they simply turned it on.  And got about
50 customers in the first couple of hours (no advertising).  
	Both the morgue workers and a lot of the refugee camp population had
laptops. 

In such situations, the Internet panoply of applications is not
essential.  E-mail and www access is.  Voice service .... is not.  One
of the things our crew found in Mississippi was some aid crews showing
up with things like video cameras to document what they were doing.
That's fine, but don't build a local web site and put all the videos up
here!  (Church groups are notorious for this).   KISS is essential.  The
crews are hooking up ad hoc configurations with players that have never
worked together before -- nature of the beast.  The deployment crew may
be novices.  Fancy configurations self-defeat.  Focus on the main event
(there's a circuit-switch cellphone vs packet switch holy war that has
to be resolved here).  


Abstracting from the experiences, tells us that things like QoS control
are not terribly valuable (beyond policing the fringe users not to be
spendthrift and a few firewall configs to enforce).  Authenticity, as
Stu mentioned, is critical -- spoofing data anywhere along this chain is
bad news.  Confidentiality is also a requirement (note the medical data
above).  Stu's again right in observing that e-mail and www access to
databases are pretty kind to packet switch plumbing and any QoS cures
are likely to be worse than the disease.   
	Distributed electrical power (a few 10s of watts in several locations
rather than kwatts in one) is an issue -- no convenient technology for
that.    There's an endless list of things that belong in the packout
kits (e.g. mosquito netting) that we could get unproductively wound up
on.  
	There is a sizable issue in high Ao engineering (to pre-empt some of
the recovery problems).  

The Katrina crew did install some VOIP capabilities.  A naive judgement
of their experiences was that QoS Control was not the problem, just
getting them configured to work _at all_ was the headache.  

Anywhere near what you were looking for?





On Thu, 2005-10-06 at 11:14 -0500, GOLDMAN, STUART O (STUART) wrote:
> Eric,
> 
> Like everyone else on the planet, I was glued to the TV during the resent disaster in New Orleans.
> 
> There were a number of occasions where the victim being interviewed said they had lost touch with family members and used the TV broadcast as an opportunity to send a message saying where they were now and how they could be contacted by the missing family members. As I watched this exchange a number of times, each time I was reminded of the ""I Am Alive" capability database that still is not in existence  in the US.
> 
> Having said that, it is my understanding that such a capability would entail the ability to post location/status type of data about individuals on a database that could be queried by the public. Perhaps the posting might need to be done by an agency such as the Red Cross in the US, to avoid malicious postings. (Mickey Mouse is OK, or worse, fraudulent information).
> 
> If that understanding is basically correct, then it would seem to me that neither the posting nor the querying of the database, while important to the participants, is of a nature that it would need preference over other traffic, such as the communications from First Responders require.  If it sufficient to support this capability with the same level of service as provided for ordinary communications, does the effort then fall on just developing the capability, which may not need any special accommodations in the IP space, or am I missing something?
> 
> 
> Stu Goldman
> Lucent Technologies
> 5531 E. Kelton LN
> Scottsdale,AZ 85254
> 602 493 8438 home office
> 623-582-7136 voicemail  
> 
> 
> -----Original Message-----
> From: ieprep-bounces@ietf.org [mailto:ieprep-bounces@ietf.org]On Behalf
> Of Eric Brunner-Williams at a VSAT somewhere
> Sent: Tuesday, October 04, 2005 7:39 PM
> To: Ieprep@ietf.org
> Subject: [Ieprep] IAA charter item query
> 
> 
> Oki all,
> 
> I've grovelled through the archives abck to the first charter and I haven't
> found a satisfactory discussion of the IAA requirement, or non-requirement,
> or operational experience(s) with any IAA specificiation or reference
> implementation.
> 
> If anyone has some clue to throw my way, I'd appreciate it. The data is
> anecdotal, but in the Katrina outage area IAA-like query and response
> attempts (absent an actual IAA mechanism other than voice-to-voice w/o
> any call routing or forwarding or logging, other than that incidental to
> voice service, contributed to network load, responder tasking, dispatch
> failure, and of course, end user stress, and no governmental or quango
> involved in Katrina response operates a "missing persons" database, though
> one quango has made an attempt in that area.
> 
> Cheers,
> Eric
> 
> _______________________________________________
> 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
-- 
b


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



From ieprep-bounces@ietf.org Thu Oct 06 13:35:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZeW-0006df-6Q; Thu, 06 Oct 2005 13:35:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZeU-0006da-C1
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 13:35:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16941
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 13:35:28 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZnc-0001hu-Ix
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:44:56 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j952tZ08018107;
	Tue, 4 Oct 2005 22:55:35 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510050255.j952tZ08018107@nic-naa.net>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [Ieprep] IAA charter item query 
In-Reply-To: Your message of "Thu, 06 Oct 2005 13:14:48 EDT."
	<43455B88.7000506@cs.columbia.edu> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18105.1128480935.1@nic-naa.net>
Date: Tue, 04 Oct 2005 22:55:35 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: "GOLDMAN, STUART O \(STUART\)" <sgoldman@lucent.com>, Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

What round hole to stuff a square peg?

Its an app. If the IETF is about interoperability by zero or more
implementations of a protocol, in this instance (and others in the
apps are specified in terms of bnf or xml schema, specified by some
syntax, it still isn't a given the WG "belongs in" any particular area.

My point isn't to distract you (all) from real-time presence data and
things that produce and/or consume such data. I'm simply interested in
a problem that can be characterized as lazy write-through or disconnected
operations presence, and mechanism(s) that produce and/or consume such data.

Yes, pigeons actually will suffice, for some data compresion densities, and
yes,  users actually do attempt to obtain resource allocation during fabric
transition events.

I only asked because IAA was on the original charter.


Thanks everyone for your time.
Eric

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



From ieprep-bounces@ietf.org Thu Oct 06 13:47:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZqA-0001Cs-3I; Thu, 06 Oct 2005 13:47:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZq8-0001Cn-Pq
	for ieprep@megatron.ietf.org; Thu, 06 Oct 2005 13:47:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17694
	for <Ieprep@ietf.org>; Thu, 6 Oct 2005 13:47:31 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZzG-0002Fn-2C
	for Ieprep@ietf.org; Thu, 06 Oct 2005 13:56:59 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j952vK17018144;
	Tue, 4 Oct 2005 22:57:20 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510050257.j952vK17018144@nic-naa.net>
To: Rex Buddenberg <budden@nps.navy.mil>
Subject: Re: [Ieprep] IAA charter item query 
In-Reply-To: Your message of "Thu, 06 Oct 2005 10:31:13 PDT."
	<1128619873.5402.693.camel@antony> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18142.1128481040.1@nic-naa.net>
Date: Tue, 04 Oct 2005 22:57:20 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: "GOLDMAN, STUART O \(STUART\)" <sgoldman@lucent.com>, Ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hi Rex,

I was pleased to see NPGS students at the Hancock Co. EOC, we're due to roll
into replace the Mobile Learning Lab's VSAT et al in a few days time, so
Jim and Heather can page back out to Toronto.

FEMA doesn't have a area-global persons-affected db, and has no placns of
record to develop one (the missing count is much higher than the dead, a
it was in the Asian Tsunami. The ARC is only doing shelter-housed padbs,
and has policy and implementation ability issues of the profoundest sort.

You are corret that for large values of use, when the fabric fails and the
services fail, shipping personal status bits (dead|missing|wounded|alive),
is done by low-b/w best-effort mechanisms -- like smtp.

If I run into any NPGS students I'll say "Hello!", my mom was on staff there
for ever.

Eric

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



From ieprep-bounces@ietf.org Fri Oct 07 11:31:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENuBY-0005vX-PA; Fri, 07 Oct 2005 11:31:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENuBW-0005tD-Sv
	for ieprep@megatron.ietf.org; Fri, 07 Oct 2005 11:30:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25588
	for <ieprep@ietf.org>; Fri, 7 Oct 2005 11:30:55 -0400 (EDT)
Received: from [65.99.1.129] (helo=nic-naa.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENuKp-0003r5-8o
	for ieprep@ietf.org; Fri, 07 Oct 2005 11:40:36 -0400
Received: from nic-naa.net (localhost [127.0.0.1])
	by nic-naa.net (8.13.3/8.13.3) with ESMTP id j96KwrSo020324;
	Thu, 6 Oct 2005 16:58:53 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200510062058.j96KwrSo020324@nic-naa.net>
To: ieprep@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20322.1128632333.1@nic-naa.net>
Date: Thu, 06 Oct 2005 16:58:53 -0400
From: Eric Brunner-Williams at a VSAT somewhere (or in Portland Maine)
	<brunner@nic-naa.net>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: brc@zurich.ibm.com
Subject: [Ieprep] IAA follow-up
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Oki all,

Off list someone was kind enough to provide a pointer to the original IAA
contributor to the WG. Thanks.

A Fench blogger (one of Le Monde's contributors) was kind enough to point
out that the International Federation of Red Cross and Red Crescent
Societies  (IFRCRC) just published (5 October) the 13th edition (2005) of
the World Disasters Report.

	People need information as much as water, food, medicine or shelter.
	Information can save lives, livelihoods and resources. It may be the
	only form of disaster preparedness that the most vulnerable can
	afford. The right kind of information leads to a deeper
	understanding of needs and ways to respond. The wrong information can
	lead to inappropriate, even dangerous interventions.

	Information bestows power. Lack of information can make people
	victims of disaster. Do aid organizations use information to
	accumulate power for themselves or to empower others? The report
	calls on agencies to focus less on gathering information for their
	own needs and more on exchanging information with the people they
	seek to support.

The quote from the blub is spot-on, we're observing "accumulation of power"
by governmental and non-governmental organizations (the Eastern Regional
BIA is an interesting exception to this, being an effective aid provider),
and the importance of information to people usually conceptualized as
"post-data-and-voice".


So I'll pursue this item, but it has nothing to do with transport (any
useful spec should be transport-independent), as someone noted, and
nothing to do with ETS or priority mechanisms for particular kinds of
transport, as others have noted, on ieprep.

Eric

P.S. Anyone with discretionary budget ($30) can order this reference and
save themselves the bother of reading it by having it delivered to me.
The URL is http://www.ifrc.org/publicat/wdr2005/order.asp (english).

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



From ieprep-bounces@ietf.org Fri Oct 21 10:14:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESxel-0001Ao-VV; Fri, 21 Oct 2005 10:14:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESxel-0001Aj-E7
	for ieprep@megatron.ietf.org; Fri, 21 Oct 2005 10:14:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23931
	for <ieprep@ietf.org>; Fri, 21 Oct 2005 10:13:52 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESxqu-0002Vr-Ax
	for ieprep@ietf.org; Fri, 21 Oct 2005 10:26:37 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 21 Oct 2005 15:13:53 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 21 Oct 2005 15:13:52 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 Oct 2005 10:13:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 21 Oct 2005 10:13:50 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
Thread-Topic: Diffserv Code Point for Emergency calls
Thread-Index: AcXUE81JfAMUtBgJRhWBEbYRrNip7wCNa7Ig
From: "Reinaldo Penno" <rpenno@juniper.net>
To: <ieprep@ietf.org>
X-OriginalArrivalTime: 21 Oct 2005 14:13:51.0672 (UTC)
	FILETIME=[A9A00380:01C5D649]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
Subject: [Ieprep] Diffserv Code Point for Emergency calls
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hello,

I understand this might have already been discussed (a lot) on the list
but I would like to voice my feedback.

I read
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
and was somewhat puzzled at section 4.1.2. I understand that the IETF
wants to be conservative in standardizing new DSCP, but it seems to an
emergency call DSCP would be accepted by the community (am I wrong?).

I am talking to customers and facing an implementation dilemma on "how
to convey better than EF treatment in a standardized manner since normal
voice calls already use EF?" Should normal voice calls be demoted to use
AFXY DSCP?

Yes, I know, customers can define their own DSCP, map to a specific
queue in their routers, etc, etc. All this is good. However, the
feedback I am getting is that they would like a standardized DSCP for
emergency. The recent tragedies accentuated the need for such
standardization.

I understand there are several levels of emergency calls, etc but maybe
we could start conservative and define _one_ DSCP for emergency calls?

Thanks,

Reinaldo


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



From ieprep-bounces@ietf.org Fri Oct 21 10:58:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESyLn-0004gW-U6; Fri, 21 Oct 2005 10:58:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESyLm-0004g8-8b
	for ieprep@megatron.ietf.org; Fri, 21 Oct 2005 10:58:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27255
	for <ieprep@ietf.org>; Fri, 21 Oct 2005 10:58:18 -0400 (EDT)
Received: from athena.hosts.co.uk ([212.84.175.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESyXv-0004TF-On
	for ieprep@ietf.org; Fri, 21 Oct 2005 11:11:04 -0400
Received: from [69.138.71.61] (helo=[192.168.1.100])
	by athena.hosts.co.uk with esmtpa (Exim 4.52)
	id 1ESyLL-0000pE-WF; Fri, 21 Oct 2005 15:58:07 +0100
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A89EB72D-7A4E-48D1-886D-DB2964B29453@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
Date: Fri, 21 Oct 2005 10:57:58 -0400
To: "Reinaldo Penno" <rpenno@juniper.net>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 2.0 (++)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hello Reinaldo,

> I read
> http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> and was somewhat puzzled at section 4.1.2. I understand that the IETF
> wants to be conservative in standardizing new DSCP, but it seems to an
> emergency call DSCP would be accepted by the community (am I wrong?).

well, from my own take, I would say that the "community" is not  
against an emergency call DSCP per se, but rather awaits specific  
proposals with a cautious mindset.  Recall from that section 4.1.2  
that there is a need to define a behavior in addition to identifying  
a code point.  So if you want a code point of 1 or more bits for  
"emergency", what would be its defined forwarding behavior?

one such proposal, primarily aimed at MLPP, is called Multi-Level  
Expedited Forwarding (MLEF) and can be found at:
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman- 
tsvwg-mlefphb-03.txt

I would also suggest reading a counter proposal that avoids defining  
a new DSCP:
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg- 
mlpp-that-works-02.txt
you can dig around the TSVWG archives over the past 2 months for some  
comments on the draft.

-ken


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



From ieprep-bounces@ietf.org Sat Oct 22 02:02:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETCSM-0006it-N9; Sat, 22 Oct 2005 02:02:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETCSK-0006fE-Mm
	for ieprep@megatron.ietf.org; Sat, 22 Oct 2005 02:02:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20013
	for <ieprep@ietf.org>; Sat, 22 Oct 2005 02:02:02 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ETCeb-0000sW-Qp
	for ieprep@ietf.org; Sat, 22 Oct 2005 02:14:55 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 21 Oct 2005 23:02:03 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j9M61xJh024990;
	Fri, 21 Oct 2005 23:02:00 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 21 Oct 2005 23:01:59 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.98.53]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 21 Oct 2005 23:01:58 -0700
Message-Id: <4.3.2.7.2.20051022005642.0374ca50@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 22 Oct 2005 01:01:57 -0500
To: "Reinaldo Penno" <rpenno@juniper.net>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
In-Reply-To: <A89EB72D-7A4E-48D1-886D-DB2964B29453@g11.org.uk>
References: <9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
	<9BD5D7887235424FA97DFC223CAE3C2801667701@proton.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 22 Oct 2005 06:01:58.0795 (UTC)
	FILETIME=[1CFE1DB0:01C5D6CE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Reinaldo

Adding fuel to a discussion that has churned on many lists over the last 
several years, I'd really want to understand the threat anaylsis observed 
by such a proposal (for a emergency DSCP) to ensure it could not be used 
for a fairly trivial to generate DDOS on the network - even all the way to 
the PSAP, or just used by neighbors wanting the very best throughput for 
their game of Doom.

At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
>Hello Reinaldo,
>
>>I read
>>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
>>and was somewhat puzzled at section 4.1.2. I understand that the IETF
>>wants to be conservative in standardizing new DSCP, but it seems to an
>>emergency call DSCP would be accepted by the community (am I wrong?).
>
>well, from my own take, I would say that the "community" is not
>against an emergency call DSCP per se, but rather awaits specific
>proposals with a cautious mindset.  Recall from that section 4.1.2
>that there is a need to define a behavior in addition to identifying
>a code point.  So if you want a code point of 1 or more bits for
>"emergency", what would be its defined forwarding behavior?
>
>one such proposal, primarily aimed at MLPP, is called Multi-Level
>Expedited Forwarding (MLEF) and can be found at:
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman- 
>tsvwg-mlefphb-03.txt
>
>I would also suggest reading a counter proposal that avoids defining
>a new DSCP:
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg- 
>mlpp-that-works-02.txt
>you can dig around the TSVWG archives over the past 2 months for some
>comments on the draft.
>
>-ken
>
>
>_______________________________________________
>Ieprep mailing list
>Ieprep@ietf.org
>https://www1.ietf.org/mailman/listinfo/ieprep


cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sat Oct 22 08:46:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETIl9-00062M-Mv; Sat, 22 Oct 2005 08:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETIl8-00062E-5H
	for ieprep@megatron.ietf.org; Sat, 22 Oct 2005 08:46:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09942
	for <ieprep@ietf.org>; Sat, 22 Oct 2005 08:45:51 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETIxS-0006MG-TH
	for ieprep@ietf.org; Sat, 22 Oct 2005 08:58:48 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sat, 22 Oct 2005 13:45:51 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sat, 22 Oct 2005 13:45:47 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Sat, 22 Oct 2005 08:45:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sat, 22 Oct 2005 08:45:43 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXWzimDCgfswVkeSJaYKqAOEsGHCAAN0izA
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "James M. Polk" <jmpolk@cisco.com>
X-OriginalArrivalTime: 22 Oct 2005 12:45:44.0167 (UTC)
	FILETIME=[84708770:01C5D706]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Your point is well taken James.

I guess the risk is no different from what we face nowadays with doom
packets marked with EF DSCP. The solution as well is no different from
what we have today to deal with those packets. Usually independently of
the DSCP an endpoint might put in a packet, the edge router perform
classification and if necessary remarks the packet with whatever DSCP it
should have.=20

Therefore, if we just continue with just EF for normal and emergency
voice calls, the risk is the same, the drawback that I see is that we
cannot prioritize emergency over normal calls.

So, in general an edge device that can perform SIP parsing and mark
emergency calls with the emergency DSCP and others with EF DSCP.
Alternatively, in a decomposed gateway scenario the SIP Proxy can let
the router know that a certain call is an emergency and that it should
be marked differently.

Regards,

Reinaldo


> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Friday, October 21, 2005 11:02 PM
> To: Reinaldo Penno
> Cc: ken carlberg; ieprep@ietf.org
> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>=20
> Reinaldo
>=20
> Adding fuel to a discussion that has churned on many lists over the
last
> several years, I'd really want to understand the threat anaylsis
observed
> by such a proposal (for a emergency DSCP) to ensure it could not be
used
> for a fairly trivial to generate DDOS on the network - even all the
way to
> the PSAP, or just used by neighbors wanting the very best throughput
for
> their game of Doom.
>=20
> At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> >Hello Reinaldo,
> >
> >>I read
>
>>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> >>and was somewhat puzzled at section 4.1.2. I understand that the
IETF
> >>wants to be conservative in standardizing new DSCP, but it seems to
an
> >>emergency call DSCP would be accepted by the community (am I
wrong?).
> >
> >well, from my own take, I would say that the "community" is not
> >against an emergency call DSCP per se, but rather awaits specific
> >proposals with a cautious mindset.  Recall from that section 4.1.2
> >that there is a need to define a behavior in addition to identifying
> >a code point.  So if you want a code point of 1 or more bits for
> >"emergency", what would be its defined forwarding behavior?
> >
> >one such proposal, primarily aimed at MLPP, is called Multi-Level
> >Expedited Forwarding (MLEF) and can be found at:
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> >tsvwg-mlefphb-03.txt
> >
> >I would also suggest reading a counter proposal that avoids defining
> >a new DSCP:
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> >mlpp-that-works-02.txt
> >you can dig around the TSVWG archives over the past 2 months for some
> >comments on the draft.
> >
> >-ken
> >
> >
> >_______________________________________________
> >Ieprep mailing list
> >Ieprep@ietf.org
> >https://www1.ietf.org/mailman/listinfo/ieprep
>=20
>=20
> cheers,
> James
>=20
>                                  *******************
>                  Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sat Oct 22 09:11:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETJ9y-00074y-OI; Sat, 22 Oct 2005 09:11:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETJ9w-000702-Lu
	for ieprep@megatron.ietf.org; Sat, 22 Oct 2005 09:11:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10793
	for <ieprep@ietf.org>; Sat, 22 Oct 2005 09:11:29 -0400 (EDT)
Received: from seahorse.shentel.net ([204.111.11.44])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETJMH-000772-ML
	for ieprep@ietf.org; Sat, 22 Oct 2005 09:24:26 -0400
Received: from Steve ([204.111.103.125])
	by seahorse.shentel.net (8.12.11/8.12.11) with SMTP id j9MDBDMQ005513; 
	Sat, 22 Oct 2005 09:11:14 -0400
From: "Steve Silverman" <steves@shentel.net>
To: "Reinaldo Penno" <rpenno@juniper.net>, "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sat, 22 Oct 2005 09:11:42 -0400
Message-ID: <CIEELMKPOOAMCIAKANLBOEFOFGAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Content-Transfer-Encoding: 7bit
Cc: ken carlberg <carlberg@g11.org.uk>, ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

If calls to a locally pre-specified emergency number (e.g., 911) are
given high priority, it is no great exposure.
One would think such calls would have locally routable destinations
and couldn't travel very far or be used for DDOS attacks.  (Except
against the actual emergency systems. How we protect them is another
problem. )

In the absence of limited addressing or strong user authentication (as
the DOD uses) giving Joe Hacker the ability to get extra high priority
seems like a bad idea to me.

It would be helpful if someone (probably ITU rather than IETF) could
standardize on a limited number of local emergency calling numbers.

Steve Silverman


> -----Original Message-----
> From: ieprep-bounces@ietf.org
> [mailto:ieprep-bounces@ietf.org]On Behalf
> Of Reinaldo Penno
> Sent: Saturday, October 22, 2005 8:46 AM
> To: James M. Polk
> Cc: ieprep@ietf.org; ken carlberg
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>
>
> Your point is well taken James.
>
> I guess the risk is no different from what we face nowadays
> with doom
> packets marked with EF DSCP. The solution as well is no
> different from
> what we have today to deal with those packets. Usually
> independently of
> the DSCP an endpoint might put in a packet, the edge router perform
> classification and if necessary remarks the packet with
> whatever DSCP it
> should have.
>
> Therefore, if we just continue with just EF for normal and emergency
> voice calls, the risk is the same, the drawback that I see
> is that we
> cannot prioritize emergency over normal calls.
>
> So, in general an edge device that can perform SIP parsing and mark
> emergency calls with the emergency DSCP and others with EF DSCP.
> Alternatively, in a decomposed gateway scenario the SIP
> Proxy can let
> the router know that a certain call is an emergency and
> that it should
> be marked differently.
>
> Regards,
>
> Reinaldo
>
>
> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk@cisco.com]
> > Sent: Friday, October 21, 2005 11:02 PM
> > To: Reinaldo Penno
> > Cc: ken carlberg; ieprep@ietf.org
> > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> >
> > Reinaldo
> >
> > Adding fuel to a discussion that has churned on many
> lists over the
> last
> > several years, I'd really want to understand the threat anaylsis
> observed
> > by such a proposal (for a emergency DSCP) to ensure it
> could not be
> used
> > for a fairly trivial to generate DDOS on the network -
> even all the
> way to
> > the PSAP, or just used by neighbors wanting the very best
> throughput
> for
> > their game of Doom.
> >
> > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > >Hello Reinaldo,
> > >
> > >>I read
> >
> >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-fram
> ework-10.txt
> > >>and was somewhat puzzled at section 4.1.2. I understand that the
> IETF
> > >>wants to be conservative in standardizing new DSCP, but
> it seems to
> an
> > >>emergency call DSCP would be accepted by the community (am I
> wrong?).
> > >
> > >well, from my own take, I would say that the "community" is not
> > >against an emergency call DSCP per se, but rather awaits specific
> > >proposals with a cautious mindset.  Recall from that
> section 4.1.2
> > >that there is a need to define a behavior in addition to
> identifying
> > >a code point.  So if you want a code point of 1 or more bits for
> > >"emergency", what would be its defined forwarding behavior?
> > >
> > >one such proposal, primarily aimed at MLPP, is called Multi-Level
> > >Expedited Forwarding (MLEF) and can be found at:
> >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > >tsvwg-mlefphb-03.txt
> > >
> > >I would also suggest reading a counter proposal that
> avoids defining
> > >a new DSCP:
> >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > >mlpp-that-works-02.txt
> > >you can dig around the TSVWG archives over the past 2
> months for some
> > >comments on the draft.
> > >
> > >-ken
> > >
> > >
> > >_______________________________________________
> > >Ieprep mailing list
> > >Ieprep@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/ieprep
> >
> >
> > cheers,
> > James
> >
> >                                  *******************
> >                  Truth is not to be argued... it is to be
> presented.
>
> _______________________________________________
> 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 ieprep-bounces@ietf.org Sat Oct 22 23:09:43 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETWEx-0004R7-D5; Sat, 22 Oct 2005 23:09:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETWEu-0004Qn-S9
	for ieprep@megatron.ietf.org; Sat, 22 Oct 2005 23:09:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11095
	for <ieprep@ietf.org>; Sat, 22 Oct 2005 23:09:28 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ETWRL-0005ii-Qo
	for ieprep@ietf.org; Sat, 22 Oct 2005 23:22:34 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-3.cisco.com with ESMTP; 22 Oct 2005 20:09:29 -0700
X-IronPort-AV: i="3.97,241,1125903600"; 
	d="scan'208"; a="355548243:sNHT27960484"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9N39E9C020667;
	Sat, 22 Oct 2005 20:09:26 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sat, 22 Oct 2005 20:09:22 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.80.233]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sat, 22 Oct 2005 20:09:20 -0700
Message-Id: <4.3.2.7.2.20051022215749.03ae19c8@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 22 Oct 2005 22:09:20 -0500
To: "Steve Silverman" <steves@shentel.net>,
	"Reinaldo Penno" <rpenno@juniper.net>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
In-Reply-To: <CIEELMKPOOAMCIAKANLBOEFOFGAA.steves@shentel.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 23 Oct 2005 03:09:21.0232 (UTC)
	FILETIME=[29D12D00:01C5D77F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: ken carlberg <carlberg@g11.org.uk>, ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

At 09:11 AM 10/22/2005 -0400, Steve Silverman wrote:
>If calls to a locally pre-specified emergency number (e.g., 911) are
>given high priority, it is no great exposure.

"a locally pre-specified number".. hmmm

several comments:

- is a URI a number in this context?
         as SIP is defining a URI, not a number, for emergency calls

- How many routers that will have a PHB on this DSCP are between you and 
the local PSAP?
         could be 5, could be 10 - that impact is greater than the local 
Class 5 switch from old telco designs

- If you DDOS the local broadband segment, you eliminate the possibility of 
anyone on that segment from making a emergency call.
         single HFC segments can be as far away as 100 miles, is that local 
anymore?

>One would think such calls would have locally routable destinations
>and couldn't travel very far or be used for DDOS attacks.  (Except
>against the actual emergency systems. How we protect them is another
>problem. )

How do you protect a layer 3 packet that has a layer 3 marking and no 
authorization indication in that packet?


>In the absence of limited addressing or strong user authentication (as
>the DOD uses) giving Joe Hacker the ability to get extra high priority
>seems like a bad idea to me.
>
>It would be helpful if someone (probably ITU rather than IETF) could
>standardize on a limited number of local emergency calling numbers.

see
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-requirements-00.txt


>Steve Silverman
>
>
> > -----Original Message-----
> > From: ieprep-bounces@ietf.org
> > [mailto:ieprep-bounces@ietf.org]On Behalf
> > Of Reinaldo Penno
> > Sent: Saturday, October 22, 2005 8:46 AM
> > To: James M. Polk
> > Cc: ieprep@ietf.org; ken carlberg
> > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> >
> >
> > Your point is well taken James.
> >
> > I guess the risk is no different from what we face nowadays
> > with doom
> > packets marked with EF DSCP. The solution as well is no
> > different from
> > what we have today to deal with those packets. Usually
> > independently of
> > the DSCP an endpoint might put in a packet, the edge router perform
> > classification and if necessary remarks the packet with
> > whatever DSCP it
> > should have.
> >
> > Therefore, if we just continue with just EF for normal and emergency
> > voice calls, the risk is the same, the drawback that I see
> > is that we
> > cannot prioritize emergency over normal calls.
> >
> > So, in general an edge device that can perform SIP parsing and mark
> > emergency calls with the emergency DSCP and others with EF DSCP.
> > Alternatively, in a decomposed gateway scenario the SIP
> > Proxy can let
> > the router know that a certain call is an emergency and
> > that it should
> > be marked differently.
> >
> > Regards,
> >
> > Reinaldo
> >
> >
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Friday, October 21, 2005 11:02 PM
> > > To: Reinaldo Penno
> > > Cc: ken carlberg; ieprep@ietf.org
> > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > > Reinaldo
> > >
> > > Adding fuel to a discussion that has churned on many
> > lists over the
> > last
> > > several years, I'd really want to understand the threat anaylsis
> > observed
> > > by such a proposal (for a emergency DSCP) to ensure it
> > could not be
> > used
> > > for a fairly trivial to generate DDOS on the network -
> > even all the
> > way to
> > > the PSAP, or just used by neighbors wanting the very best
> > throughput
> > for
> > > their game of Doom.
> > >
> > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > >Hello Reinaldo,
> > > >
> > > >>I read
> > >
> > >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-fram
> > ework-10.txt
> > > >>and was somewhat puzzled at section 4.1.2. I understand that the
> > IETF
> > > >>wants to be conservative in standardizing new DSCP, but
> > it seems to
> > an
> > > >>emergency call DSCP would be accepted by the community (am I
> > wrong?).
> > > >
> > > >well, from my own take, I would say that the "community" is not
> > > >against an emergency call DSCP per se, but rather awaits specific
> > > >proposals with a cautious mindset.  Recall from that
> > section 4.1.2
> > > >that there is a need to define a behavior in addition to
> > identifying
> > > >a code point.  So if you want a code point of 1 or more bits for
> > > >"emergency", what would be its defined forwarding behavior?
> > > >
> > > >one such proposal, primarily aimed at MLPP, is called Multi-Level
> > > >Expedited Forwarding (MLEF) and can be found at:
> > >
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > >tsvwg-mlefphb-03.txt
> > > >
> > > >I would also suggest reading a counter proposal that
> > avoids defining
> > > >a new DSCP:
> > >
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > >mlpp-that-works-02.txt
> > > >you can dig around the TSVWG archives over the past 2
> > months for some
> > > >comments on the draft.
> > > >
> > > >-ken
> > > >
> > > >
> > > >_______________________________________________
> > > >Ieprep mailing list
> > > >Ieprep@ietf.org
> > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > >
> > >
> > > cheers,
> > > James
> > >
> > >                                  *******************
> > >                  Truth is not to be argued... it is to be
> > presented.
> >
> > _______________________________________________
> > Ieprep mailing list
> > Ieprep@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ieprep
> >


cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sat Oct 22 23:23:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETWS6-0003LQ-8l; Sat, 22 Oct 2005 23:23:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETWS4-0003I5-CG
	for ieprep@megatron.ietf.org; Sat, 22 Oct 2005 23:23:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11424
	for <ieprep@ietf.org>; Sat, 22 Oct 2005 23:23:04 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ETWeX-00063C-On
	for ieprep@ietf.org; Sat, 22 Oct 2005 23:36:10 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-3.cisco.com with ESMTP; 22 Oct 2005 20:23:07 -0700
X-IronPort-AV: i="3.97,241,1125903600"; 
	d="scan'208"; a="355550375:sNHT28280234"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9N3N098022604;
	Sat, 22 Oct 2005 20:23:05 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sat, 22 Oct 2005 20:23:00 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.80.233]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sat, 22 Oct 2005 20:22:59 -0700
Message-Id: <4.3.2.7.2.20051022220937.029380f8@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 22 Oct 2005 22:22:58 -0500
To: "Reinaldo Penno" <rpenno@juniper.net>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 23 Oct 2005 03:22:59.0982 (UTC)
	FILETIME=[11D482E0:01C5D781]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
>Your point is well taken James.
>
>Therefore, if we just continue with just EF for normal and emergency
>voice calls, the risk is the same, the drawback that I see is that we
>cannot prioritize emergency over normal calls.

so here's the problem as has been presented to me by both regulators and 
lawyers:

In larger emergencies, many people will likely be calling for emergency 
help, and some of them are not going to be calling (the equivalent of) 911, 
they will be calling their doctors directly - yet to "the system", these 
will appear as normal packets, or normal voice (EF marked) packets. In your 
pondering, these packets will be subject to some form of lesser treatment 
than perhaps the 10th or 100th call to 911, informing the PSAP of the same 
event (perhaps a building burning).

Here's the catch: who determined the 10th or 100th call to the PSAP is more 
important than the patient's call with their doctor - getting one-on-one 
advice/help.

I think the first lawsuit will stop that preferential treatment. I've had 
this hinted to me by many


>So, in general an edge device that can perform SIP parsing and mark
>emergency calls with the emergency DSCP and others with EF DSCP.
>Alternatively, in a decomposed gateway scenario the SIP Proxy can let
>the router know that a certain call is an emergency and that it should
>be marked differently.

or there could be a path coupled mechanism for such calls, but that has its 
challenges too


>Regards,
>
>Reinaldo
>
>
> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk@cisco.com]
> > Sent: Friday, October 21, 2005 11:02 PM
> > To: Reinaldo Penno
> > Cc: ken carlberg; ieprep@ietf.org
> > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> >
> > Reinaldo
> >
> > Adding fuel to a discussion that has churned on many lists over the
>last
> > several years, I'd really want to understand the threat anaylsis
>observed
> > by such a proposal (for a emergency DSCP) to ensure it could not be
>used
> > for a fairly trivial to generate DDOS on the network - even all the
>way to
> > the PSAP, or just used by neighbors wanting the very best throughput
>for
> > their game of Doom.
> >
> > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > >Hello Reinaldo,
> > >
> > >>I read
> >
> >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > >>and was somewhat puzzled at section 4.1.2. I understand that the
>IETF
> > >>wants to be conservative in standardizing new DSCP, but it seems to
>an
> > >>emergency call DSCP would be accepted by the community (am I
>wrong?).
> > >
> > >well, from my own take, I would say that the "community" is not
> > >against an emergency call DSCP per se, but rather awaits specific
> > >proposals with a cautious mindset.  Recall from that section 4.1.2
> > >that there is a need to define a behavior in addition to identifying
> > >a code point.  So if you want a code point of 1 or more bits for
> > >"emergency", what would be its defined forwarding behavior?
> > >
> > >one such proposal, primarily aimed at MLPP, is called Multi-Level
> > >Expedited Forwarding (MLEF) and can be found at:
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > >tsvwg-mlefphb-03.txt
> > >
> > >I would also suggest reading a counter proposal that avoids defining
> > >a new DSCP:
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > >mlpp-that-works-02.txt
> > >you can dig around the TSVWG archives over the past 2 months for some
> > >comments on the draft.
> > >
> > >-ken
> > >
> > >
> > >_______________________________________________
> > >Ieprep mailing list
> > >Ieprep@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/ieprep
> >
> >
> > cheers,
> > James
> >
> >                                  *******************
> >                  Truth is not to be argued... it is to be presented.


cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sun Oct 23 02:30:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETZMs-0002ru-1X; Sun, 23 Oct 2005 02:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETZMq-0002po-FQ
	for ieprep@megatron.ietf.org; Sun, 23 Oct 2005 02:30:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17528
	for <ieprep@ietf.org>; Sun, 23 Oct 2005 02:29:51 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETZZJ-0002Qv-Cx
	for ieprep@ietf.org; Sun, 23 Oct 2005 02:42:59 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 23 Oct 2005 07:29:38 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 23 Oct 2005 07:29:38 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Sun, 23 Oct 2005 02:29:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sun, 23 Oct 2005 02:29:36 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667706@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXXgR/5W72ZlfIsTsG+9OlXr3I43wAFABkQ
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "James M. Polk" <jmpolk@cisco.com>
X-OriginalArrivalTime: 23 Oct 2005 06:29:36.0811 (UTC)
	FILETIME=[23A907B0:01C5D79B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Content-Transfer-Encoding: quoted-printable
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

That is also possible and it might happen all the time.

I think the threats you mention are quite valid but they will be no
different if we have an emergency DSCP. The whole problem around
contention of resources will continue to happen.

My point is the same as before. How this hypothetical scenario is any
different from what could happen today?=20

For example, today if something happens in an enterprise, will the
emergency calls to 911 have better treatment than the doctor's call? You
can also imagine a reversed scenario where I could argue that if the
call made by the person in the next cubicle to his doctor blocks my call
to 911 I will sue the company/telco.=20

Any hospital in the US has the following recording "if this is an
emergency, hang up and dial 911". If you really have an emergency, you
should be calling 911, and not your doctor. If you call your doctor, you
are implicitly telling the "system" that this is not an emergency.

Somebody in a Telco told me that 911 calls are signaled different (which
imply a priority over normal calls). Do you know if this a fact?

Regards,

Reinaldo



> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Saturday, October 22, 2005 8:23 PM
> To: Reinaldo Penno
> Cc: ken carlberg; ieprep@ietf.org
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>=20
> At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> >Your point is well taken James.
> >
> >Therefore, if we just continue with just EF for normal and emergency
> >voice calls, the risk is the same, the drawback that I see is that we
> >cannot prioritize emergency over normal calls.
>=20
> so here's the problem as has been presented to me by both regulators
and
> lawyers:
>=20
> In larger emergencies, many people will likely be calling for
emergency
> help, and some of them are not going to be calling (the equivalent of)
> 911,
> they will be calling their doctors directly - yet to "the system",
these
> will appear as normal packets, or normal voice (EF marked) packets. In
> your
> pondering, these packets will be subject to some form of lesser
treatment
> than perhaps the 10th or 100th call to 911, informing the PSAP of the
same
> event (perhaps a building burning).
>=20
> Here's the catch: who determined the 10th or 100th call to the PSAP is
> more
> important than the patient's call with their doctor - getting
one-on-one
> advice/help.
>=20
> I think the first lawsuit will stop that preferential treatment. I've
had
> this hinted to me by many
>=20
>=20
> >So, in general an edge device that can perform SIP parsing and mark
> >emergency calls with the emergency DSCP and others with EF DSCP.
> >Alternatively, in a decomposed gateway scenario the SIP Proxy can let
> >the router know that a certain call is an emergency and that it
should
> >be marked differently.
>=20
> or there could be a path coupled mechanism for such calls, but that
has
> its
> challenges too
>=20
>=20
> >Regards,
> >
> >Reinaldo
> >
> >
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Friday, October 21, 2005 11:02 PM
> > > To: Reinaldo Penno
> > > Cc: ken carlberg; ieprep@ietf.org
> > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > > Reinaldo
> > >
> > > Adding fuel to a discussion that has churned on many lists over
the
> >last
> > > several years, I'd really want to understand the threat anaylsis
> >observed
> > > by such a proposal (for a emergency DSCP) to ensure it could not
be
> >used
> > > for a fairly trivial to generate DDOS on the network - even all
the
> >way to
> > > the PSAP, or just used by neighbors wanting the very best
throughput
> >for
> > > their game of Doom.
> > >
> > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > >Hello Reinaldo,
> > > >
> > > >>I read
> > >
> >
>>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > > >>and was somewhat puzzled at section 4.1.2. I understand that the
> >IETF
> > > >>wants to be conservative in standardizing new DSCP, but it seems
to
> >an
> > > >>emergency call DSCP would be accepted by the community (am I
> >wrong?).
> > > >
> > > >well, from my own take, I would say that the "community" is not
> > > >against an emergency call DSCP per se, but rather awaits specific
> > > >proposals with a cautious mindset.  Recall from that section
4.1.2
> > > >that there is a need to define a behavior in addition to
identifying
> > > >a code point.  So if you want a code point of 1 or more bits for
> > > >"emergency", what would be its defined forwarding behavior?
> > > >
> > > >one such proposal, primarily aimed at MLPP, is called Multi-Level
> > > >Expedited Forwarding (MLEF) and can be found at:
> > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > >tsvwg-mlefphb-03.txt
> > > >
> > > >I would also suggest reading a counter proposal that avoids
defining
> > > >a new DSCP:
> > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > >mlpp-that-works-02.txt
> > > >you can dig around the TSVWG archives over the past 2 months for
some
> > > >comments on the draft.
> > > >
> > > >-ken
> > > >
> > > >
> > > >_______________________________________________
> > > >Ieprep mailing list
> > > >Ieprep@ietf.org
> > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > >
> > >
> > > cheers,
> > > James
> > >
> > >                                  *******************
> > >                  Truth is not to be argued... it is to be
presented.
>=20
>=20
> cheers,
> James
>=20
>                                  *******************
>                  Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sun Oct 23 02:40:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETZWi-000827-Bd; Sun, 23 Oct 2005 02:40:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETZWg-00080v-SY
	for ieprep@megatron.ietf.org; Sun, 23 Oct 2005 02:40:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17796
	for <ieprep@ietf.org>; Sun, 23 Oct 2005 02:40:01 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETZjB-0002fQ-Pu
	for ieprep@ietf.org; Sun, 23 Oct 2005 02:53:10 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 23 Oct 2005 07:40:05 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 23 Oct 2005 07:40:04 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Sun, 23 Oct 2005 02:40:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sun, 23 Oct 2005 02:40:03 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667707@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXXfzj1LZbZIC78ShWqzrNrsrh2QQAG+xCA
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "James M. Polk" <jmpolk@cisco.com>, "Steve Silverman" <steves@shentel.net>
X-OriginalArrivalTime: 23 Oct 2005 06:40:03.0760 (UTC)
	FILETIME=[9959DB00:01C5D79C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Content-Transfer-Encoding: quoted-printable
Cc: ken carlberg <carlberg@g11.org.uk>, ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hello James,

I am not going to elaborate again but as I mentioned in the previous
email the DDOS HFC threat already exists today without emergency DSCP.

I can DDOS the local broadband segment with EF packets and prevent
emergency calls.

I would like to understand if there are any new threats that an
emergency DSCP bring to the game that do not exist today with EF DSCP.
And if there are new threats, do they outweigh the benefit of an
emergency DSCP?

On the same topic. Do you believe we should do something (not
necessarily DSCP) to prioritize emergency calls or not?=20

Thanks,

Reinaldo

> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Saturday, October 22, 2005 8:09 PM
> To: Steve Silverman; Reinaldo Penno
> Cc: ieprep@ietf.org; ken carlberg
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>=20
> At 09:11 AM 10/22/2005 -0400, Steve Silverman wrote:
> >If calls to a locally pre-specified emergency number (e.g., 911) are
> >given high priority, it is no great exposure.
>=20
> "a locally pre-specified number".. hmmm
>=20
> several comments:
>=20
> - is a URI a number in this context?
>          as SIP is defining a URI, not a number, for emergency calls
>=20
> - How many routers that will have a PHB on this DSCP are between you
and
> the local PSAP?
>          could be 5, could be 10 - that impact is greater than the
local
> Class 5 switch from old telco designs
>=20
> - If you DDOS the local broadband segment, you eliminate the
possibility
> of
> anyone on that segment from making a emergency call.
>          single HFC segments can be as far away as 100 miles, is that
> local
> anymore?
[[Reinaldo]]=20









>=20
> >One would think such calls would have locally routable destinations
> >and couldn't travel very far or be used for DDOS attacks.  (Except
> >against the actual emergency systems. How we protect them is another
> >problem. )
>=20
> How do you protect a layer 3 packet that has a layer 3 marking and no
> authorization indication in that packet?
>=20
>=20
> >In the absence of limited addressing or strong user authentication
(as
> >the DOD uses) giving Joe Hacker the ability to get extra high
priority
> >seems like a bad idea to me.
> >
> >It would be helpful if someone (probably ITU rather than IETF) could
> >standardize on a limited number of local emergency calling numbers.
>=20
> see
>
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-requirements-00.txt
>=20
>=20
> >Steve Silverman
> >
> >
> > > -----Original Message-----
> > > From: ieprep-bounces@ietf.org
> > > [mailto:ieprep-bounces@ietf.org]On Behalf
> > > Of Reinaldo Penno
> > > Sent: Saturday, October 22, 2005 8:46 AM
> > > To: James M. Polk
> > > Cc: ieprep@ietf.org; ken carlberg
> > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > >
> > > Your point is well taken James.
> > >
> > > I guess the risk is no different from what we face nowadays
> > > with doom
> > > packets marked with EF DSCP. The solution as well is no
> > > different from
> > > what we have today to deal with those packets. Usually
> > > independently of
> > > the DSCP an endpoint might put in a packet, the edge router
perform
> > > classification and if necessary remarks the packet with
> > > whatever DSCP it
> > > should have.
> > >
> > > Therefore, if we just continue with just EF for normal and
emergency
> > > voice calls, the risk is the same, the drawback that I see
> > > is that we
> > > cannot prioritize emergency over normal calls.
> > >
> > > So, in general an edge device that can perform SIP parsing and
mark
> > > emergency calls with the emergency DSCP and others with EF DSCP.
> > > Alternatively, in a decomposed gateway scenario the SIP
> > > Proxy can let
> > > the router know that a certain call is an emergency and
> > > that it should
> > > be marked differently.
> > >
> > > Regards,
> > >
> > > Reinaldo
> > >
> > >
> > > > -----Original Message-----
> > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > To: Reinaldo Penno
> > > > Cc: ken carlberg; ieprep@ietf.org
> > > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > > >
> > > > Reinaldo
> > > >
> > > > Adding fuel to a discussion that has churned on many
> > > lists over the
> > > last
> > > > several years, I'd really want to understand the threat anaylsis
> > > observed
> > > > by such a proposal (for a emergency DSCP) to ensure it
> > > could not be
> > > used
> > > > for a fairly trivial to generate DDOS on the network -
> > > even all the
> > > way to
> > > > the PSAP, or just used by neighbors wanting the very best
> > > throughput
> > > for
> > > > their game of Doom.
> > > >
> > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > >Hello Reinaldo,
> > > > >
> > > > >>I read
> > > >
> > > >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-fram
> > > ework-10.txt
> > > > >>and was somewhat puzzled at section 4.1.2. I understand that
the
> > > IETF
> > > > >>wants to be conservative in standardizing new DSCP, but
> > > it seems to
> > > an
> > > > >>emergency call DSCP would be accepted by the community (am I
> > > wrong?).
> > > > >
> > > > >well, from my own take, I would say that the "community" is not
> > > > >against an emergency call DSCP per se, but rather awaits
specific
> > > > >proposals with a cautious mindset.  Recall from that
> > > section 4.1.2
> > > > >that there is a need to define a behavior in addition to
> > > identifying
> > > > >a code point.  So if you want a code point of 1 or more bits
for
> > > > >"emergency", what would be its defined forwarding behavior?
> > > > >
> > > > >one such proposal, primarily aimed at MLPP, is called
Multi-Level
> > > > >Expedited Forwarding (MLEF) and can be found at:
> > > >
> > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > >tsvwg-mlefphb-03.txt
> > > > >
> > > > >I would also suggest reading a counter proposal that
> > > avoids defining
> > > > >a new DSCP:
> > > >
> > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > >mlpp-that-works-02.txt
> > > > >you can dig around the TSVWG archives over the past 2
> > > months for some
> > > > >comments on the draft.
> > > > >
> > > > >-ken
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >Ieprep mailing list
> > > > >Ieprep@ietf.org
> > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > >
> > > >
> > > > cheers,
> > > > James
> > > >
> > > >                                  *******************
> > > >                  Truth is not to be argued... it is to be
> > > presented.
> > >
> > > _______________________________________________
> > > Ieprep mailing list
> > > Ieprep@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/ieprep
> > >
>=20
>=20
> cheers,
> James
>=20
>                                  *******************
>                  Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sun Oct 23 15:50:43 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETlrf-0000FJ-Dv; Sun, 23 Oct 2005 15:50:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETlre-0000FB-4G
	for ieprep@megatron.ietf.org; Sun, 23 Oct 2005 15:50:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22305
	for <ieprep@ietf.org>; Sun, 23 Oct 2005 15:50:28 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETm4F-0004rk-QW
	for ieprep@ietf.org; Sun, 23 Oct 2005 16:03:44 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by sj-iport-5.cisco.com with ESMTP; 23 Oct 2005 12:50:33 -0700
X-IronPort-AV: i="3.97,242,1125903600"; 
	d="scan'208"; a="222993301:sNHT28337268"
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j9NJoP8m001833;
	Sun, 23 Oct 2005 12:50:28 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sun, 23 Oct 2005 12:50:29 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.97.168]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sun, 23 Oct 2005 12:50:28 -0700
Message-Id: <4.3.2.7.2.20051023143437.029f6948@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 23 Oct 2005 14:50:27 -0500
To: "Reinaldo Penno" <rpenno@juniper.net>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667706@proton.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 23 Oct 2005 19:50:28.0697 (UTC)
	FILETIME=[04D0F490:01C5D80B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Reinaldo

Comments in-line

At 02:29 AM 10/23/2005 -0400, Reinaldo Penno wrote:
>That is also possible and it might happen all the time.
>
>I think the threats you mention are quite valid but they will be no
>different if we have an emergency DSCP. The whole problem around
>contention of resources will continue to happen.
>
>My point is the same as before. How this hypothetical scenario is any
>different from what could happen today?

Because, as I see it - and please correct me if I am seeing this 
incorrectly - that doctor's call in the enterprise will not be starved off 
by any other call.

Yet, the way I have understood most, and I think the scenario you have 
brought up, the emergency calls will starve off, or at least adversely 
affect existing calls that can be the equivalent of EF marked in treatment.

Plus there is the issue that most employees operate under a subtly 
different set of laws and rules than the general public, usually starting 
with when an employee candidate signs a contract of employment reducing 
that person's rights in some ways.


>For example, today if something happens in an enterprise, will the
>emergency calls to 911 have better treatment than the doctor's call? You
>can also imagine a reversed scenario where I could argue that if the
>call made by the person in the next cubicle to his doctor blocks my call
>to 911 I will sue the company/telco.
>
>Any hospital in the US has the following recording "if this is an
>emergency, hang up and dial 911". If you really have an emergency, you
>should be calling 911, and not your doctor.

While in general, I would agree with you, there are some cases in which a 
doctor is who is to be called when you have an issue with something under 
their care.  I have experienced this first hand to know it is true in the US.

>If you call your doctor, you
>are implicitly telling the "system" that this is not an emergency.

That's the legacy system you are telling.  Whereas, with IP, we have many 
more capabilities (or should) to be able to differentiate one call from 
another. I believe that should one of the IETF's (and other SDO's) goals 
for emergency calling.

Please review ECRIT WG discussions as there are many references to this 
capability being on the to-do list of many areas dealing with this scenario.


>Somebody in a Telco told me that 911 calls are signaled different (which
>imply a priority over normal calls). Do you know if this a fact?

Yes, there are special facilities that 911 calls traverse, after the 
initial Class 5 switch towards the Selective Router, and on to the PSAP.


>Regards,
>
>Reinaldo
>
>
>
> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk@cisco.com]
> > Sent: Saturday, October 22, 2005 8:23 PM
> > To: Reinaldo Penno
> > Cc: ken carlberg; ieprep@ietf.org
> > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> >
> > At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> > >Your point is well taken James.
> > >
> > >Therefore, if we just continue with just EF for normal and emergency
> > >voice calls, the risk is the same, the drawback that I see is that we
> > >cannot prioritize emergency over normal calls.
> >
> > so here's the problem as has been presented to me by both regulators
>and
> > lawyers:
> >
> > In larger emergencies, many people will likely be calling for
>emergency
> > help, and some of them are not going to be calling (the equivalent of)
> > 911,
> > they will be calling their doctors directly - yet to "the system",
>these
> > will appear as normal packets, or normal voice (EF marked) packets. In
> > your
> > pondering, these packets will be subject to some form of lesser
>treatment
> > than perhaps the 10th or 100th call to 911, informing the PSAP of the
>same
> > event (perhaps a building burning).
> >
> > Here's the catch: who determined the 10th or 100th call to the PSAP is
> > more
> > important than the patient's call with their doctor - getting
>one-on-one
> > advice/help.
> >
> > I think the first lawsuit will stop that preferential treatment. I've
>had
> > this hinted to me by many
> >
> >
> > >So, in general an edge device that can perform SIP parsing and mark
> > >emergency calls with the emergency DSCP and others with EF DSCP.
> > >Alternatively, in a decomposed gateway scenario the SIP Proxy can let
> > >the router know that a certain call is an emergency and that it
>should
> > >be marked differently.
> >
> > or there could be a path coupled mechanism for such calls, but that
>has
> > its
> > challenges too
> >
> >
> > >Regards,
> > >
> > >Reinaldo
> > >
> > >
> > > > -----Original Message-----
> > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > To: Reinaldo Penno
> > > > Cc: ken carlberg; ieprep@ietf.org
> > > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > > >
> > > > Reinaldo
> > > >
> > > > Adding fuel to a discussion that has churned on many lists over
>the
> > >last
> > > > several years, I'd really want to understand the threat anaylsis
> > >observed
> > > > by such a proposal (for a emergency DSCP) to ensure it could not
>be
> > >used
> > > > for a fairly trivial to generate DDOS on the network - even all
>the
> > >way to
> > > > the PSAP, or just used by neighbors wanting the very best
>throughput
> > >for
> > > > their game of Doom.
> > > >
> > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > >Hello Reinaldo,
> > > > >
> > > > >>I read
> > > >
> > >
> >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > > > >>and was somewhat puzzled at section 4.1.2. I understand that the
> > >IETF
> > > > >>wants to be conservative in standardizing new DSCP, but it seems
>to
> > >an
> > > > >>emergency call DSCP would be accepted by the community (am I
> > >wrong?).
> > > > >
> > > > >well, from my own take, I would say that the "community" is not
> > > > >against an emergency call DSCP per se, but rather awaits specific
> > > > >proposals with a cautious mindset.  Recall from that section
>4.1.2
> > > > >that there is a need to define a behavior in addition to
>identifying
> > > > >a code point.  So if you want a code point of 1 or more bits for
> > > > >"emergency", what would be its defined forwarding behavior?
> > > > >
> > > > >one such proposal, primarily aimed at MLPP, is called Multi-Level
> > > > >Expedited Forwarding (MLEF) and can be found at:
> > > >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > >tsvwg-mlefphb-03.txt
> > > > >
> > > > >I would also suggest reading a counter proposal that avoids
>defining
> > > > >a new DSCP:
> > > >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > >mlpp-that-works-02.txt
> > > > >you can dig around the TSVWG archives over the past 2 months for
>some
> > > > >comments on the draft.
> > > > >
> > > > >-ken
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >Ieprep mailing list
> > > > >Ieprep@ietf.org
> > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > >
> > > >
> > > > cheers,
> > > > James
> > > >
> > > >                                  *******************
> > > >                  Truth is not to be argued... it is to be
>presented.
> >
> >
> > cheers,
> > James
> >
> >                                  *******************
> >                  Truth is not to be argued... it is to be presented.


cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sun Oct 23 22:55:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETsUl-0004aO-7l; Sun, 23 Oct 2005 22:55:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETsUj-0004a9-5D
	for ieprep@megatron.ietf.org; Sun, 23 Oct 2005 22:55:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08788
	for <ieprep@ietf.org>; Sun, 23 Oct 2005 22:55:16 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETshN-0008P7-NV
	for ieprep@ietf.org; Sun, 23 Oct 2005 23:08:35 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 03:55:18 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 03:55:17 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Sun, 23 Oct 2005 22:55:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sun, 23 Oct 2005 22:55:15 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C280166770C@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXYCxEPj8gtnTTSSQKcqDVHZuimywAOkRkw
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "James M. Polk" <jmpolk@cisco.com>
X-OriginalArrivalTime: 24 Oct 2005 02:55:16.0561 (UTC)
	FILETIME=[5CC45C10:01C5D846]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 025f8c5000216988bfe31585db759250
Content-Transfer-Encoding: quoted-printable
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org



> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Sunday, October 23, 2005 12:50 PM
> To: Reinaldo Penno
> Cc: ken carlberg; ieprep@ietf.org
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>=20
> Reinaldo
>=20
> Comments in-line
>=20
> At 02:29 AM 10/23/2005 -0400, Reinaldo Penno wrote:
> >That is also possible and it might happen all the time.
> >
> >I think the threats you mention are quite valid but they will be no
> >different if we have an emergency DSCP. The whole problem around
> >contention of resources will continue to happen.
> >
> >My point is the same as before. How this hypothetical scenario is any
> >different from what could happen today?
>=20
> Because, as I see it - and please correct me if I am seeing this
> incorrectly - that doctor's call in the enterprise will not be starved
off
> by any other call.
>=20
> Yet, the way I have understood most, and I think the scenario you have
> brought up, the emergency calls will starve off, or at least adversely
> affect existing calls that can be the equivalent of EF marked in
> treatment.

[[Reinaldo]]=20

But...the doctor call can will fight for resources in the same level as
an emergency call. I guess we should introduce the concept of "personal
emergency" and "collective emergency". If the building is burning up, I
try to call the fire department, and the person in the next cubicle
tries to call his priest, which call is more important? I guess this is
a complex issue. We will not be able to resolve it here.

If the PSTN today gives better priority to 911 calls, we should strive
to do the same for VoIP calls.

Regards,

Reinaldo

>=20
> Plus there is the issue that most employees operate under a subtly
> different set of laws and rules than the general public, usually
starting
> with when an employee candidate signs a contract of employment
reducing
> that person's rights in some ways.
>=20
>=20
> >For example, today if something happens in an enterprise, will the
> >emergency calls to 911 have better treatment than the doctor's call?
You
> >can also imagine a reversed scenario where I could argue that if the
> >call made by the person in the next cubicle to his doctor blocks my
call
> >to 911 I will sue the company/telco.
> >
> >Any hospital in the US has the following recording "if this is an
> >emergency, hang up and dial 911". If you really have an emergency,
you
> >should be calling 911, and not your doctor.
>=20
> While in general, I would agree with you, there are some cases in
which a
> doctor is who is to be called when you have an issue with something
under
> their care.  I have experienced this first hand to know it is true in
the
> US.
>=20
> >If you call your doctor, you
> >are implicitly telling the "system" that this is not an emergency.
>=20
> That's the legacy system you are telling.  Whereas, with IP, we have
many
> more capabilities (or should) to be able to differentiate one call
from
> another. I believe that should one of the IETF's (and other SDO's)
goals
> for emergency calling.
>=20
> Please review ECRIT WG discussions as there are many references to
this
> capability being on the to-do list of many areas dealing with this
> scenario.
>=20
>=20
> >Somebody in a Telco told me that 911 calls are signaled different
(which
> >imply a priority over normal calls). Do you know if this a fact?
>=20
> Yes, there are special facilities that 911 calls traverse, after the
> initial Class 5 switch towards the Selective Router, and on to the
PSAP.
>=20
>=20
> >Regards,
> >
> >Reinaldo
> >
> >
> >
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Saturday, October 22, 2005 8:23 PM
> > > To: Reinaldo Penno
> > > Cc: ken carlberg; ieprep@ietf.org
> > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > > At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> > > >Your point is well taken James.
> > > >
> > > >Therefore, if we just continue with just EF for normal and
emergency
> > > >voice calls, the risk is the same, the drawback that I see is
that we
> > > >cannot prioritize emergency over normal calls.
> > >
> > > so here's the problem as has been presented to me by both
regulators
> >and
> > > lawyers:
> > >
> > > In larger emergencies, many people will likely be calling for
> >emergency
> > > help, and some of them are not going to be calling (the equivalent
of)
> > > 911,
> > > they will be calling their doctors directly - yet to "the system",
> >these
> > > will appear as normal packets, or normal voice (EF marked)
packets. In
> > > your
> > > pondering, these packets will be subject to some form of lesser
> >treatment
> > > than perhaps the 10th or 100th call to 911, informing the PSAP of
the
> >same
> > > event (perhaps a building burning).
> > >
> > > Here's the catch: who determined the 10th or 100th call to the
PSAP is
> > > more
> > > important than the patient's call with their doctor - getting
> >one-on-one
> > > advice/help.
> > >
> > > I think the first lawsuit will stop that preferential treatment.
I've
> >had
> > > this hinted to me by many
> > >
> > >
> > > >So, in general an edge device that can perform SIP parsing and
mark
> > > >emergency calls with the emergency DSCP and others with EF DSCP.
> > > >Alternatively, in a decomposed gateway scenario the SIP Proxy can
let
> > > >the router know that a certain call is an emergency and that it
> >should
> > > >be marked differently.
> > >
> > > or there could be a path coupled mechanism for such calls, but
that
> >has
> > > its
> > > challenges too
> > >
> > >
> > > >Regards,
> > > >
> > > >Reinaldo
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > > To: Reinaldo Penno
> > > > > Cc: ken carlberg; ieprep@ietf.org
> > > > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > > > >
> > > > > Reinaldo
> > > > >
> > > > > Adding fuel to a discussion that has churned on many lists
over
> >the
> > > >last
> > > > > several years, I'd really want to understand the threat
anaylsis
> > > >observed
> > > > > by such a proposal (for a emergency DSCP) to ensure it could
not
> >be
> > > >used
> > > > > for a fairly trivial to generate DDOS on the network - even
all
> >the
> > > >way to
> > > > > the PSAP, or just used by neighbors wanting the very best
> >throughput
> > > >for
> > > > > their game of Doom.
> > > > >
> > > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > > >Hello Reinaldo,
> > > > > >
> > > > > >>I read
> > > > >
> > > >
> >
>>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > > > > >>and was somewhat puzzled at section 4.1.2. I understand that
the
> > > >IETF
> > > > > >>wants to be conservative in standardizing new DSCP, but it
seems
> >to
> > > >an
> > > > > >>emergency call DSCP would be accepted by the community (am I
> > > >wrong?).
> > > > > >
> > > > > >well, from my own take, I would say that the "community" is
not
> > > > > >against an emergency call DSCP per se, but rather awaits
specific
> > > > > >proposals with a cautious mindset.  Recall from that section
> >4.1.2
> > > > > >that there is a need to define a behavior in addition to
> >identifying
> > > > > >a code point.  So if you want a code point of 1 or more bits
for
> > > > > >"emergency", what would be its defined forwarding behavior?
> > > > > >
> > > > > >one such proposal, primarily aimed at MLPP, is called
Multi-Level
> > > > > >Expedited Forwarding (MLEF) and can be found at:
> > > > >
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > > >tsvwg-mlefphb-03.txt
> > > > > >
> > > > > >I would also suggest reading a counter proposal that avoids
> >defining
> > > > > >a new DSCP:
> > > > >
> > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > > >mlpp-that-works-02.txt
> > > > > >you can dig around the TSVWG archives over the past 2 months
for
> >some
> > > > > >comments on the draft.
> > > > > >
> > > > > >-ken
> > > > > >
> > > > > >
> > > > > >_______________________________________________
> > > > > >Ieprep mailing list
> > > > > >Ieprep@ietf.org
> > > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > > >
> > > > >
> > > > > cheers,
> > > > > James
> > > > >
> > > > >                                  *******************
> > > > >                  Truth is not to be argued... it is to be
> >presented.
> > >
> > >
> > > cheers,
> > > James
> > >
> > >                                  *******************
> > >                  Truth is not to be argued... it is to be
presented.
>=20
>=20
> cheers,
> James
>=20
>                                  *******************
>                  Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Sun Oct 23 23:42:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETtEb-0007FP-3P; Sun, 23 Oct 2005 23:42:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETtEX-0007Ey-C8
	for ieprep@megatron.ietf.org; Sun, 23 Oct 2005 23:42:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10593
	for <ieprep@ietf.org>; Sun, 23 Oct 2005 23:42:36 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ETtRD-0001JL-6y
	for ieprep@ietf.org; Sun, 23 Oct 2005 23:55:55 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-1.cisco.com with ESMTP; 23 Oct 2005 20:42:40 -0700
X-IronPort-AV: i="3.97,243,1125903600"; 
	d="scan'208"; a="668523555:sNHT28865850"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j9O3gNup005943;
	Sun, 23 Oct 2005 20:42:38 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sun, 23 Oct 2005 20:42:36 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.145.144]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Sun, 23 Oct 2005 20:42:35 -0700
Message-Id: <4.3.2.7.2.20051023223818.031b77f0@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 23 Oct 2005 22:42:34 -0500
To: "Reinaldo Penno" <rpenno@juniper.net>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C280166770C@proton.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 24 Oct 2005 03:42:35.0658 (UTC)
	FILETIME=[F9002EA0:01C5D84C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e267523e0685e5aa2dbbdde4b659686
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Reinaldo

Actually, the PSTN does not give better priority to 911 calls (vs. normal 
calls), they just use separate cirucuits once the 911 call gets to the 
first Class-5 switch.  Typically, a Class-5 Switch will have a small number 
of dedicated circuits that connect directly to a 911 Selective Router 
(which is a special instance of a Class-5 switch). 911 calls are routed 
over these dedicated circuits towards the SR to then be routed to the 
appropriate PSAP. This isn't really anything special - since the circuit 
world is not bandwidth contending, they are circuit contending.

At 10:55 PM 10/23/2005 -0400, Reinaldo Penno wrote:


> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk@cisco.com]
> > Sent: Sunday, October 23, 2005 12:50 PM
> > To: Reinaldo Penno
> > Cc: ken carlberg; ieprep@ietf.org
> > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> >
> > Reinaldo
> >
> > Comments in-line
> >
> > At 02:29 AM 10/23/2005 -0400, Reinaldo Penno wrote:
> > >That is also possible and it might happen all the time.
> > >
> > >I think the threats you mention are quite valid but they will be no
> > >different if we have an emergency DSCP. The whole problem around
> > >contention of resources will continue to happen.
> > >
> > >My point is the same as before. How this hypothetical scenario is any
> > >different from what could happen today?
> >
> > Because, as I see it - and please correct me if I am seeing this
> > incorrectly - that doctor's call in the enterprise will not be starved
>off
> > by any other call.
> >
> > Yet, the way I have understood most, and I think the scenario you have
> > brought up, the emergency calls will starve off, or at least adversely
> > affect existing calls that can be the equivalent of EF marked in
> > treatment.
>
>[[Reinaldo]]
>
>But...the doctor call can will fight for resources in the same level as
>an emergency call. I guess we should introduce the concept of "personal
>emergency" and "collective emergency". If the building is burning up, I
>try to call the fire department, and the person in the next cubicle
>tries to call his priest, which call is more important? I guess this is
>a complex issue. We will not be able to resolve it here.
>
>If the PSTN today gives better priority to 911 calls, we should strive
>to do the same for VoIP calls.
>
>Regards,
>
>Reinaldo
>
> >
> > Plus there is the issue that most employees operate under a subtly
> > different set of laws and rules than the general public, usually
>starting
> > with when an employee candidate signs a contract of employment
>reducing
> > that person's rights in some ways.
> >
> >
> > >For example, today if something happens in an enterprise, will the
> > >emergency calls to 911 have better treatment than the doctor's call?
>You
> > >can also imagine a reversed scenario where I could argue that if the
> > >call made by the person in the next cubicle to his doctor blocks my
>call
> > >to 911 I will sue the company/telco.
> > >
> > >Any hospital in the US has the following recording "if this is an
> > >emergency, hang up and dial 911". If you really have an emergency,
>you
> > >should be calling 911, and not your doctor.
> >
> > While in general, I would agree with you, there are some cases in
>which a
> > doctor is who is to be called when you have an issue with something
>under
> > their care.  I have experienced this first hand to know it is true in
>the
> > US.
> >
> > >If you call your doctor, you
> > >are implicitly telling the "system" that this is not an emergency.
> >
> > That's the legacy system you are telling.  Whereas, with IP, we have
>many
> > more capabilities (or should) to be able to differentiate one call
>from
> > another. I believe that should one of the IETF's (and other SDO's)
>goals
> > for emergency calling.
> >
> > Please review ECRIT WG discussions as there are many references to
>this
> > capability being on the to-do list of many areas dealing with this
> > scenario.
> >
> >
> > >Somebody in a Telco told me that 911 calls are signaled different
>(which
> > >imply a priority over normal calls). Do you know if this a fact?
> >
> > Yes, there are special facilities that 911 calls traverse, after the
> > initial Class 5 switch towards the Selective Router, and on to the
>PSAP.
> >
> >
> > >Regards,
> > >
> > >Reinaldo
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > Sent: Saturday, October 22, 2005 8:23 PM
> > > > To: Reinaldo Penno
> > > > Cc: ken carlberg; ieprep@ietf.org
> > > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > > >
> > > > At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> > > > >Your point is well taken James.
> > > > >
> > > > >Therefore, if we just continue with just EF for normal and
>emergency
> > > > >voice calls, the risk is the same, the drawback that I see is
>that we
> > > > >cannot prioritize emergency over normal calls.
> > > >
> > > > so here's the problem as has been presented to me by both
>regulators
> > >and
> > > > lawyers:
> > > >
> > > > In larger emergencies, many people will likely be calling for
> > >emergency
> > > > help, and some of them are not going to be calling (the equivalent
>of)
> > > > 911,
> > > > they will be calling their doctors directly - yet to "the system",
> > >these
> > > > will appear as normal packets, or normal voice (EF marked)
>packets. In
> > > > your
> > > > pondering, these packets will be subject to some form of lesser
> > >treatment
> > > > than perhaps the 10th or 100th call to 911, informing the PSAP of
>the
> > >same
> > > > event (perhaps a building burning).
> > > >
> > > > Here's the catch: who determined the 10th or 100th call to the
>PSAP is
> > > > more
> > > > important than the patient's call with their doctor - getting
> > >one-on-one
> > > > advice/help.
> > > >
> > > > I think the first lawsuit will stop that preferential treatment.
>I've
> > >had
> > > > this hinted to me by many
> > > >
> > > >
> > > > >So, in general an edge device that can perform SIP parsing and
>mark
> > > > >emergency calls with the emergency DSCP and others with EF DSCP.
> > > > >Alternatively, in a decomposed gateway scenario the SIP Proxy can
>let
> > > > >the router know that a certain call is an emergency and that it
> > >should
> > > > >be marked differently.
> > > >
> > > > or there could be a path coupled mechanism for such calls, but
>that
> > >has
> > > > its
> > > > challenges too
> > > >
> > > >
> > > > >Regards,
> > > > >
> > > > >Reinaldo
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > > > To: Reinaldo Penno
> > > > > > Cc: ken carlberg; ieprep@ietf.org
> > > > > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> > > > > >
> > > > > > Reinaldo
> > > > > >
> > > > > > Adding fuel to a discussion that has churned on many lists
>over
> > >the
> > > > >last
> > > > > > several years, I'd really want to understand the threat
>anaylsis
> > > > >observed
> > > > > > by such a proposal (for a emergency DSCP) to ensure it could
>not
> > >be
> > > > >used
> > > > > > for a fairly trivial to generate DDOS on the network - even
>all
> > >the
> > > > >way to
> > > > > > the PSAP, or just used by neighbors wanting the very best
> > >throughput
> > > > >for
> > > > > > their game of Doom.
> > > > > >
> > > > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > > > >Hello Reinaldo,
> > > > > > >
> > > > > > >>I read
> > > > > >
> > > > >
> > >
> >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > > > > > >>and was somewhat puzzled at section 4.1.2. I understand that
>the
> > > > >IETF
> > > > > > >>wants to be conservative in standardizing new DSCP, but it
>seems
> > >to
> > > > >an
> > > > > > >>emergency call DSCP would be accepted by the community (am I
> > > > >wrong?).
> > > > > > >
> > > > > > >well, from my own take, I would say that the "community" is
>not
> > > > > > >against an emergency call DSCP per se, but rather awaits
>specific
> > > > > > >proposals with a cautious mindset.  Recall from that section
> > >4.1.2
> > > > > > >that there is a need to define a behavior in addition to
> > >identifying
> > > > > > >a code point.  So if you want a code point of 1 or more bits
>for
> > > > > > >"emergency", what would be its defined forwarding behavior?
> > > > > > >
> > > > > > >one such proposal, primarily aimed at MLPP, is called
>Multi-Level
> > > > > > >Expedited Forwarding (MLEF) and can be found at:
> > > > > >
> > > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > > > >tsvwg-mlefphb-03.txt
> > > > > > >
> > > > > > >I would also suggest reading a counter proposal that avoids
> > >defining
> > > > > > >a new DSCP:
> > > > > >
> > > >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > > > >mlpp-that-works-02.txt
> > > > > > >you can dig around the TSVWG archives over the past 2 months
>for
> > >some
> > > > > > >comments on the draft.
> > > > > > >
> > > > > > >-ken
> > > > > > >
> > > > > > >
> > > > > > >_______________________________________________
> > > > > > >Ieprep mailing list
> > > > > > >Ieprep@ietf.org
> > > > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > > > >
> > > > > >
> > > > > > cheers,
> > > > > > James
> > > > > >
> > > > > >                                  *******************
> > > > > >                  Truth is not to be argued... it is to be
> > >presented.
> > > >
> > > >
> > > > cheers,
> > > > James
> > > >
> > > >                                  *******************
> > > >                  Truth is not to be argued... it is to be
>presented.
> >
> >
> > cheers,
> > James
> >
> >                                  *******************
> >                  Truth is not to be argued... it is to be presented.


cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Mon Oct 24 00:15:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETtkD-000798-LI; Mon, 24 Oct 2005 00:15:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETtkC-000793-80
	for ieprep@megatron.ietf.org; Mon, 24 Oct 2005 00:15:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11898
	for <ieprep@ietf.org>; Mon, 24 Oct 2005 00:15:19 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETtws-0002LJ-DI
	for ieprep@ietf.org; Mon, 24 Oct 2005 00:28:39 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 05:15:22 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 05:15:22 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Mon, 24 Oct 2005 00:15:20 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Mon, 24 Oct 2005 00:15:20 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C280166770D@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXYTQYYFK867GbAQ+6X59uC72OxDAAA/MwQ
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "James M. Polk" <jmpolk@cisco.com>
X-OriginalArrivalTime: 24 Oct 2005 04:15:20.0827 (UTC)
	FILETIME=[8C552CB0:01C5D851]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e3901bdd61b234d82da85cc76f05a7e8
Content-Transfer-Encoding: quoted-printable
Cc: ieprep@ietf.org, ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Well, given that PSTN is resource contending having a different circuit
is a form of special treatment, isn't it?

The analogous in the IP world (which in bandwidth contending) would be
to have bandwidth reservation for a certain number of emergency calls?
Is that the direction the several WGs are leaning towards?

Regards,

Reinaldo


> -----Original Message-----
> From: James M. Polk [mailto:jmpolk@cisco.com]
> Sent: Sunday, October 23, 2005 8:43 PM
> To: Reinaldo Penno
> Cc: ken carlberg; ieprep@ietf.org
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>=20
> Reinaldo
>=20
> Actually, the PSTN does not give better priority to 911 calls (vs.
normal
> calls), they just use separate cirucuits once the 911 call gets to the
> first Class-5 switch.  Typically, a Class-5 Switch will have a small
> number
> of dedicated circuits that connect directly to a 911 Selective Router
> (which is a special instance of a Class-5 switch). 911 calls are
routed
> over these dedicated circuits towards the SR to then be routed to the
> appropriate PSAP. This isn't really anything special - since the
circuit
> world is not bandwidth contending, they are circuit contending.
>=20
> At 10:55 PM 10/23/2005 -0400, Reinaldo Penno wrote:
>=20
>=20
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Sunday, October 23, 2005 12:50 PM
> > > To: Reinaldo Penno
> > > Cc: ken carlberg; ieprep@ietf.org
> > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > > Reinaldo
> > >
> > > Comments in-line
> > >
> > > At 02:29 AM 10/23/2005 -0400, Reinaldo Penno wrote:
> > > >That is also possible and it might happen all the time.
> > > >
> > > >I think the threats you mention are quite valid but they will be
no
> > > >different if we have an emergency DSCP. The whole problem around
> > > >contention of resources will continue to happen.
> > > >
> > > >My point is the same as before. How this hypothetical scenario is
any
> > > >different from what could happen today?
> > >
> > > Because, as I see it - and please correct me if I am seeing this
> > > incorrectly - that doctor's call in the enterprise will not be
starved
> >off
> > > by any other call.
> > >
> > > Yet, the way I have understood most, and I think the scenario you
have
> > > brought up, the emergency calls will starve off, or at least
adversely
> > > affect existing calls that can be the equivalent of EF marked in
> > > treatment.
> >
> >[[Reinaldo]]
> >
> >But...the doctor call can will fight for resources in the same level
as
> >an emergency call. I guess we should introduce the concept of
"personal
> >emergency" and "collective emergency". If the building is burning up,
I
> >try to call the fire department, and the person in the next cubicle
> >tries to call his priest, which call is more important? I guess this
is
> >a complex issue. We will not be able to resolve it here.
> >
> >If the PSTN today gives better priority to 911 calls, we should
strive
> >to do the same for VoIP calls.
> >
> >Regards,
> >
> >Reinaldo
> >
> > >
> > > Plus there is the issue that most employees operate under a subtly
> > > different set of laws and rules than the general public, usually
> >starting
> > > with when an employee candidate signs a contract of employment
> >reducing
> > > that person's rights in some ways.
> > >
> > >
> > > >For example, today if something happens in an enterprise, will
the
> > > >emergency calls to 911 have better treatment than the doctor's
call?
> >You
> > > >can also imagine a reversed scenario where I could argue that if
the
> > > >call made by the person in the next cubicle to his doctor blocks
my
> >call
> > > >to 911 I will sue the company/telco.
> > > >
> > > >Any hospital in the US has the following recording "if this is an
> > > >emergency, hang up and dial 911". If you really have an
emergency,
> >you
> > > >should be calling 911, and not your doctor.
> > >
> > > While in general, I would agree with you, there are some cases in
> >which a
> > > doctor is who is to be called when you have an issue with
something
> >under
> > > their care.  I have experienced this first hand to know it is true
in
> >the
> > > US.
> > >
> > > >If you call your doctor, you
> > > >are implicitly telling the "system" that this is not an
emergency.
> > >
> > > That's the legacy system you are telling.  Whereas, with IP, we
have
> >many
> > > more capabilities (or should) to be able to differentiate one call
> >from
> > > another. I believe that should one of the IETF's (and other SDO's)
> >goals
> > > for emergency calling.
> > >
> > > Please review ECRIT WG discussions as there are many references to
> >this
> > > capability being on the to-do list of many areas dealing with this
> > > scenario.
> > >
> > >
> > > >Somebody in a Telco told me that 911 calls are signaled different
> >(which
> > > >imply a priority over normal calls). Do you know if this a fact?
> > >
> > > Yes, there are special facilities that 911 calls traverse, after
the
> > > initial Class 5 switch towards the Selective Router, and on to the
> >PSAP.
> > >
> > >
> > > >Regards,
> > > >
> > > >Reinaldo
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > Sent: Saturday, October 22, 2005 8:23 PM
> > > > > To: Reinaldo Penno
> > > > > Cc: ken carlberg; ieprep@ietf.org
> > > > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > > > >
> > > > > At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> > > > > >Your point is well taken James.
> > > > > >
> > > > > >Therefore, if we just continue with just EF for normal and
> >emergency
> > > > > >voice calls, the risk is the same, the drawback that I see is
> >that we
> > > > > >cannot prioritize emergency over normal calls.
> > > > >
> > > > > so here's the problem as has been presented to me by both
> >regulators
> > > >and
> > > > > lawyers:
> > > > >
> > > > > In larger emergencies, many people will likely be calling for
> > > >emergency
> > > > > help, and some of them are not going to be calling (the
equivalent
> >of)
> > > > > 911,
> > > > > they will be calling their doctors directly - yet to "the
system",
> > > >these
> > > > > will appear as normal packets, or normal voice (EF marked)
> >packets. In
> > > > > your
> > > > > pondering, these packets will be subject to some form of
lesser
> > > >treatment
> > > > > than perhaps the 10th or 100th call to 911, informing the PSAP
of
> >the
> > > >same
> > > > > event (perhaps a building burning).
> > > > >
> > > > > Here's the catch: who determined the 10th or 100th call to the
> >PSAP is
> > > > > more
> > > > > important than the patient's call with their doctor - getting
> > > >one-on-one
> > > > > advice/help.
> > > > >
> > > > > I think the first lawsuit will stop that preferential
treatment.
> >I've
> > > >had
> > > > > this hinted to me by many
> > > > >
> > > > >
> > > > > >So, in general an edge device that can perform SIP parsing
and
> >mark
> > > > > >emergency calls with the emergency DSCP and others with EF
DSCP.
> > > > > >Alternatively, in a decomposed gateway scenario the SIP Proxy
can
> >let
> > > > > >the router know that a certain call is an emergency and that
it
> > > >should
> > > > > >be marked differently.
> > > > >
> > > > > or there could be a path coupled mechanism for such calls, but
> >that
> > > >has
> > > > > its
> > > > > challenges too
> > > > >
> > > > >
> > > > > >Regards,
> > > > > >
> > > > > >Reinaldo
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > > > > To: Reinaldo Penno
> > > > > > > Cc: ken carlberg; ieprep@ietf.org
> > > > > > > Subject: Re: [Ieprep] Diffserv Code Point for Emergency
calls
> > > > > > >
> > > > > > > Reinaldo
> > > > > > >
> > > > > > > Adding fuel to a discussion that has churned on many lists
> >over
> > > >the
> > > > > >last
> > > > > > > several years, I'd really want to understand the threat
> >anaylsis
> > > > > >observed
> > > > > > > by such a proposal (for a emergency DSCP) to ensure it
could
> >not
> > > >be
> > > > > >used
> > > > > > > for a fairly trivial to generate DDOS on the network -
even
> >all
> > > >the
> > > > > >way to
> > > > > > > the PSAP, or just used by neighbors wanting the very best
> > > >throughput
> > > > > >for
> > > > > > > their game of Doom.
> > > > > > >
> > > > > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > > > > >Hello Reinaldo,
> > > > > > > >
> > > > > > > >>I read
> > > > > > >
> > > > > >
> > > >
> >
>>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-framework-10.txt
> > > > > > > >>and was somewhat puzzled at section 4.1.2. I understand
that
> >the
> > > > > >IETF
> > > > > > > >>wants to be conservative in standardizing new DSCP, but
it
> >seems
> > > >to
> > > > > >an
> > > > > > > >>emergency call DSCP would be accepted by the community
(am I
> > > > > >wrong?).
> > > > > > > >
> > > > > > > >well, from my own take, I would say that the "community"
is
> >not
> > > > > > > >against an emergency call DSCP per se, but rather awaits
> >specific
> > > > > > > >proposals with a cautious mindset.  Recall from that
section
> > > >4.1.2
> > > > > > > >that there is a need to define a behavior in addition to
> > > >identifying
> > > > > > > >a code point.  So if you want a code point of 1 or more
bits
> >for
> > > > > > > >"emergency", what would be its defined forwarding
behavior?
> > > > > > > >
> > > > > > > >one such proposal, primarily aimed at MLPP, is called
> >Multi-Level
> > > > > > > >Expedited Forwarding (MLEF) and can be found at:
> > > > > > >
> > > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > > > > >tsvwg-mlefphb-03.txt
> > > > > > > >
> > > > > > > >I would also suggest reading a counter proposal that
avoids
> > > >defining
> > > > > > > >a new DSCP:
> > > > > > >
> > > >
>ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > > > > >mlpp-that-works-02.txt
> > > > > > > >you can dig around the TSVWG archives over the past 2
months
> >for
> > > >some
> > > > > > > >comments on the draft.
> > > > > > > >
> > > > > > > >-ken
> > > > > > > >
> > > > > > > >
> > > > > > > >_______________________________________________
> > > > > > > >Ieprep mailing list
> > > > > > > >Ieprep@ietf.org
> > > > > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > > > > >
> > > > > > >
> > > > > > > cheers,
> > > > > > > James
> > > > > > >
> > > > > > >                                  *******************
> > > > > > >                  Truth is not to be argued... it is to be
> > > >presented.
> > > > >
> > > > >
> > > > > cheers,
> > > > > James
> > > > >
> > > > >                                  *******************
> > > > >                  Truth is not to be argued... it is to be
> >presented.
> > >
> > >
> > > cheers,
> > > James
> > >
> > >                                  *******************
> > >                  Truth is not to be argued... it is to be
presented.
>=20
>=20
> cheers,
> James
>=20
>                                  *******************
>                  Truth is not to be argued... it is to be presented.

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



From ieprep-bounces@ietf.org Mon Oct 24 08:51:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1nD-00008L-U7; Mon, 24 Oct 2005 08:51:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1nC-00007W-28; Mon, 24 Oct 2005 08:51:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07682;
	Mon, 24 Oct 2005 08:50:56 -0400 (EDT)
Received: from amer-mta02.csc.com ([20.137.2.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EU1zu-0002MZ-Vu; Mon, 24 Oct 2005 09:04:21 -0400
Received: from amer-gw09.csc.com (amer-gw09.csc.com [20.6.39.245])
	by amer-mta02.csc.com (8.12.11/Switch-3.1.6) with ESMTP id
	j9OCp1Nv017030; Mon, 24 Oct 2005 08:51:01 -0400 (EDT)
In-Reply-To: <4.3.2.7.2.20051023223818.031b77f0@email.cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
To: "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OF00F8DBE3.8FAE76FF-ON852570A4.00462EE3-852570A4.00469457@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Mon, 24 Oct 2005 08:50:59 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 6.5.3|September
	14, 2004) at 10/24/2005 08:50:37 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: ieprep-bounces@ietf.org, ieprep@ietf.org,
	ken carlberg <carlberg@g11.org.uk>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org





James,

The PSTN DOES give emergency (911) calls priority in a small way.

The SS7 signaling messages have an associated priority, called MTP.  When
an SS7 "server" is congested, it will shed MTP 0 messages before it sheds
MTP 1 messages.

Normal call request messages ( ISUP IAMs) are MTP 0.
Emergency (911), NS/EP. and MLPP call request messages are MTP 1.

Janet

ieprep-bounces@ietf.org wrote on 10/23/2005 11:42:34 PM:

> Reinaldo
>
> Actually, the PSTN does not give better priority to 911 calls (vs. normal

> calls), they just use separate cirucuits once the 911 call gets to the
> first Class-5 switch.  Typically, a Class-5 Switch will have a small
number
> of dedicated circuits that connect directly to a 911 Selective Router
> (which is a special instance of a Class-5 switch). 911 calls are routed
> over these dedicated circuits towards the SR to then be routed to the
> appropriate PSAP. This isn't really anything special - since the circuit
> world is not bandwidth contending, they are circuit contending.


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



From ieprep-bounces@ietf.org Mon Oct 24 09:03:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1yv-0002mg-Da; Mon, 24 Oct 2005 09:03:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1yt-0002mW-F0
	for ieprep@megatron.ietf.org; Mon, 24 Oct 2005 09:03:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08244
	for <ieprep@ietf.org>; Mon, 24 Oct 2005 09:03:01 -0400 (EDT)
Received: from hammerhead.shentel.net ([204.111.11.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU2Bd-0002ln-CJ
	for ieprep@ietf.org; Mon, 24 Oct 2005 09:16:26 -0400
Received: from Steve ([204.111.101.215])
	by hammerhead.shentel.net (8.13.3/8.13.3) with SMTP id j9OD2rdt029886; 
	Mon, 24 Oct 2005 09:02:54 -0400
From: "Steve Silverman" <steves@shentel.net>
To: "James M. Polk" <jmpolk@cisco.com>, "Reinaldo Penno" <rpenno@juniper.net>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Mon, 24 Oct 2005 09:03:27 -0400
Message-ID: <CIEELMKPOOAMCIAKANLBMEGOFGAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <4.3.2.7.2.20051023143437.029f6948@email.cisco.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
Content-Transfer-Encoding: 7bit
Cc: ken carlberg <carlberg@g11.org.uk>, ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

James,

We can only base our actions on what is detectible.  We can prioritize
calls to 911 (or equivalent).  I don't know
how to detect emergency calls to a doctor's office.  Or at least how
to distinguish emergencies from routine traffic.
In the absence of both user authentication and mind reading
technology, I don't think we can give special treatment to your
doctor's call example. This is another reason to call 911 for
emergencies rather than a doctor's office. I know my wife tells her
patients to call 911 if there is a true emergency.

Steve

> -----Original Message-----
> From: ieprep-bounces@ietf.org
> [mailto:ieprep-bounces@ietf.org]On Behalf
> Of James M. Polk
> Sent: Sunday, October 23, 2005 3:50 PM
> To: Reinaldo Penno
> Cc: ieprep@ietf.org; ken carlberg
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>
>
> Reinaldo
>
> Comments in-line
>
> At 02:29 AM 10/23/2005 -0400, Reinaldo Penno wrote:
> >That is also possible and it might happen all the time.
> >
> >I think the threats you mention are quite valid but they will be no
> >different if we have an emergency DSCP. The whole problem around
> >contention of resources will continue to happen.
> >
> >My point is the same as before. How this hypothetical
> scenario is any
> >different from what could happen today?
>
> Because, as I see it - and please correct me if I am seeing this
> incorrectly - that doctor's call in the enterprise will not
> be starved off
> by any other call.
Yes it will if there are too many emergency calls.

>
> Please review ECRIT WG discussions as there are many
> references to this
> capability being on the to-do list of many areas dealing
> with this scenario.
>
>
> >Somebody in a Telco told me that 911 calls are signaled
> different (which
> >imply a priority over normal calls). Do you know if this a fact?
>
> Yes, there are special facilities that 911 calls traverse,
> after the
> initial Class 5 switch towards the Selective Router, and on
> to the PSAP.
>
>
> >Regards,
> >
> >Reinaldo
> >
> >
> >
> > > -----Original Message-----
> > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > Sent: Saturday, October 22, 2005 8:23 PM
> > > To: Reinaldo Penno
> > > Cc: ken carlberg; ieprep@ietf.org
> > > Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
> > >
> > > At 08:45 AM 10/22/2005 -0400, Reinaldo Penno wrote:
> > > >Your point is well taken James.
> > > >
> > > >Therefore, if we just continue with just EF for normal
> and emergency
> > > >voice calls, the risk is the same, the drawback that I
> see is that we
> > > >cannot prioritize emergency over normal calls.
> > >
> > > so here's the problem as has been presented to me by
> both regulators
> >and
> > > lawyers:
> > >
> > > In larger emergencies, many people will likely be calling for
> >emergency
> > > help, and some of them are not going to be calling (the
> equivalent of)
> > > 911,
> > > they will be calling their doctors directly - yet to
> "the system",
> >these
> > > will appear as normal packets, or normal voice (EF
> marked) packets. In
> > > your
> > > pondering, these packets will be subject to some form of lesser
> >treatment
> > > than perhaps the 10th or 100th call to 911, informing
> the PSAP of the
> >same
> > > event (perhaps a building burning).
> > >
> > > Here's the catch: who determined the 10th or 100th call
> to the PSAP is
> > > more
> > > important than the patient's call with their doctor - getting
> >one-on-one
> > > advice/help.
> > >
> > > I think the first lawsuit will stop that preferential
> treatment. I've
> >had
> > > this hinted to me by many
> > >
> > >
> > > >So, in general an edge device that can perform SIP
> parsing and mark
> > > >emergency calls with the emergency DSCP and others
> with EF DSCP.
> > > >Alternatively, in a decomposed gateway scenario the
> SIP Proxy can let
> > > >the router know that a certain call is an emergency and that it
> >should
> > > >be marked differently.
> > >
> > > or there could be a path coupled mechanism for such
> calls, but that
> >has
> > > its
> > > challenges too
> > >
> > >
> > > >Regards,
> > > >
> > > >Reinaldo
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: James M. Polk [mailto:jmpolk@cisco.com]
> > > > > Sent: Friday, October 21, 2005 11:02 PM
> > > > > To: Reinaldo Penno
> > > > > Cc: ken carlberg; ieprep@ietf.org
> > > > > Subject: Re: [Ieprep] Diffserv Code Point for
> Emergency calls
> > > > >
> > > > > Reinaldo
> > > > >
> > > > > Adding fuel to a discussion that has churned on
> many lists over
> >the
> > > >last
> > > > > several years, I'd really want to understand the
> threat anaylsis
> > > >observed
> > > > > by such a proposal (for a emergency DSCP) to ensure
> it could not
> >be
> > > >used
> > > > > for a fairly trivial to generate DDOS on the
> network - even all
> >the
> > > >way to
> > > > > the PSAP, or just used by neighbors wanting the very best
> >throughput
> > > >for
> > > > > their game of Doom.
> > > > >
> > > > > At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> > > > > >Hello Reinaldo,
> > > > > >
> > > > > >>I read
> > > > >
> > > >
> >
> >>http://www.ietf.org/internet-drafts/draft-ietf-ieprep-fram
> ework-10.txt
> > > > > >>and was somewhat puzzled at section 4.1.2. I
> understand that the
> > > >IETF
> > > > > >>wants to be conservative in standardizing new
> DSCP, but it seems
> >to
> > > >an
> > > > > >>emergency call DSCP would be accepted by the
> community (am I
> > > >wrong?).
> > > > > >
> > > > > >well, from my own take, I would say that the
> "community" is not
> > > > > >against an emergency call DSCP per se, but rather
> awaits specific
> > > > > >proposals with a cautious mindset.  Recall from
> that section
> >4.1.2
> > > > > >that there is a need to define a behavior in addition to
> >identifying
> > > > > >a code point.  So if you want a code point of 1 or
> more bits for
> > > > > >"emergency", what would be its defined forwarding behavior?
> > > > > >
> > > > > >one such proposal, primarily aimed at MLPP, is
> called Multi-Level
> > > > > >Expedited Forwarding (MLEF) and can be found at:
> > > > >
> >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> > > > > >tsvwg-mlefphb-03.txt
> > > > > >
> > > > > >I would also suggest reading a counter proposal that avoids
> >defining
> > > > > >a new DSCP:
> > > > >
> >
> >ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> > > > > >mlpp-that-works-02.txt
> > > > > >you can dig around the TSVWG archives over the
> past 2 months for
> >some
> > > > > >comments on the draft.
> > > > > >
> > > > > >-ken
> > > > > >
> > > > > >
> > > > > >_______________________________________________
> > > > > >Ieprep mailing list
> > > > > >Ieprep@ietf.org
> > > > > >https://www1.ietf.org/mailman/listinfo/ieprep
> > > > >
> > > > >
> > > > > cheers,
> > > > > James
> > > > >
> > > > >                                  *******************
> > > > >                  Truth is not to be argued... it is to be
> >presented.
> > >
> > >
> > > cheers,
> > > James
> > >
> > >                                  *******************
> > >                  Truth is not to be argued... it is to
> be presented.
>
>
> cheers,
> James
>
>                                  *******************
>                  Truth is not to be argued... it is to be presented.
>
> _______________________________________________
> 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 ieprep-bounces@ietf.org Mon Oct 24 19:24:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUBgK-0002Tt-11; Mon, 24 Oct 2005 19:24:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUBgI-0002Tl-Lj; Mon, 24 Oct 2005 19:24:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05193;
	Mon, 24 Oct 2005 19:24:29 -0400 (EDT)
Received: from mail131.messagelabs.com ([216.82.242.99])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EUBt3-0006DS-2d; Mon, 24 Oct 2005 19:37:59 -0400
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-4.tower-131.messagelabs.com!1130196162!11662183!11
X-StarScan-Version: 5.4.15; banners=-,-,-
X-Originating-IP: [192.128.167.132]
Received: (qmail 21299 invoked from network); 24 Oct 2005 23:24:26 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (192.128.167.132)
	by server-4.tower-131.messagelabs.com with SMTP;
	24 Oct 2005 23:24:26 -0000
Received: from OCCLUST04EVS1.ugd.att.com (135.38.164.12) by
	attrh3i.attrh.att.com (7.2.052)
	id 435BB4FA0002CA28; Mon, 24 Oct 2005 19:24:25 -0400
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Mon, 24 Oct 2005 18:24:25 -0500
Message-ID: <28F05913385EAC43AF019413F674A0170DE0BD25@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXYmdPyOf3lWdP5T2uyTBa89ZzvagAWCJng
From: "Dolly, Martin C, ALABS" <mdolly@att.com>
To: "Janet P Gunn" <jgunn6@csc.com>, "James M. Polk" <jmpolk@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Cc: ieprep-bounces@ietf.org, ken carlberg <carlberg@g11.org.uk>,
	ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

James,

There are additional Switch call processing requirements.

Cheers,

Martin



> -----Original Message-----
> From: ieprep-bounces@ietf.org=20
> [mailto:ieprep-bounces@ietf.org]On Behalf
> Of Janet P Gunn
> Sent: Monday, October 24, 2005 5:51 AM
> To: James M. Polk
> Cc: ieprep-bounces@ietf.org; ieprep@ietf.org; ken carlberg
> Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
>=20
>=20
>=20
>=20
>=20
>=20
> James,
>=20
> The PSTN DOES give emergency (911) calls priority in a small way.
>=20
> The SS7 signaling messages have an associated priority,=20
> called MTP.  When
> an SS7 "server" is congested, it will shed MTP 0 messages=20
> before it sheds
> MTP 1 messages.
>=20
> Normal call request messages ( ISUP IAMs) are MTP 0.
> Emergency (911), NS/EP. and MLPP call request messages are MTP 1.
>=20
> Janet
>=20
> ieprep-bounces@ietf.org wrote on 10/23/2005 11:42:34 PM:
>=20
> > Reinaldo
> >
> > Actually, the PSTN does not give better priority to 911=20
> calls (vs. normal
>=20
> > calls), they just use separate cirucuits once the 911 call=20
> gets to the
> > first Class-5 switch.  Typically, a Class-5 Switch will have a small
> number
> > of dedicated circuits that connect directly to a 911=20
> Selective Router
> > (which is a special instance of a Class-5 switch). 911=20
> calls are routed
> > over these dedicated circuits towards the SR to then be=20
> routed to the
> > appropriate PSAP. This isn't really anything special -=20
> since the circuit
> > world is not bandwidth contending, they are circuit contending.
>=20
>=20
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>=20

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



From ieprep-bounces@ietf.org Wed Oct 26 16:41:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUs5R-0007O0-1W; Wed, 26 Oct 2005 16:41:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUs5N-0007MW-OM
	for ieprep@megatron.ietf.org; Wed, 26 Oct 2005 16:41:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11595
	for <ieprep@ietf.org>; Wed, 26 Oct 2005 16:41:09 -0400 (EDT)
Received: from 130.155.216.216.transedge.com ([216.216.155.130]
	helo=vbn.0053136.lodgenet.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUsIZ-0007zE-HD
	for ieprep@ietf.org; Wed, 26 Oct 2005 16:55:05 -0400
Received: from [10.2.2.144] (helo=[10.2.2.144])
	by vbn.0053136.lodgenet.net with esmtp (Exim 3.34 #1)
	id 1EUs58-0002oH-00; Wed, 26 Oct 2005 16:41:10 -0400
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667705@proton.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <94255790-FA0D-4D0A-823B-F6F7DFACD98C@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
Date: Wed, 26 Oct 2005 14:59:05 -0400
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: 7bit
Cc: "James M. Polk" <jmpolk@cisco.com>, ken carlberg <carlberg@g11.org.uk>,
	ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

 From my perspective, the question in the data plane is not whether  
the packet is part of an emergency session, but whether it is  
authorized to use the bandwidth. Emergency authorization is a control  
plane problem.

That is why I have suggested authorization of users to use the EF  
code point during CAC.

On Oct 22, 2005, at 8:45 AM, Reinaldo Penno wrote:

> Your point is well taken James.
>
> I guess the risk is no different from what we face nowadays with doom
> packets marked with EF DSCP. The solution as well is no different from
> what we have today to deal with those packets. Usually  
> independently of
> the DSCP an endpoint might put in a packet, the edge router perform
> classification and if necessary remarks the packet with whatever  
> DSCP it
> should have.
>
> Therefore, if we just continue with just EF for normal and emergency
> voice calls, the risk is the same, the drawback that I see is that we
> cannot prioritize emergency over normal calls.
>
> So, in general an edge device that can perform SIP parsing and mark
> emergency calls with the emergency DSCP and others with EF DSCP.
> Alternatively, in a decomposed gateway scenario the SIP Proxy can let
> the router know that a certain call is an emergency and that it should
> be marked differently.
>
> Regards,
>
> Reinaldo
>
>
>
>> -----Original Message-----
>> From: James M. Polk [mailto:jmpolk@cisco.com]
>> Sent: Friday, October 21, 2005 11:02 PM
>> To: Reinaldo Penno
>> Cc: ken carlberg; ieprep@ietf.org
>> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>>
>> Reinaldo
>>
>> Adding fuel to a discussion that has churned on many lists over the
>>
> last
>
>> several years, I'd really want to understand the threat anaylsis
>>
> observed
>
>> by such a proposal (for a emergency DSCP) to ensure it could not be
>>
> used
>
>> for a fairly trivial to generate DDOS on the network - even all the
>>
> way to
>
>> the PSAP, or just used by neighbors wanting the very best throughput
>>
> for
>
>> their game of Doom.
>>
>> At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
>>
>>> Hello Reinaldo,
>>>
>>>
>>>> I read
>>>>
>>
>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-ieprep- 
>>> framework-10.txt
>>>
>>>> and was somewhat puzzled at section 4.1.2. I understand that the
>>>>
> IETF
>
>>>> wants to be conservative in standardizing new DSCP, but it seems to
>>>>
> an
>
>>>> emergency call DSCP would be accepted by the community (am I
>>>>
> wrong?).
>
>>>
>>> well, from my own take, I would say that the "community" is not
>>> against an emergency call DSCP per se, but rather awaits specific
>>> proposals with a cautious mindset.  Recall from that section 4.1.2
>>> that there is a need to define a behavior in addition to identifying
>>> a code point.  So if you want a code point of 1 or more bits for
>>> "emergency", what would be its defined forwarding behavior?
>>>
>>> one such proposal, primarily aimed at MLPP, is called Multi-Level
>>> Expedited Forwarding (MLEF) and can be found at:
>>> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
>>> tsvwg-mlefphb-03.txt
>>>
>>> I would also suggest reading a counter proposal that avoids defining
>>> a new DSCP:
>>> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
>>> mlpp-that-works-02.txt
>>> you can dig around the TSVWG archives over the past 2 months for  
>>> some
>>> comments on the draft.
>>>
>>> -ken
>>>
>>>
>>> _______________________________________________
>>> Ieprep mailing list
>>> Ieprep@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ieprep
>>>
>>
>>
>> cheers,
>> James
>>
>>                                  *******************
>>                  Truth is not to be argued... it is to be presented.
>>
>
> _______________________________________________
> 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 ieprep-bounces@ietf.org Thu Oct 27 23:30:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVKwc-00061l-Os; Thu, 27 Oct 2005 23:30:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVKwc-00061H-0M
	for ieprep@megatron.ietf.org; Thu, 27 Oct 2005 23:30:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15870
	for <ieprep@ietf.org>; Thu, 27 Oct 2005 23:30:01 -0400 (EDT)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVLA4-0005mN-9Y
	for ieprep@ietf.org; Thu, 27 Oct 2005 23:44:14 -0400
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 28 Oct 2005 04:29:57 +0100
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 28 Oct 2005 04:29:57 +0100
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 27 Oct 2005 23:29:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Thu, 27 Oct 2005 23:29:55 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C2801667743@proton.jnpr.net>
Thread-Topic: [Ieprep] Diffserv Code Point for Emergency calls
Thread-Index: AcXabbGMzkNgVybQSGeGV4j4+bJyhgA//nGQ
From: "Reinaldo Penno" <rpenno@juniper.net>
To: "Fred Baker" <fred@cisco.com>
X-OriginalArrivalTime: 28 Oct 2005 03:29:55.0623 (UTC)
	FILETIME=[DDA30B70:01C5DB6F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Content-Transfer-Encoding: quoted-printable
Cc: "James M. Polk" <jmpolk@cisco.com>, ken carlberg <carlberg@g11.org.uk>,
	ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Hello,

I read draft draft-ietf-tsvwg-mlpp-that-works-02, which I assume it is
your proposal.

Some questions:

1. The example is the end if quite complex. I would like to start with a
bare bores one. Which priority you suggest for everyday 911 calls as
opposed to normal telephone calls? I believe the priorities are below

  The DSN has 5 precedence levels of IEPS in descending order:

        dsn.flash-override

        dsn.flash

        dsn.immediate

        dsn.priority

        dsn.routine

2. It seems to me your proposal and an emergency DSCP are complementary
and not mutually exclusive. If signal with RSVP and if you get
bandwidth, you mark packets with the emergency DSCP.

3. Not trying to simplify things but premise of this proposal is that
all IP phones will support RSVP, right?=20

4. Should the phones use RSVP just for emergency calls or for all calls
in general? I guess they should otherwise the other devices would loose
track of how much bandwidth has been consumed?

Thanks,

Reinaldo



> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]
> Sent: Wednesday, October 26, 2005 11:59 AM
> To: Reinaldo Penno
> Cc: James M. Polk; ieprep@ietf.org; ken carlberg
> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>=20
>  From my perspective, the question in the data plane is not whether
> the packet is part of an emergency session, but whether it is
> authorized to use the bandwidth. Emergency authorization is a control
> plane problem.
>=20
> That is why I have suggested authorization of users to use the EF
> code point during CAC.
>=20
> On Oct 22, 2005, at 8:45 AM, Reinaldo Penno wrote:
>=20
> > Your point is well taken James.
> >
> > I guess the risk is no different from what we face nowadays with
doom
> > packets marked with EF DSCP. The solution as well is no different
from
> > what we have today to deal with those packets. Usually
> > independently of
> > the DSCP an endpoint might put in a packet, the edge router perform
> > classification and if necessary remarks the packet with whatever
> > DSCP it
> > should have.
> >
> > Therefore, if we just continue with just EF for normal and emergency
> > voice calls, the risk is the same, the drawback that I see is that
we
> > cannot prioritize emergency over normal calls.
> >
> > So, in general an edge device that can perform SIP parsing and mark
> > emergency calls with the emergency DSCP and others with EF DSCP.
> > Alternatively, in a decomposed gateway scenario the SIP Proxy can
let
> > the router know that a certain call is an emergency and that it
should
> > be marked differently.
> >
> > Regards,
> >
> > Reinaldo
> >
> >
> >
> >> -----Original Message-----
> >> From: James M. Polk [mailto:jmpolk@cisco.com]
> >> Sent: Friday, October 21, 2005 11:02 PM
> >> To: Reinaldo Penno
> >> Cc: ken carlberg; ieprep@ietf.org
> >> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
> >>
> >> Reinaldo
> >>
> >> Adding fuel to a discussion that has churned on many lists over the
> >>
> > last
> >
> >> several years, I'd really want to understand the threat anaylsis
> >>
> > observed
> >
> >> by such a proposal (for a emergency DSCP) to ensure it could not be
> >>
> > used
> >
> >> for a fairly trivial to generate DDOS on the network - even all the
> >>
> > way to
> >
> >> the PSAP, or just used by neighbors wanting the very best
throughput
> >>
> > for
> >
> >> their game of Doom.
> >>
> >> At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
> >>
> >>> Hello Reinaldo,
> >>>
> >>>
> >>>> I read
> >>>>
> >>
> >>
> >>> http://www.ietf.org/internet-drafts/draft-ietf-ieprep-
> >>> framework-10.txt
> >>>
> >>>> and was somewhat puzzled at section 4.1.2. I understand that the
> >>>>
> > IETF
> >
> >>>> wants to be conservative in standardizing new DSCP, but it seems
to
> >>>>
> > an
> >
> >>>> emergency call DSCP would be accepted by the community (am I
> >>>>
> > wrong?).
> >
> >>>
> >>> well, from my own take, I would say that the "community" is not
> >>> against an emergency call DSCP per se, but rather awaits specific
> >>> proposals with a cautious mindset.  Recall from that section 4.1.2
> >>> that there is a need to define a behavior in addition to
identifying
> >>> a code point.  So if you want a code point of 1 or more bits for
> >>> "emergency", what would be its defined forwarding behavior?
> >>>
> >>> one such proposal, primarily aimed at MLPP, is called Multi-Level
> >>> Expedited Forwarding (MLEF) and can be found at:
> >>> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
> >>> tsvwg-mlefphb-03.txt
> >>>
> >>> I would also suggest reading a counter proposal that avoids
defining
> >>> a new DSCP:
> >>>
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
> >>> mlpp-that-works-02.txt
> >>> you can dig around the TSVWG archives over the past 2 months for
> >>> some
> >>> comments on the draft.
> >>>
> >>> -ken
> >>>
> >>>
> >>> _______________________________________________
> >>> Ieprep mailing list
> >>> Ieprep@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/ieprep
> >>>
> >>
> >>
> >> cheers,
> >> James
> >>
> >>                                  *******************
> >>                  Truth is not to be argued... it is to be
presented.
> >>
> >
> > _______________________________________________
> > 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 ieprep-bounces@ietf.org Sat Oct 29 21:03:15 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EW1bP-0006Tc-P0; Sat, 29 Oct 2005 21:03:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EW1bO-0006TP-9Q; Sat, 29 Oct 2005 21:03:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03843;
	Sat, 29 Oct 2005 21:02:55 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EW1pG-0004R9-TC; Sat, 29 Oct 2005 21:17:35 -0400
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com
	[135.1.23.83])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j9U12kot010236; 
	Sat, 29 Oct 2005 20:02:46 -0500 (CDT)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service
	(5.5.2657.72) id <VTLD5775>; Sat, 29 Oct 2005 20:02:45 -0500
Message-ID: <17D8724A2A8D9542B2B8AE546B9E5BBC0557ED0A@az4315exch001u.phx.lucent.com>
From: "GOLDMAN, STUART O (STUART)" <sgoldman@lucent.com>
To: Janet P Gunn <jgunn6@csc.com>, "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sat, 29 Oct 2005 20:02:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ieprep-bounces@ietf.org, ken carlberg <carlberg@g11.org.uk>,
	ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Folks,

What Janet say is of course exactly correct but only when SS7 is in fact used. If the call is routed to the PSAP via MF trunking this indicator is not present. 

James is correct about the typical use of a small number of trunks for the routing which makes sense if you think about the equally small number of call takers at the PSAP. Having significantly more trunks doesn't help with completion if the limiting factor is the human call takers.

So you are all right! 


Stu Goldman
Lucent Technologies
5531 E. Kelton LN
Scottsdale,AZ 85254
602 493 8438 home office
623-582-7136 voicemail  

-----Original Message-----
From: ieprep-bounces@ietf.org [mailto:ieprep-bounces@ietf.org] On Behalf Of Janet P Gunn
Sent: Monday, October 24, 2005 5:51 AM
To: James M. Polk
Cc: ieprep-bounces@ietf.org; ieprep@ietf.org; ken carlberg
Subject: RE: [Ieprep] Diffserv Code Point for Emergency calls





James,

The PSTN DOES give emergency (911) calls priority in a small way.

The SS7 signaling messages have an associated priority, called MTP.  When an SS7 "server" is congested, it will shed MTP 0 messages before it sheds MTP 1 messages.

Normal call request messages ( ISUP IAMs) are MTP 0.
Emergency (911), NS/EP. and MLPP call request messages are MTP 1.

Janet

ieprep-bounces@ietf.org wrote on 10/23/2005 11:42:34 PM:

> Reinaldo
>
> Actually, the PSTN does not give better priority to 911 calls (vs. 
> normal

> calls), they just use separate cirucuits once the 911 call gets to the 
> first Class-5 switch.  Typically, a Class-5 Switch will have a small
number
> of dedicated circuits that connect directly to a 911 Selective Router 
> (which is a special instance of a Class-5 switch). 911 calls are 
> routed over these dedicated circuits towards the SR to then be routed 
> to the appropriate PSAP. This isn't really anything special - since 
> the circuit world is not bandwidth contending, they are circuit contending.


_______________________________________________
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 ieprep-bounces@ietf.org Sun Oct 30 14:26:40 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWIpE-0007Tg-Rk; Sun, 30 Oct 2005 14:26:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EWIpB-0007SZ-LN
	for ieprep@megatron.ietf.org; Sun, 30 Oct 2005 14:26:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10494
	for <ieprep@ietf.org>; Sun, 30 Oct 2005 14:26:18 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EWDkH-00013Y-1A
	for ieprep@ietf.org; Sun, 30 Oct 2005 09:01:13 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-3.cisco.com with ESMTP; 30 Oct 2005 05:46:36 -0800
X-IronPort-AV: i="3.97,266,1125903600"; 
	d="scan'208"; a="358597206:sNHT27178188"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j9UDkYJh007378
	for <ieprep@ietf.org>; Sun, 30 Oct 2005 05:46:34 -0800 (PST)
Received: from [10.2.2.142] (sjc-vpn7-25.cisco.com [10.21.144.25])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j9UDOY41014942
	for <ieprep@ietf.org>; Sun, 30 Oct 2005 05:24:35 -0800
Mime-Version: 1.0 (Apple Message framework v734)
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667743@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667743@proton.jnpr.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <52DFF95F-3121-432D-9020-0AB3EF678052@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Sun, 30 Oct 2005 08:14:48 -0500
To: ieprep@ietf.org
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=2818; t=1130678675; x=1131110875;
	c=nowsp; s=nebraska;
	h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; 
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:A=20suggestion=20to=20the=20chairs|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Sun,=2030=20Oct=202005=2008=3A14=3A48=20-0500|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=n7cjNyq7mPcYtWx5EooCEpGxUUxfHSk99kjJPTyuk8L8VG08aPutyVy7jsdEo1Gw8jTf7+5/
	b9kCprxrrRuTAroGgoj6LE3WsipwcL+3UzPQumW8k+putRVCwrvHd+wDbvXZXirY1PB3WG0rhYX
	cn8psAdV22PpV5Gk0y8g8aNc=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( message from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [Ieprep] A suggestion to the chairs
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

The discussion that is being had right now under the thread "Diffserv  
Code Point for Emergency calls" has been had roughly a zillion times  
since the start of the working group. We have had discussions of  
MLEF, of a single DSCP, and a list of others things. Look in the  
archive; they are there.

CAC as defined in SIP/H.323/<proprietary> applies to the systems that  
participate in the SIP exchange, which would generally be the  
endpoint itself and its controlling proxy - the SIP proxy, the  
gatekeeper, the Cisco Call Manager, or whatever else one uses. It can  
accomplish certain things: if Alice calls Bob when Bob is on the  
phone with Carol, it can tell Bob that his wife is calling and give  
him the opportunity to take the call, and it can permit a pre- 
engineered network to do some fairly general things in terms of call  
counting. Step away from those fixed networks, or run that as an  
enterprise service running over an arbitrary collection of  
intermediate ISPs that don't participate in the service, and life  
becomes far more interesting. For example, Monday evening at the IETF  
there will be an ad hoc BOF discussing the GIG, which has two major  
components in the core - a fixed fiber optic network of arbitrarily  
high speed and a satellite network characterized by single-digit- 
megabit up/down links that have potentially large networks behind  
them. And we could discuss FCS etc, where we are talking about manet  
networks that constantly shift. Say "city of linked hot spots" and  
the various other kinds of networks we are building these days...

BTW, what we are discussing right now is only voice on IP. We already  
have significant use of video on IP, and the subject matter also  
covers requirements for email and a variety of other applications.

We need to stop traveling in circles in the ieprep discussion. Life  
is boring when you pass the same place over and over again without  
reaching the destination.

The objective here, so I'm told, is to enable people like DoD, NATO,  
NCS, and the counterparts of NCS in 193+ countries to build a network  
in which a first responder or an official with certain credentials  
can go anywhere, jack in his laptop-or-whatever (or, in the dreams of  
some, commandeer a laptop-or-whatever), and use it under a policy  
that authorizes him to have acceptable service when nobody else is  
getting acceptable service. There are definitions of "acceptable  
service", and those of us that are working with military and civilian  
networks to build this - those of us for whom this is not an armchair  
exercise - are being held to those definitions rigorously. To do  
that, we need to provide tools for the likes of Verizon and BT to be  
able to deploy and manage those networks, and they need to work in  
the specialized environments that DoD and NATO build.

Would those who advocate simply assigning a DSCP and being done with  
the discussion please explain to us how to build a service network  
that delivers a special service to an authorized user, one that a  
network operator can deploy and use, bill for the service, track and  
minimize fraudulent use, deliver a priority email in 7 minutes as  
specified, deliver both voice and video on IP with "acceptable"  
service as "acceptable" is defined, and so on, without authorization/ 
authentication and using only the very limited CAC designed for a  
fixed-and-specifically-tuned network? Could we get an RFC that  
describes that?

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



From ieprep-bounces@ietf.org Sun Oct 30 14:28:26 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWIqv-000063-Tk; Sun, 30 Oct 2005 14:28:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EWIqt-00004w-IK
	for ieprep@megatron.ietf.org; Sun, 30 Oct 2005 14:28:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11682
	for <ieprep@ietf.org>; Sun, 30 Oct 2005 14:28:00 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EWCfg-0002Ur-PU
	for ieprep@ietf.org; Sun, 30 Oct 2005 07:52:25 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-3.cisco.com with ESMTP; 30 Oct 2005 04:37:49 -0800
X-IronPort-AV: i="3.97,266,1125903600"; 
	d="scan'208"; a="358588890:sNHT33216772"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j9UCbZJh022797;
	Sun, 30 Oct 2005 04:37:46 -0800 (PST)
Received: from [10.2.2.142] (sjc-vpn7-25.cisco.com [10.21.144.25])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j9UClJ2X014876;
	Sun, 30 Oct 2005 04:47:19 -0800
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C2801667743@proton.jnpr.net>
References: <9BD5D7887235424FA97DFC223CAE3C2801667743@proton.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5E7EB875-098D-424A-8287-C7305A482818@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
Date: Sun, 30 Oct 2005 07:37:33 -0500
To: Reinaldo Penno <rpenno@juniper.net>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=6537; t=1130676440; x=1131108640;
	c=nowsp; s=nebraska;
	h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; 
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20[Ieprep]=20Diffserv=20Code=20Point=20for=20Emergency=20calls|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Sun,=2030=20Oct=202005=2007=3A37=3A33=20-0500|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=Kx2v2r2y8Cch1MjvBmjKydTFh+DuMB+vVko7cNzM7J4srdJgChmFI6fVK39+7ftidLYjMJPV
	dr4BGvOIEILHSpxdJTyZIT+7OlyMdsqGfMvIziBIDZcahZ5LyrvfTQcoz8UxcO1PZm64zzv/zeX
	zAAHb0UizmqdrthfqJ6S14Fw=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( message from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Content-Transfer-Encoding: 7bit
Cc: "James M. Polk" <jmpolk@cisco.com>, ken carlberg <carlberg@g11.org.uk>,
	ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org


On Oct 27, 2005, at 11:29 PM, Reinaldo Penno wrote:

> Hello,
>
> I read draft draft-ietf-tsvwg-mlpp-that-works-02, which I assume it is
> your proposal.
>
> Some questions:
>
> 1. The example is the end if quite complex. I would like to start  
> with a
> bare bores one. Which priority you suggest for everyday 911 calls as
> opposed to normal telephone calls?

mlpp-that-works is not a 911 solution; 911 is about providing a  
service in which an arbitrary user goes to a special peer. MLPP (and  
GETS) are about a special user going to a peer of its choosing and  
getting priority service - and about the peer getting priority  
service while communicating with the MLPP-special user.

> I believe the priorities are below
>
>   The DSN has 5 precedence levels of IEPS in descending order:
>
>         dsn.flash-override
>         dsn.flash
>         dsn.immediate
>         dsn.priority
>         dsn.routine

that is true in the DSN for MLPP service. There are other networks,  
such as GETS which uses the same names but has two levels, the DRSN  
which has six levels, and ADNS which has seven. GSM allows for 15.

> 2. It seems to me your proposal and an emergency DSCP are  
> complementary
> and not mutually exclusive. If signal with RSVP and if you get
> bandwidth, you mark packets with the emergency DSCP.

why?

In the circuit switch network, MLPP/GETS is about getting a circuit.  
There is nothing special about the circuit - it is the same as any  
other circuit. The question is whether you get one or someone else  
does, and MLPP/GETS makes it so that you get one. Ditto ATM - what is  
the marking in the ATM cell for a VC assigned in a priority manner?  
In the PSTN and the ATM networks, this is all in call control. Having  
done it in call control, there is no need to do anything in the data  
plane. Why should IP be different?

And note the security issue with putting it in the data plane. If you  
build a superhighway for script kiddies, they will come. You will  
still have to authenticate and authorize the use of the special DSCP.  
So the DSCP doesn't do away with the need for call signaling seen by  
the network.

You can gratuitously dump mechanisms in to your heart's content. But  
if you don't need them, why? Note RFC 1958 and 3439's comments on  
simplicity and elegance of design. Note RFC 2804's assertion that the  
the random complexity of traditional LI solutions being the best  
reason to not deploy them. I'd really like an answer.

> 3. Not trying to simplify things but premise of this proposal is that
> all IP phones will support RSVP, right?

no. Only the ones you want to provide an emergency service to. But it  
would be simpler and more reliable if they all did.

There are two ways to manage the service at the data layer. You are  
going to have to have an ACL that ensures that only authorized users  
get to use the magic DSCP, or if you simply use EF you will need an  
ACL that ensures that losses, if they come, come from unauthorized  
users.

> 4. Should the phones use RSVP just for emergency calls or for all  
> calls
> in general? I guess they should otherwise the other devices would  
> loose
> track of how much bandwidth has been consumed?

see above.

> Thanks,
>
> Reinaldo
>
>
>
>
>> -----Original Message-----
>> From: Fred Baker [mailto:fred@cisco.com]
>> Sent: Wednesday, October 26, 2005 11:59 AM
>> To: Reinaldo Penno
>> Cc: James M. Polk; ieprep@ietf.org; ken carlberg
>> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>>
>>  From my perspective, the question in the data plane is not whether
>> the packet is part of an emergency session, but whether it is
>> authorized to use the bandwidth. Emergency authorization is a control
>> plane problem.
>>
>> That is why I have suggested authorization of users to use the EF
>> code point during CAC.
>>
>> On Oct 22, 2005, at 8:45 AM, Reinaldo Penno wrote:
>>
>>
>>> Your point is well taken James.
>>>
>>> I guess the risk is no different from what we face nowadays with
>>>
> doom
>
>>> packets marked with EF DSCP. The solution as well is no different
>>>
> from
>
>>> what we have today to deal with those packets. Usually
>>> independently of
>>> the DSCP an endpoint might put in a packet, the edge router perform
>>> classification and if necessary remarks the packet with whatever
>>> DSCP it
>>> should have.
>>>
>>> Therefore, if we just continue with just EF for normal and emergency
>>> voice calls, the risk is the same, the drawback that I see is that
>>>
> we
>
>>> cannot prioritize emergency over normal calls.
>>>
>>> So, in general an edge device that can perform SIP parsing and mark
>>> emergency calls with the emergency DSCP and others with EF DSCP.
>>> Alternatively, in a decomposed gateway scenario the SIP Proxy can
>>>
> let
>
>>> the router know that a certain call is an emergency and that it
>>>
> should
>
>>> be marked differently.
>>>
>>> Regards,
>>>
>>> Reinaldo
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: James M. Polk [mailto:jmpolk@cisco.com]
>>>> Sent: Friday, October 21, 2005 11:02 PM
>>>> To: Reinaldo Penno
>>>> Cc: ken carlberg; ieprep@ietf.org
>>>> Subject: Re: [Ieprep] Diffserv Code Point for Emergency calls
>>>>
>>>> Reinaldo
>>>>
>>>> Adding fuel to a discussion that has churned on many lists over the
>>>>
>>>>
>>> last
>>>
>>>
>>>> several years, I'd really want to understand the threat anaylsis
>>>>
>>>>
>>> observed
>>>
>>>
>>>> by such a proposal (for a emergency DSCP) to ensure it could not be
>>>>
>>>>
>>> used
>>>
>>>
>>>> for a fairly trivial to generate DDOS on the network - even all the
>>>>
>>>>
>>> way to
>>>
>>>
>>>> the PSAP, or just used by neighbors wanting the very best
>>>>
> throughput
>
>>>>
>>>>
>>> for
>>>
>>>
>>>> their game of Doom.
>>>>
>>>> At 10:57 AM 10/21/2005 -0400, ken carlberg wrote:
>>>>
>>>>
>>>>> Hello Reinaldo,
>>>>>
>>>>>
>>>>>
>>>>>> I read
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>> http://www.ietf.org/internet-drafts/draft-ietf-ieprep-
>>>>> framework-10.txt
>>>>>
>>>>>
>>>>>> and was somewhat puzzled at section 4.1.2. I understand that the
>>>>>>
>>>>>>
>>> IETF
>>>
>>>
>>>>>> wants to be conservative in standardizing new DSCP, but it seems
>>>>>>
> to
>
>>>>>>
>>>>>>
>>> an
>>>
>>>
>>>>>> emergency call DSCP would be accepted by the community (am I
>>>>>>
>>>>>>
>>> wrong?).
>>>
>>>
>>>>>
>>>>> well, from my own take, I would say that the "community" is not
>>>>> against an emergency call DSCP per se, but rather awaits specific
>>>>> proposals with a cautious mindset.  Recall from that section 4.1.2
>>>>> that there is a need to define a behavior in addition to
>>>>>
> identifying
>
>>>>> a code point.  So if you want a code point of 1 or more bits for
>>>>> "emergency", what would be its defined forwarding behavior?
>>>>>
>>>>> one such proposal, primarily aimed at MLPP, is called Multi-Level
>>>>> Expedited Forwarding (MLEF) and can be found at:
>>>>> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-silverman-
>>>>> tsvwg-mlefphb-03.txt
>>>>>
>>>>> I would also suggest reading a counter proposal that avoids
>>>>>
> defining
>
>>>>> a new DSCP:
>>>>>
>>>>>
> ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-
>
>>>>> mlpp-that-works-02.txt
>>>>> you can dig around the TSVWG archives over the past 2 months for
>>>>> some
>>>>> comments on the draft.
>>>>>
>>>>> -ken
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Ieprep mailing list
>>>>> Ieprep@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/ieprep
>>>>>
>>>>>
>>>>
>>>>
>>>> cheers,
>>>> James
>>>>
>>>>                                  *******************
>>>>                  Truth is not to be argued... it is to be
>>>>
> presented.
>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Ieprep mailing list
>>> Ieprep@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/ieprep
>>>
>

--------------------------------------------------------------
"Don't worry about the world coming to an end today. It's already  
tomorrow in Australia." (Charles Schulz )


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



From ieprep-bounces@ietf.org Mon Oct 31 09:36:47 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWamF-0004Hj-Br; Mon, 31 Oct 2005 09:36:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EWamD-0004Hb-5l
	for ieprep@megatron.ietf.org; Mon, 31 Oct 2005 09:36:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11346
	for <ieprep@ietf.org>; Mon, 31 Oct 2005 09:36:25 -0500 (EST)
Received: from mclmx.mail.saic.com ([149.8.64.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWb0O-0001SY-F3
	for ieprep@ietf.org; Mon, 31 Oct 2005 09:51:25 -0500
Received: from 0015-its-ieg01.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx.mail.saic.com; Mon, 31 Oct 2005 09:36:27 -0500
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
	by 0015-its-ieg01.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2005103109362613815 ; Mon, 31 Oct 2005 09:36:26 -0500
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <TVVJHTV7>; Mon, 31 Oct 2005 09:36:25 -0500
Message-Id: <4797F6E414C24D4A96AAC14B320BCAD7A3278B@0015-its-exmb02.us.saic.com>
From: "King, Kimberly  S." <KIMBERLY.S.KING@saic.com>
To: Fred Baker <fred@cisco.com>, ieprep@ietf.org
Subject: RE: [Ieprep] A suggestion to the chairs
Date: Mon, 31 Oct 2005 09:36:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

Fred,

I agree that it is d=E9j=E0 vu.

And it stems from the same issue.  The concrete problem statement,
requirements and network context is not defined thus people argue ad =
nauseum
about vague notions of what constitutes an emergency connection, the
environment in which it is deployed, miscellaneous mechanisms in =
isolation,
etc.

Requirements should come before solutions especially when there is =
little
agreement about the concrete problem to be solved.  I understand at =
least
one potential requirements document is in process.  Things are =
currently too
vague and vast to make progress.

Kimberly



-----Original Message-----
From: ieprep-bounces@ietf.org [mailto:ieprep-bounces@ietf.org] On =
Behalf Of
Fred Baker
Sent: Sunday, October 30, 2005 8:15 AM
To: ieprep@ietf.org
Subject: [Ieprep] A suggestion to the chairs

The discussion that is being had right now under the thread "Diffserv =20
Code Point for Emergency calls" has been had roughly a zillion times =20
since the start of the working group. We have had discussions of =20
MLEF, of a single DSCP, and a list of others things. Look in the =20
archive; they are there.

CAC as defined in SIP/H.323/<proprietary> applies to the systems that =20
participate in the SIP exchange, which would generally be the =20
endpoint itself and its controlling proxy - the SIP proxy, the =20
gatekeeper, the Cisco Call Manager, or whatever else one uses. It can =20
accomplish certain things: if Alice calls Bob when Bob is on the =20
phone with Carol, it can tell Bob that his wife is calling and give =20
him the opportunity to take the call, and it can permit a pre-=20
engineered network to do some fairly general things in terms of call =20
counting. Step away from those fixed networks, or run that as an =20
enterprise service running over an arbitrary collection of =20
intermediate ISPs that don't participate in the service, and life =20
becomes far more interesting. For example, Monday evening at the IETF =20
there will be an ad hoc BOF discussing the GIG, which has two major =20
components in the core - a fixed fiber optic network of arbitrarily =20
high speed and a satellite network characterized by single-digit-=20
megabit up/down links that have potentially large networks behind =20
them. And we could discuss FCS etc, where we are talking about manet =20
networks that constantly shift. Say "city of linked hot spots" and =20
the various other kinds of networks we are building these days...

BTW, what we are discussing right now is only voice on IP. We already =20
have significant use of video on IP, and the subject matter also =20
covers requirements for email and a variety of other applications.

We need to stop traveling in circles in the ieprep discussion. Life =20
is boring when you pass the same place over and over again without =20
reaching the destination.

The objective here, so I'm told, is to enable people like DoD, NATO, =20
NCS, and the counterparts of NCS in 193+ countries to build a network =20
in which a first responder or an official with certain credentials =20
can go anywhere, jack in his laptop-or-whatever (or, in the dreams of =20
some, commandeer a laptop-or-whatever), and use it under a policy =20
that authorizes him to have acceptable service when nobody else is =20
getting acceptable service. There are definitions of "acceptable =20
service", and those of us that are working with military and civilian =20
networks to build this - those of us for whom this is not an armchair =20
exercise - are being held to those definitions rigorously. To do =20
that, we need to provide tools for the likes of Verizon and BT to be =20
able to deploy and manage those networks, and they need to work in =20
the specialized environments that DoD and NATO build.

Would those who advocate simply assigning a DSCP and being done with =20
the discussion please explain to us how to build a service network =20
that delivers a special service to an authorized user, one that a =20
network operator can deploy and use, bill for the service, track and =20
minimize fraudulent use, deliver a priority email in 7 minutes as =20
specified, deliver both voice and video on IP with "acceptable" =20
service as "acceptable" is defined, and so on, without authorization/=20
authentication and using only the very limited CAC designed for a =20
fixed-and-specifically-tuned network? Could we get an RFC that =20
describes that?

_______________________________________________
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 ieprep-bounces@ietf.org Mon Oct 31 16:23:04 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWh4B-0004dy-2O; Mon, 31 Oct 2005 16:19:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWh43-0004d5-U5; Mon, 31 Oct 2005 16:19:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10628;
	Mon, 31 Oct 2005 16:19:16 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EWhIK-0005uD-1E; Mon, 31 Oct 2005 16:34:20 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1EWh43-0004cO-Ae; Mon, 31 Oct 2005 16:19:35 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1EWh43-0004cO-Ae@newodin.ietf.org>
Date: Mon, 31 Oct 2005 16:19:35 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ieprep chair <kimberly.s.king@saic.com>,
	Internet Architecture Board <iab@iab.org>, ieprep chair <sob@harvard.edu>,
	ieprep mailing list <ieprep@ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Ieprep] Document Action: 'Emergency Telecommunications Services
 (ETS) 
 Requirements for a Single Administrative Domain' to Informational RFC 
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>,
	<mailto:ieprep-request@ietf.org?subject=subscribe>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

The IESG has approved the following document:

- 'Emergency Telecommunications Services (ETS) Requirements for a Single 
   Administrative Domain '
   <draft-ietf-ieprep-domain-req-05.txt> as an Informational RFC

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

The IESG contact persons are Jon Peterson and Allison Mankin.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ieprep-domain-req-05.txt

Technical Summary

This document presents a list of requirements in support of Emergency
Telecommunications Service (ETS) within a single administrative domain.

Working Group Summary
 
The IEPREP Working Group supported the advancement of this document.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.

Note to RFC Editor
 
Please change the Abstract as follows:

OLD:

   This document presents a list of requirements in support of Emergency
   Telecommunications Service (ETS) within a single administrative
   domain. This document is an extension of the General Requirements of
   [rfc3689] and focuses on a more specific set of administrative
   constraints and scope.  Solutions to these requirements are not
   presented in this document.

NEW:

   This document presents a list of requirements in support of Emergency
   Telecommunications Service (ETS) within a single administrative
   domain. This document focuses on a specific set of administrative
   constraints and scope.  Solutions to these requirements are not
   presented in this document.


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



