IETF Logo Mail Archive

[EME] transport recovery at the APP layer ?

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkO7o-00064z-59; Wed, 15 Nov 2006 12:00:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkO5d-0003yF-Tq for eme@irtf.org; Wed, 15 Nov 2006 11:58:21 -0500
Received: from smtp12.orange.fr ([193.252.22.20] helo=smtp-msa-out12.orange.fr) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkO5b-0000NM-FC for eme@irtf.org; Wed, 15 Nov 2006 11:58:21 -0500
Received: from [127.0.0.1] (APuteaux-152-1-60-44.w82-120.abo.wanadoo.fr [82.120.170.44]) by mwinf1202.orange.fr (SMTP Server) with ESMTP id 9BFA61C000A7; Wed, 15 Nov 2006 17:58:15 +0100 (CET)
X-ME-UUID: 20061115165815639.9BFA61C000A7@mwinf1202.orange.fr
Message-ID: <455B472A.9000303@wanadoo.fr>
Date: Wed, 15 Nov 2006 17:58:18 +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>
References: <E6F7A586E0A3F94D921755964F6BE00662575C@EXCHANGE2.cs.cornell.edu> <4559FC5C.1090803@rd-iptech.com> <455A14AA.6010007@isi.edu> <455B3DDC.2060903@rd-iptech.com> <455B4094.1080400@isi.edu>
In-Reply-To: <455B4094.1080400@isi.edu>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-Mailman-Approved-At: Wed, 15 Nov 2006 12:00:35 -0500
Cc: eme@irtf.org
Subject: [EME] transport recovery at the APP layer ?
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="===============0654133202=="
Errors-To: eme-bounces@irtf.org

Joe Touch wrote :
> It'd be useful to decide whether recovery includes the assumption that
> the app layer will reconnect and restore E2E context. If that's
> _assumed_ here, it'd be a first IMO.
>
> Joe
This is IMO an important question.

We agree, I believe, that forbidding middleboxes that do some transport 
relaying is unrealistic.
(In other words, for the real world Internet,.the EME model must be 
accepted in addition to the E2E one.)

Then, there seems to be no simpler place, to recover from transport 
relay failures, than just above the transport layer..
It is thus not a surprise that  real applications, that had to adapt to 
the real transport world with no extra layer between transport and 
themselves, already have that recovery mechanism.

 It would indeed be a first _as an recognized model_, but AFAIK not in 
implemented code.

RD



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

v2.23.0 | Report a Bug | By Email