ietf-mxcomp
[Top] [All Lists]

Re: IPR Disclosure for Sender-ID

2004-08-03 10:29:35

In 
<3056(_dot_)130(_dot_)129(_dot_)132(_dot_)229(_dot_)1091551103(_dot_)squirrel(_at_)harry(_dot_)mail-abuse(_dot_)org>
 "Douglas Otis" <dotis(_at_)mail-abuse(_dot_)org> writes:

I find it difficult to imagine the licensing terms to be reasonable for
most.  See:

I agree.  From the research that I have done, it appears that the
SenderID license is incompatible with several important free software
packages (exim, postfix, spamassassin, bogofilter, etc.).

As far as I'm concerned, this makes the PRA a non-starter.  Even if
the PRA RFC makes it past the working group last call, I see very
little chance that it would make it through the general IETF last
call.

I think that Microsoft's failure to come up with an acceptable license
has created a very unfortunate waste of time for this working group.


An alternative with the _same_ feature set can be found as follows:

1) Authenticate and verify the authorization of the EHLO domain with CSV.

2) To restrict the RFC 2822 From domain, list all acceptable EHLO domains
for From domain allowed in a MARID TXT record.

Yes, this general idea has been suggested many times by many people,
including me near the beginning of the on the SPF lists and PHB during
the interim meeting.  I'm sure I'm not the first, nor will you be the
last to see this obvious idea.



So, the one I-D with the PRA algorithm could be replaced with:

http://www.ietf.org/internet-drafts/draft-schlitt-marid-spf-from-hdr-00.txt


-wayne