IETF Logo Mail Archive

Re: [ietf-dkim] SSP requirements

Damon <deepvoice@gmail.com> Mon, 07 August 2006 16:30 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GA7zp-0007cU-1z for ietf-dkim-archive@lists.ietf.org; Mon, 07 Aug 2006 12:30:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GA7zn-0005bo-Mq for ietf-dkim-archive@lists.ietf.org; Mon, 07 Aug 2006 12:30:29 -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 k77GUBR7010517; Mon, 7 Aug 2006 09:30:11 -0700
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k77GU1jN010471 for <ietf-dkim@mipassoc.org>; Mon, 7 Aug 2006 09:30:02 -0700
Received: by wx-out-0506.google.com with SMTP id t10so105516wxc for <ietf-dkim@mipassoc.org>; Mon, 07 Aug 2006 09:29:32 -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=bFqqOKUfzvDd6X+NmaezZX6BXAfk9M7jvZKKS3/yKbuziDN4F82IilPb+RtZvDrVkWUaOcPg1SUfgKoC+AdC/j+eLpoSFd5NjNO5ESRpHntExwsIAI4z2mQ9gpHlKxT4kkP1yiMWQDp1lUS94t03UhC+sooxJMKg1HqthRoj/RE=
Received: by 10.78.183.8 with SMTP id g8mr2449015huf; Mon, 07 Aug 2006 09:29:32 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Mon, 7 Aug 2006 09:29:31 -0700 (PDT)
Message-ID: <62146370608070929g4195761fj3d8de7cde1e19dcc@mail.gmail.com>
Date: Mon, 07 Aug 2006 12:29:31 -0400
From: Damon <deepvoice@gmail.com>
To: Douglas Otis <dotis@mail-abuse.org>
Subject: Re: [ietf-dkim] SSP requirements
In-Reply-To: <6D2FE363-D3F0-4242-BAB9-9E89EC5567BA@mail-abuse.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060805034058.861.qmail@simone.iecc.com> <44D4FB5A.5020704@mtcc.com> <20060805163953.Q47527@simone.iecc.com> <6D2FE363-D3F0-4242-BAB9-9E89EC5567BA@mail-abuse.org>
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: d6b246023072368de71562c0ab503126

> The DKIM authentication convention could be noted at the EHLO by
> having the host-name for the client utilize a "_dkim." prefix.  This
> prefix signals the mode of authentication made possible by the DKIM
> convention claiming this prefix.  This could fall into the same realm
> as the key, and From policy records.  There would be zero additional
> transactions needed to support this form of client authentication,
> assuming an A record lookup would be performed anyway.  The "_dkim."
> prefix can make this authentication more stringent, instead of this
> being allowed to fail as currently defined in RFC2821.
>

I like this idea...
But not for stringency.. more for reducing the number of lookups.

Regards,
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