MARID

From Wikipedia, the free encyclopedia

MARID was an IETF working group in the applications area tasked to propose standards for E-mail authentication in 2004. The name is an acronym of MTA Authorization Records In DNS.

Lightweight MTA Authentication Protocol (LMAP) was a generic name for a set of 'designated sender' proposals that were discussed in the ASRG in the Fall of 2003, including:

  • Designated Mailers Protocol (DMP)
  • Designated Relays Inquiry Protocol (DRIP)
  • Flexible Sender Validation (FSV)
  • MTAMARK
  • Reverse MX (RMX)
  • Sender Policy Framework SPF

These schemes attempt to list the valid IP addresses that can send mail for a domain. The lightweight in LMAP essentially stands for no crypto as opposed to DomainKeys.

In March of 2004, the Internet Engineering Task Force IETF held a Birds Of A Feather BoF on these proposals and as the result of that meeting, chartered the MARID working group.

Microsoft's Caller-ID proposal was a late and highly controversial addition to this mix:

  • use of XML policies with DNS - this was reduced to what is now known as Sender ID,
  • proposals of an unfriendly takeover of SPF policies by Sender ID,
  • use of RFC 2822 mail header fields as by DomainKeys, all other LMAP drafts used the SMTP envelope,
  • specific questions and unspecific flame wars about patents and licensing.

For many the use of RFC 2822 mail header fields is already beyond the lightweight LMAP limits, because it operates on the SMTP DATA, or in other words the mail. In this sense Caller-ID started outside of its class.

The WG co-Chairs decided to postpone the question of RFC 2821 SMTP identities - i.e. MAIL FROM covered by SPF, or HELO covered by CSV and SPF - in favour of RFC 2822 identities covered by Caller-ID's and later Sender-ID's Purported Responsible Address (PRA).

The WG finally arrived at a point, where sender policies could be split into different scopes like the 2821 MAIL FROM or the 2822 PRA. The MARID spf2.0 syntax also allowed to join different scopes into one policy record, if the sets of permitted IPs are identical, as it's often the case.

Less than a week after the publication of a first mfrom or MAIL FROM draft the WG was terminated unilaterally by its leadership. MARID existed only seven months, no RFCs were published.

A podcast with a former co-Chair tries to explain the MARID fiasco. Another view of these events is the observation that the WG did not support a division of the E-mail authentication field into PRA for 2822 and CSV for 2821, squeezing out the MAIL FROM.

The responsible IETF Area Director agreed to sponsor the publication of some MARID fallout as IETF experiments, this happened in 2005. Both classic pre-MARID SPF and Sender ID were approved as experimental RFCs. The latter is to a certain degree a result of MARID.

The ongoing disputes on technical issues and incompatibilities in Sender ID resulted later in appeals to the IESG and the IAB.

Advanced Search
Included Web Search Engines


Safe Search

close

Top Matching Results

Occasionally Search.com will highlight specialized results that are based on the context of your query. Examples of specialized results include specific links to news, images, or video.

Top Matching Results may highlight information from other Search.com pages, content from the CNET Network of sites, or third party content. The listings are based purely on relevance. Search.com does not receive payment for listings in this section but our partners that provide this data may get paid for listing these products.

Sponsored Links

This section contains paid listings which have been purchased by companies that want to have their sites appear for specific search terms and related content. These listings are administered, sorted and maintained by a third party and are not endorsed by Search.com.

Search Results

Search.com sends your search query to several search engines at one time and integrates the results into one list which has been sorted by relevance using Search.com's proprietary algorithm. You can customize the list of search engines included in your metasearch from the preferences.

The search engines that are used in your metasearch may allow companies to pay to have their Web sites included within the results. To view the Paid Inclusion policy for a specific search engine, please visit their Web site. Search.com does not accept payment or share revenue with any search engine partner for listings in this section.