RFC 3974: SMTP Operational Experience in Mixed IPv4/v6 Environments
In plain English — editorial summary, not part of the RFC
This document discusses SMTP operational experiences in IPv4/v6 dual stack environments. As IPv6-capable SMTP servers are deployed, it has become apparent that certain configurations of MX records are necessary for stable dual-stack (IPv4 and IPv6) SMTP operation. This document clarifies the existing problems in the transition period between IPv4 SMTP and IPv6 SMTP. It also defines operational requirements for stable IPv4/v6 SMTP operation. This document does not define any new protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3974
- Published
- January 2005
- Authors
- M. Nakamura; J. Hagino
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5214Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
March 2008
- RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
January 2010
- RFC 5579Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) InterfacesCurrent
February 2010
- RFC 6964Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
May 2013
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?