Re: [Ips] [rddp] STORM proposed charter - 31 May 2009 version

<Black_David@emc.com> Mon, 15 June 2009 19:50 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B800C3A69EB; Mon, 15 Jun 2009 12:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.273
X-Spam-Level:
X-Spam-Status: No, score=-6.273 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 RwxqjaN+FU+j; Mon, 15 Jun 2009 12:50:24 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 9FAB23A6A74; Mon, 15 Jun 2009 12:50:24 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id n5FJoUBk005214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 15:50:30 -0400
Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Mon, 15 Jun 2009 15:50:25 -0400
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n5FJoLee022636; Mon, 15 Jun 2009 15:50:25 -0400
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 15 Jun 2009 15:50:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9EDF2.85F8DD12"
Date: Mon, 15 Jun 2009 15:50:23 -0400
Message-ID: <9FA859626025B64FBC2AF149D97C944A02F62252@CORPUSMX80A.corp.emc.com>
In-Reply-To: <DBFBCB90599B2C46992032279293D10010A0A1058C@SJEXCHCCR01.corp.ad.broadcom.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rddp] STORM proposed charter - 31 May 2009 version
Thread-Index: AcnjyKvkptOEgm1dRES7kc7ggd6dTgKILcEAAABB2GAAAMsvQAABMiVw
References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com><517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> <9FA859626025B64FBC2AF149D97C944A02F621CD@CORPUSMX80A.corp.emc.com> <DBFBCB90599B2C46992032279293D10010A0A1058C@SJEXCHCCR01.corp.ad.broadcom.com>
From: <Black_David@emc.com>
To: <pthaler@broadcom.com>, <arkady.kanevsky@gmail.com>
X-OriginalArrivalTime: 15 Jun 2009 19:50:24.0651 (UTC) FILETIME=[8638D5B0:01C9EDF2]
X-EMM-EM: Active
Cc: imss@ietf.org, ips@ietf.org, storm@ietf.org, rddp@ietf.org
Subject: Re: [Ips] [rddp] STORM proposed charter - 31 May 2009 version
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2009 19:50:26 -0000

Hmm .. I read:
 
"but not limited to TCP with MPA markers and SCTP" as being motivated
by non-IP uses, e.g., InfiniBand and FC.  Arkady?

Thanks,
--David


 


________________________________

	From: Pat Thaler [mailto:pthaler@broadcom.com] 
	Sent: Monday, June 15, 2009 3:17 PM
	To: Black, David; arkady.kanevsky@gmail.com
	Cc: imss@ietf.org; ips@ietf.org; rddp@ietf.org; storm@ietf.org
	Subject: RE: [rddp] STORM proposed charter - 31 May 2009 version
	
	
	Did you mean "are not based on TCP" rather than "are not based
on IP"?
	Arkady was asking about connection setup for SCTP which the
former fits but not the latter.
	 
	Regards,
	Pat

________________________________

	From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On
Behalf Of Black_David@emc.com
	Sent: Monday, June 15, 2009 11:53 AM
	To: Black_David@emc.com; arkady.kanevsky@gmail.com
	Cc: imss@ietf.org; ips@ietf.org; storm@ietf.org; rddp@ietf.org
	Subject: Re: [Ips] [rddp] STORM proposed charter - 31 May 2009
version
	
	
	And here's what I just did to that bullet ...

	(5) RDDP Connection Setup: Good support for MPI applications
requires a small update to MPA startup functionality to allow either end
of the connection to initiate. In addition, a couple of minor changes to
RDDP connection setup (based on implementation experience) are needed to
generalize it for effective use with protocols that are not based on IP.

	I'm about to send the result to Lars for wider review ...

	Thanks,
	--David
	

	 


________________________________

		From: rddp-bounces@ietf.org
[mailto:rddp-bounces@ietf.org] On Behalf Of Black_David@emc.com
		Sent: Monday, June 15, 2009 2:46 PM
		To: arkady.kanevsky@gmail.com
		Cc: imss@ietf.org; ips@ietf.org; rddp@ietf.org;
storm@ietf.org
		Subject: Re: [rddp] STORM proposed charter - 31 May 2009
version
		
		
		Arkady,
		 
		I'll beef up the bullet, but probably not with that
		degree of specifics.  Thanks for pointing this out,
		and I apologize for the delay in responding.

		Thanks,
		--David
		

		 


________________________________

			From: arkady kanevsky
[mailto:arkady.kanevsky@gmail.com] 
			Sent: Tuesday, June 02, 2009 5:26 PM
			To: Black, David
			Cc: storm@ietf.org; imss@ietf.org; ips@ietf.org;
rddp@ietf.org
			Subject: Re: [rddp] STORM proposed charter - 31
May 2009 version
			
			
			David, 
			The description of RDDP MPA bullet is too
narrow.
			(5) RDDP MPA: Good support for MPI applications
requires a small
			update to MPA startup functionality to allow
either end
			of the connection to initiate.

			This bullet should also cover ORD/IRD
negotiation as part of
			connection setup. Also current RDDP connection
setup is part of MPA
			spec which is primarily for TCP stream markers.
This bullet should provide
			RDDP connection setup for both TCP and SCTP and
for any message based
			protocol.

			How about:
			(5) RDDP Connection Setup: Good support for MPI
applications requires a small
			update to MPA startup functionality to allow
either end
			of the connection to initiate. Add RDMA Read
credits to RDDP Connection
			        Setup. Make RDDP connection setup to be
applicable for any message based
			        protocols, including but not limited to
TCP with MPA markers and SCTP.

			I hope it is not too late to beef up this
bullet.
			Thanks,
			Arkady

			On Sun, May 31, 2009 at 4:03 PM,
<Black_David@emc.com>; wrote:
			

				What I believe is the final draft of the
proposed charter
				for the STORM WG is attached; I've done
a bunch of editing
				and added the info about T10 and T11 doc
access.  This is
				about to go out for wider review.
				
				Also, a reminder that STORM discussion
will stop cc:'ing
				other mailing lists soon.  If you're
interested in STORM
				work, please subscribe to the
storm@ietf.org mailing list:
	
https://www.ietf.org/mailman/listinfo/storm
				
				Finally - this is a near-final reminder
that the rddp@ietf.org
				mailing list will be closing soon - all
discussion of RDDP
				protocols will move to the
storm@ietf.org mailing list.
				
				Thanks,
				--David
	
----------------------------------------------------
				David L. Black, Distinguished Engineer
				EMC Corporation, 176 South St.,
Hopkinton, MA  01748
				+1 (508) 293-7953             FAX: +1
(508) 293-7786
				black_david@emc.com        Mobile: +1
(978) 394-7754
	
----------------------------------------------------
				
	
_______________________________________________
				rddp mailing list
				rddp@ietf.org
	
https://www.ietf.org/mailman/listinfo/rddp
				
				




			-- 
			Cheers,
			Arkady Kanevsky