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

"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com> Wed, 08 October 2008 15:25 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 253863A6BD0; Wed, 8 Oct 2008 08:25:52 -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 33F313A6B30 for <ecrit@core3.amsl.com>; Wed, 8 Oct 2008 08:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599]
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 OSRl1VrPeh96 for <ecrit@core3.amsl.com>; Wed, 8 Oct 2008 08:25:50 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 3C8D53A67DF for <ecrit@ietf.org>; Wed, 8 Oct 2008 08:25:49 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m98FPD25019223; Wed, 8 Oct 2008 10:25:13 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Oct 2008 10:25:13 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Oct 2008 17:25:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 08 Oct 2008 17:25:13 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180023B06A7@DEEXC1U01.de.lucent.com>
In-Reply-To: <068a01c92944$7a72d230$6f587690$@net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
Thread-Index: AckooC/i8oVjuBu8S0uFXP7ygv670wABB+lAAAfRXW4AH/rlAAAFmpzQ
References: <04e701c928a4$d9277880$8b766980$@net><C5114CA4.CD1A%mlinsner@cisco.com> <068a01c92944$7a72d230$6f587690$@net>
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Brian Rosen <br@brianrosen.net>, Marc Linsner <mlinsner@cisco.com>
X-OriginalArrivalTime: 08 Oct 2008 15:25:09.0999 (UTC) FILETIME=[0D1427F0:01C9295A]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
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

So now we seem to be indulging in the discussion of whether we should
honour the requirements.

There are still open issues on the requirements that have been raised.
Until we have got the requirements right, we cannot decide that we
should work on implementing them or not.

Regards

Keith 

> -----Original Message-----
> From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] 
> On Behalf Of Brian Rosen
> Sent: Wednesday, October 08, 2008 1:51 PM
> To: 'Marc Linsner'
> Cc: 'ECRIT'
> Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call 
> Termination
> 
> 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
> 
_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit