IETF Logo Mail Archive

Re: [ietf-dkim] SSP requirements

Michael Thomas <mike@mtcc.com> Sat, 05 August 2006 20:16 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9SZl-0000uq-TR for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 16:16:49 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9SZk-0001Lc-HW for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 16:16:49 -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 k75KBsOC021910; Sat, 5 Aug 2006 13:11:55 -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 k75KBoA6021895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 13:11:51 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=819; t=1154808675; x=115 5672675; c=relaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subje ct:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=F rom:=20Michael=20Thomas=20<mike@mtcc.com>|Subject:=20Re=3A=20[ietf-dkim]=20 SSP=20requirements|Sender:=20|To:=20John=20Levine=20<johnl@iecc.com>|Cc:=20 =20ietf-dkim@mipassoc.org|Content-Transfer-Encoding:=207bit|MIME-Version:=2 01.0|Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflo we d; bh=0tFFmlSXGdqBnfp4RaFYvHoafiTsUl5UqYhwhQsh2zM=; b=LySwjXM3QSlYPLQDiHI5OoLoa3+d1tsUnG/362aj/zClbqVogeeITFsWz3rzPFUllBRiJCwb y2e7z5Wmss0r2WaxcDJoEt27JMPJbQgXrHcpEq3Nk7Q7MoNABjQMob6X;
DKIM-Signature: a=rsa-sha1; q=dns; l=819; t=1154808675; x=1155672675; c=re laxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subject:Content-Tr ansfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael=2 0Thomas=20<mike@mtcc.com>|Subject:Re=3A=20[ietf-dkim]=20SSP=20requirements| Sender:|To:John=20Levine=20<johnl@iecc.com>|Cc:=20ietf-dkim@mipassoc.org|Co ntent-Transfer-Encoding:7bit|MIME-Version:1.0|Content-Type:text/plain=3B=20 charset=3DISO-8859-1=3B=20format=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DLnZFOizGNvYWpcCctxTTPb/mIno=3D; b=CmDXvbapGPSNg+FSqMgen8ntspqzpP+eeSAj/JuxYIcSgI4wKe3ncOKN39alS8/+KvlHUBaI LKVy+WFlnc/P5OaqpSkMj7Dmy3pLsjd4d1ocmLD8z7BLA9DTv/cjq5Qr;
Received: from [192.168.0.102] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k75KBDeO000532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Aug 2006 13:11:15 -0700
Message-ID: <44D4FB5A.5020704@mtcc.com>
Date: Sat, 05 Aug 2006 13:11:06 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: [ietf-dkim] SSP requirements
References: <20060805034058.861.qmail@simone.iecc.com>
In-Reply-To: <20060805034058.861.qmail@simone.iecc.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; ACD=1.00; CLAM=0.00; COMPLY=0.00; URL=0.00; SA=0.00; HONEY=0.00;
X-Songbird: Clean, Clean
Cc: 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.2 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

John Levine wrote:

>>I can't gather requirements if I can't make any sense of what you're saying.
>>    
>>
>
>That's a reasonable concern.
>
>The fog around SSP is so opaque that I'm really wondering if it
>wouldn't make more sense to punt and wait for people to do enough
>experiments to understand what turns out to be useful.
>
That's a pretty reasonable question, frankly. The set of domains that 
would actually
benefit from SSP from the consensus I've seen seems like it's a pretty 
tiny fraction of
the internet at large and almost certainly could be handled by third 
party dnsbl-like
or accreditation schemes as well. But it may be worth it if for no other 
reason to
provide the transport, discovery, and syntax framework for putting 
goodies in for the
experiment.

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

v2.23.0 | Report a Bug | By Email