[Sip] Re: willis-sip-answeralert-00

Dean Willis <dean.willis@softarmor.com> Fri, 29 July 2005 16:44 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXyO-0001ty-5W; Fri, 29 Jul 2005 12:44:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXyM-0001to-DR for sip@megatron.ietf.org; Fri, 29 Jul 2005 12:44:34 -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 MAA22883 for <sip@ietf.org>; Fri, 29 Jul 2005 12:44:31 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyYU2-0007TY-UH for sip@ietf.org; Fri, 29 Jul 2005 13:17:20 -0400
Received: from [192.168.2.100] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j6TGlIu7015855 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 29 Jul 2005 11:47:19 -0500
In-Reply-To: <SEA-ALPHA-E2K30QUUB0000031a@sea-alpha-e2k3.sea-alpha.cisco.com>
References: <SEA-ALPHA-E2K30QUUB0000031a@sea-alpha-e2k3.sea-alpha.cisco.com>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <38b7da1cc2cf53161777d0600ec5172f@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Date: Fri, 29 Jul 2005 11:43:38 -0500
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org
Subject: [Sip] Re: 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

On Jul 29, 2005, at 11:29 AM, Cullen Jennings wrote:

>
> 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.
>

Hey, I only put my phone in the corporate directory under duress.

I couldn't change my rate of spam -- it currently approaches the link 
speed on my server. I'm either filtering or rejecting about 3,000 a day 
now. I get these HUGE sendmail log files on stuff it rejects because of 
spamhaus.org. Then SpamAssassin kicks in and picks out about another 
500 a day. But still, 50 or 60 get through.

> 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.
>

Either I don't understand the question, or it's what I had in the first 
rev that Paul K made me change.


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

As opposed to "just authorization"?

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

I suppose it could, but OMA needs something for POC last month.

> 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.
>

X means "I want you to use this, but if you can't, do it normally" 
whereas XReq says "I want you to do this so much so that if you can't 
or don't want to, I'd rather you rejected the call."

--
Dean


_______________________________________________
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