Re: [Rucus] SPIT from operator
"Charzinski, Joachim (NSN - DE/Munich)" <joachim.charzinski@nsn.com> Thu, 09 July 2009 07:01 UTC
Return-Path: <joachim.charzinski@nsn.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 EE37C3A6AD0 for <rucus@core3.amsl.com>; Thu, 9 Jul 2009 00:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 7+Ng17BjOnFb for <rucus@core3.amsl.com>; Thu, 9 Jul 2009 00:01:00 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 82C803A6873 for <rucus@ietf.org>; Thu, 9 Jul 2009 00:01:00 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n6971QLT008708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 9 Jul 2009 09:01:26 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n6971M5Y009706; Thu, 9 Jul 2009 09:01:26 +0200
Received: from DEMUEXC005.nsn-intra.net ([10.150.128.17]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 9 Jul 2009 09:01:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Jul 2009 09:01:30 +0200
Message-ID: <E993E3D8979F074987D482D4448C802D020B45D1@DEMUEXC005.nsn-intra.net>
In-Reply-To: <18a603a60907080834x46599d2fmb54763f0857df09c@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Rucus] SPIT from operator
Thread-Index: Acn/4aNzP2t2hudtSm+f+cGRNKCrpAAe6uyA
References: <18a603a60907080834x46599d2fmb54763f0857df09c@mail.gmail.com>
From: "Charzinski, Joachim (NSN - DE/Munich)" <joachim.charzinski@nsn.com>
To: ext Pars Mutaf <pars.mutaf@gmail.com>, Rucus BoF <rucus@ietf.org>
X-OriginalArrivalTime: 09 Jul 2009 07:01:25.0538 (UTC) FILETIME=[1314E820:01CA0063]
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 07:01:02 -0000
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. 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
- [Rucus] SPIT from operator Pars Mutaf
- Re: [Rucus] SPIT from operator Charzinski, Joachim (NSN - DE/Munich)
- Re: [Rucus] SPIT from operator Pars Mutaf
- Re: [Rucus] SPIT from operator David Schwartz
- Re: [Rucus] SPIT from operator Avasarala Ranjit-A20990