[ietf-dkim] SSP issues

Jim Fenton <fenton@cisco.com> Wed, 30 May 2007 22:26 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 1HtWd0-0002DX-8m for ietf-dkim-archive@lists.ietf.org; Wed, 30 May 2007 18:26:50 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtWcy-0000pT-Pm for ietf-dkim-archive@lists.ietf.org; Wed, 30 May 2007 18:26:50 -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 l4UMNAQu022946; Wed, 30 May 2007 15:23:16 -0700
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4UMN5aO022902 for <ietf-dkim@mipassoc.org>; Wed, 30 May 2007 15:23:05 -0700
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 30 May 2007 15:23:05 -0700
X-IronPort-AV: i="4.14,595,1170662400"; d="scan'208"; a="156610743:sNHT41395383"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l4UMN5cd007343 for <ietf-dkim@mipassoc.org>; Wed, 30 May 2007 15:23:05 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l4UMN024029517 for <ietf-dkim@mipassoc.org>; Wed, 30 May 2007 22:23:05 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 May 2007 15:23:02 -0700
Received: from dhcp-171-71-97-219.cisco.com ([171.71.97.219]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 30 May 2007 15:23:02 -0700
Message-ID: <465DF93D.1080306@cisco.com>
Date: Wed, 30 May 2007 15:22:53 -0700
From: Jim Fenton <fenton@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: IETF DKIM WG <ietf-dkim@mipassoc.org>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 May 2007 22:23:02.0626 (UTC) FILETIME=[1639AC20:01C7A309]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1359; t=1180563785; x=1181427785; c=relaxed/simple; s=sjdkim3002; 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:=20SSP=20issues |Sender:=20; bh=Fi7GSZxRn/v+MtB8MZ+vcJTEQMPBWlfcD/eilKBH1iw=; b=OTRhDHFCTAVDrG2RunWS7kbVsGeCyfCal0WD3YDDtEF17yJWvmLPB2A0SUsTPLoqFyBuaTv2 Pt0vGGSAidiVFFztoyPjlG7OdXEAtA1RwJEZHKOmabU6sytPXXfxXorr;
Authentication-Results: sj-dkim-3; header.From=fenton@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Songbird: Clean, Clean
Subject: [ietf-dkim] SSP issues
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: 1ac7cc0a4cd376402b85bc1961a86ac2

What we had hoped to do in the next revision of the allman-ssp draft was to unify it as much as possible with Phill Hallam-Baker's draft.  I opened three new issues on April 16 that I think need to be resolved in order to do that.

(1) Use of XPTR records for SSP.  The idea here is to create a more general policy mechanism that can be used by WS-* and such.  There were about 20 messages discussing this from 5 people.  I'm not reading a clear consensus on this.

(2) SSP record type (TXT vs. something new). Only 4 messages in discussion, mostly saying "if you support TXT, don't bother with anything else."  Again, no clear consensus.

(3) Upward query vs. wildcard publication.  27 messages in discussion from 15 people.  Most of the discussion was a rehash of the idea of associating semantics with DNS zone-cuts, which we had already discussed and rejected.  I have also been trying to get an opinion from DNSOP on the idea of a one-level upward search (which I think solves 90% of the problem), but haven't gotten any response.

So I don't know what to write in a revision of the draft.  I could just write my opinions, but that's basically what's in the draft-allman-dkim-ssp-02 draft already and doesn't make any progress toward unifying the different proposals.  I want to get something done soon, well before the July 2 deadline.

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