IETF Logo Mail Archive

Re: [EME] Re: transport recovery at the APP layer ?

Joe Touch <touch@ISI.EDU> Wed, 15 November 2006 17:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkOjQ-0005Xv-Bq; Wed, 15 Nov 2006 12:39:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkOjP-0005Xq-G9 for eme@irtf.org; Wed, 15 Nov 2006 12:39:27 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkOjN-00066b-4h for eme@irtf.org; Wed, 15 Nov 2006 12:39:27 -0500
Received: from [127.0.0.1] (67.sub-75-209-245.myvzw.com [75.209.245.67]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id kAFHcoEC027324; Wed, 15 Nov 2006 09:38:53 -0800 (PST)
Message-ID: <455B50A7.10405@isi.edu>
Date: Wed, 15 Nov 2006 09:38:47 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
Subject: Re: [EME] Re: transport recovery at the APP layer ?
References: <24CCCC428EFEA2469BF046DB3C7A8D2214131D@namail5.corp.adobe.com>
In-Reply-To: <24CCCC428EFEA2469BF046DB3C7A8D2214131D@namail5.corp.adobe.com>
X-Enigmail-Version: 0.94.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: eme@irtf.org, Rémi Després <remi.despres@wanadoo.fr>
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="===============0442683451=="
Errors-To: eme-bounces@irtf.org


Henry Sinnreich wrote:
>> The transport layer no longer becomes an E2E service, and 
>> all the capabilities it provides - reliable transport in particular
>> must be reinvented at the app layer.
> 
> This seems to be the case for all P2P applications running on some
> overlay network such as the openDHT. It certainly applies to P2P SIP.

Agreed - that P2P reinvents networking at the application layer is
well-known.

> Please see http://p2psip.org 
> 
> Transport is indeed not e2e due to NAT and as we have seen, Skype for
> example manages to provide e2e over discontinuities at the IP layer.

Transport is E2E for NAT on dial-out, and dial-in when ports are
registered at the NAT. Otherwise, right, it's not E2E, and that's where
the problems have been.

Joe


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

v2.23.0 | Report a Bug | By Email