Reverse MX: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>David MacQuigg
mNo edit summary
imported>Hadmut Danisch
No edit summary
Line 1: Line 1:
{{subpages}}
{{subpages}}
{{TOC|right}}
'''Reverse MX''' (RMX) is an email authentication method developed by Hadmut Danisch.  It became a basis for the two most commonly used methods - [[Sender Policy Framework]] and [[Sender ID]].
'''Reverse MX''' (RMX) is an email authentication method developed by Hadmut Danisch.  It became a basis for the two most commonly used methods - [[Sender Policy Framework]] and [[Sender ID]].
http://www.danisch.de/work/security/txt/draft-danisch-dns-rr-smtp-04.txt
== Development of RMX ==
=== Background and Motivation ===
=== Design Criterions ===
=== The Concept of Reverse MX Records ===
=== Publication at the IRTF and IETF ===


http://www.danisch.de/work/security/txt/draft-danisch-dns-rr-smtp-04.txt
 
== Technical Description ==
=== Implementation as DNS Records ===
 
 
 
== Reasons for Failure ==
=== SPF and Microsoft's Attitudes ===
=== IRTF/IETF-specific Reasons ===
=== Design flaws of DNS ===
=== Design flaws of the SMTP email protocol ===
=== Economical Reasons ===
=== Freedom of Speech and Cultural Reasons ===
=== Education ===
=== Perceptions of Identity and Juristic Reasons ===
=== Personal and European Reasons ===
 
 
 
 
 
==References==
{{reflist}}

Revision as of 10:27, 22 November 2009

This article is a stub and thus not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

Reverse MX (RMX) is an email authentication method developed by Hadmut Danisch. It became a basis for the two most commonly used methods - Sender Policy Framework and Sender ID. http://www.danisch.de/work/security/txt/draft-danisch-dns-rr-smtp-04.txt


Development of RMX

Background and Motivation

Design Criterions

The Concept of Reverse MX Records

Publication at the IRTF and IETF

Technical Description

Implementation as DNS Records

Reasons for Failure

SPF and Microsoft's Attitudes

IRTF/IETF-specific Reasons

Design flaws of DNS

Design flaws of the SMTP email protocol

Economical Reasons

Freedom of Speech and Cultural Reasons

Education

Perceptions of Identity and Juristic Reasons

Personal and European Reasons

References