IETF Logo Mail Archive

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

"Mark Baker" <distobj@acm.org> Fri, 17 November 2006 16:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl6Yj-0000s2-KK; Fri, 17 Nov 2006 11:27:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl6Yi-0000pn-FN for eme@irtf.org; Fri, 17 Nov 2006 11:27:20 -0500
Received: from ug-out-1314.google.com ([66.249.92.170]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gl6Ye-0000qM-5j for eme@irtf.org; Fri, 17 Nov 2006 11:27:20 -0500
Received: by ug-out-1314.google.com with SMTP id o4so882278uge for <eme@irtf.org>; Fri, 17 Nov 2006 08:27:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=CQEetdrIvK1Yxr0c0+0Dvf886wTKCJZEeLwaEXyIEg9taqeyd6yzo0aTlsm79Wy1GcNTIewIZBY8y5oYm1DsAG37kKD3OcA1suaiTC6g05fBoCW5dl/YykMdt3hYXgKoPH+qhMCEL485ITKbfhDIaQE/BrB57Tpw1UleW3YqsQI=
Received: by 10.78.136.9 with SMTP id j9mr2079069hud.1163780834488; Fri, 17 Nov 2006 08:27:14 -0800 (PST)
Received: by 10.78.174.12 with HTTP; Fri, 17 Nov 2006 08:27:14 -0800 (PST)
Message-ID: <c70bc85d0611170827t36b9443fm2b5581721142b769@mail.gmail.com>
Date: Fri, 17 Nov 2006 11:27:14 -0500
From: Mark Baker <distobj@acm.org>
To: Saikat Guha <saikat@cs.cornell.edu>
Subject: Re: [EME] Re: transport recovery at the APP layer ?
In-Reply-To: <1163775763.8736.114.camel@sioux.systems.cs.cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E6F7A586E0A3F94D921755964F6BE00662575C@EXCHANGE2.cs.cornell.edu> <455B4094.1080400@isi.edu> <455B472A.9000303@wanadoo.fr> <455B48BD.5050201@isi.edu> <455B56C9.7080307@rd-iptech.com> <455B6358.4000703@isi.edu> <455C38AC.1090306@rd-iptech.com> <455CDFFF.8000500@isi.edu> <455D9BD5.7000900@wanadoo.fr> <1163775763.8736.114.camel@sioux.systems.cs.cornell.edu>
X-Google-Sender-Auth: 56cc7b99cd4e0603
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: eme <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>
Errors-To: eme-bounces@irtf.org

On 11/17/06, Saikat Guha <saikat@cs.cornell.edu> wrote:
> TCP can only provide guarantees about TCP, and not the application above
> it.

Thank you.  I was just writing a message which was going to say exactly that.

While it's certainly true that applications are free to attribute
application layer semantics to transport layer signals (e.g. HTTP
1.0), it is not the case that all applications do so (e.g. HTTP 1.1).

Mark.

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

v2.23.0 | Report a Bug | By Email