IETF Logo Mail Archive

Re: [Rucus] SPIT Misuse Classification?

"Avasarala Ranjit-A20990" <ranjit@motorola.com> Wed, 10 February 2010 10:59 UTC

Return-Path: <ranjit@motorola.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 3E6DF3A72D4 for <rucus@core3.amsl.com>; Wed, 10 Feb 2010 02:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QC0NsMTyB-po for <rucus@core3.amsl.com>; Wed, 10 Feb 2010 02:59:51 -0800 (PST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with ESMTP id 66C9F3A72CE for <rucus@ietf.org>; Wed, 10 Feb 2010 02:59:51 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: ranjit@motorola.com
X-Msg-Ref: server-11.tower-128.messagelabs.com!1265799660!9269965!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [136.182.1.15]
Received: (qmail 8161 invoked from network); 10 Feb 2010 11:01:00 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (136.182.1.15) by server-11.tower-128.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Feb 2010 11:01:00 -0000
Received: from il27exr04.cig.mot.com ([10.17.196.73]) by motgate5.mot.com (8.14.3/8.14.3) with ESMTP id o1AB0sxh009346 for <rucus@ietf.org>; Wed, 10 Feb 2010 04:01:00 -0700 (MST)
Received: from il27vts02.mot.com (il27vts02.cig.mot.com [10.17.196.86]) by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id o1AB0s9B002712 for <rucus@ietf.org>; Wed, 10 Feb 2010 05:00:54 -0600 (CST)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26]) by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id o1AB0o2l002670 for <rucus@ietf.org>; Wed, 10 Feb 2010 05:00:51 -0600 (CST)
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
Date: Wed, 10 Feb 2010 19:00:28 +0800
Message-ID: <750BBC72E178114F9DC4872EBFF29A5B0A2CD530@ZMY16EXM66.ds.mot.com>
In-Reply-To: <3D3C75174CB95F42AD6BCC56E5555B45022D524F@FIESEXC015.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Rucus] SPIT Misuse Classification?
thread-index: Acqpjoo3SnsHFkWTQMuSZHaocG+tFwAAKaNQACweWgA=
References: <3D3C75174CB95F42AD6BCC56E5555B45022D51B7@FIESEXC015.nsn-intra.net><592946D5-B7B1-4C18-9B4F-25DABD67C0E8@cs.columbia.edu> <3D3C75174CB95F42AD6BCC56E5555B45022D524F@FIESEXC015.nsn-intra.net>
From: Avasarala Ranjit-A20990 <ranjit@motorola.com>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>, ext Henning Schulzrinne <hgs@cs.columbia.edu>
X-CFilter-Loop: Reflected
Cc: rucus@ietf.org
Subject: Re: [Rucus] SPIT Misuse Classification?
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: Wed, 10 Feb 2010 10:59:52 -0000

Hi

The 3GPP spec 24.611 addresses the procedures for Dynamic Incoming
Communication Barring (ICB) where the subscribers upon understanding
that the incoming communication is unwanted could indicate to the
network to block the calling user. This uses the SIP request BYE with
Reason header.

E.g
BYE ...
......
Reason: block; cause=1; text="Telemarketer"

Similarly the caller could be blocked during call alerting phase too by
putting the Reason header in a 4xx message.

Thanks


Regards
Ranjit

-----Original Message-----
From: rucus-bounces@ietf.org [mailto:rucus-bounces@ietf.org] On Behalf
Of Tschofenig, Hannes (NSN - FI/Espoo)
Sent: Tuesday, February 09, 2010 7:27 PM
To: ext Henning Schulzrinne
Cc: rucus@ietf.org
Subject: Re: [Rucus] SPIT Misuse Classification?

That was a bit unfortunate wording and Joachim noticed this mistake as
well. 

What I would like to hear is whether someone tried to classify the
different versions of SPIT in some way already. For example, I could
classify them according to the source (fixed vs. mobile networks), the
intented outcome, some technical approaches being used, etc. 



>-----Original Message-----
>From: ext Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
>Sent: 09 February, 2010 15:48
>To: Tschofenig, Hannes (NSN - FI/Espoo)
>Cc: rucus@ietf.org
>Subject: Re: [Rucus] SPIT Misuse Classification?
>
>Can you explain what you mean by "SPIT misuse"? All SPIT would seem to 
>be mis/abuse...
>
>On Feb 9, 2010, at 8:16 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>
>> Hi all,
>> 
>> I am looking for a classification of SPIT misuse. Has someone worked 
>> on such a classification terminology or seen it elsewhere?
>> 
>> Thanks in advance!
>> 
>> Ciao
>> Hannes
>> _______________________________________________
>> Rucus mailing list
>> Rucus@ietf.org
>> https://www.ietf.org/mailman/listinfo/rucus
>> 
>
>
_______________________________________________
Rucus mailing list
Rucus@ietf.org
https://www.ietf.org/mailman/listinfo/rucus

v2.23.0 | Report a Bug | By Email