Re: [ietf-dkim] SSP issues
Jim Fenton <fenton@cisco.com> Fri, 01 June 2007 19:04 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 1HuCQH-0005QA-IA for ietf-dkim-archive@lists.ietf.org; Fri, 01 Jun 2007 15:04:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuCQF-0004ag-2N for ietf-dkim-archive@lists.ietf.org; Fri, 01 Jun 2007 15:04:29 -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 l51J2jrP004662; Fri, 1 Jun 2007 12:02:48 -0700
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l51J2bmS004637 for <ietf-dkim@mipassoc.org>; Fri, 1 Jun 2007 12:02:37 -0700
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 01 Jun 2007 12:02:41 -0700
X-IronPort-AV: i="4.16,373,1175497200"; d="scan'208"; a="3877637:sNHT23476524"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l51J2fVJ022516; Fri, 1 Jun 2007 12:02:41 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l51J2YV5019541; Fri, 1 Jun 2007 19:02:39 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Jun 2007 12:02:36 -0700
Received: from dhcp-171-71-97-219.cisco.com ([171.71.97.219]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Jun 2007 12:02:36 -0700
Message-ID: <46606D41.30103@cisco.com>
Date: Fri, 01 Jun 2007 12:02:25 -0700
From: Jim Fenton <fenton@cisco.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [ietf-dkim] SSP issues
References: <465DF93D.1080306@cisco.com> <466016F5.50900@cs.tcd.ie>
In-Reply-To: <466016F5.50900@cs.tcd.ie>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Jun 2007 19:02:36.0564 (UTC) FILETIME=[6AF5BD40:01C7A47F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3017; t=1180724561; x=1181588561; c=relaxed/simple; s=sjdkim5002; 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]=20SSP=20issues |Sender:=20; bh=TqDh5+HBnZ63NLm5HnpqTQ8LUnzkGylPo1gLr8H1m3I=; b=KoawIcfLZEhXx8JWB2M9jTRNgoBA8dnyZcnJbQBmS/eUYaYGmZw50FstNYtT78Or4eQNmknW C++RJydhqxRdZXZAjCEY/DHSL6Y7/gKdwEbGJuPkK0Van0gIzZgwsGYQ;
Authentication-Results: sj-dkim-5; header.From=fenton@cisco.com; dkim=pass ( sig from cisco.com/sjdkim5002 verified; );
X-Songbird: Clean, Clean
Cc: IETF DKIM WG <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: 0fa76816851382eb71b0a882ccdc29ac
Works for me. Actually, due to vacation schedules, I need to accelerate that a bit and get the draft submitted by June 15. So, WG participants (especially the 'usual suspects'), let's hear from you. -Jim Stephen Farrell wrote: > > Hi Jim, > > Barry and I would like us to do the following: > > Continue the discussion on the list for a few more days since > not all the usual suspects have reacted yet (please do!) and > the context is slightly different (with XPTR anyway) from the > (many;-) other times we've discussed these topics in the past. > > Then, (say the week after next?) you get the co-authors of > draft-ietf-dkim-ssp-00 together and just pick your current > best answer for each relevant issue and submit the -00 > around June 24. If you think some concalls/jabbering or > whatever will help there, just let Barry & I know. > > Then, we'll look for offers of concrete alternative text > to be sent to the list before Chicago. > > In Chicago we discuss. With one another and with the > DNS folks. > > And then (back on the list) we resolve each of these well-worn > issues once and for all (using strawpolls or whatever's > necessary) over the following weeks and aim for a draft on > which we can have WGLC in September. (With the reality being > that it'll be October before we're ready.) > > Regards > Stephen & Barry. > > > Jim Fenton wrote: >> 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 >> > _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
- [ietf-dkim] SSP issues Jim Fenton
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues Michael Thomas
- Re: [ietf-dkim] SSP issues william(at)elan.net
- Re: [ietf-dkim] SSP issues Douglas Otis
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues william(at)elan.net
- Re: [ietf-dkim] SSP issues Michael Thomas
- Re: [ietf-dkim] SSP issues Douglas Otis
- Re: [ietf-dkim] SSP issues Hector Santos
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues John Levine
- Re: [ietf-dkim] SSP issues John L
- Re: [ietf-dkim] SSP issues John L
- Re: [ietf-dkim] SSP issues Graham Murray
- Re: [ietf-dkim] Domain Lists versus SSP Wildcards Douglas Otis
- RE: [ietf-dkim] SSP issues Hallam-Baker, Phillip
- Re: [ietf-dkim] SSP issues Jim Fenton
- Re: [ietf-dkim] SSP issues Jim Fenton
- RE: [ietf-dkim] SSP issues Bill.Oxley
- Re: [ietf-dkim] SSP issues Jim Fenton
- RE: [ietf-dkim] SSP issues Bill.Oxley
- Re: [ietf-dkim] Domain Lists versus SSP wildcards Douglas Otis
- Re: [ietf-dkim] SSP issues Stephen Farrell
- Re: [ietf-dkim] SSP issues Jim Fenton
- Re: [ietf-dkim] SSP issues Arvel Hathcock
- Re: [ietf-dkim] SSP issues Hector Santos
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues Hector Santos
- Re: [ietf-dkim] SSP issues TXT and no wildcards. Douglas Otis
- Re: [ietf-dkim] SSP issues Eliot Lear
- Re: [ietf-dkim] SSP issues Hector Santos
- Re: [ietf-dkim] SSP issues Eliot Lear
- [ietf-dkim] Single Organization TXT Lookup with M… Hector Santos
- [ietf-dkim] Re: Single Organization TXT Lookup wi… Douglas Otis
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues Douglas Otis
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues J.D. Falk
- Re: [ietf-dkim] SSP issues Scott Kitterman
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues Dave Crocker
- Re: [ietf-dkim] SSP issues John Levine
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: [ietf-dkim] TXT wildcards SSP issues John Levine
- Re: [ietf-dkim] TXT wildcards SSP issues Steve Atkins
- Re: [ietf-dkim] SSP issues Douglas Otis
- Re: [ietf-dkim] TXT wildcards SSP issues william(at)elan.net
- Re: [ietf-dkim] TXT wildcards SSP issues John Levine
- RE: [ietf-dkim] SSP issues Hallam-Baker, Phillip
- RE: [ietf-dkim] SSP issues Hallam-Baker, Phillip
- RE: [ietf-dkim] SSP issues Hallam-Baker, Phillip
- RE: [ietf-dkim] TXT wildcards SSP issues Hallam-Baker, Phillip
- MX dot RE: [ietf-dkim] TXT wildcards SSP issues Hallam-Baker, Phillip
- Re: MX dot RE: [ietf-dkim] TXT wildcards SSP issu… Steve Atkins
- RE: MX dot RE: [ietf-dkim] TXT wildcards SSP issu… Hallam-Baker, Phillip
- Re: [ietf-dkim] TXT wildcards SSP issues Scott Kitterman
- MX dot was (Re: [ietf-dkim] TXT wildcards SSP iss… Steve Atkins
- Re: [ietf-dkim] TXT wildcards SSP issues Douglas Otis
- Re: [ietf-dkim] TXT wildcards SSP issues Scott Kitterman
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Scott Kitterman
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Eliot Lear
- Re: [ietf-dkim] TXT wildcards SSP issues Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Steve Atkins
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Scott Kitterman
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Stephen Farrell
- Re: [ietf-dkim] SSP issues Steve Atkins
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Charles Lindsey
- RE: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hallam-Baker, Phillip
- Re: [ietf-dkim] Re: Single Organization TXT Looku… Damon
- Re: [ietf-dkim] SSP issues Damon
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Michael Thomas
- Re: [ietf-dkim] Re: Single Organization TXT Looku… Douglas Otis
- Re: [ietf-dkim] SSP issues Jim Fenton
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Damon
- Re: [ietf-dkim] SSP issues Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Stephen Farrell
- Re: [ietf-dkim] SSP issues Michael Thomas
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… stephen.farrell
- RE: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Bill.Oxley
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- [ietf-dkim] I think we can punt the hard stuff as… Hallam-Baker, Phillip
- [ietf-dkim] Re: I think we can punt the hard stuf… Michael Thomas
- [ietf-dkim] RE: I think we can punt the hard stuf… Hallam-Baker, Phillip
- [ietf-dkim] Re: I think we can punt the hard stuf… Michael Thomas
- [ietf-dkim] RE: I think we can punt the hard stuf… Hallam-Baker, Phillip
- Re: [ietf-dkim] I think we can punt the hard stuf… Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- [ietf-dkim] Re: I think we can punt the hard stuf… Michael Thomas
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- Re: [ietf-dkim] SSP issues Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- RE: [ietf-dkim] RE: I think we can punt the hard … Bill.Oxley
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Damon
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- RE: [ietf-dkim] RE: I think we can punt the hard … Bill.Oxley
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Charles Lindsey
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- RE: [ietf-dkim] RE: I think we can punt the hard … Bill.Oxley
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Damon
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- [ietf-dkim] lets add one more shall we? Bill.Oxley
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] lets add one more shall we? Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- Re: [ietf-dkim] lets add one more shall we? Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Stephen Farrell
- RE: [ietf-dkim] RE: I think we can punt the hard … Hallam-Baker, Phillip
- [ietf-dkim] "I sign everything" != "No mail" Michael Thomas
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jon Callas
- [ietf-dkim] SSP DOMAIN Discovery Relationship to … Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Steve Atkins
- RE: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Bill.Oxley
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Damon
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Michael Thomas
- Re: [ietf-dkim] lets add one more shall we? Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Steve Atkins
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jon Callas
- Re: [ietf-dkim] RE: I think we can punt the hard … Jim Fenton
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jim Fenton
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] lets add one more shall we? Charles Lindsey
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] lets add one more shall we? Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jim Fenton
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… william(at)elan.net
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Damon
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Steve Atkins
- [ietf-dkim] Zone Files Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jim Fenton
- Re: [ietf-dkim] lets add one more shall we? Charles Lindsey
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jon Callas
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jon Callas
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: [ietf-dkim] Zone Files Charles Lindsey
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Wietse Venema
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- RE: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Bill.Oxley
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] Zone Files Hector Santos
- Re: [ietf-dkim] Zone Files william(at)elan.net
- Re: [ietf-dkim] Zone Files Steve Atkins
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… J.D. Falk
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… SM
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- RE: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Patrick Peterson
- RE: [ietf-dkim] RE: I think we can punt the hard … Patrick Peterson
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Jim Fenton
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Jim Fenton
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … John Levine
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Wietse Venema
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… John Levine
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Hector Santos
- Re: [ietf-dkim] lets add one more shall we? Jeff Macdonald
- Re: [ietf-dkim] RE: I think we can punt the hard … Jeff Macdonald
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … John L
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Douglas Otis
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Jim Fenton
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: [ietf-dkim] RE: I think we can punt the hard … Hector Santos
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Steve Atkins
- Re: MX dot was (Re: [ietf-dkim] TXT wildcards SSP… Douglas Otis