Re: [tcpm] dctcp

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Sat, 13 November 2010 16:45 UTC

Return-Path: <ananth@cisco.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 544E63A6BC7 for <tcpm@core3.amsl.com>; Sat, 13 Nov 2010 08:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1+h+aDglszxB for <tcpm@core3.amsl.com>; Sat, 13 Nov 2010 08:45:27 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 580ED3A6B7F for <tcpm@ietf.org>; Sat, 13 Nov 2010 08:45:27 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAN1P3kyrRN+K/2dsb2JhbACiVXGiQ5puhUoEhFqJD4gF
X-IronPort-AV: E=Sophos;i="4.59,191,1288569600"; d="scan'208";a="285569556"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 13 Nov 2010 16:46:03 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id oADGk3aC028652; Sat, 13 Nov 2010 16:46:03 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 13 Nov 2010 08:46:02 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 13 Nov 2010 08:46:01 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC580B2CD428@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4CDD9E20.8030308@isi.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] dctcp
Thread-Index: AcuCpTmpCgCrEwNrRv+yJ0jXNLbPigABOkEw
References: <5FDC413D5FA246468C200652D63E627A0B65CA86@LDCMVEXC1-PRD.hq.netapp.com> <4CDD9E20.8030308@isi.edu>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: Joe Touch <touch@isi.edu>, "Scheffenegger, Richard" <rs@netapp.com>
X-OriginalArrivalTime: 13 Nov 2010 16:46:02.0819 (UTC) FILETIME=[42023930:01CB8352]
Cc: Murari Sridharan <muraris@microsoft.com>, tcpm <tcpm@ietf.org>, Andrew McGregor <andrewmcgr@gmail.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 16:45:34 -0000

Well,

My thoughts here are :-

- If someone is using a protocol defined by IETF, then it is desirable
to abide by the standards, irrespective of the type of network. 

- interoperability across different devices (may be coming from
different vendors), using the same protocol, is one of the reason you
need standards! 

-  From an implementation perspective you don't want "private TCP" and
"public TCP" in the same stack since the same stack needs to cater to
TCP connections from *both* private and public networks!

- The problems and the solutions which are posed by the data center
environments may not be unique. The question to ask is : "what is the
problem and whether the problems and solutions would have a generic
applicability.  

- Also how do you draw a boundary as to a what is private network and
what isn't ? Why is data center environment considered a "private
network" ?

IMO, it is an issue that can be well addressed (if there is a need) by
the IETF,  if changes are being planned with TCP protocol, yes TCPM is
the right place for such efforts.

$0.02,
-Anantha

-----Original Message-----
From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of
Joe Touch
Sent: Friday, November 12, 2010 12:06 PM
To: Scheffenegger, Richard
Cc: Murari Sridharan; tcpm; Andrew McGregor
Subject: Re: [tcpm] dctcp



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
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm