[v6ops] Fw: New Version Notification for draft-mawatari-v6ops-464xlat-00.txt
MAWATARI Masataka <mawatari@jpix.ad.jp> Mon, 16 January 2012 01:51 UTC
Return-Path: <mawatari@jpix.ad.jp>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2E621F84D8 for <v6ops@ietfa.amsl.com>; Sun, 15 Jan 2012 17:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.51
X-Spam-Level:
X-Spam-Status: No, score=0.51 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id My9ycWpO1uho for <v6ops@ietfa.amsl.com>; Sun, 15 Jan 2012 17:51:21 -0800 (PST)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1B421F844E for <v6ops@ietf.org>; Sun, 15 Jan 2012 17:51:20 -0800 (PST)
Received: from [10.10.31.235] (eth3-1-bb-fw-34.jpix.ad.jp [210.171.226.102]) by mx20.jpix.ad.jp (Postfix) with ESMTP id CCEABFC021 for <v6ops@ietf.org>; Mon, 16 Jan 2012 10:51:17 +0900 (JST)
Date: Mon, 16 Jan 2012 10:51:18 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: v6ops@ietf.org
Message-Id: <20120116105118.9F36.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------_4F136D67000000009F2B_MULTIPART_MIXED_"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.57.03 [ja]
Subject: [v6ops] Fw: New Version Notification for draft-mawatari-v6ops-464xlat-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2012 01:51:22 -0000
Dear v6ops, I am Masataka Mawatari from JPIX. We had submitted a draft that describes an architecture and our experience for providing IPv4 connectivity across IPv6 network by combining stateful protocol translation RFC 6146 in network and stateless protocol translation RFC 6145 at CPE. This architecture in the draft is called "464XLAT". http://tools.ietf.org/html/draft-mawatari-v6ops-464xlat-00 We believe the 464XLAT informational draft fits with #1 and #4 in the v6ops charter for identifying solutions that promote the ability of network operators to deploy IPv6 and integrate with the IPv4/IPv6 internet. The 464XLAT architecture uses standards created in BEHAVE WG. We believe this draft best fits with v6ops WG since it outlines a proven and deployed architecture that leverages existing standards for solving the IP number problem by better enabling IPv6-only networks to meet the needs of operators (cost, simplicity, time to market...) and subscribers (it just works ...). T-Mobile USA has been operating a beta IPv6-only NAT64/DNS64 network for nearly 2 years now, and on that trial network (which is full production in SF Bay, and will be national full production by end of Q1) the need for 464XLAT emerged to overcome the issue of IPv4-only applications and IPv4 referrals. The T-Mobile USA users solved the problem themselves by coding a stateless translation application on the Nokia N900: http://code.google.com/p/n900ipv6/wiki/Nat64D JPIX (Japan Internet Exchange) has been providing 464XLAT trial service for JPIX members since July 2010 to deploy IPv6 access service in wireline networks. Especially small-medium ISPs do not have a operation resource and much IPv4 address pool to solve IPv4 address exhaustion in each ISP backbone network so JPIX proposes to support IPv4 address sharing solution. We have a CPE router with stateless translation implemented by NEC AccessTechnica. http://www.apricot.net/apricot2011/media/Masataka_Mawatari_IPv6v4_Exchange_Service_for_sharing_IPv4_address.pdf From there, it became apparent that the solution was viable both in wireless and wireline networks. We are currently in the process of stewarding the 464XLAT CLAT code via the Android code contribution process, and we have a working implementation here: http://code.google.com/p/android-clat/ We believe our draft creates a reasonable solution for the problem statement created in draft-arkko-ipv6-only-experience. We are seeking the groups feedback on if this draft should be a working group item that would benefit from working group review and refinement to better extend and repeat what has already been achieved with 464XLAT. Kind Regards, Masataka MAWATARI
--- Begin Message ---A new version of I-D, draft-mawatari-v6ops-464xlat-00.txt has been successfully submitted by Masanobu Kawashima and posted to the IETF repository. Filename: draft-mawatari-v6ops-464xlat Revision: 00 Title: 464XLAT: Combination of Stateful and Stateless Translation Creation date: 2012-01-15 WG ID: Individual Submission Number of pages: 14 Abstract: This document describes an architecture (464XLAT) for providing IPv4 connectivity across an IPv6-only network by combining existing and well-known stateful protocol translation RFC 6146 and stateless protocol translation RFC 6145. 464XLAT is a simple and scalable technique to quickly deploy IPv4 access service to mobile and wireline IPv6-only networks without encapsulation. The IETF Secretariat--- End Message ---
- [v6ops] Fw: New Version Notification for draft-ma… MAWATARI Masataka