Sender ID: Difference between revisions
m Dating maintenance tags: {{Cleanup HTML}} |
Replaced deprecated <tt> with <code>, as per instructions in Category:Articles_with_HTML_markup |
||
| Line 1: | Line 1: | ||
'''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 there are additional parts in RFC 4405, RFC 4407 and RFC 4408. | '''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 there are additional parts in RFC 4405, RFC 4407 and RFC 4408. | ||
| Line 10: | Line 9: | ||
However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in RFC 4407 a Purported Responsible Address (PRA) as well as a set of heuristic rules to establish this address from the many typical headers in an email. | However, there are many similar email header fields that all contain sending party information; therefore Sender ID defines in RFC 4407 a Purported Responsible Address (PRA) as well as a set of heuristic rules to establish this address from the many typical headers in an email. | ||
Syntactically, Sender ID is almost identical to SPF except that < | Syntactically, Sender ID is almost identical to SPF except that <code>v=spf1</code> is replaced with one of: | ||
* < | * <code>spf2.0/mfrom</code> - meaning to verify the envelope sender address just like SPF. | ||
* < | * <code>spf2.0/mfrom,pra</code> or <code>spf2.0/pra,mfrom</code> - meaning to verify both the envelope sender and the PRA. | ||
* < | * <code>spf2.0/pra</code> - meaning to verify only the PRA. | ||
The only other syntactical difference is that Sender ID offers the feature of ''positional'' modifiers not supported in SPF. In practice, so far no ''positional'' modifier has been specified in any Sender ID implementation. | The only other syntactical difference is that Sender ID offers the feature of ''positional'' modifiers not supported in SPF. In practice, so far no ''positional'' modifier has been specified in any Sender ID implementation. | ||
| Line 28: | Line 27: | ||
The ''pra'' has the disadvantage that forwarders and | The ''pra'' has the disadvantage that forwarders and | ||
mailing lists can only support it by modifying the mail header, | mailing lists can only support it by modifying the mail header, | ||
e.g. insert a < | e.g. insert a <code>Sender</code> or <code>Resent-Sender</code>. The | ||
latter violates RFC 2822 and can be incompatible with RFC 822. | latter violates RFC 2822 and can be incompatible with RFC 822. | ||
| Line 37: | Line 36: | ||
added their host name to the reverse path in the MAIL FROM. | added their host name to the reverse path in the MAIL FROM. | ||
The most problematic point in the core Sender ID specification is its recommendation to interpret < | The most problematic point in the core Sender ID specification is its recommendation to interpret <code>v=spf1</code> policies like | ||
< | <code>spf2.0/mfrom,pra</code> instead of <code>spf2.0/mfrom</code>. This was never intended by all published SPF drafts since 2003, and for an unknown large number of <code>v=spf1</code> policies an evaluation for ''pra'' could cause bogus results for many cases where ''pra'' and ''mfrom'' are different. This problem was the basis of an appeal to the [[Internet Architecture Board|Internet Architecture Board (IAB)]]. In response to another prior appeal the [[IESG]] already noted that Sender ID cannot advance on the [[IETF]] standards track without addressing the incompatibility with a MUST in RFC 2822. | ||
== Intellectual property == | == Intellectual property == | ||
| Line 56: | Line 55: | ||
==External links== | ==External links== | ||
* [http://www.apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]] | * [http://www.apache.org/foundation/docs/sender-id-position.html ''ASF Position Regarding Sender ID''] statement from the [[Apache Software Foundation]] | ||
* [http://www.iab.org/appeals/2006-02-08-mehnle-appeal.html IAB appeal] about Sender ID's reuse of < | * [http://www.iab.org/appeals/2006-02-08-mehnle-appeal.html IAB appeal] about Sender ID's reuse of <code>v=spf1</code> for PRA from the [https://web.archive.org/web/20060702025443/http://new.openspf.org/ SPF project] (2006). | ||
* [http://www.debian.org/News/2004/20040904 ''Debian project unable to deploy Sender ID''] statement by the [[Debian]] project | * [http://www.debian.org/News/2004/20040904 ''Debian project unable to deploy Sender ID''] statement by the [[Debian]] project | ||
* [http://slashdot.org/article.pl?sid=04/09/13/1317238 ''IETF Decides on SPF / Sender-ID issue''] coverage and discussion on [[slashdot]] | * [http://slashdot.org/article.pl?sid=04/09/13/1317238 ''IETF Decides on SPF / Sender-ID issue''] coverage and discussion on [[slashdot]] | ||