[v4v6interim] Translation-based IPv4/IPv6 interworking for IPv4 networks
Christian Vogt <christian.vogt@ericsson.com> Thu, 02 October 2008 09:42 UTC
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DD0E3A6B15; Thu, 2 Oct 2008 02:42:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03B223A6B1A for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 02:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5iyqHfA0+91 for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 02:42:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 486923A6811 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 02:42:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9435620ED6; Thu, 2 Oct 2008 11:42:44 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-65-48e4979497c9
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 31AF720C67; Thu, 2 Oct 2008 11:42:44 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 11:42:05 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 11:42:05 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 2DF8A2469; Thu, 2 Oct 2008 12:42:05 +0300 (EEST)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4CB1F4DAC2; Thu, 2 Oct 2008 12:42:01 +0300 (EEST)
Message-Id: <65137CB2-F5E9-48F2-8084-11BF17B34291@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 02 Oct 2008 05:41:59 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 09:42:05.0133 (UTC) FILETIME=[21105FD0:01C92473]
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] Translation-based IPv4/IPv6 interworking for IPv4 networks
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
Dear all, Alain and I have worked on a translation-based IPv4/IPv6 interworking method that we would like to share with you. This method is for deployment in IPv4-only networks, and in this regard differs from many of the existing translation-based interworking methods that are for deployment in IPv6 networks. The main advantage of IPv4-side deployment is that no extra, globally unique IPv4 addresses are required. You find Alain's and my proposal here: http://users.piuha.net/chvogt/pub/2008/virtual-ip6-connectivity.txt In the early days of IPv6 introduction, the responsibility for IPv4/IPv6 interworking must clearly be on the side of the new IPv6 networks, for incentives reasons. But interworking will become increasingly important also for IPv4 networks as IPv6 gets more prevalent. IPv4-side interworking methods will then be useful. Furthermore, IPv4-side interworking can already today solve some of the key problem scenarios, namely those involving IPv6 clients and IPv4 servers in the absence of a unique global IPv4 addresses for each server. We realize we are submitting this very late -- and I could myself not even participate in the discussion around tunneling-based interworking yesterday. I wish that had been different. But perhaps our document can still provide a bit of valuable input for today's discussion. - Christian, for Alain and Christian _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] Translation-based IPv4/IPv6 interwo… Christian Vogt