RE: How to handle Validation failures was RE: [Sipping-emergency]proposed charter, new wg on emergency
"James M. Polk" <jmpolk@cisco.com> Wed, 29 September 2004 00:42 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09770 for <sipping-emergency-web-archive@ietf.org>; Tue, 28 Sep 2004 20:42:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCSgO-0007yv-2l for sipping-emergency-web-archive@ietf.org; Tue, 28 Sep 2004 20:51:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCSPB-000808-PQ; Tue, 28 Sep 2004 20:33:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCS5L-0002nE-Si for sipping-emergency@megatron.ietf.org; Tue, 28 Sep 2004 20:12:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07797 for <sipping-emergency@ietf.org>; Tue, 28 Sep 2004 20:12:42 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCSDG-0007Nv-GV for sipping-emergency@ietf.org; Tue, 28 Sep 2004 20:20:55 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 28 Sep 2004 17:18:31 -0700
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8T0C6lr021240; Tue, 28 Sep 2004 17:12:07 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id RAA27261; Tue, 28 Sep 2004 17:12:07 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040928191103.0380c008@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 28 Sep 2004 19:12:08 -0500
To: wilcox@e911.psd.state.vt.us, Henning Schulzrinne <hgs@cs.columbia.edu>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: How to handle Validation failures was RE: [Sipping-emergency]proposed charter, new wg on emergency
In-Reply-To: <B4D8D0C58294F54DA9DB6C6A9AEF38502A9721@artemis.vt911.local >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 1.1 (+)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: sipping-emergency@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: sipping-emergency.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Sender: sipping-emergency-bounces@ietf.org
Errors-To: sipping-emergency-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
At 09:06 AM 9/28/2004 -0400, wilcox@e911.psd.state.vt.us wrote: >I agree with non-interfering testing end to end. > >Ultimately, routing of a call does not stop at an ECC. For all practical >purposes it also derives a means for determining the correct response, >which is part of the message relay (incorporating emergency responders in >the chain). Validation of location information also ensures that the >correct response recommendation is assigned. Take for example two >locations that reside side-by-side, one is a residence and the other is a >nuclear power plant. What if the residential caller is calling about the power plant that is on fire? ;-) >For the residence, a standard response for fire apparatus is fine however, >for the nuclear power plant an entirely different response scenario may be >necessary (perhaps the fire department located at the facility itself). If >the call is routed to the ECC responsible for that location without >validation of that location information (and ultimately validation of >responder information), there will be no indication that a different >response is necessary and correct routing of the call has not been >accomplished. Currently, this is accomplished in the US 9-1-1 system by >assigning a special zone (ESZ) to that location and assigning an indicator >(ESN) to that location that derives the correct police, fire and EMS response. > > > >To give you a real world example: Ford Motor Company just selected to >replace all of their traditional phone systems with VoIP service (50,000+ >end devices). You can bet that in some of the larger plants, they have >their own responders for Police, Fire and EMS services. > > > >Nate > >-----Original Message----- >From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] >Sent: Tue 9/28/2004 8:29 AM >To: wilcox@e911.psd.state.vt.us >Cc: Peterson, Jon; sipping-emergency@ietf.org >Subject: Re: How to handle Validation failures was RE: >[Sipping-emergency]proposed charter, new wg on emergency > > > > This can be seen as a special case of testing. Thus, if you > assume that > there is a test mode that attempts to reach the PSAP, but does not > actually ring, you'd have tested the full routing chain, including > whether the civic address is indeed mappable. > > A separate question is whether a separate address-only validation > mode > is appropriate. This probably depends on the overall architecture. As > we've discussed before, I think there is general agreement that you'd > want the ability for end-to-end non-interfering testing in any event. > > wilcox@e911.psd.state.vt.us wrote: > > Validating location information is implicit for routing. Otherwise, > > all calls would be treated as "default" routed or worse, would rely > > on other mechanisms to provide routing instructions outside the > > control of the ECC (the ECC currently provides instructions and > input > > on the construct of the MSAG to the extent possible, which is used > > for the validation process). Unvalidated location information could > > reduce or even prevent a timely emergency response to a particular > > location. As I implied before, the lack of validation should not > > prevent delivery of a call to a geographically appropriate ECC > > however, all efforts need to be made to ensure that end devices > > utilize validated location information. So, if the charter of this > > effort is to decide on how routing is accomplished than > validation of > > the information used to make that routing decision should be > > considered in the process as well. > > > > Nate > > > >_______________________________________________ >Sipping-emergency mailing list >Sipping-emergency@ietf.org >https://www1.ietf.org/mailman/listinfo/sipping-emergency cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency
- RE: How to handle Validation failures was RE: [Si… wilcox
- Re: How to handle Validation failures was RE: [Si… Henning Schulzrinne
- RE: How to handle Validation failures was RE: [Si… wilcox
- RE: How to handle Validation failures was RE: [Si… James M. Polk
- Re: How to handle Validation failures was RE: [Si… James M. Polk
- RE: How to handle Validation failures was RE: [Si… James M. Polk