Re: [Rucus] [spitstop] Botnets, take 2... Re: Draft RUCUS charter

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Fri, 22 February 2008 12:40 UTC

Return-Path: <rucus-bounces@ietf.org>
X-Original-To: ietfarch-rucus-archive@core3.amsl.com
Delivered-To: ietfarch-rucus-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D57928C340; Fri, 22 Feb 2008 04:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[AWL=-0.312, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, SARE_UNSUB30=0.351, SARE_UNSUB30B=0.041]
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 bcVvFVPGHUWE; Fri, 22 Feb 2008 04:40:08 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8781E28C2FD; Fri, 22 Feb 2008 04:40:08 -0800 (PST)
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 0480228C301 for <rucus@core3.amsl.com>; Fri, 22 Feb 2008 04:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 SP303FZx1jqN for <rucus@core3.amsl.com>; Fri, 22 Feb 2008 04:40:06 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id C553828C2B8 for <rucus@ietf.org>; Fri, 22 Feb 2008 04:40:05 -0800 (PST)
Received: (qmail invoked by alias); 22 Feb 2008 12:40:01 -0000
Received: from proxy1-nsn.nsn-inter.net (EHLO [217.115.75.229]) [217.115.75.229] by mail.gmx.net (mp013) with SMTP; 22 Feb 2008 13:40:01 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19uQMhQtP9uABpdZDtkVF4Uqyb7kyDB9nEZu484tN JeWBdQUt974MkC
Message-ID: <47BEC2A8.50201@gmx.net>
Date: Fri, 22 Feb 2008 14:40:08 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Saverio Niccolini <Saverio.Niccolini@nw.neclab.eu>
References: <C3E0C78D.4346A%Quittek@nw.neclab.eu> <3A86FA4E-6D4A-43FE-B380-6676CD4BCD90@voxeo.com> DEFANGED[4]:<42B56C6A683EBA4581C01CB49A914CA70E6EA261@MAILFAXSRV.gfimalta.com><909E8DC8-CB3A-478D-995F-94A4B3656D8D@cs.columbia.edu><47BEAEE3.4040701@gmx.net><113091BD57179D4491C19DA7E10CD69601B5639F@mx1.offi " " ce> <47BEB721.8040305@gmx.net> <5F6519BF2DE0404D99B7C75607FF76FF53DB8D@mx1.office>
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF53DB8D@mx1.office>
X-Y-GMX-Trusted: 0
Cc: rucus@ietf.org
Subject: Re: [Rucus] [spitstop] Botnets, take 2... Re: Draft RUCUS charter
X-BeenThere: rucus@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Hannes.Tschofenig@gmx.net
List-Id: <rucus.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/rucus>
List-Post: <mailto:rucus@ietf.org>
List-Help: <mailto:rucus-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/rucus>, <mailto:rucus-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rucus-bounces@ietf.org
Errors-To: rucus-bounces@ietf.org

Hi Saverio,

Saverio Niccolini wrote:
> Hannes, all,
>
>   
>> Let's take an example:
>> When Henning's host is compromised and a bot is using 
>> Henning's account to send me spam then I would contact 
>> Henning (by using various ways) to tell him that something is 
>> wrong with his PC/phone/etc. I would not tell my VoIP 
>> provider that there is something wrong with Henning's account. 
>> Typically, this will lead to more problems rather than less 
>> -- such as no communication to Columbia University anymore 
>> because my VoIP provider just blocks all calls from that domain.
>>
>> (Just to reflect my experience with email problems in the company....)
>>     
>
> You do not contact Henning directly to tell him that something
> is wrong. You have to rely on your infrastructure to take the
> necessary countermeasures otherwise it is the anarchy...
>   
Why wouldn't I contact him directly?

> That is why exchanging reputation of identities (as perceived by
> end-users or domains) is an important building block.
> Such reputation system (one of the points of RFC 5039) can be built
> using mechanisms like feedbacks:
> http://tools.ietf.org/html/draft-niccolini-sipping-spam-feedback-00
> and spam scores:
> http://tools.ietf.org/html/draft-wing-sipping-spam-score-01
> of course there are privacy issues that apply (but this is 
> a problem of reputation systems as well) :-)
>   
There is a long way to go between a global reputation system and the 
drafts you mention above.

> It seems this list is converging to the point we tried to raise 
> since 2006, I should be happy :-)
>   

Nobody is saying that these mechanisms do not exist on paper. They just 
have a quite challenging deployment story and the protocol issue is the 
least problematic thing to worry about: it is the trust relationships 
you have to establish between the VoIP provider. If you think about a 
model similar to email then you will have a hard time to establish such 
an infrastructure.

Ciao
Hannes

> Saverio
>
> ============================================================
> Dr. Saverio Niccolini
> Senior Researcher
> NEC Laboratories Europe, Network Research Division	
> Kurfuerstenanlage 36, D-69115 Heidelberg
> Tel.     +49 (0)6221 4342-118
> Fax:     +49 (0)6221 4342-155
> e-mail:  saverio.niccolini@nw.neclab.eu <-- !!! NEW ADDRESS !!!
> ============================================================
> NEC Europe Limited Registered Office: NEC House, 1 Victoria
> Road, London W3 6BL Registered in England 2832014
>  
> _______________________________________________
> spitstop mailing list
> spitstop@listserv.netlab.nec.de
> https://listserv.netlab.nec.de/mailman/listinfo/spitstop
>   

_______________________________________________
Rucus mailing list
Rucus@ietf.org
http://www.ietf.org/mailman/listinfo/rucus