Re: IESG position on NAT traversal and IPv4/IPv6

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 15 November 2010 09:26 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 014E53A69B9 for <ietf@core3.amsl.com>; Mon, 15 Nov 2010 01:26:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.03
X-Spam-Level: **
X-Spam-Status: No, score=2.03 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 mpBx53f4xJMr for <ietf@core3.amsl.com>; Mon, 15 Nov 2010 01:26:43 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id CBB973A6860 for <ietf@ietf.org>; Mon, 15 Nov 2010 01:26:42 -0800 (PST)
Received: (qmail 70359 invoked from network); 15 Nov 2010 10:00:46 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO ?131.112.32.134?) (131.112.32.134) by necom830.hpcl.titech.ac.jp with SMTP; 15 Nov 2010 10:00:46 -0000
Message-ID: <4CE0FCC9.5030201@necom830.hpcl.titech.ac.jp>
Date: Mon, 15 Nov 2010 18:26:33 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IESG position on NAT traversal and IPv4/IPv6
References: <F443844F-67B6-418F-9E32-B2F498686650@acmepacket.com> <AANLkTimnQo=gAXa3FQWWfTp004t-Uv_RDzgOd=30Q49b@mail.gmail.com>
In-Reply-To: <AANLkTimnQo=gAXa3FQWWfTp004t-Uv_RDzgOd=30Q49b@mail.gmail.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
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: Mon, 15 Nov 2010 09:26:44 -0000

Phillip Hallam-Baker wrote:

> NAT traversal should be something that is supported at a higher level of
> abstraction than one protocol. And there seem to be moves towards that
> support.

As there are various kinds of NAT, it is a waste of effort to try
to have a universal NAT traversing protocol.

Instead, we should define some standard NAT for which simplest
NAT traversal is required for widest range of applications.

As end to end NAT with complete end to end transparency does not
require any NAT traversal for all applications, we are done.

> But the idea of trying to starve protocols of features in order to encourage
> transition to IPv6 has been tried for the past ten years and utterly failed.

So true.

						Masataka Ohta