Re: [Rucus] Operator-assisted SPIT filtering (was Re: SPIT fromoperator)

True. That is the reason why an Operator cannot mark any caller or call
as spam. Only the target users can mark a particular caller or a call as
unwanted or malicious and may want to block the caller from further
calling. 

Regards
Ranjit

-----Original Message-----
From: rucus-bounces@ietf.org [mailto:rucus-bounces@ietf.org] On Behalf
Of Pars Mutaf
Sent: Thursday, July 09, 2009 5:31 PM
To: David Schwartz
Cc: Rucus BoF
Subject: Re: [Rucus] Operator-assisted SPIT filtering (was Re: SPIT
fromoperator)

Hello,

On Thu, Jul 9, 2009 at 2:49 PM, David Schwartz<dschwartz@xconnect.net>
wrote:
>
> Hi
>
>> What is the advantage of operator marking and forwarding the message,

>> over the cell phone marking the message and storing marked as SPIT?
>
> The operator has much more information to base a decision on
(including input he gets from the endpoint) than the endpoint has.
> The operator can "share" information better with other users
(including ones who did not actually mark the particular caller) as
well. > Email systems have been doing this for years where a spam
indication by one of its members is propagated to others.

Is there any reference for this? (if not too difficult to find any).
In my view, there may exist messages marked as spam by one user, that
may not be considered as spam by other users.
I mean, users may have different spam criteria.

In any case I would suggest that these points be clarified. They don't
seem obvious to me.

Thanks,

pars

>
>> Perhaps the operator would have more information about SPITers and 
>> can perform better filtering on behalf of users? (I'm not sure about 
>> that). This could be clarified?
>
> My point is, that regardless of the actual SPAM indication harvesting
technique (e.g. the receiving user "blocked" the call), without the
ability to warn others as well the information is of limited value -
hence my reference to the Wing draft.
>
>> Or it is an energy conservation issue?
>
> :)
>
> Thanks,
>
> pars
>
>
_______________________________________________
Rucus mailing list
Rucus@ietf.org
https://www.ietf.org/mailman/listinfo/rucus