Sender ID: Difference between revisions

Adding short description: "Failed anti-spoofing proposal" (Shortdesc helper)
Add: date, title, authors 1-1. Changed bare reference to CS1/2. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Abductive | Category:Articles with specifically marked weasel-worded phrases from March 2021 | #UCB_Category 334/425
Line 1: Line 1:
{{Short description|Failed anti-spoofing proposal}}
{{Short description|Failed anti-spoofing proposal}}
'''Sender ID''' is an historic<ref>{{cite web| url=https://datatracker.ietf.org/doc/status-change-change-sender-id-to-historic/| title=Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic| author=Alexey Melnikov| date=7 February 2020| website=[[Internet Engineering Task Force|IETF]]}}</ref> 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 <nowiki>RFC 4406</nowiki>,<ref>{{Cite web|last=Wong|first=Meng Weng|last2=Lyon|first2=Jim|title=Sender ID: Authenticating E-Mail|url=https://tools.ietf.org/html/rfc4406.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> but there are additional parts in <nowiki>RFC 4405</nowiki>,<ref>{{Cite web|last=Katz|first=Harry|last2=Allman|first2=Eric|title=SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message|url=https://tools.ietf.org/html/rfc4405.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> <nowiki>RFC 4407</nowiki><ref name=":0">{{Cite web|last=Lyon <jimlyon@microsoft.com>|first=Jim|title=Purported Responsible Address in E-Mail Messages|url=https://tools.ietf.org/html/rfc4407.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> and <nowiki>RFC 4408</nowiki>.<ref>{{Cite web|last=Schlitt|first=Wayne|last2=Wong|first2=Meng Weng|title=Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1|url=https://tools.ietf.org/html/rfc4408.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref>
'''Sender ID''' is an historic<ref>{{cite web| url=https://datatracker.ietf.org/doc/status-change-change-sender-id-to-historic/| title=Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic| author=Alexey Melnikov| date=7 February 2020| website=[[Internet Engineering Task Force|IETF]]}}</ref> 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 <nowiki>RFC 4406</nowiki>,<ref>{{Cite web|last1=Wong|first1=Meng Weng|last2=Lyon|first2=Jim|title=Sender ID: Authenticating E-Mail|url=https://tools.ietf.org/html/rfc4406.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> but there are additional parts in <nowiki>RFC 4405</nowiki>,<ref>{{Cite web|last1=Katz|first1=Harry|last2=Allman|first2=Eric|title=SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message|url=https://tools.ietf.org/html/rfc4405.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> <nowiki>RFC 4407</nowiki><ref name=":0">{{Cite web|last=Lyon <jimlyon@microsoft.com>|first=Jim|title=Purported Responsible Address in E-Mail Messages|url=https://tools.ietf.org/html/rfc4407.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref> and <nowiki>RFC 4408</nowiki>.<ref>{{Cite web|last1=Schlitt|first1=Wayne|last2=Wong|first2=Meng Weng|title=Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1|url=https://tools.ietf.org/html/rfc4408.html|access-date=2021-03-11|website=tools.ietf.org|language=en}}</ref>


== Principles of operation ==
== Principles of operation ==
Line 32: Line 32:
== Patents ==
== Patents ==
   
   
The Sender ID proposal was the subject of controversy regarding [[licensing]] issues: [[Microsoft]] holds [[patent]]s<ref>{{cite web |url=http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |title=Archived copy |accessdate=2011-12-20 |url-status=dead |archiveurl=https://web.archive.org/web/20120414184741/http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |archivedate=2012-04-14 }}</ref><ref>http://www.internetnews.com/dev-news/article.php/3409971/Exposed+Sender+ID+Patents+Up+Debate.htm</ref> 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 some free and open source licenses, but not with the most recent version of the GPL license, version 3.x.{{Citation needed|date=March 2021}}
The Sender ID proposal was the subject of controversy regarding [[licensing]] issues: [[Microsoft]] holds [[patent]]s<ref>{{cite web |url=http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |title=Archived copy |accessdate=2011-12-20 |url-status=dead |archiveurl=https://web.archive.org/web/20120414184741/http://www.imc.org/ietf-mxcomp/mail-archive/msg04844.html |archivedate=2012-04-14 }}</ref><ref>{{Cite web|url=http://www.internetnews.com/dev-news/article.php/3409971/Exposed+Sender+ID+Patents+Up+Debate.htm|title=Exposed Sender ID Patents up Debate|date=20 September 2004}}</ref> 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 some free and open source licenses, but not with the most recent version of the GPL license, version 3.x.{{Citation needed|date=March 2021}}


==See also==
==See also==