AW: [Sipping] RE: I-D ACTION:draft-jennings-sipping-pay-02.txt

"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Wed, 20 July 2005 17:16 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvIBH-00008z-1r; Wed, 20 Jul 2005 13:16:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvIBE-00008e-Df for sipping@megatron.ietf.org; Wed, 20 Jul 2005 13:16:24 -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 NAA10853 for <sipping@ietf.org>; Wed, 20 Jul 2005 13:16:21 -0400 (EDT)
Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvIf6-0002bT-4B for sipping@ietf.org; Wed, 20 Jul 2005 13:47:16 -0400
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id j6KHGDu2001928; Wed, 20 Jul 2005 19:16:13 +0200
Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net [157.163.133.201]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id j6KHGD6w000244; Wed, 20 Jul 2005 19:16:13 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.146]) by fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 20 Jul 2005 19:16:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [Sipping] RE: I-D ACTION:draft-jennings-sipping-pay-02.txt
Date: Wed, 20 Jul 2005 19:16:10 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C393421EEC@MCHP7IEA.ww002.siemens.net>
Thread-Topic: [Sipping] RE: I-D ACTION:draft-jennings-sipping-pay-02.txt
Thread-Index: AcWMrlW0lrIplrCeSHauvImPs6H6pwAjWgagAAGfUCAAASKXMAAB5j9A
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: henry@pulver.com, henry@sinnreich.net, sipping WG <sipping@ietf.org>
X-OriginalArrivalTime: 20 Jul 2005 17:16:10.0951 (UTC) FILETIME=[B986C570:01C58D4E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Content-Transfer-Encoding: quoted-printable
Cc:
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

henry, 

i forgot to mention one issue:

the fact that the customer is offered a flat rate still requires authentication and authorization of the user. 
there is only the question of how to perform the message exchange. 

ciao
hannes


> -----Ursprüngliche Nachricht-----
> Von: Henry Sinnreich [mailto:henry@pulver.com] 
> Gesendet: Mittwoch, 20. Juli 2005 18:48
> An: Tschofenig, Hannes; henry@sinnreich.net; 'sipping WG'
> Betreff: RE: [Sipping] RE: I-D 
> ACTION:draft-jennings-sipping-pay-02.txt 
> 
> 
> >could you elaborate a bit more on your statement about 
> >voip payments using either flat rate or complex 3rd party 
> business models?
> 
> Most VoIP consumer services on the market have flat rates, 
> such as $20/month
> unlimited. See for example http://www.packet8.net/ 
> (unlimited) that I happen
> to use. Many PSTN consumer services are also flat rate, see 
> for example
> http://consumer.mci.com/TheNeighborhood/res_local_service/jsps
> /default.jsp 
> 
> There are also many mobile services with flat rate, such as
> http://sprintpcs.com/ 
> 
> My apology for picking service examples I am most familiar with.
> 
> Third party consumer-business payment models could involve a 
> search engine
> to deliver product information along some advertismens and finally a
> click-to-call service to connect the buyer with the seller. 
> Such calls are
> obviously much more valuable to the seller and the revenue 
> sharing models
> are an interesting topic apart.
> 
> I would be still interested in the motivation for choosing 
> the particular
> approach in this I-D as well as the pros and cons, though the 
> reference
> <draft-ietf-sipping-spam-00.txt> is most welcome. This is more of a
> discussion paper after all, since no experimental data are 
> available, as
> required for a standards track document.
> 
> Last but not least, these nits are only meant to enahnce the 
> proposal that I
> believe is very interesting.
> 
> Thanks, Henry
> 
>  
> 
> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf
> Of Tschofenig, Hannes
> Sent: Wednesday, July 20, 2005 10:50 AM
> To: henry@sinnreich.net; sipping WG
> Subject: AW: [Sipping] RE: I-D 
> ACTION:draft-jennings-sipping-pay-02.txt 
> 
> hi henry, 
> 
> thanks for pointing to the draft. 
> i think a comparison with other spit proposals is not really 
> necessary given
> the detailed description in 
> <draft-ietf-sipping-spam-00.txt> 
> 
> could you elaborate a bit more on your statement about voip 
> payments using
> either flat rate or complex 3rd party business models?
> 
> ciao
> hannes
> 
> > -----Ursprüngliche Nachricht-----
> > Von: sipping-bounces@ietf.org 
> > [mailto:sipping-bounces@ietf.org] Im Auftrag von henry@sinnreich.net
> > Gesendet: Mittwoch, 20. Juli 2005 17:17
> > An: 'sipping WG'
> > Betreff: [Sipping] RE: I-D ACTION:draft-jennings-sipping-pay-02.txt 
> > 
> > 
> > This is an interesting proposal and deserves some attention.
> > 
> > The title of the ID could be better chosen, even if longer 
> or by some
> > abbreviation, so as to indicate it is an option from SPIT 
> > prevention and not
> > for VoIP payments which are either flat rate (mostly) or have 
> > some complex
> > 3rd party business models.
> > 
> > Also, in the introduction, a short comparison with other SPIT 
> > prevention
> > mechanism would be helpful, as well as presenting the motivation for
> > choosing this particular approach.
> > 
> > Thanks, Henry
> > 
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> > Sent: Tuesday, July 19, 2005 2:50 PM
> > To: i-d-announce@ietf.org
> > Subject: I-D ACTION:draft-jennings-sipping-pay-02.txt 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > 
> > 
> > 	Title		: Payment for Services in Session Initiation
> >                           Protocol (SIP)
> > 	Author(s)	: C. Jennings, et al.
> > 	Filename	: draft-jennings-sipping-pay-02.txt
> > 	Pages		: 22
> > 	Date		: 2005-7-19
> > 	
> > Communication systems require that a person receiving a call be able
> >    able to charge the caller when they are from different 
> > administrative
> >    domains.  This is necessary for making fair exchanges of service
> >    between two different communicating parties and is a 
> major strategy
> >    for reducing the viability of SPAM.  This draft proposes 
> > an approach
> >    for doing this in SIP.  The approach relies on a third 
> party to act
> >    as a payment service provider and is optimized for very 
> simple, low
> >    value transactions.  It does not provide the full range 
> of services
> >    that are desirable in typical online trading systems.
> > 
> >    This draft is being discussed on the sipping@ietf.org 
> mailing list.
> >    There is currently work to substantially change this draft to use
> >    SAML.
> > 
> > A URL for this Internet-Draft is:
> > 
> http://www.ietf.org/internet-drafts/draft-jennings-sipping-pay-02.txt
> > 
> > To remove yourself from the I-D Announcement list, send a 
> message to 
> > i-d-announce-request@ietf.org with the word unsubscribe in 
> > the body of the
> > message.  
> > You can also visit 
> > https://www1.ietf.org/mailman/listinfo/I-D-announce 
> > to change your subscription settings.
> > 
> > 
> > Internet-Drafts are also available by anonymous FTP. Login 
> > with the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > 	"get draft-jennings-sipping-pay-02.txt".
> > 
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html 
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > 
> > 
> > Internet-Drafts can also be obtained by e-mail.
> > 
> > Send a message to:
> > 	mailserv@ietf.org.
> > In the body type:
> > 	"FILE /internet-drafts/draft-jennings-sipping-pay-02.txt".
> > 	
> > NOTE:	The mail server at ietf.org can return the document in
> > 	MIME-encoded form by using the "mpack" utility.  To use this
> > 	feature, insert the command "ENCODING mime" before the "FILE"
> > 	command.  To decode the response(s), you will need "munpack" or
> > 	a MIME-compliant mail reader.  Different MIME-compliant 
> > mail readers
> > 	exhibit different behavior, especially when dealing with
> > 	"multipart" MIME messages (i.e. documents which have been split
> > 	up into multiple messages), so check your local documentation on
> > 	how to manipulate these messages.
> > 		
> > 		
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> > 
> > 
> > _______________________________________________
> > 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
> 
> 
> 
> 

_______________________________________________
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