IETF Logo Mail Archive

Re: [ietf-dkim] New Issue: New resource record type

Jim Fenton <fenton@cisco.com> Mon, 16 October 2006 11:20 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZQW9-0003jd-9i for ietf-dkim-archive@lists.ietf.org; Mon, 16 Oct 2006 07:20:25 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZQW4-0006xb-S4 for ietf-dkim-archive@lists.ietf.org; Mon, 16 Oct 2006 07:20:25 -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 k9GBIkkD009566; Mon, 16 Oct 2006 04:18:52 -0700
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9GBIbM4009538 for <ietf-dkim@mipassoc.org>; Mon, 16 Oct 2006 04:18:37 -0700
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 16 Oct 2006 04:18:20 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9GBIKmg030535; Mon, 16 Oct 2006 04:18:20 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9GBIJin012532; Mon, 16 Oct 2006 04:18:19 -0700 (PDT)
Received: from [10.21.120.179] (sjc-vpn6-179.cisco.com [10.21.120.179]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k9GB6Ra6013428; Mon, 16 Oct 2006 04:06:27 -0700
Message-ID: <45336A79.3040008@cisco.com>
Date: Mon, 16 Oct 2006 04:18:17 -0700
From: Jim Fenton <fenton@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: [ietf-dkim] New Issue: New resource record type
References: <200610141114.40215.ietf-dkim@kitterman.com> <45329650.30202@cisco.com> <4532EEFE.2030106@cisco.com> <45331F7D.4060109@cisco.com>
In-Reply-To: <45331F7D.4060109@cisco.com>
X-Enigmail-Version: 0.94.1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Authentication-Results: sj-dkim-3.cisco.com; header.From=fenton@cisco.com; dkim=pass ( sig from cisco.com verified; );
DKIM-Signature: a=rsa-sha1; q=dns; l=575; t=1160997500; x=1161861500; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fenton@cisco.com; z=From:Jim=20Fenton=20<fenton@cisco.com> |Subject:Re=3A=20[ietf-dkim]=20New=20Issue=3A=20New=20resource=20record=20type; X=v=3Dcisco.com=3B=20h=3DA77+zW7e1vJxD2ughhZFxYH9GMI=3D; b=TwQvScoL3rfIlR3Q5I5bXUnGsXEaQgGldJg8ugH+kDJfltShYp91TTlrnY7C8bbvNmy4K5MY irmop0ib423ugNzI1oGNsU0Y7RxL93GlkIoI4tTYIifGOCcH+f8400rX;
X-Songbird: Clean, Clean
Cc: Scott Kitterman <ietf-dkim@kitterman.com>, 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

Eliot Lear wrote:
> Jim,
>
> Fair points.  One possibility, by the way, is that we use the SAME
> prefix but simply with new attributes.  That way you get the whole thing
> in one shot.
>   
I'm not sure what you have in mind here.  One of the benefits of using a
new RR type is that it may allow us to get away from the use of a prefix
entirely, which in turn may shorten the search process by detecting
nonexistent domains more easily.  I'm not certain how well this
mechanism works, but you can see what I'm talking about in
draft-allman-dkim-ssp-02.

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

v2.23.0 | Report a Bug | By Email