Re: [ietf-dkim] Re: Additional per user policy requirments

Damon <deepvoice@gmail.com> Wed, 06 September 2006 14:13 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GKy9E-0008Qe-EV for ietf-dkim-archive@lists.ietf.org; Wed, 06 Sep 2006 10:13:00 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKy6T-0000aw-91 for ietf-dkim-archive@lists.ietf.org; Wed, 06 Sep 2006 10:10:11 -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 k86E9B2n010031; Wed, 6 Sep 2006 07:09:15 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k86E95xK010017 for <ietf-dkim@mipassoc.org>; Wed, 6 Sep 2006 07:09:06 -0700
Received: by nf-out-0910.google.com with SMTP id n28so266405nfc for <ietf-dkim@mipassoc.org>; Wed, 06 Sep 2006 07:08:43 -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=LVBxahEZbxvPl5d3eTaEBeG78oHBLOzHxGq/Z9KmXFrp7eEIwp1HRuvsNUMlHFW+NHXGSQ3aPTndsFd0KPDLbR+kXqvA7xWWEAvWeps2Eux7CoPSAnQLhwmir6i9/ZkwrHoiQ9jiFsjMprfgIomtX7g7rd3Mu0ke0cNKVIGDFZU=
Received: by 10.49.8.4 with SMTP id l4mr917043nfi; Wed, 06 Sep 2006 07:08:43 -0700 (PDT)
Received: by 10.49.81.16 with HTTP; Wed, 6 Sep 2006 07:08:42 -0700 (PDT)
Message-ID: <62146370609060708o2b7e9efah75215c7424492a71@mail.gmail.com>
Date: Wed, 06 Sep 2006 10:08:42 -0400
From: Damon <deepvoice@gmail.com>
To: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: [ietf-dkim] Re: Additional per user policy requirments
In-Reply-To: <44FE4209.3E43@xyzzy.claranet.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44F7429A.80908@cisco.com> <C8D7F5BA-F91B-4066-9EDB-91309E4D07E7@mail-abuse.org> <42693A91-F645-441F-9DB6-BD2539A2FF5C@mail-abuse.org> <1157406595.17458.74.camel@bash.adsl-64-142-13-68> <44FCD260.19CF@xyzzy.claranet.de> <44FD1D8B.3030008@cs.tcd.ie> <44FE4209.3E43@xyzzy.claranet.de>
X-Songbird: Clean, Clean
Cc: 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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

On 9/5/06, Frank Ellermann <nobody@xyzzy.claranet.de> wrote:
> Stephen Farrell wrote:
>
> > As Doug said that predates the WG.
>
> The WG charter says "policy" (incl. the quotes) and mentions
> draft-allman-dkim-ssp
>
> > once reqs-01 is out. we're planning to move back into
> > using the issue tracker, so you can of course raise this
> > as an issue if you like
>
> Yes.  I fear the SSP adventure is over, PRA is bad, anything
> else is impossible.  On the SPF lists folks tried for years
> to invent wild and wonderful new "identities" in addition to
> the Return-Path, and they all failed miserably, incompatible
> with 2822, only PRA makes remotely sense.
>
> This "first address of the From" can't work.  Maybe you could
> get the RFC 2822 author as external expert about this idea,
> IIRC he was also invited to comment on some MARID proposals.
>
> Frank
>

Only because people insist that it *must* work in every scheme they can make up.
I believe that we could implement what we have discussed and the fact
that it won't work for everybody should be an asterisk. It will work
for most systems and I am comfortable with that. Implementation is not
a requirement.


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