Analysis of Stateful 64 Translation
draft-ietf-behave-64-analysis-06

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-03-01 (latest revision 2012-02-21)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Has enough positions to pass.
Responsible AD David Harrington
IESG note Dan Wing (dwing@cisco.com) is the document shepherd.
Send notices to behave-chairs@tools.ietf.org, draft-ietf-behave-64-analysis@tools.ietf.org
Behavior Engineering for Hindrance                              R. Penno
Avoidance                                               Juniper Networks
Internet-Draft                                                 T. Saxena
Intended status: Informational                             Cisco Systems
Expires: August 24, 2012                                    M. Boucadair
                                                          France Telecom
                                                            S. Sivakumar
                                                           Cisco Systems
                                                       February 21, 2012

                  Analysis of Stateful 64 Translation
                    draft-ietf-behave-64-analysis-06

Abstract

   Due to specific problems, NAT-PT was deprecated by the IETF as a
   mechanism to perform IPv6-IPv4 translation.  Since then, new efforts
   have been undertaken within IETF to standardize alternative
   mechanisms to perform IPv6-IPv4 translation.  This document evaluates
   how the new stateful translation mechanisms avoid the problems that
   caused the IETF to deprecate NAT-PT.

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 August 24, 2012.

Copyright Notice

   Copyright (c) 2012 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

Penno, et al.            Expires August 24, 2012                [Page 1]
Internet-Draft         Analysis of 64 Translation          February 2012

   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
     1.1.  Definition . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.2.  Context  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.3.  Scope  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Requirements Language  . . . . . . . . . . . . . . . . . . . .  4
   3.  Analysis of 64 Translation Against Concerns of RFC4966 . . . .  4
     3.1.  Problems Impossible to Solve . . . . . . . . . . . . . . .  5
     3.2.  Problems Which Can be Solved . . . . . . . . . . . . . . .  5
     3.3.  Problems Solved  . . . . . . . . . . . . . . . . . . . . .  7
   4.  Conclusions  . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 12
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

Penno, et al.            Expires August 24, 2012                [Page 2]
Internet-Draft         Analysis of 64 Translation          February 2012

1.  Introduction

1.1.  Definition

   This document uses stateful 64 (or 64 for short) to refer to the
   mechanisms defined in the following documents:

   o  IP/ICMP Translation Algorithm [RFC6145]

   o  Stateful NAT64: Network Address and Protocol Translation from IPv6
      Clients to IPv4 Servers [RFC6146]

   o  DNS64: DNS extensions for Network Address Translation from IPv6
      Clients to IPv4 Servers [RFC6147]

   o  IPv6 Addressing of IPv4/IPv6 Translators [RFC6052]

   o  Framework for IPv4/IPv6 Translation [RFC6144]

1.2.  Context

   Stateful 64 is widely seen as a major interconnection technique
Show full document text