Email transfer in the IPv6 introduction phase
Author(s): Martin Rosenau
During the introduction phase of IPv6 (as of Jan 2013) many existing mail servers are not able to do IPv6 communication, yet. However new networks will be assigned IPv6 addresses only so new mail servers will not be...
Network Working Group M. Rosenau Internet-Draft Hobbyist developer Expires: July 18, 2013 January 14, 2013 Email transfer in the IPv6 introduction phase draft-mrosenau-email-ipv4-to-6-00 Abstract During the introduction phase of IPv6 (as of Jan 2013) many existing mail servers are not able to do IPv6 communication, yet. However new networks will be assigned IPv6 addresses only so new mail servers will not be able to do IPv4 communication. This document proposes the installation of special servers that are able to route mail between IPv4-only and IPv6-only mail servers to solve this problem. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on July 18, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Rosenau Expires July 18, 2013 [Page 1] Internet-Draft Email transfers between IPv4 and IPv6 January 2013 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Rosenau Expires July 18, 2013 [Page 2] Internet-Draft Email transfers between IPv4 and IPv6 January 2013 1. Background As of the end 2012 IPv4 addresses are no longer available to companies. For this reason new mail servers (especially mail servers of companies that do not have IPv4 addresses, yet) are IPv6-only. The introcuction of IPv6 on existing mail servers, however, is often not done right now. RFC 3974 proposes that every mail server should have an IPv4 address even if it is able to do IPv6. However this is no longer possible due to the depletion of IPv4 addresses. For this reason it may be impossible to send an electronic mail from a domain that has an IPv4-only server to a domain using an IPv6-only server and vice versa. Rosenau Expires July 18, 2013 [Page 3] Internet-Draft Email transfers between IPv4 and IPv6 January 2013 2. Implementation 2.1. Tunnel servers This document proposes the installation of IPv4-to-IPv6 translation servers to manage the problem. Such a server would work the following way: o Accept incoming SMTP connections on IPv4 AND IPv6 o For each mail "received" simply forward the received mail to the SMTP server that is really responsible for the destination address In our example such servers have the addresses 184.108.40.206 and 220.127.116.11. The DNS configuration may look like this: example.org. IN MX 1 mx1.example.org. example.com. IN MX 1 mx1.example.com. ip4only.example. IN MX 1 mx1.ip4only.example. mail-tunnel.example. IN AAAA 2001:db8:ffff::1 mail-tunnel.example. IN AAAA 2001:db8:ffff::2 mail-tunnel.example. IN A 18.104.22.168 mail-tunnel.example. IN A 22.214.171.124 mx1.example.org. IN AAAA 2001:db8:ffff::1:1 mx1.example.org. IN A 126.96.36.199 mx1.example.org. IN A 188.8.131.52 mx1.example.com. IN AAAA 2001:db8:ffff::2:1 mx1.example.com. IN A 184.108.40.206 mx1.example.com. IN A 220.127.116.11 mx1.ip4only.example. IN A 192.0.2.1 Note that mx1.example.com and mx1.example.org are different (!) servers. However the IPv4 address in the DNS configuration is the same. The DNS query for their IPv4 address will result in the IPv4 address of the server "mail-tunnel.example" because they do not support IPv4. 2.2. IPv4-to-IPv6 mail transport Scenario: An Email is sent from email@example.com to firstname.lastname@example.org. The mail server of the domain ip4only.example will now query the IPv4 address of mx1.example.com. The DNS server will return the address 18.104.22.168 which is in fact the address of the tunnel server. The mail is now delivered to the tunnel server, that then forwards the mail to the actual mail server. Rosenau Expires July 18, 2013 [Page 4] Internet-Draft Email transfers between IPv4 and IPv6 January 2013 2.3. IPv6-to-IPv4 mail transport Scenario: An Email is sent from email@example.com to firstname.lastname@example.org. The mail server of the domain example.com will now query the IPv6 address of mx1.ipv4only.example. The DNS server will return no result. In this case the mail server's implementation must be done in a way to allow transmission to IPv4-only domains: It must detect this case and directly connect the tunnel server or use other tunneling mechanisms that allow connecting the IPv4 mail server using a TCP connection from an IPv6-only network directly (like NAT64). Note: If an IPv6 mail server has access to NAT64 and DNS64 it can send mail directly to an IPv4 mail server Rosenau Expires July 18, 2013 [Page 5] Internet-Draft Email transfers between IPv4 and IPv6 January 2013 Author's Address Martin D. J. Rosenau Hobbyist developer Email: email@example.com Rosenau Expires July 18, 2013 [Page 6]