RE: [Sipping] A Framework for Reducing Spam for Internet Telephony

"Saverio Niccolini" <Saverio.Niccolini@netlab.nec.de> Fri, 15 June 2007 09:24 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz82N-0006s4-Ia; Fri, 15 Jun 2007 05:24:11 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Hz82M-0006ro-GL for sipping-confirm+ok@megatron.ietf.org; Fri, 15 Jun 2007 05:24:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz82L-0006rd-Rq for sipping@ietf.org; Fri, 15 Jun 2007 05:24:09 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz82K-0006e6-Bz for sipping@ietf.org; Fri, 15 Jun 2007 05:24:09 -0400
Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id CF01220102C1; Fri, 15 Jun 2007 11:24:07 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5RphZoQCCV9Y; Fri, 15 Jun 2007 11:24:07 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id BAC78200017E; Fri, 15 Jun 2007 11:23:57 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] A Framework for Reducing Spam for Internet Telephony
Date: Fri, 15 Jun 2007 11:24:01 +0200
Message-ID: <113091BD57179D4491C19DA7E10CD6960150DFF5@mx1.office>
In-Reply-To: <4671268A.8070602@gmx.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] A Framework for Reducing Spam for Internet Telephony
Thread-Index: Aceud17o1pXFXurwTdud9T1omk2qbAAtVpbw
From: Saverio Niccolini <Saverio.Niccolini@netlab.nec.de>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, SIPPING LIST <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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>
Errors-To: sipping-bounces@ietf.org

Dear Hannes,

This is a nice work that clearly matches also what we have in mind for the SPIT prevention system we are currently running.

Actually I wanted to let you know that for some of the interactions or authorization policies you describe in Figure 1 there are already available drafts that propose solutions:
http://tools.ietf.org/id/draft-niccolini-sipping-feedback-spit-03.txt
or describe scenarios for the interactions:
http://tools.ietf.org/id/draft-niccolini-sipping-spitstop-00.txt

It would be nice to have them referenced as well in the draft.

Moreover, our SPIT prevention framework (you can find references of it in proceedings of Globecom 2006) uses already some of the authorization policies you are describing also in the other draft (http://fon.gs/spit-requirements), namely:
-- we have built white/black list based on identities (or part of it), this matches Req-C 1 and Req-C 2
-- we block certain messages based on the spam-level marking, this supports Req-C 7
-- we mark the messages with a certain spam-level and forward this to the caller, this supports Req-A 2
-- we use some kind of Turing Tests built in answering machines, this supports Req-A 4
-- we also run anomaly detection methods able to mark the calls and make this available for other entities, this supports Req-T 1

I think all in all these two drafts you recently wrote complement well the SPITSTOP work we are currently discussing in the SPITSTOP mailing list, it is just a pity that they are coming too late to support the BOF request that was just rejected.

I hope we can sit together in Chicago at the BAR BOF and discuss the way to move the all work on SPIT forward in the IETF.

Cheers,
Saverio

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]
> Sent: Thursday, June 14, 2007 1:29 PM
> To: SIPPING LIST
> Subject: [Sipping] A Framework for Reducing Spam for Internet Telephony
> 
> Hi all,
> 
> we have just submitted a new draft on "A Framework for Reducing Spam for
> Internet Telephony".
> Please find the document here: http://fon.gs/spit-framework
> 
> This document attempts to scope the work on reducing Spam for Internet
> Telephony.
> 
> Ciao
> Hannes
> 
> 
> 
> _______________________________________________
> 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