IETF Logo Mail Archive

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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G96qa-0004Kh-8j for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:04:44 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G96qY-0004Mi-TP for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 17:04:44 -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 k74Kx0fb019267; Fri, 4 Aug 2006 13:59:00 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74Kwpht019238 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 13:58:52 -0700
Received: by nf-out-0910.google.com with SMTP id g2so555554nfe for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 13:58:25 -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=lfCGu2N1tK9QeudD4A3rSJzEjBTKNCoZ3i7bIiph8q2byRIDnegXx0gq6wsaK7e/h0gm0JhfXlzTvBJXgyJbhN6PsDxXhRd8KVZq34eEVz5OvQyqYjQ2afU5SNE7GUiNflueSjaJbspzDRpB/2XrC6auZdDUvy0VefLu+NjXzoA=
Received: by 10.78.139.5 with SMTP id m5mr1715365hud; Fri, 04 Aug 2006 13:58:25 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 13:58:02 -0700 (PDT)
Message-ID: <62146370608041358y7b914897qdfecdc3c67a1e53d@mail.gmail.com>
Date: Fri, 04 Aug 2006 16:58:02 -0400
From: Damon <deepvoice@gmail.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <198A730C2044DE4A96749D13E167AD37C669A3@MOU1WNEXMB04.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <198A730C2044DE4A96749D13E167AD37C669A3@MOU1WNEXMB04.vcorp.ad.vrsn.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: 856eb5f76e7a34990d1d457d8e8e5b7f

> 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_

I kind of like the idea. I have an issue with implementation and all
the spamming that will be done to the yet to be developed protocol
though. We went through this "new protocol" argument with SPF. I am
hoping that people will have learned their lesson and say.. if it
doesn't break base, adding new protocols, etc. as an option isn't
automatically dismissed.

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

v2.23.0 | Report a Bug | By Email