IETF Logo Mail Archive

Re: [ietf-dkim] A more fundamental SSP axiom

"Hector Santos" <hsantos@santronics.com> Fri, 04 August 2006 21:41 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G97QW-0002FK-Gr for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:41:52 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G97Nh-000239-HV for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:38:58 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74LbpYl024804; Fri, 4 Aug 2006 14:37:51 -0700
Received: from winserver.com (catinthebox.net [208.247.131.9]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74Lbk1D024767 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 14:37:46 -0700
Received: by winserver.com (Wildcat! SMTP Router v6.1.451.8) for ietf-dkim@mipassoc.org; Fri, 04 Aug 2006 17:39:49 -0400
Received: from hdev1 ([72.144.136.116]) by winserver.com (Wildcat! SMTP v6.1.451.8) with ESMTP id 1481372922; Fri, 04 Aug 2006 17:39:48 -0400
Message-ID: <015301c6b80e$053fad70$0201a8c0@hdev1>
From: Hector Santos <hsantos@santronics.com>
To: DKIM List <ietf-dkim@mipassoc.org>
References: <198A730C2044DE4A96749D13E167AD37C669A3@MOU1WNEXMB04.vcorp.ad.vrsn.com> <62146370608041358y7b914897qdfecdc3c67a1e53d@mail.gmail.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
Date: Fri, 04 Aug 2006 17:36:12 -0400
Organization: Santronics Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Songbird: Clean, Clean
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

----- Original Message ----- 
From: "Damon" <deepvoice@gmail.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>


>> Actually I have a business plan where people pay me to 
>> make the reports on their behalf.

> > Making reports could improve your reputation.
> 
> Will it have a "Only one entry per household" rule? _sniff_

In my DSAP "welfare" <g> version of reporting,  I describe this very issue:

 4.5.  DSAP Tag: r=<abuse-address>

   ....

   Verifiers should be aware this reporting address can be a source of
   an report attack vector (Section 7.4).  One possible implementation
   considerations would to limit the report to one report only and to
   track the reception and/or response of the reporting.

-- 
Hector Santos, Santronics Software, Inc.
http://www.santronics.com





_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email