Recommendations for the transition of email services from IPv4 to IPv6 for Internet Service Providers
draft-oreirdan-rosenwald-ipv6mail-transition-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Heather Lord , Jordan Rosenwald | ||
| Last updated | 2012-03-26 (Latest revision 2011-09-12) | ||
| 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
This document contains a phased plan for how providers of email services can effect and manage the transition of email services from IPv4 to IPv6. It is expected that this will be effected over a period of years and it is unlikely that any transition will completely exclude the ongoing possibility of using IPv4 as a transport mechanism for email. This provides one possible implementation plan for transitioning email services on the Internet from a predominantly IPv4-based connectivity model that suports IPv6.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)