----- Original Message -----
From: "Hallam-Baker, Phillip" <pbaker(_at_)verisign(_dot_)com>
To: "william(at)elan.net" <william(_at_)elan(_dot_)net>; "Edward Shallow"
<ed(_dot_)shallow(_at_)rogers(_dot_)com>
Cc: "Hector Santos" <hsantos(_at_)santronics(_dot_)com>; "Andrew Newton"
<andy(_at_)hxr(_dot_)us>;
"IETF MASS WG" <ietf-mailsig(_at_)imc(_dot_)org>
Sent: Thursday, June 02, 2005 6:47 PM
Subject: RE: Yahoo!'s DomainKeys and Cisco's IIM have merged
As a basic point of principle here, I care about there being one common
spec here more than anything else, including whether the spec actually
works.
We are engineers, if the spec is broken we can and we will fix it.
What I am afraid is how this common spec and its possible exclusive nature
might define how SMTP behaves to the extent that it is more than just the
protocol itself by the framework.
What if a better mouse trap is invented?
I agree 100% with the merging of IIM/DK, the concern from my standpoint it
show it will fit into the SMTP process and how SMTP vendors will address the
non-IIM/DK market place. If a system still needs to use other protocols,
then IIM/DK needs to be compliant with these other methods as well.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com