IETF Logo Mail Archive

Re: [EME] The virtual circuit trap mentioned in the EME charter - need for clarification

Rémi Després <remi.despres@wanadoo.fr> Wed, 15 November 2006 15:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkN5B-0001Dp-9l; Wed, 15 Nov 2006 10:53:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkMXS-0005ng-8T for eme@irtf.org; Wed, 15 Nov 2006 10:18:58 -0500
Received: from smtp5.orange.fr ([193.252.22.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkMXQ-00022b-RO for eme@irtf.org; Wed, 15 Nov 2006 10:18:58 -0500
Received: from smtp-msa-out05.orange.fr (mwinf0509 [172.22.136.39]) by mwinf0510.orange.fr (SMTP Server) with ESMTP id A9DC9715B for <eme@irtf.org>; Wed, 15 Nov 2006 16:15:15 +0100 (CET)
Received: from [127.0.0.1] (APuteaux-152-1-60-44.w82-120.abo.wanadoo.fr [82.120.170.44]) by mwinf0509.orange.fr (SMTP Server) with ESMTP id 840931C002A6; Wed, 15 Nov 2006 16:15:14 +0100 (CET)
X-ME-UUID: 20061115151514541.840931C002A6@mwinf0509.orange.fr
Message-ID: <455B2F05.5000201@wanadoo.fr>
Date: Wed, 15 Nov 2006 16:15:17 +0100
From: Rémi Després <remi.despres@wanadoo.fr>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [EME] The virtual circuit trap mentioned in the EME charter - need for clarification
References: <E6F7A586E0A3F94D921755964F6BE00662575C@EXCHANGE2.cs.cornell.edu> <4559FC5C.1090803@rd-iptech.com> <455A14AA.6010007@isi.edu>
In-Reply-To: <455A14AA.6010007@isi.edu>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-Mailman-Approved-At: Wed, 15 Nov 2006 10:53:47 -0500
Cc: eme@irtf.org
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2073153534=="
Errors-To: eme-bounces@irtf.org


Joe Touch a écrit :
> Rémi Després wrote:
>   
>> 2. I am not aware, personally, of failures of classical NATs that cannot
>> be recovered (I mean those NATs that all of us use extensively)..
>>     
>
> When there are multiple NATs that could be used for egress or ingress.
>
> An outgoing SYN establishes state at one NAT that is typically not
> shared with the other NATs; if the routing changes behind the NAT to the
> egress, or in front of the NAT on the return path, the connection
> breaks. FWIW, that routing can change for many reasons, including
> failure of a NAT box itself.
>
> Whether that's recoverable depends on whether you're willing to
> reestablish a connection as part of recovery.
>
> Joe
>
>   

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme

v2.23.0 | Report a Bug | By Email