IETF Logo Mail Archive

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

<mohamed.boucadair@orange-ftgroup.com> Thu, 12 November 2009 14:19 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
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 6790F3A6A0C for <shara@core3.amsl.com>; Thu, 12 Nov 2009 06:19:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 CsbJu08Z8BVJ for <shara@core3.amsl.com>; Thu, 12 Nov 2009 06:19:28 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by core3.amsl.com (Postfix) with ESMTP id 52BF73A69A5 for <shara@ietf.org>; Thu, 12 Nov 2009 06:19:27 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id E80862483CB; Thu, 12 Nov 2009 15:19:54 +0100 (CET)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id C7ABB238047; Thu, 12 Nov 2009 15:19:54 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Thu, 12 Nov 2009 15:19:54 +0100
From: <mohamed.boucadair@orange-ftgroup.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Date: Thu, 12 Nov 2009 15:19:53 +0100
Thread-Topic: [shara] Comments on the A+P issues (D. Thaler presentation)
Thread-Index: AcpjogSyqHC6aDY4SX63rHB3dk43UQAAHmcQ
Message-ID: <9167_1258035594_4AFC198A_9167_5495_1_94C682931C08B048B7A8645303FDC9F307914E60EB@PUEXCB1B.nanterre.francetelecom.fr>
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> <4AFC176B.9010106@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4AFC176B.9010106@necom830.hpcl.titech.ac.jp>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: multipart/mixed; boundary="_002_94C682931C08B048B7A8645303FDC9F307914E60EBPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2009.11.12.120321
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:19:29 -0000

Re-


-----Message d'origine-----
De : Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp] 
Envoyé : jeudi 12 novembre 2009 15:11
À : BOUCADAIR Mohamed NCPI/NAD/TIP
Cc : shara@ietf.org
Objet : Re: [shara] Comments on the A+P issues (D. Thaler presentation)

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.

Med: Do you have in mind something like what is illustrated in the attached figure (assumes that )? This requires that the source knows the ID which will be used to relay the ICMP message to the appropriate device sharing the same address.


						Masataka Ohta


*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

v2.8.7 | Report a Bug | By Email