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

Damon <deepvoice@gmail.com> Fri, 04 August 2006 16:49 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G92re-00053o-JY for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 12:49:34 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G92kg-0002i2-D1 for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 12:42:23 -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 k74GfWgh015252; Fri, 4 Aug 2006 09:41:33 -0700
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.234]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74GfOMw015222 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 09:41:24 -0700
Received: by wr-out-0506.google.com with SMTP id i31so27269wra for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 09:40:57 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=G2YxNQryCJjkwrBuwMHpgZkBdyyO+7o9Ob8jEpO3ptU9b+B7qpfNfG0ow4ud0qWIDYP+osqCRcCWQj+dBw6gcbmXRDvPHZKnrlstPT9rlQc+F7/2rh2esj/NZ8yJ/ETg+V9L8KAPt9JuLFwdF1udjLWErIm8TlBz7kWSEpJOBZU=
Received: by 10.78.120.6 with SMTP id s6mr1624604huc; Fri, 04 Aug 2006 09:40:56 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 09:40:56 -0700 (PDT)
Message-ID: <62146370608040940h2bcfb78ct13b6447d0cefad00@mail.gmail.com>
Date: Fri, 04 Aug 2006 12:40:56 -0400
From: Damon <deepvoice@gmail.com>
To: Michael Thomas <mike@mtcc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <44D37376.4020408@mtcc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060802002353.U59653@simone.iecc.com> <44D160BD.7080209@mtcc.com> <20060802223619.E86316@simone.iecc.com> <44D24A20.6050109@mtcc.com> <20060803153457.X33570@simone.iecc.com> <44D36203.2060803@mtcc.com> <20060804112731.I21459@simone.iecc.com> <44D36B4A.2050903@mtcc.com> <20060804114527.Y27352@simone.iecc.com> <44D37376.4020408@mtcc.com>
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: 244a2fd369eaf00ce6820a760a3de2e8

On 8/4/06, Michael Thomas <mike@mtcc.com> wrote:
> John L wrote:
>
> >>> I don't see the point.  That last suggestion is, to the recipient,
> >>> the equivalent of a useless "I sign some mail" since you're telling
> >>> the recipient it's OK to accept some amount of both signed and
> >>> unsigned mail.
> >>
> >
> >> For us, the amount of mail that is in the false positive quandry is
> >> really really small, though the people it would effect primiarly are
> >> people who could make it a living hell in IT. A policy which is more
> >> relaxed could, however, say that it's well worth the effort be
> >> extremely cautious about such mail -- a far higher barrier to entry
> >> than the current one-size-fits-all filters.
> >
> >
> > But you're talking about your own mail here, for which I expect that
> > you have all sorts of special treatment.
>
>
> No, I'm concerned about how others will treat it. I don't have to publish a
> policy to differentially treat that mail for myself.
>

If I read this right, I think he was saying- Do unto others...


> >
> > I'm trying to think about what I'll do when DKIM is in wide use, I get
> > mail from thousands of sources that publish SSP info.  If SSP says "I
> > sign everything" I have trouble figuring a use for it other than a
> > flat reject of unsigned messages or at least 4.9 points in a five
> > point scoring spam filter.
>
>
> That's the problem: if you do that, domains like Cisco -- or anybody else
> who uses mailing lists -- will *never* publish a "we sign everything" policy
> even though we do. I hardly think that Cisco is a outlier here, and in fact
> I expect that we'd be pretty similar to just about any medium to large
> sized business.
>
> >   I REALLY do not want an SSP that says "I sign everything, and here
> > is my estimate on a 0 to 10 scale of how much you should care."
>
> I assume that you'd complain if it boiled down to a single bit?
>
> 0: "mail from this domain may transit manglers, adjust accordingly"

So basically a 0 means: I have a published a record just so you have
to do more CPU/DNS work... because you are going to have to accept it
anyway.

> 1: "the signature should always be intact"

I think this should be assumed. If it's not, refering to the above-
Don't publish a record.


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