RE: [Sipping] Re: Questions on draft-jennings-sipping-pay-00

Tschofenig Hannes <hannes.tschofenig@siemens.com> Tue, 26 October 2004 11:25 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25286 for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 07:25:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMPg8-0000ns-Pt for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 07:39:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMPQc-0007jM-3t; Tue, 26 Oct 2004 07:23:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMPOn-00079X-Ec for sipping@megatron.ietf.org; Tue, 26 Oct 2004 07:21:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24966 for <sipping@ietf.org>; Tue, 26 Oct 2004 07:21:56 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMPcR-0000jO-3S for sipping@ietf.org; Tue, 26 Oct 2004 07:36:03 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i9QBLqP6015886; Tue, 26 Oct 2004 13:21:52 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i9QBLqBO012034; Tue, 26 Oct 2004 13:21:52 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id <4BVR6260>; Tue, 26 Oct 2004 13:21:52 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F051C86AE@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org
Subject: RE: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
Date: Tue, 26 Oct 2004 13:21:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: fluffy@cisco.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

hi wolfgang, 

thanks for pointing to saml-sip. in fact i have added a few lines to the
updated draft on the compensation issue (section 6.4 of
http://www.tschofenig.priv.at/drafts/draft-tschofenig-sip-saml-01.txt) . 
i agree with you that there is some potential for new services beyond just
spam prevention. 

ciao
hannes

> -----Original Message-----
> From: Beck01, Wolfgang [mailto:BeckW@t-systems.com]
> Sent: Montag, 25. Oktober 2004 17:41
> To: sipping@ietf.org
> Cc: fluffy@cisco.com
> Subject: AW: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
> 
> 
> >On 7/15/04 3:01 AM, "Elwell, John" <john.elwell@siemens.com> wrote:
> 
> >> Cullen,
> >> 
> >> 1. I see nothing to indicate what happens if the called
> user is busy,
> >> switched off, etc. at the time the request with receipt
> arrives. This
> >> might be a particular problem for the case where the UAS is a PSTN 
> >> gateway, since it probably won't check on the availability of the 
> >> destination user before sending the 402, so if the party is not 
> >> available or busy it will probably still be not available or busy 
> >> when the request with receipt arrives.
> 
> > yes - this is a somewhat fundamental limitation of the
> whole system. 
> > It somewhat assumes that if you pay, you will at least go to 
> > voicemail. Even if the proxy found out if the UA was
> online, there is
> > no  way to know if the user will answer, or if they do
> answer, will they instantly hangup.
> 
> By the end of the month, the merchant presents his receipts to the 
> Payment Service Provider and gets the money. The merchant (= the PSTN 
> gateway
> provider) could choose to discard receipts for calls to unavailable 
> destinations.
> 
> When I wrote
> http://www.potaroo.net/ietf/idref/draft-beck-sipping-svc-charging-req/
> (http://www.ietf.org/proceedings/03mar/slides/sipping-8.pdf)
> two years ago, I had such a scheme in mind. Re-INVITEs carrying 
> receipts of small sums could limit the damage for the caller if the 
> called party cheats.

>  
> As there is a financial incentive for malicious users, security is 
> even more critical than for other protocols.
> Installing malicious programs on a victim's PC that call expensive 
> numbers is worse than just installing DDoS bots (but perhaps clueless 
> users will finally secure their system if they have to pay). On the 
> other hand, will users accept a system where they have to type in a 
> password every time they make a call? Can 
> http://www.ietf.org/internet-drafts/draft-tschofenig-sip-saml-00.txt
> help?
> 
> Besides Spam prevention, draft-jennings-sipping-pay allows new useful 
> services.


ciao
hannes

> 
> 
> Wolfgang
> 
> --
> T-Systems
> IP Platform Services
> Am Kavalleriesand 3
> 64295 Darmstadt
> Germany
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP