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

"william(at)elan.net" <william@elan.net> Fri, 04 August 2006 22:22 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G983g-00008B-OM for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 18:22:20 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G983f-0008Lc-Bv for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 18:22:20 -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 k74MLpYS031007; Fri, 4 Aug 2006 15:21:51 -0700
Received: from sokol.elan.net (sokol.elan.net [216.151.192.200]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74MLfWA030990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 15:21:41 -0700
Received: from sokol.elan.net (sokol [127.0.0.1]) by sokol.elan.net (8.13.1/8.13.1) with ESMTP id k74MLCma002351; Fri, 4 Aug 2006 15:21:12 -0700
Received: from localhost (william@localhost) by sokol.elan.net (8.13.1/8.13.1/Submit) with ESMTP id k74MLCWd002345; Fri, 4 Aug 2006 15:21:12 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Fri, 04 Aug 2006 15:21:12 -0700
From: "william(at)elan.net" <william@elan.net>
To: Damon <deepvoice@gmail.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <62146370608041508m1a4064eeg4bc6732ad1ed94bf@mail.gmail.com>
Message-ID: <Pine.LNX.4.62.0608041513250.31733@sokol.elan.net>
References: <20060802002353.U59653@simone.iecc.com> <20060804114527.Y27352@simone.iecc.com> <44D37376.4020408@mtcc.com> <20060804132203.Y49810@simone.iecc.com> <EAF17954-74A3-4374-A059-B31A1414B350@mail-abuse.org> <62146370608041122t779d200h1b29a659ac8ad612@mail.gmail.com> <44D3B49D.9090800@mtcc.com> <62146370608041406i74f707ffgf708bafe87784d97@mail.gmail.com> <44D3BB65.20702@mtcc.com> <016201c6b811$0532d4d0$0201a8c0@hdev1> <62146370608041508m1a4064eeg4bc6732ad1ed94bf@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Songbird: Clean, Clean
Cc: DKIM List <ietf-dkim@mipassoc.org>
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.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336

On Fri, 4 Aug 2006, Damon wrote:

>>  4.7.  DSAP Tag: t=y
>> 
>>   The t=y tag is optional.  If defined, the domain is currently testing
>>   DKIM.  Verifiers SHOULD NOT treat testers any different from
>>   production mode signers.  It SHOULD NOT be used as a way to bypass a
>>   failed signature classification policies.  However, verifiers SHOULD
>>   track testers for over extended usage of test signatures and MAY
>>   consider using the results to provide feedback to the domain.
>> 
>> And other words, the testing flag will not be tolerated as well.
>> 
>
> Whew Hector,
>
> I see what you are getting at but... have any idea how many domains I
> am currently tracking for reputation?! How long would I have to keep
> that data?
> The bots would cause me to get google size boxes alone.
> Reminds me of the time I suggested a "auto-expiring" DNS tag. That
> went over like a lead balloon.
>
> Is there another way you could do this?

The above text should have had "MAY" in place of "SHOULD", i.e.

    The t=y tag is optional.  If defined, the domain is currently testing
    DKIM.  Verifiers SHOULD NOT treat testers any different from
    production mode signers. It SHOULD NOT be used as a way to bypass
    a failed signature classification policies. Verifiers MAY use
    this flag when tracking usage of test signatures and consider
    using the results to provide feedback to the domain owner.

In other words if program you have already has capability to track
usage you should than use 't' flag as part of that data. If you do
not have capbility to track usage or do not want to use it, then
you would not care about it.

-- 
William Leibzon
Elan Networks
william@elan.net
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html