[ietf-dkim] draft-ietf-dkim-threats-02 nit//Claim Responsibility for email address use?
Douglas Otis <dotis@mail-abuse.org> Thu, 06 April 2006 20:09 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRanN-0005EC-L2 for ietf-dkim-archive@lists.ietf.org; Thu, 06 Apr 2006 16:09:33 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRanN-0005ul-9U for ietf-dkim-archive@lists.ietf.org; Thu, 06 Apr 2006 16:09:33 -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 k36JphVK002684; Thu, 6 Apr 2006 12:51:43 -0700
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k36Jpex4002632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Thu, 6 Apr 2006 12:51:40 -0700
Received: from [168.61.10.151] (SJC-Office-DHCP-151.Mail-Abuse.ORG [168.61.10.151]) (authenticated bits=0) by a.mail.sonic.net (8.13.6/8.13.3) with ESMTP id k36Jp3bG003255 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for <ietf-dkim@mipassoc.org>; Thu, 6 Apr 2006 12:51:04 -0700
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Transfer-Encoding: 7bit
Message-Id: <C86277B2-79D9-4019-A752-1E5F82790916@mail-abuse.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: IETF-DKIM <ietf-dkim@mipassoc.org>
From: Douglas Otis <dotis@mail-abuse.org>
Date: Thu, 06 Apr 2006 12:51:25 -0700
X-Mailer: Apple Mail (2.749.3)
X-Songbird: Clean, Clean
Subject: [ietf-dkim] draft-ietf-dkim-threats-02 nit//Claim Responsibility for email address use?
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: 52e1467c2184c31006318542db5614d5
,---- |1. Introduction | | DomainKeys Identified Mail (DKIM) [I-D.ietf-dkim-base] defines a | mechanism by which email messages can be cryptographically signed, | permitting a signing domain to claim responsibility for the use of a | given email address. '---- The signature establishes that the signing-domain has handled the message. DKIM does not require an email-address be associated with a signing-domain. Even when a signing-domain can be seen as associated with an email-address in the message, there is no safe assurance the signing-domain is authoritative or controls use of the email- address. This statement is confusing the DKIM base with questionable concepts found in SSP. This statement in isolation implies the goal of DKIM is to establish constrains on the use of one's email-address. A provider may elect to sign all messages irrespective of the email-address utilized by their customers, for example. Suggested correction: : DomainKeys Identified Mail (DKIM) [I-D.ietf-dkim-base] defines a : mechanism by which email messages can be cryptographically signed, : permitting a signing domain to be identified as handling the signed : portion of the message. -Doug _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
- [ietf-dkim] draft-ietf-dkim-threats-02 nit//Claim… Douglas Otis
- [ietf-dkim] draft-ietf-dkim-threats-02 nit//Claim… Douglas Otis