Re: [Rucus] SPIT from operator

Pars Mutaf <pars.mutaf@gmail.com> Thu, 09 July 2009 10:46 UTC

Return-Path: <pars.mutaf@gmail.com>
X-Original-To: rucus@core3.amsl.com
Delivered-To: rucus@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C03A13A6B40 for <rucus@core3.amsl.com>; Thu, 9 Jul 2009 03:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=0.612, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUfIQXpR8tkQ for <rucus@core3.amsl.com>; Thu, 9 Jul 2009 03:46:20 -0700 (PDT)
Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by core3.amsl.com (Postfix) with ESMTP id 3891E3A67E3 for <rucus@ietf.org>; Thu, 9 Jul 2009 03:46:19 -0700 (PDT)
Received: by ewy26 with SMTP id 26so76808ewy.37 for <rucus@ietf.org>; Thu, 09 Jul 2009 03:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=w4RI7r7nIc/0nBkOJB889D5Ggc/n6b7NWyT3AJGf7L8=; b=Gt3ZxfKru3i0mJm0cC5b7xZp1L49FTOXMQf9f6+9+IEnL8476D4WMgFYFuwYFg0xGk rigaw33zFwsvp5JOYBmBOMgeiLbp0w6rOWs5s6ZCTn9+s+BC9EpihMX1hcTsxlKHbCxU HBrCwzFFXSUJa3qgBLikh3AR9e8hhan1A38SI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=X2FqyhZKwXyXkUdJ2+KpHbs9I3Yyehm+qvjj/MWe490+SnayhtMH2cjWwOCY0q9S3Q 88HGGIrTr4tJidd3YJloNnoMlDq42t+FbagAqHXk+yz9LUH70EuoUfoSyEM/j84P+/j0 xYEYxqknbBZ7CVAj0XMCaiyNaM2TKdK81z47Q=
MIME-Version: 1.0
Received: by 10.210.132.3 with SMTP id f3mr757778ebd.64.1247136403882; Thu, 09 Jul 2009 03:46:43 -0700 (PDT)
In-Reply-To: <E993E3D8979F074987D482D4448C802D020B45D1@DEMUEXC005.nsn-intra.net>
References: <18a603a60907080834x46599d2fmb54763f0857df09c@mail.gmail.com> <E993E3D8979F074987D482D4448C802D020B45D1@DEMUEXC005.nsn-intra.net>
Date: Thu, 09 Jul 2009 13:46:43 +0300
Message-ID: <18a603a60907090346i21790a3eu677e6f7d1c77249e@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: "Charzinski, Joachim (NSN - DE/Munich)" <joachim.charzinski@nsn.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Rucus BoF <rucus@ietf.org>
Subject: Re: [Rucus] SPIT from operator
X-BeenThere: rucus@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Reducing Unwanted Communication Using SIP \(RUCUS\)" <rucus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rucus>
List-Post: <mailto:rucus@ietf.org>
List-Help: <mailto:rucus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2009 10:46:21 -0000

Hi Joachim,

To clarify, I don't receive calls but messages from the operator about
new services,
new songs available as ring tone, and various non-sense stuff. I would
like to filter
these messages on my cell phone. As far as I know, there this no easy way to
inform the operator that I'm not interested in these messages.

We seem to agree that the cell phone should be able to filter operator's SPIT.

Please see below for more...

On Thu, Jul 9, 2009 at 10:01 AM, Charzinski, Joachim (NSN -
DE/Munich)<joachim.charzinski@nsn.com> wrote:
> Hi Pars,
>
>> This makes me think that SPIT solutions must be operator independent.
>
> I think this is generalizing too much. Solutions against the type of
> SPIT you mention will have to be operator independent (possibly also
> involving some regulatory power that forces operators to respect
> entries on "don't call" lists). The same will be true for the kind of
> Spam distribution services we find with the postal service ("distribute
> this to every household with a street address") - wherever the operator
> actually makes money from Spam or SPIT, it will be necessary to have an
> operator independent solution for fighting Spam and SPIT.
>
> On the other hand, it is probably the operators that are currently
> preventing large scale SPIT by performing ingress address filtering and
> enforcing rate caps on SIP signalling. Also, in a traditional telephony
> environment, it would be the operator that strips off the origin address
> for anonymous calls, so the operator has more power in filtering SPIT
> than the end user / end device would have.

I am not sure that the operator is willing to filter SPIT. This is
open to discussion.

By the way, I note here that in your operator-based filtering approach, the
operator should forward the messages marked as SPIT to the target cell phone
anyways. This is because the false positive probability is never zero.
The target user should make the decision whether or not a message is SPIT
before deleting a message from inbox.

As a consequence, this makes be believe that operator-based filtering is not
really necessary. Just forward all messages to the target cell phone, the
target cell phone can filter them and store the ones marked as SPIT for
eventual user inspection.

I missed something?

Thanks

pars




>
> Therefore I think we need two solutions that help both parties - the
> operator and the end user - to fight SPIT independently. They may even
> cooperate, but they cannot completely substitute one another.
>
>> What is the situation in other countries?
>
> I am living in germany, and I used to get a lot of cold calls, most of
> them machine assisted but actually connecting to a personal agent. Only
> a few calls were completely automated. My cold calls frequency has dropped
> drastically since I started asking the callers for permission to record
> the calls for usage in court. They seem to have deleted my number from
> their address lists.
> If operators didn't interfer (see the above mentioned rate caps and
> address filters), we would probably get a lot more calls, as there are
> a lot of VoIP contracts around where you can reach most of the fixed
> phone network within a flat rate.
>
> Best regards
>
>        Joachim.
>
>
> -----Original Message-----
> From: rucus-bounces@ietf.org [mailto:rucus-bounces@ietf.org] On Behalf Of ext Pars Mutaf
> Sent: Wednesday, July 08, 2009 5:34 PM
> To: Rucus BoF
> Subject: [Rucus] SPIT from operator
>
> Hello,
>
> I my country, subscribers receive a lot of SPIT from their operators.
> In my cell phone experience, the operator itself is the most serious
> SPIT problem.
>
> This makes me think that SPIT solutions must be operator independent.
>
> Would you have any comments on that? What is the situation in other
> countries? Which solutions can be applied?
>
> Thanks
>
> pars
> _______________________________________________
> Rucus mailing list
> Rucus@ietf.org
> https://www.ietf.org/mailman/listinfo/rucus
>
> ----------------------------------------------------------
> Joachim Charzinski
>
> Nokia Siemens Networks
> Research, Technology and Platforms
> Research & Technology / Network Evolution
>
> St.-Martin-Str. 53
> Post box: D-80240 Muenchen
> D-81541 Muenchen
> Germany
> Tel: +49 89 636 79902
>
> Joachim.Charzinski@nsn.com
> http://www.nokiasiemensnetworks.com/global/
>
> Think before you print
>
> Nokia Siemens Networks GmbH & Co. KG
> Sitz der Gesellschaft: München / Registered office: Munich
> Registergericht: München / Commercial registry: Munich, HRA 88537
> WEEE-Reg.-Nr.: DE 52984304
>
> Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management GmbH
> Geschäftsleitung / Board of Directors: Lydia Sommer, Olaf Horsthemke
> Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Lauri Kivinen
> Sitz der Gesellschaft: München / Registered office: Munich
> Registergericht: München / Commercial registry: Munich, HRB 163416
>