IETF Logo Mail Archive

Re: [tcpm] dctcp

Andrew McGregor <andrewmcgr@gmail.com> Sat, 13 November 2010 10:04 UTC

Return-Path: <andrewmcgr@gmail.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E7DC28C0CE for <tcpm@core3.amsl.com>; Sat, 13 Nov 2010 02:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VIjnKeZe8FSI for <tcpm@core3.amsl.com>; Sat, 13 Nov 2010 02:04:07 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9FB0028B797 for <tcpm@ietf.org>; Sat, 13 Nov 2010 02:04:07 -0800 (PST)
Received: by iwn40 with SMTP id 40so4762996iwn.31 for <tcpm@ietf.org>; Sat, 13 Nov 2010 02:04:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=sbOHOdAyalf4fnvZu33zIR/Atk5gG1WPyI8JtaTHHm0=; b=aM3QEVNjNbNpg+tEF/Fp5nd2ZS7lhf01G14WpHkRajslC/LvBrv8jSvv6OyE3vuenv gjGbJpwanyKytVGk5ILeQ/k1Mwr0oubh1+lq6bKSAB5hRYQuZ0s2t+6DP+63OGA1Zffg X9CWDUiAnzcZv6C54ByYhI+vLi5mlWSar82HY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=mryi8hP5Y4YX/lZQVBrTUUd8BGB5QldXOGFCaomMOswxOr4UVfD+BZFsvgfu96Cc9R 6XV6X50IjVVf2yI/p+a3zBL4idxdcJ+O8BRFpHk+oS3FaAzH9GbpKhwSTVcC9fjJvWsk bBAeHBpffCL7YIPYdQ7qgxjcKY+XeydFQrtDI=
Received: by 10.231.37.201 with SMTP id y9mr2888392ibd.76.1289642681846; Sat, 13 Nov 2010 02:04:41 -0800 (PST)
Received: from n11648178139.netvigator.com (n11648178139.netvigator.com [116.48.178.139]) by mx.google.com with ESMTPS id d21sm4689312ibg.9.2010.11.13.02.04.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 13 Nov 2010 02:04:40 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Andrew McGregor <andrewmcgr@gmail.com>
In-Reply-To: <4CDD9E20.8030308@isi.edu>
Date: Sat, 13 Nov 2010 17:59:28 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A78D89F-F754-4A7B-A2EC-7B871B351E5A@gmail.com>
References: <5FDC413D5FA246468C200652D63E627A0B65CA86@LDCMVEXC1-PRD.hq.netapp.com> <4CDD9E20.8030308@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1081)
X-Mailman-Approved-At: Sun, 14 Nov 2010 10:20:02 -0800
Cc: tcpm <tcpm@ietf.org>, Murari Sridharan <muraris@microsoft.com>
Subject: Re: [tcpm] dctcp
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Nov 2010 10:04:08 -0000

That's true, but if it can be made to happen automatically that would, I suspect, be in scope.

Andrew

On 13/11/2010, at 4:05 AM, Joe Touch wrote:

> 
> 
> On 11/11/2010 3:51 AM, Scheffenegger, Richard wrote:
> ...
>> Reading the TSVAREA material, it was also pointed out (storage teaser -
>> NFSv4, iSCSI) that TCPM may need to look closer at datacenter
>> environments rather soon.
> 
> Tuning TCP for private networks (i.e., not using the Internet, or competing with Internet flows) seems out of scope for TCPM.
> 
> It might not even be relevant elsewhere in the IETF, except as an issue of common interest. Protocols running over private networks don't need to adhere to standards.
> 
> Joe

v2.23.0 | Report a Bug | By Email