Re: [tcpm] Is this a problem?

Lloyd Wood <L.Wood@surrey.ac.uk> Wed, 21 November 2007 06:55 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IujUj-0004wM-Q2; Wed, 21 Nov 2007 01:55:33 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1IujUh-0004w8-Uh for tcpm-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 01:55:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IujUh-0004w0-6I for tcpm@ietf.org; Wed, 21 Nov 2007 01:55:31 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IujUc-0002Tq-Br for tcpm@ietf.org; Wed, 21 Nov 2007 01:55:30 -0500
X-IronPort-AV: E=Sophos;i="4.21,444,1188770400"; d="scan'208";a="158327188"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 21 Nov 2007 07:55:26 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAL6tPIa020563; Wed, 21 Nov 2007 07:55:25 +0100
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lAL6tNUm010027; Wed, 21 Nov 2007 06:55:25 GMT
Received: from lwood-wxp01.cisco.com (ams3-vpn-dhcp4559.cisco.com [10.61.81.206]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id GAA05704; Wed, 21 Nov 2007 06:55:21 GMT
Message-Id: <200711210655.GAA05704@cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 21 Nov 2007 06:55:11 +0000
To: Ethan Blanton <eblanton@cs.ohiou.edu>, tcpm@ietf.org
From: Lloyd Wood <L.Wood@surrey.ac.uk>
Subject: Re: [tcpm] Is this a problem?
In-Reply-To: <20071121011105.GQ5881@elb.elitists.net>
References: <299249.88905.qm@web31703.mail.mud.yahoo.com> <20071120121238.740442F6E0C@lawyers.icir.org> <200711202201.WAA05926@cisco.com> <47437551.7020205@isi.edu> <20071121004427.GI26548@cisco.com> <20071121011105.GQ5881@elb.elitists.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Authentication-Results: ams-dkim-1; header.From=L.Wood@surrey.ac.uk; dkim=neutral
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc:
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

At Tuesday 20/11/2007 20:11 -0500, Ethan Blanton wrote:

>Chandrashekhar Appanna spake unto us the following wisdom:
>> On Tue, Nov 20, 2007 at 04:01:21PM -0800, Joe Touch wrote:
>> > Lloyd Wood wrote:
>> > > The community standardised TCP window size advertisements. That's a
>> > > local resource control issue, surely?
>> > 
>> > That's something you have to tell the other end, i.e., it requires a
>> > change to the protocol on the wire. This one can be implemented without
>> > any change to the protocol at all - entirely at the app layer.
>> 
>> And I think the authors are positioning that there is a better place
>> in the architecture to solve this and that is in tcp. I think it is
>> boiling down to just a matter of opinions so far.. esp when you keep
>> repeating that it could be solved in the app layer (for as long as I
>> recall!!)
>
>Joe keeps making this point because it is _very important_.  Any
>feature which can be accomplished at Layer N can be accomplished at
>Layer N - 1, and vice-versa.  

One obvious exception: end-to-end reliabililty.

Another: error-coding for the channel.

L.


_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm