IETF Logo Mail Archive

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

Michael Thomas <mike@mtcc.com> Mon, 16 October 2006 12:56 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZS1F-00074P-5K for ietf-dkim-archive@lists.ietf.org; Mon, 16 Oct 2006 08:56:37 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZS1B-00004y-OR for ietf-dkim-archive@lists.ietf.org; Mon, 16 Oct 2006 08:56:37 -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 k9GCqAXM026752; Mon, 16 Oct 2006 05:52:13 -0700
Received: from fasolt.mtcc.com (adsl-216-102-208-10.dsl.snfc21.pacbell.net [216.102.208.10]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9GCpsth026708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Mon, 16 Oct 2006 05:51:55 -0700
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1211; t=1161003095; x=1161867095; c=relaxed/simple; s=dicks.drop.kirkwood; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[ietf-dkim]=20New=20Issue=3A=20New=20resource=20recor d=20type |Sender:=20 |To:=20Jim=20Fenton=20<fenton@cisco.com> |Cc:=20Eliot=20Lear=20<lear@cisco.com>, =20=0A=20Scott=20Kitterman=20<ietf -dkim@kitterman.com>,=0A=20=20ietf-dkim@mipassoc.org |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0 |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; bh=Bbd8xe7RN7d1HJeK30cqqxIwsOBeQ5ULP7YU6BacW5Y=; b=Jbp3V/mOutVZt7E94+JK8ZVcnd6RTlorTDkGD1CqKJ1FkjlZ3ZsYdP8T8knTqT4leNvpWuDf s7RkXWanBanHLFod669vjRiDCAhx9sBn5XF+bwMNv5YgUvdzfD3Gj08C;
DKIM-Signature: a=rsa-sha1; q=dns; l=1211; t=1161003095; x=1161867095; c=relaxed/simple; s=dicks.drop.kirkwood; h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael=20Thomas=20<mike@mtcc.com> |Subject:Re=3A=20[ietf-dkim]=20New=20Issue=3A=20New=20resource=20recor d=20type |Sender: |To:Jim=20Fenton=20<fenton@cisco.com> |Cc:Eliot=20Lear=20<lear@cisco.com>, =20=0A=20Scott=20Kitterman=20<ietf -dkim@kitterman.com>,=0A=20=20ietf-dkim@mipassoc.org |Content-Transfer-Encoding:7bit |MIME-Version:1.0 |Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DDjx+2/XtFekDcAHg1c+6SkvaYhc=3D; b=J95BZxFs12n1V1i6TGigPL2rf0i3sVGgredUjgPgJjg1n19g4aNWUKAYUg6l/ns8+n1YPPKf yrErBrTp+5gQnj4MEGF18Zx7gT2pszHY0veXbxC37dOR2YIz6lPDu0Jf;
Received: from [216.102.208.10] (IDENT:U2FsdGVkX1+1O4ZtbDe+eJqfwBkOijCLtgq5A4vgNyU@fasolt.mtcc.com [216.102.208.10] (may be forged)) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k9GCpYHh001165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Oct 2006 05:51:34 -0700
Message-ID: <45338055.9060309@mtcc.com>
Date: Mon, 16 Oct 2006 05:51:33 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Thunderbird/1.0.6 Fedora/1.0.6-1.1.fc3 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Fenton <fenton@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> <45336A79.3040008@cisco.com>
In-Reply-To: <45336A79.3040008@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: fasolt.mtcc.com; header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; ); header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; );
X-XIPE-SCORES: dispose=pass; (null)=1.00; URL=0.00; HONEY=0.00; COMPLY=0.00; CLAM=0.00; EOM=0.00;
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.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

 From a requirements standpoint, I'd just assume we not go into this level
of detail. The high level bits of deterministic number of lookups and other
things seem fairly uncontroversial, but the engineering/deployment 
considerations
of the RR problem require a lot more detail and/or experimental evidence 
to be
examined. I don't think that a requirements document is the right venue 
to run
that debate.

       Mike

Jim Fenton wrote:

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

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

v2.23.0 | Report a Bug | By Email