Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination
"Brian Rosen" <br@brianrosen.net> Mon, 06 October 2008 21: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 4AACC3A69F2; Mon, 6 Oct 2008 14:20:45 -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 39CD83A676A for <ecrit@core3.amsl.com>; Mon, 6 Oct 2008 14:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 YOtwoisBDFY8 for <ecrit@core3.amsl.com>; Mon, 6 Oct 2008 14:20:43 -0700 (PDT)
Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130]) by core3.amsl.com (Postfix) with ESMTP id 3E1E83A69F2 for <ecrit@ietf.org>; Mon, 6 Oct 2008 14:20:43 -0700 (PDT)
Received: from neustargw.va.neustar.com ([209.173.53.233] helo=BROSVMxp) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from <br@brianrosen.net>) id 1KmxVv-00078U-En; Mon, 06 Oct 2008 16:21:11 -0500
From: Brian Rosen <br@brianrosen.net>
To: "'James M. Polk'" <jmpolk@cisco.com>, 'Henning Schulzrinne' <hgs@cs.columbia.edu>, 'Hannes Tschofenig' <Hannes.Tschofenig@gmx.net>
References: <48EA3476.6000806@gmx.net> <A3DFA850-D495-4045-9CA0-3A0F4888A4D5@cs.columbia.edu> <02eb01c927e8$18468320$48d38960$@net> <XFE-SJC-212scE8Npqh00000452@xfe-sjc-212.amer.cisco.com>
In-Reply-To: <XFE-SJC-212scE8Npqh00000452@xfe-sjc-212.amer.cisco.com>
Date: Mon, 06 Oct 2008 17:21:20 -0400
Message-ID: <034401c927f9$7c1041f0$7430c5d0$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ackn7mBpsNy08kg3Qwq91ApWs0OP0QACul+g
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Source:
X-Source-Args:
X-Source-Dir:
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
No, actually, it's pretty precise. It's "premature" unless the PSAP says otherwise (that is, if the caller attempts to disconnect before the PSAP does, then it's a premature disconnect). Brian -----Original Message----- From: James M. Polk [mailto:jmpolk@cisco.com] Sent: Monday, October 06, 2008 4:01 PM To: Brian Rosen; 'Henning Schulzrinne'; 'Hannes Tschofenig' Cc: 'ECRIT' Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination This sounds a bit like a subjective thing, verses a quantifiable definitive thing. How exactly does a UAC know when it has achieved this status (i.e., provided enough information)? I assume the goal is to have something in signaling that communicates this to the UAC, right? Or is this merely at the discretion of the called party (i.e., the call taker's personal satisfaction)? Where I'm going with this is that I'm beginning to wonder if, then how a signaling protocol document should address this, or should this not be dealt with in signaling (which is nearly 100% of what we are defining -- only!) IMO... James At 02:16 PM 10/6/2008, Brian Rosen wrote: >It was defined in draft-rosen-ecrit-abpd-reqs-00. It was: >when on an emergency call, a caller hangs up the call before the call taker >is finished acquiring enough information. > >Brian > >-----Original Message----- >From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of >Henning Schulzrinne >Sent: Monday, October 06, 2008 2:27 PM >To: Hannes Tschofenig >Cc: 'ECRIT' >Subject: Re: [Ecrit] IETF ECRIT Design Team on Premature Call Termination > >I agree with Ted's concerns. In particular, "premature call >termination" has never been defined precisely and many of the fears >are based on the old single-line physical phone model which just don't >apply here. Carrying forward notions that apply to black phones with >rotary dials just seems unhelpful. In particular, the topic is >strongly connected to call-back and should not be treated in isolation. > >Henning > >On Oct 6, 2008, at 11:53 AM, Hannes Tschofenig wrote: > > > Hi all, > > > > we had a chat with Jon on how to make some progress on the subject > > of "Premature Call Termination" and here is the plan we came up with: > > > > * We delete the sentence that talks about the UAC not generating a > > BYE request in > > http://www.ietf.org/internet-drafts/draft-ietf-ecrit-phonebcp-05.txt > > We progress the document through the IETF process as "planned". > > > > * At the same time we create a design team in ECRIT to work on > > "Premature Call Termination". > > > > Depending on the progress of the design team we are able to > > incorporate the results of it into the document (even at a fairly > > late stage > > of the document process). If the design team does not produce > > results then anything that comes out of it can be seen as an > > extension to the > > Phone BCP document. > > > > We need members for the design team! We have already received the > > commitment of folks from NENA but we also need some guys from the > > ECRIT group. Who is interested in participating? > > > > Ciao > > Hannes & 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 > >_______________________________________________ >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
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Henning Schulzrinne
- [Ecrit] IETF ECRIT Design Team on Premature Call … Hannes Tschofenig
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Henning Schulzrinne
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… James M. Polk
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… DRAGE, Keith (Keith)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… DRAGE, Keith (Keith)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… James M. Polk
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Marc Linsner
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… James M. Polk
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Marc Linsner
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… DRAGE, Keith (Keith)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… DRAGE, Keith (Keith)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Ted Hardie
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Marc Linsner
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Henning Schulzrinne
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Marc Linsner
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Randall Gellens
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Randall Gellens
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Brian Rosen
- Re: [Ecrit] IETF ECRIT Design Team on Premature C… Henning Schulzrinne