[Sip] Comment on willis-sip-answeralert-00

Kelley Sean-Q12059 <seankelley@motorola.com> Mon, 01 August 2005 16:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzd3J-0005jv-N9; Mon, 01 Aug 2005 12:22:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzd3H-0005ji-2F for sip@megatron.ietf.org; Mon, 01 Aug 2005 12:22:07 -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 MAA21757 for <sip@ietf.org>; Mon, 1 Aug 2005 12:22:04 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzdZZ-0000j0-15 for sip@ietf.org; Mon, 01 Aug 2005 12:55:30 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j71GVedX005661 for <sip@ietf.org>; Mon, 1 Aug 2005 09:31:40 -0700 (MST)
Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j71GRHmm001091 for <sip@ietf.org>; Mon, 1 Aug 2005 11:27:18 -0500 (CDT)
Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.72) id <N41ZKMDR>; Mon, 1 Aug 2005 11:21:59 -0500
Message-ID: <8E4E38BF6D087F4488E80ABAACA2F3F414AE4738@il27exm02.cig.mot.com>
From: Kelley Sean-Q12059 <seankelley@motorola.com>
To: sip@ietf.org
Date: Mon, 01 Aug 2005 11:21:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Subject: [Sip] Comment on willis-sip-answeralert-00
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0492935774=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Regarding the UAS procedures for handling the Answer-Mode value of "ManualReq", the draft indicates that the UAS SHOULD answer in manual mode, and the UAS SHOULD reject the request if it is unwilling or incapable of answering in manual mode.
 
However, there is a use case for Push to Talk (as it is being specified in OMA) that might justify changing these SHOULDs to SHALLs (similar to how the UAS procedures for handling AutoReq are currently defined).  The requesting user may not want their initial talk burst to be automatically played out from the called UA's speaker phone, due to privacy concerns of the calling user.  The common example is a mistress who does not want the call to be auto answered, for fear that the wife is present.  Another example is when the requesting user is concerned that he/she might be interupting the called user (i.e. calling user suspects that the called user is having lunch with a customer, or is in a meeting) and therefore wants to "politely" alert the user prior to the initial talk burst being played out, in order to giving the called user an opportunity to reject the call.  In each of these cases, the calling user's behavior is based upon a "guarantee" from the PoC service that thei!
 r initial talk burst will only be played out if the called user manually accepts the call.
 
It also would seem more logical to have the semantics of "ManualReq" be truly "manual mode required", rather than the current "manual mode strongly recommended".
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip