[ietf-dkim] All done on potential SSP requirements?

[Hector Santos]

Oh well, there goes the last input :-)

This is good Stephen.  I am looking forward for Mike's work.

I can only hope Mike has taken into account all considerations and input
even from those he wishes to either ignore or disagrees with.  In my
opinion, I would rather see larger set of requirements which can then be
prune down once we have a focused list or requirements, as opposed to having
a lopsided short list which will most likely guarantee a new round of heated
battles to add more key considerations that were talked about but ignored.

The last thing the DKIM Policy or SSP proponents will want to see is a
lopsided, one-sided highly subjective conclusion for a list of requirements
that intentionally ignores key concerns from others.  It would be a waste of
time.

--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com




----- Original Message -----
From: "Stephen Farrell" <stephen.farrell at cs.tcd.ie>
To: "ietf-dkim" <ietf-dkim at mipassoc.org>
Sent: Friday, August 04, 2006 6:59 AM
Subject: [ietf-dkim] All done on potential SSP requirements?


>
> Folks,
>
> We've batted about a load of stuff this week on SSP requirements.
> Some of it was new, some repeated from earlier rounds of discussion,
> but all of stuff we needed to go over. But I guess that Mike now
> has *plenty* of material to write up his reqs-00 I-D (which
> he'll hopefully still manage to keep very short:-)
>
> Rather than try resolve our different opinions based on these list
> threads, I reckon we'd probably be better off waiting to and try
> get consensus on requirements until after we've seen them written
> down, so I suggest we let this week's discussion rest for a little
> bit while Mike writes.
>
> However, are there any potential SSP requirements that we've not
> mentioned at all this past week or so?
>
> Stephen.
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html
>