[Sip] willis-sip-answeralert-00

"Cullen Jennings" <fluffy@cisco.com> Fri, 29 July 2005 16:29 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXjX-0005aP-Ve; Fri, 29 Jul 2005 12:29:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXjU-0005XC-HK for sip@megatron.ietf.org; Fri, 29 Jul 2005 12:29:12 -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 MAA21206 for <sip@ietf.org>; Fri, 29 Jul 2005 12:29:09 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyYFB-0006oB-RH for sip@ietf.org; Fri, 29 Jul 2005 13:01:58 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 29 Jul 2005 09:29:02 -0700
X-IronPort-AV: i="3.95,153,1120460400"; d="scan'208"; a="327271854:sNHT26830280"
Received: from sea-alpha-e2k3.sea-alpha.cisco.com (sea-alpha-e2k3.cisco.com [10.93.132.88]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j6TGT1JL012930; Fri, 29 Jul 2005 09:29:02 -0700 (PDT)
Received: from FluffyNotebootk ([171.68.225.134]) by sea-alpha-e2k3.sea-alpha.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 29 Jul 2005 09:33:37 -0700
From: Cullen Jennings <fluffy@cisco.com>
To: sip@ietf.org
Date: Fri, 29 Jul 2005 12:29:06 -0400
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcWT1hXIkesHTnZaRJ6U9Q5RTfxcYQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <SEA-ALPHA-E2K30QUUB0000031a@sea-alpha-e2k3.sea-alpha.cisco.com>
X-OriginalArrivalTime: 29 Jul 2005 16:33:37.0636 (UTC) FILETIME=[45599240:01C5945B]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 'Dean Willis' <dean.willis@softarmor.com>
Subject: [Sip] 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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean, first of all, I would like to point out the irony of you want my phone
to auto answer and you will not even include your phone number in the draft.
Just to prove you are too paranoid, I put my cell phone number and my email
address in all my recent drafts - contrary to urban legend, it did not
change my rate of spam or telemarketing in the slightest.

I'd like this better if it clearly diffracted between answer and receive
media and answer and send and receive. I will want different policy for the
two.

I would like it better if the UAS had an explicit consent mechanism to allow
the UAC to do this. (ala consent framework)

Seems like the alert mode could be a separate draft that might be better
bundled with the loop back stuff.

I think we need this auto answer stuff, we just need to figure out how to do
it such that it is possible to authorize it. (and this looks like reasonable
direction)

I find the x and xReq a bit weird and under motivated by we need all of them
but assume you will enlighten me on next rev.

Cullen





_______________________________________________
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