DNS MX Record Deployment for Large Mail Sites
draft-myers-mail-largesite-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | John G. Myers | ||
| Last updated | 1996-12-17 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Domains which recieve a large number of incoming mail messages have a need to distribute incoming requests over a large number of SMTP servers. The most obvious method for advertising DNS records these SMTP servers leads to undesirable behavior when certain network failures occur. For example, on XXXX, 1996 [XXXREF] a single routing failure at a large site led to the catastrophic failure of a large portion of mail systems on the Internet. This document gives recommendations for how large sites should advertise DNS records for their SMTP servers to avoid these problems and for how SMTP client implementations should insulate themselves against large sites which do not follow these recommendations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)