Sender ID: Difference between revisions
clean up using AWB |
Moved "patent" stuff to separate section adding "fact" tag: They wanted a patent, but did they ever get it? |
||
| Line 1: | Line 1: | ||
'''Sender ID''' is an anti-[[E-mail spoofing|spoofing]] proposal from the former [[MARID]] [[IETF]] | '''Sender ID''' is an anti-[[E-mail spoofing|spoofing]] proposal from the former [[MARID]] [[IETF]] working group that tried to join [[Sender Policy Framework]] (SPF) and Caller ID. Sender ID is defined primarily in Experimental RFC 4406, but additional parts in RFC 4405, RFC 4407 and RFC 4408. | ||
== Principles of operation == | == Principles of operation == | ||
| Line 7: | Line 5: | ||
Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions. This article will mostly discuss just these differences. | Sender ID is heavily based on [[Sender Policy Framework|SPF]], with only a few additions. This article will mostly discuss just these differences. | ||
* | * They both are TXT records published by the [[Domain Name System|DNS]] servers of a domain name. | ||
* | * They both give rules that the owner of this domain name intends to respect in all headers of his genuinely sent emails. | ||
* | * They differ on what rules they apply to what fields contained in the message header. | ||
* | * They both want to be used by some [[E-mail client|mail clients]] and [[Web-based email|web mail servers]] (and some [[Mail transfer agent|MTA]] servers) to distinguish good mail from junk by helping to authenticate the sender. | ||
Syntactically, SPF and Sender ID are almost identical: | Syntactically, SPF and Sender ID are almost identical: | ||
| Line 102: | Line 100: | ||
Sender ID cannot advance on the [[IETF]] standards track without | Sender ID cannot advance on the [[IETF]] standards track without | ||
addressing the incompatibility with a MUST in RFC 2822. | addressing the incompatibility with a MUST in RFC 2822. | ||
== Intellectual Property == | |||
The Sender ID proposal was the subject of controversy regarding [[intellectual property]] [[licensing]] issues: [[Microsoft]] holds [[patent]]s {{fact}} on key parts of Sender ID and used to license those patents under terms that were not compatible with the [[GNU General Public License]] and which were considered problematic for [[free software]] [[implementation]]s in general. On October 23, 2006, Microsoft placed those patents under the [[Open Specification Promise]], which is compatible with free and open source licenses. | |||
==See also== | ==See also== | ||