Re: IPv6 standard?

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Fri, 25 September 2009 04:50 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C9943A6912 for <ietf@core3.amsl.com>; Thu, 24 Sep 2009 21:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.399
X-Spam-Level: *
X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 JqYTnSHvaO8J for <ietf@core3.amsl.com>; Thu, 24 Sep 2009 21:50:46 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 993C13A659B for <ietf@ietf.org>; Thu, 24 Sep 2009 21:50:45 -0700 (PDT)
Received: (qmail 329 invoked from network); 25 Sep 2009 05:09:12 -0000
Received: from bmdi2173.bmobile.ne.jp (HELO necom830.hpcl.titech.ac.jp) (202.221.174.173) by necom830.hpcl.titech.ac.jp with SMTP; 25 Sep 2009 05:09:12 -0000
Message-ID: <4ABC4C3C.8060706@necom830.hpcl.titech.ac.jp>
Date: Fri, 25 Sep 2009 13:51:08 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: trejrco@gmail.com
Subject: Re: IPv6 standard?
References: <4E63AD59-D559-448F-A5A5-AB727AABFEA0@muada.com><04a501ca36e1$17e69790$0600a8c0@china.huawei.com><3f4922c70909160836u69ebe6fbl1f48466428987335@mail.gmail.com><4AB1078F.3020701@cisco.com> <693FDCF7-66EE-4C9C-ADAF-FE1F60E8A80B@shinkuro.com> <848EF00B003A4B4AA054AC16383333D2@GIH.CO.UK> <E2B2E50E-AA04-4839-91E6-60578B20C141@shinkuro.com> <0bdb01ca37e7$66dfb370$349f1a50$@net> <0EC96C28-2C54-4BBE-B24D-1684C49898D9@shinkuro.com><B1A70E9FC5194A2D80A6A1954AEFBB57@GIH.CO.UK><4ABAB4CB.403@necom830.hpcl.titech.ac.jp> <1699409148-1253755691-cardhu_decombobulator_blackberry.rim.net-1128193451-@bda575.bisx.prod.on.blackberry>
In-Reply-To: <1699409148-1253755691-cardhu_decombobulator_blackberry.rim.net-1128193451-@bda575.bisx.prod.on.blackberry>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 04:50:47 -0000

trejrco@gmail.com wrote:

> While the case for "transparent NAT" may be valid,

A+P and other technologies may also have end to end transparency.

> I believe IPv6 to also be a valid and valuable technology forthe
> continued growth and expansion of the Internet.  

> (Even eliding the amount of change required to implement "e2e NAT",

FYI, end to end NAT is already implemented and is running (several
hundreds lines of code, essential part of which is 10 lines for
forward/reverse translation and 100 lines for port number restriction).

Because end to end NAT can be implemented with upward compatibility
to legacy NAT, it can be deployed smoothly. NAT GW may be upgraded
to end to end NAT, which is not visible to legacy end hosts. End
hosts may be upgraded, which will start working after an end to
end NAT gateway is installed.

> and how this comes close to the amount of work (in many regards)
> as deploying IPv6, w/o all of the same capabilities.)

If it comes close to, it means it has failed totally, just as the
amount of effort to deploy IPv6 is an evidence that IPv6 deployment
has totally failed. As for capabilities, IPv6 is no better than IPv4
(with or without end to end NAT).

> And FWIW, I also continue to believe 'the world' agrees with IPv6
> being 'the solution' ... Based not upon current traffic volumes
> (of course), but rather the number of deployments

IPv6 failed because of lack of not only deployments but also
an essential feature.

The objectives of IPng are to extend address space and to aggregate
routing table aggressively.

However, as has discussed recently on renumbering, IPv6 lacks the
capability of renumbering, which makes aggressive aggregation
impossible.

> Or the US federal govt's re-invigorated push towards IPv6 ...

Do you know that USG pushed towards CLNP?

						Masataka Ohta