IETF Logo Mail Archive

Re: [shara] Comments on the A+P issues (D. Thaler presentation)

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 12 November 2009 14:11 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FD553A6BD5 for <shara@core3.amsl.com>; Thu, 12 Nov 2009 06:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.21
X-Spam-Level: *
X-Spam-Status: No, score=1.21 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 GIrfUIOp-qQH for <shara@core3.amsl.com>; Thu, 12 Nov 2009 06:11:04 -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 D6D623A6BCD for <shara@ietf.org>; Thu, 12 Nov 2009 06:11:03 -0800 (PST)
Received: (qmail 11581 invoked from network); 12 Nov 2009 14:43:02 -0000
Received: from bmdi2117.bmobile.ne.jp (HELO necom830.hpcl.titech.ac.jp) (202.221.174.117) by necom830.hpcl.titech.ac.jp with SMTP; 12 Nov 2009 14:43:02 -0000
Message-ID: <4AFC176B.9010106@necom830.hpcl.titech.ac.jp>
Date: Thu, 12 Nov 2009 23:10:51 +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: mohamed.boucadair@orange-ftgroup.com
References: <14721_1258014719_4AFBC7FF_14721_33113_1_94C682931C08B048B7A8645303FDC9F307914E5ECF@PUEXCB1B.nanterre.francetelecom.fr> <4AFC0AC3.8070406@necom830.hpcl.titech.ac.jp> <29471_1258033673_4AFC1209_29471_2973_1_94C682931C08B048B7A8645303FDC9F307914E609E@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <29471_1258033673_4AFC1209_29471_2973_1_94C682931C08B048B7A8645303FDC9F307914E609E@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "shara@ietf.org" <shara@ietf.org>
Subject: Re: [shara] Comments on the A+P issues (D. Thaler presentation)
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2009 14:11:05 -0000

mohamed.boucadair@orange-ftgroup.com wrote:

> Just treat identifier and sequence numbers of ICMP echo request
> as source and destination port numbers and of ICMP echo reply as
> destination and source port numbers, respectively.
> 
> Med: This is why I mentioned "with the current ICMP version" since
> changes may be required if we want to solve the exchange of ICMP
> messages when both the source and destination are located behind
> NAT devices.

All you need are fields which can be regarded as source and
destination port numbers and the current ICMP works as is just
as current TCP works.
 
> ICMP echo with end to end NAT is just working so.
> 
> Med: Even when you have two NATs/PRR in the path (this was the
> scenario I'm referring to)?

Sure.

						Masataka Ohta

v2.8.7 | Report a Bug | By Email