IPv6 SMTP operational requirements
draft-motonori-ipv6-smtp-requirement-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Motonori Nakamura , Jun-ichiro Itoh | ||
| Last updated | 2000-09-05 | ||
| 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
The memo lists operational requirements for IPv6 SMTP, and IPv6-capable MX DNS records. As we deploy IPv6 SMTP servers, it became apparent that we need certain configuration in IPv6-capable MX DNS record, for stable dual-stack (IPv4 and IPv6) SMTP operations. The document tries to clarify the problems we have in transition period between IPv4 SMTP and IPv6 SMTP, and operational requirements for stable IPv4/v6 SMTP operation.
Authors
Motonori Nakamura
Jun-ichiro Itoh
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)