datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

464XLAT: Combination of Stateful and Stateless Translation
RFC 6877

Internet Engineering Task Force (IETF)                       M. Mawatari
Request for Comments: 6877                       Japan Internet Exchange
Category: Informational                                     M. Kawashima
ISSN: 2070-1721                                 NEC AccessTechnica, Ltd.
                                                                C. Byrne
                                                            T-Mobile USA
                                                              April 2013

       464XLAT: Combination of Stateful and Stateless Translation

Abstract

   This document describes an architecture (464XLAT) for providing
   limited IPv4 connectivity across an IPv6-only network by combining
   existing and well-known stateful protocol translation (as described
   in RFC 6146) in the core and stateless protocol translation (as
   described in RFC 6145) at the edge. 464XLAT is a simple and scalable
   technique to quickly deploy limited IPv4 access service to IPv6-only
   edge networks without encapsulation.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6877.

Mawatari, et al.              Informational                     [Page 1]
RFC 6877                         464XLAT                      April 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Motivation and Uniqueness of 464XLAT . . . . . . . . . . . . .  4
   4.  Network Architecture . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Wireline Network Architecture  . . . . . . . . . . . . . .  4
     4.2.  Wireless 3GPP Network Architecture . . . . . . . . . . . .  5
   5.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Wireline Network Applicability . . . . . . . . . . . . . .  6
     5.2.  Wireless 3GPP Network Applicability  . . . . . . . . . . .  7
   6.  Implementation Considerations  . . . . . . . . . . . . . . . .  7
     6.1.  IPv6 Address Format  . . . . . . . . . . . . . . . . . . .  7
     6.2.  IPv4/IPv6 Address Translation Chart  . . . . . . . . . . .  7
     6.3.  IPv6 Prefix Handling . . . . . . . . . . . . . . . . . . .  9
     6.4.  DNS Proxy Implementation . . . . . . . . . . . . . . . . .  9
     6.5.  CLAT in a Gateway  . . . . . . . . . . . . . . . . . . . .  9
     6.6.  CLAT-to-CLAT Communications  . . . . . . . . . . . . . . . 10
   7.  Deployment Considerations  . . . . . . . . . . . . . . . . . . 10
     7.1.  Traffic Engineering  . . . . . . . . . . . . . . . . . . . 10
     7.2.  Traffic Treatment Scenarios  . . . . . . . . . . . . . . . 10
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
     10.2. Informative References . . . . . . . . . . . . . . . . . . 12
   Appendix A.  Examples of IPv4/IPv6 Address Translation . . . . . . 13

Mawatari, et al.              Informational                     [Page 2]
RFC 6877                         464XLAT                      April 2013

1.  Introduction

   With the exhaustion of the unallocated IPv4 address pools, it will be
   difficult for many networks to assign IPv4 addresses to end users.

   This document describes an IPv4-over-IPv6 solution as one of the

[include full document text]