Re: [ietf-dkim] New Issue: Use of XPTR records in SSP

Jim Fenton <fenton@cisco.com> Wed, 18 April 2007 03:41 UTC

Return-path: <ietf-dkim-bounces@mipassoc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1He135-0007sG-Ld for ietf-dkim-archive@lists.ietf.org; Tue, 17 Apr 2007 23:41:39 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1He135-0002H4-4b for ietf-dkim-archive@lists.ietf.org; Tue, 17 Apr 2007 23:41:39 -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 l3I3Zr8p004264; Tue, 17 Apr 2007 20:35:53 -0700
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l3I3ZjuP004246 for <ietf-dkim@mipassoc.org>; Tue, 17 Apr 2007 20:35:46 -0700
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 17 Apr 2007 23:35:46 -0400
X-IronPort-AV: i="4.14,420,1170651600"; d="scan'208"; a="57929340:sNHT45551088"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3I3ZkWl022403; Tue, 17 Apr 2007 23:35:46 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3I3ZkGd005617; Wed, 18 Apr 2007 03:35:46 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Apr 2007 23:35:45 -0400
Received: from [63.138.97.208] ([10.82.218.16]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Apr 2007 23:35:45 -0400
Message-ID: <46259208.5090604@cisco.com>
Date: Tue, 17 Apr 2007 20:35:36 -0700
From: Jim Fenton <fenton@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Douglas Otis <dotis@mail-abuse.org>
Subject: Re: [ietf-dkim] New Issue: Use of XPTR records in SSP
References: <462415FC.9000807@cisco.com> <F814A440-D552-4A58-806E-BF33013F20E4@mail-abuse.org>
In-Reply-To: <F814A440-D552-4A58-806E-BF33013F20E4@mail-abuse.org>
X-Enigmail-Version: 0.94.3.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Apr 2007 03:35:45.0517 (UTC) FILETIME=[A60461D0:01C7816A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1191; t=1176867346; x=1177731346; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fenton@cisco.com; z=From:=20Jim=20Fenton=20<fenton@cisco.com> |Subject:=20Re=3A=20[ietf-dkim]=20New=20Issue=3A=20Use=20of=20XPTR=20reco rds=20in=20SSP |Sender:=20 |To:=20Douglas=20Otis=20<dotis@mail-abuse.org>; bh=X0vQuRADg5mpUxs7VBsg1P+JdeKuNLi54je+oFUnrKQ=; b=BQRSJ7MPzI+Rrtfk1Fo7gQ4YuutKmX7vD+WVtfayJiNWkdL5c4diKbd1oJAChYk8AaFLHcB/ EXfK03oDPzqy+5SWCLfDCP3BSzhglYDclypZOmOH62r19VWosO4rNiVb;
Authentication-Results: rtp-dkim-2; header.From=fenton@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Songbird: Clean, Clean
Cc: "ietf-dkim@mipassoc.org" <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: 0bc60ec82efc80c84b8d02f4b0e4de22

Douglas Otis wrote:
>
> On Apr 16, 2007, at 5:34 PM, Jim Fenton wrote:
>
>> This is the first of a few issues that come in trying to rationalize
>> at least two of the SSP proposals, draft-hallambaker-dkimpolicy-00
>> and draft-allman-dkim-ssp.  I'd like to keep the issues separate,
>> because I think they're largely independent, so please respond in
>> kind if at all possible.
>
> This assumes a simple authorization scheme is not effective at
> protecting a principal domain.  For example, if the industry creates a
> list of domains used for the purpose of registries, then this would
> identify precisely which domain should be queried.  As there are some
> TLDs publishing MX records, such a list becomes even more important
> from the prospect of limiting the scope of TLDs with respect to DKIM
> sub-domain validations.

I'm not clear on specifically who "the industry" is that you're
referring to that creates and maintains the list.  It sounds like you're
proposing some other kind of non-self-published database that identifies
mailing domains.  It doesn't sound like the SSP of which we just
completed the last-call of the requirements document.

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