Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination

Marc Linsner <mlinsner@cisco.com> Wed, 08 October 2008 13:20 UTC

Return-Path: <ecrit-bounces@ietf.org>
X-Original-To: ecrit-archive@megatron.ietf.org
Delivered-To: ietfarch-ecrit-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B32A53A6892; Wed, 8 Oct 2008 06:20:42 -0700 (PDT)
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8C253A6892 for <ecrit@core3.amsl.com>; Wed, 8 Oct 2008 06:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4SsKXgOLY39 for <ecrit@core3.amsl.com>; Wed, 8 Oct 2008 06:20:40 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 941E93A6803 for <ecrit@ietf.org>; Wed, 8 Oct 2008 06:20:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,378,1220227200"; d="scan'208";a="23626752"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 08 Oct 2008 13:20:23 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m98DKMqG002880; Wed, 8 Oct 2008 09:20:23 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m98DKLUP003392; Wed, 8 Oct 2008 13:20:22 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Oct 2008 09:19:10 -0400
Received: from [10.116.195.115] ([10.116.195.115]) by xmb-rtp-205.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Oct 2008 09:19:09 -0400
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Wed, 08 Oct 2008 09:19:07 -0400
From: Marc Linsner <mlinsner@cisco.com>
To: Brian Rosen <br@brianrosen.net>
Message-ID: <C5122B8B.CD64%mlinsner@cisco.com>
Thread-Topic: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
Thread-Index: AckooC/i8oVjuBu8S0uFXP7ygv670wABB+lAAAfRXW4AH/rlAAABPCgY
In-Reply-To: <068a01c92944$7a72d230$6f587690$@net>
Mime-version: 1.0
X-OriginalArrivalTime: 08 Oct 2008 13:19:09.0389 (UTC) FILETIME=[729A9FD0:01C92948]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2867; t=1223472023; x=1224336023; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mlinsner@cisco.com; z=From:=20Marc=20Linsner=20<mlinsner@cisco.com> |Subject:=20Re=3A=20[Ecrit]=20IETF=20ECRIT=20Design=20Team= 20on=20Premature=20Call=20=20=20Termination |Sender:=20 |To:=20Brian=20Rosen=20<br@brianrosen.net>; bh=JYc0TeBpHl4rGoeEV2AB7Q66UWrifeuVYVO4jEDZfXw=; b=ekxPLhHGPXJ5bJAwL8ba45QcUuT7LtfgAkoGdGv2CzjCc1piURI7nAF2yQ snp2FLpmJ44D50i398cc4SEJJKTwP2xEkV7GledOoFEgi5Be5dnhlqs904a2 6GyZNPRTTe;
Authentication-Results: rtp-dkim-1; header.From=mlinsner@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: 'ECRIT' <ecrit@ietf.org>
Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ecrit-bounces@ietf.org
Errors-To: ecrit-bounces@ietf.org

Brian,

I have no problem entertaining new requirements.  I simply want the
motivation ("We have to do this because") to be spun correctly.

I also believe this demands a viewpoint from the 'other' party, the PSAP
customer, Joe Citizen.

If in fact a solution can to designed that fulfills the requirement and
protects Joe's desires, I have no problem.

-Marc- 


On 10/8/08 8:50 AM, "Brian Rosen" <br@brianrosen.net> wrote:

> So, what, because wireless carriers refused to implement it, despite
> repeated requests to do so, and wireless is now more popular, we should
> strike the requirement?
> 
> PSAPs I talk to consider this a requirement.  They are VERY unhappy the
> carriers do not honor the requirement, in both wireline and wireless, in the
> U.S.  Canada is very unhappy about the wireless situation.  Both are adamant
> that they have a REQUIREMENT for this capability.
> 
> As with any other protocol issue, there are no protocol police.  We can
> define the mechanism, but implementation may or may not occur.  The PSAPs
> have a requirement.  It comes from experience.  We should honor it I think.
> 
> Brian
> 
> -----Original Message-----
> From: Marc Linsner [mailto:mlinsner@cisco.com]
> Sent: Tuesday, October 07, 2008 5:28 PM
> To: Brian Rosen
> Cc: 'ECRIT'
> Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
> 
> Brian,
> 
> On 10/7/08 1:48 PM, "Brian Rosen" <br@brianrosen.net> wrote:
> 
>> It is in use in some jurisdictions now.  Canada is an example.  It was
>> deployed in the U.S., it got lost, and they mostly want it back.  It is
> not
>> deployed in some areas.  The requirements state that if it's not needed,
> it
>> doesn't stop termination, which implies some feature signaling with the
>> appropriate defaults.
> 
> Remember, in the jurisdictions where this is currently deployed, it works
> for only 35% of 9-1-1 calls (as 65% are from cellular).
> 
>> 
>> In jurisdictions that have it deployed, I am not aware of the kind of
>> problems you were imagining.  The current implementations put the call
> taker
>> in charge of signaling alerts.
>> 
>> Brian
>> 
>> -----Original Message-----
>> From: Ted Hardie [mailto:hardie@qualcomm.com]
>> Sent: Tuesday, October 07, 2008 1:15 PM
>> To: Brian Rosen; 'James M. Polk'; 'Henning Schulzrinne'; 'Hannes
> Tschofenig'
>> Cc: 'ECRIT'
>> Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
>> 
>> At 7:15 AM -0700 10/7/08, Brian Rosen wrote:
>>> It's manual, not automatic.
>>> 
>>> When the PSAP call taker decides the call is over, then call termination
>>> occurs.  They release the call (with a button).  In the proposed
>> mechanisms,
>>> the caller cannot terminate until then.
> 
> What document contains the proposed mechanisms?
> 
> -Marc-
> 
> 


_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit