From ietfdbh@comcast.net Tue Jun 2 07:20:19 2009 Return-Path: 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 6779328C23B for ; Tue, 2 Jun 2009 07:20:19 -0700 (PDT) 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 2vNaS03fJ-WF for ; Tue, 2 Jun 2009 07:20:19 -0700 (PDT) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 093593A6A87 for ; Tue, 2 Jun 2009 07:19:34 -0700 (PDT) Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20]) by QMTA08.westchester.pa.mail.comcast.net with comcast id yz771b0030SCNGk582KTdh; Tue, 02 Jun 2009 14:19:27 +0000 Received: from Harrington73653 ([24.147.240.21]) by OMTA09.westchester.pa.mail.comcast.net with comcast id z2KT1b0030UQ6dC3V2KTul; Tue, 02 Jun 2009 14:19:27 +0000 From: "David Harrington" To: , References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> Date: Tue, 2 Jun 2009 10:19:24 -0400 Message-ID: <01b801c9e38d$21e01fc0$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-index: AcniKt3kwsrwnKNkQcK1TD1CcyrQkgBYhoOg Cc: imss@ietf.org, ips@ietf.org, rddp@ietf.org Subject: Re: [Ips] STORM proposed charter - 31 May 2009 version X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 14:20:19 -0000 Hi, I am satisfied with the text of the charter. The milestones look aggressive to me, but you have a better feel for the amount of work involved. Thanks for the update, David Harrington dbharrington@comcast.net ietfdbh@comcast.net dharrington@huawei.com > -----Original Message----- > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On > Behalf Of Black_David@emc.com > Sent: Sunday, May 31, 2009 4:03 PM > To: storm@ietf.org > Cc: imss@ietf.org; ips@ietf.org; rddp@ietf.org > Subject: [Ips] STORM proposed charter - 31 May 2009 version > Importance: High > > 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 > ---------------------------------------------------- > From arkady.kanevsky@gmail.com Tue Jun 2 14:25:34 2009 Return-Path: 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 A8FAE3A68E0; Tue, 2 Jun 2009 14:25:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 nAVyU8yHBU0H; Tue, 2 Jun 2009 14:25:33 -0700 (PDT) Received: from mail-qy0-f136.google.com (mail-qy0-f136.google.com [209.85.221.136]) by core3.amsl.com (Postfix) with ESMTP id 1EB8A3A687A; Tue, 2 Jun 2009 14:25:33 -0700 (PDT) Received: by qyk42 with SMTP id 42so103782qyk.29 for ; Tue, 02 Jun 2009 14:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=eV8N6CqXXmC9IjasAn9CI8289B6wja2KOHf/x8QaQ9U=; b=FqoA+yIjdsjoAWH4AKU37DdEWRaqX06tGXIGl8FOqy2yFHSquRThVwuOcd4hZ7vVwM 38MPyrzM9orEXYdZYHzf5JCE3srg9psx+I8tpOp7O5GHlx5eKatSBeMfQm03PGoLSrLt Du5BkuB6NJq2fOy2PWFhshfyRNEcKU4PUtnCY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XdG/6cw5hPivk1xNXCveix7Vo/NMcd+d66UvStRotqnA4XclH1FNap2B9tKUrCUiMX VKjjlliwYcrw63B+tt3W4mnccmTwg++IQSVmtN4jEYteyYAYwHFj7l7VTs7q6easdFGb tmesaL+jEh99JYt+hUMrOgJotso0ijz0XtaK8= MIME-Version: 1.0 Received: by 10.151.121.3 with SMTP id y3mr504667ybm.24.1243977930713; Tue, 02 Jun 2009 14:25:30 -0700 (PDT) In-Reply-To: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> Date: Tue, 2 Jun 2009 17:25:30 -0400 Message-ID: <517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> From: arkady kanevsky To: Black_David@emc.com Content-Type: multipart/alternative; boundary=001e680f1634ab2c3a046b642e61 X-Mailman-Approved-At: Wed, 03 Jun 2009 09:17:04 -0700 Cc: imss@ietf.org, ips@ietf.org, rddp@ietf.org, storm@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 21:25:34 -0000 --001e680f1634ab2c3a046b642e61 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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, 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 --001e680f1634ab2c3a046b642e61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 th= e connection to initiate.

This bullet should also = cover ORD/IRD negotiation as part of
connection setup. Also curre= nt RDDP connection setup is part of MPA
spec which is=A0primarily=A0for 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 requ= ires a small
update to MPA startup functionality to allow either end
of= the connection to initiate. Add RDMA Read credits to RDDP Connection
=
=A0=A0 =A0 =A0 =A0Setup. Make RDDP connection setup to be applicable f= or any message based
=A0=A0 =A0 =A0 =A0protocols, 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. =A0This is
about to go out for wider review.

Also, a reminder that STORM discussion will stop cc:'ing
other mailing lists soon. =A0If you're interested in STORM
work, please subscribe to the storm@ietf.= org mailing list:
h= ttps://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 =A001748
+1 (508) 293-7953 =A0 =A0 =A0 =A0 =A0 =A0 FAX: +1 (508) 293-7786
black_david@emc.com =A0 =A0 =A0 = =A0Mobile: +1 (978) 394-7754
----------------------------------------------------

_______________________________________________
rddp mailing list
rddp@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/rddp




--
Cheers,
Arkady K= anevsky
--001e680f1634ab2c3a046b642e61-- From Black_David@emc.com Mon Jun 15 11:46:04 2009 Return-Path: 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 7553A3A6B81; Mon, 15 Jun 2009 11:46:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.949 X-Spam-Level: X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.649, 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 gbTk7BF-iYTm; Mon, 15 Jun 2009 11:46:03 -0700 (PDT) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 439D13A6ABD; Mon, 15 Jun 2009 11:46:03 -0700 (PDT) Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id n5FIjt8q003449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:45:55 -0400 Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si03.isus.emc.com (Tablus Interceptor); Mon, 15 Jun 2009 14:45:46 -0400 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n5FIjg2N011504; Mon, 15 Jun 2009 14:45:45 -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 14:45:44 -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_01C9EDE9.7D1101BA" Date: Mon, 15 Jun 2009 14:45:43 -0400 Message-ID: <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> In-Reply-To: <517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rddp] STORM proposed charter - 31 May 2009 version Thread-Index: AcnjyKvkptOEgm1dRES7kc7ggd6dTgKILcEA References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> <517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> From: To: X-OriginalArrivalTime: 15 Jun 2009 18:45:44.0317 (UTC) FILETIME=[7D5CDAD0:01C9EDE9] X-EMM-EM: Active Cc: imss@ietf.org, ips@ietf.org, rddp@ietf.org, storm@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 18:46:04 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9EDE9.7D1101BA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Arkady, =20 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 =20 ________________________________ From: arkady kanevsky [mailto:arkady.kanevsky@gmail.com]=20 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 =09 =09 David,=20 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, wrote: =09 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. =09 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 =09 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. =09 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 ---------------------------------------------------- =09 _______________________________________________ rddp mailing list rddp@ietf.org https://www.ietf.org/mailman/listinfo/rddp =09 =09 --=20 Cheers, Arkady Kanevsky =09 ------_=_NextPart_001_01C9EDE9.7D1101BA Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Arkady,
 
I'll beef up=20 the bullet, but probably not with that
degree of=20 specifics.  Thanks for pointing this out,
and I=20 apologize for the delay in responding.

Thanks,
--David

 

From: arkady kanevsky=20 [mailto:arkady.kanevsky@gmail.com]
Sent: Tuesday, June 02, = 2009=20 5:26 PM
To: Black, David
Cc: storm@ietf.org;=20 imss@ietf.org; ips@ietf.org; rddp@ietf.org
Subject: Re: = [rddp] STORM=20 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=20 startup functionality to allow either end
of = the=20 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=20 should provide
RDDP connection setup for both TCP and SCTP and for any message=20 based
protocol.

How about:
(5) RDDP Connection Setup: Good support for MPI applications = requires a=20 small
update to MPA=20 startup functionality to allow either end
of = the=20 connection to initiate. Add RDMA Read credits to RDDP Connection
        Setup. Make RDDP connection = setup to be=20 applicable for any message based
        protocols, including but not = limited to=20 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=20 I believe is the final draft of the proposed charter
for the = STORM WG is=20 attached; I've done a bunch of editing
and added the info about = T10 and=20 T11 doc access.  This is
about to go out for wider=20 review.

Also, a reminder that STORM discussion will stop=20 cc:'ing
other mailing lists soon.  If you're interested in=20 STORM
work, please subscribe to the storm@ietf.org mailing = list:
https://www.ietf.org/mailman/listinfo/storm

Fi= nally=20 - this is a near-final reminder that the rddp@ietf.org
mailing list will = be=20 closing soon - all discussion of RDDP
protocols will move to the = storm@ietf.org mailing=20 = list.

Thanks,
--David
--------------------------------------= --------------
David=20 L. Black, Distinguished Engineer
EMC Corporation, 176 South St.,=20 Hopkinton, MA  01748
+1 (508) 293-7953       =  =20     FAX: +1 (508) 293-7786
black_david@emc.com   =  =20    Mobile: +1 (978)=20 = 394-7754
----------------------------------------------------

_= ______________________________________________
rddp=20 mailing list
rddp@ietf.org
https://www.ietf.org/mailman/listinfo/rddp



--
Cheers,
Arkady=20 Kanevsky
------_=_NextPart_001_01C9EDE9.7D1101BA-- From Black_David@emc.com Mon Jun 15 11:53:30 2009 Return-Path: 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 0D2AB3A6C7E; Mon, 15 Jun 2009 11:53:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.165 X-Spam-Level: X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.433, 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 3WUQcPVDTH+S; Mon, 15 Jun 2009 11:53:28 -0700 (PDT) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 968863A6D04; Mon, 15 Jun 2009 11:53:28 -0700 (PDT) Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id n5FIrPX2012402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:53:25 -0400 Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si03.isus.emc.com (Tablus Interceptor); Mon, 15 Jun 2009 14:53:25 -0400 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n5FIrMVZ022311; Mon, 15 Jun 2009 14:53:24 -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 14:53: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_01C9EDEA.8F3ED95C" Date: Mon, 15 Jun 2009 14:53:23 -0400 Message-ID: <9FA859626025B64FBC2AF149D97C944A02F621CD@CORPUSMX80A.corp.emc.com> In-Reply-To: <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rddp] STORM proposed charter - 31 May 2009 version Thread-Index: AcnjyKvkptOEgm1dRES7kc7ggd6dTgKILcEAAABB2GA= References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com><517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> From: To: , X-OriginalArrivalTime: 15 Jun 2009 18:53:24.0282 (UTC) FILETIME=[8F85F1A0:01C9EDEA] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 18:53:30 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9EDEA.8F3ED95C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 =20 ________________________________ 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 =09 =09 Arkady, =20 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 =09 =20 ________________________________ 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 =09 =09 David,=20 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, wrote: =09 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. =09 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 =09 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. =09 Thanks, --David =09 ---------------------------------------------------- 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 =09 ---------------------------------------------------- =09 _______________________________________________ rddp mailing list rddp@ietf.org https://www.ietf.org/mailman/listinfo/rddp =09 =09 --=20 Cheers, Arkady Kanevsky =09 ------_=_NextPart_001_01C9EDEA.8F3ED95C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

And here's=20 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=20 allow either end of the = connection to=20 initiate. In addition, a couple of minor=20 changes to RDDP connection setup (based on implementation experience) are needed to generalize = it for=20 effective use with protocols = that are not=20 based on IP.

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

Thanks,
--David

 

From: rddp-bounces@ietf.org=20 [mailto:rddp-bounces@ietf.org] On Behalf Of=20 Black_David@emc.com
Sent: Monday, June 15, 2009 2:46=20 PM
To: arkady.kanevsky@gmail.com
Cc: = imss@ietf.org;=20 ips@ietf.org; rddp@ietf.org; storm@ietf.org
Subject: Re: = [rddp]=20 STORM proposed charter - 31 May 2009 version

Arkady,
 
I'll beef=20 up the bullet, but probably not with that
degree of=20 specifics.  Thanks for pointing this out,
and I=20 apologize for the delay in responding.

Thanks,
--David

 

From: arkady kanevsky=20 [mailto:arkady.kanevsky@gmail.com]
Sent: Tuesday, June = 02, 2009=20 5:26 PM
To: Black, David
Cc: storm@ietf.org;=20 imss@ietf.org; ips@ietf.org; rddp@ietf.org
Subject: Re: = [rddp]=20 STORM proposed charter - 31 May 2009 version

David,=20
The description of RDDP MPA bullet is too narrow.
(5) RDDP MPA: Good support for MPI applications requires a = small
update to=20 MPA startup functionality to allow either end
of the=20 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=20 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=20 small
update to=20 MPA startup functionality to allow either end
of the=20 connection to initiate. Add RDMA Read credits to RDDP = Connection
        Setup. Make RDDP connection = setup to=20 be applicable for any message based
        protocols, including but not = limited=20 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>=20 wrote:
What=20 I believe is the final draft of the proposed charter
for the = STORM WG=20 is attached; I've done a bunch of editing
and added the info = about T10=20 and T11 doc access.  This is
about to go out for wider=20 review.

Also, a reminder that STORM discussion will stop=20 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

Fi= nally=20 - this is a near-final reminder that the rddp@ietf.org
mailing list = will be=20 closing soon - all discussion of RDDP
protocols will move to = the storm@ietf.org mailing=20 = list.

Thanks,
--David
--------------------------------------= --------------
David=20 L. Black, Distinguished Engineer
EMC Corporation, 176 South = St.,=20 Hopkinton, MA  01748
+1 (508) 293-7953     =    =20     FAX: +1 (508) 293-7786
black_david@emc.com   =  =20    Mobile: +1 (978)=20 = 394-7754
----------------------------------------------------

_= ______________________________________________
rddp=20 mailing list
rddp@ietf.org
https://www.ietf.org/mailman/listinfo/rddp



--
Cheers,
Arkady=20 Kanevsky
------_=_NextPart_001_01C9EDEA.8F3ED95C-- From pthaler@broadcom.com Mon Jun 15 12:17:40 2009 Return-Path: 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 D38443A6CC0; Mon, 15 Jun 2009 12:17:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 8DpGyWpcot-B; Mon, 15 Jun 2009 12:17:39 -0700 (PDT) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 4BE683A6A74; Mon, 15 Jun 2009 12:17:39 -0700 (PDT) Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 15 Jun 2009 12:17:07 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from SJEXCHCCR01.corp.ad.broadcom.com ([10.252.49.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Mon, 15 Jun 2009 12:17:07 -0700 From: "Pat Thaler" To: "Black_David@emc.com" , "arkady.kanevsky@gmail.com" Date: Mon, 15 Jun 2009 12:17:05 -0700 Thread-Topic: [rddp] STORM proposed charter - 31 May 2009 version Thread-Index: AcnjyKvkptOEgm1dRES7kc7ggd6dTgKILcEAAABB2GAAAMsvQA== Message-ID: References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com><517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> <9FA859626025B64FBC2AF149D97C944A02F621CD@CORPUSMX80A.corp.emc.com> In-Reply-To: <9FA859626025B64FBC2AF149D97C944A02F621CD@CORPUSMX80A.corp.emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 662841B93847906573-01-01 Content-Type: multipart/alternative; boundary=_000_DBFBCB90599B2C46992032279293D10010A0A1058CSJEXCHCCR01co_ 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 19:17:40 -0000 --_000_DBFBCB90599B2C46992032279293D10010A0A1058CSJEXCHCCR01co_ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 sma= ll update to MPA startup functionality to allow either end of the connectio= n to initiate. In addition, a couple of minor changes to RDDP connection se= tup (based on implementation experience) are needed to generalize it for ef= fective 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 Bla= ck_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 sma= ll 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 SC= TP. I hope it is not too late to beef up this bullet. Thanks, Arkady On Sun, May 31, 2009 at 4:03 PM, > 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 li= st. 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 --_000_DBFBCB90599B2C46992032279293D10010A0A1058CSJEXCHCCR01co_ Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable
Did you mean "are not based on TCP" rather than "a= re not=20 based on IP"?
Arkady was asking about connection setup for SCTP = which the=20 former fits but not the latter.
 
Regards,
Pat

From: ips-bounces@ietf.org=20 [mailto:ips-bounces@ietf.org] On Behalf Of=20 Black_David@emc.com
Sent: Monday, June 15, 2009 11:53=20 AM
To: Black_David@emc.com; arkady.kanevsky@gmail.com
Cc:=20 imss@ietf.org; ips@ietf.org; storm@ietf.org; rddp@ietf.org
Subject:=20 Re: [Ips] [rddp] STORM proposed charter - 31 May 2009=20 version

And= here's=20 what I just did to that bullet ...

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

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

Thanks,
--David

 

From: rddp-bounces@ietf.org=20 [mailto:rddp-bounces@ietf.org] On Behalf Of=20 Black_David@emc.com
Sent: Monday, June 15, 2009 2:46=20 PM
To: arkady.kanevsky@gmail.com
Cc: imss@ietf.org;=20 ips@ietf.org; rddp@ietf.org; storm@ietf.org
Subject: Re: [rddp]= =20 STORM proposed charter - 31 May 2009 version

Arkady,
 
I'll beef=20 up the bullet, but probably not with that
degree of=20 specifics.  Thanks for pointing this out,
and I=20 apologize for the delay in responding.

Thanks,
--David

 

From: arkady kanevsky=20 [mailto:arkady.kanevsky@gmail.com]
Sent: Tuesday, June 02, 2= 009=20 5:26 PM
To: Black, David
Cc: storm@ietf.org;=20 imss@ietf.org; ips@ietf.org; rddp@ietf.org
Subject: Re: [rddp= ]=20 STORM proposed charter - 31 May 2009 version

David,=20
The description of RDDP MPA bullet is too narrow.
(5) RDDP MPA: Good support for MPI applications requires a small
upd= ate to=20 MPA startup functionality to allow either end
of = the=20 connection to initiate.

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

How about:
(5) RDDP Connection Setup: Good support for MPI applications requi= res a=20 small
upd= ate to=20 MPA startup functionality to allow either end
of = the=20 connection to initiate. Add RDMA Read credits to RDDP Connection
        Setup. Make RDDP connection setup= to=20 be applicable for any message based
        protocols, including but not limi= ted=20 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>= =20 wrote:
What=20 I believe is the final draft of the proposed charter
for the STORM= WG=20 is attached; I've done a bunch of editing
and added the info about= T10=20 and T11 doc access.  This is
about to go out for wider=20 review.

Also, a reminder that STORM discussion will stop=20 cc:'ing
other mailing lists soon.  If you're interested in=20 STORM
work, please subscribe to the storm@ietf.org mailing list:
https://www.ietf.org/mailman/listinfo/storm
Finally=20 - this is a near-final reminder that the rddp@ietf.org
mailing list will = be=20 closing soon - all discussion of RDDP
protocols will move to the <= A=20 href=3D"mailto:storm@ietf.org">storm@ietf.org mailing=20 list.

Thanks,
--David
----------------------------------= ------------------
David=20 L. Black, Distinguished Engineer
EMC Corporation, 176 South St.,=20 Hopkinton, MA  01748
+1 (508) 293-7953       &= nbsp;=20     FAX: +1 (508) 293-7786
black_david@emc.com   &n= bsp;=20    Mobile: +1 (978)=20 394-7754
----------------------------------------------------
<= BR>_______________________________________________
rddp=20 mailing list
rddp@ietf.orghttps://www.ietf.org/mailman/listinfo/rddp


--
Cheers,
Arkady=20 Kanevsky
--_000_DBFBCB90599B2C46992032279293D10010A0A1058CSJEXCHCCR01co_-- From Black_David@emc.com Mon Jun 15 12:50:26 2009 Return-Path: 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: 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> From: To: , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 19:50:26 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9EDF2.85F8DD12 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hmm .. I read: =20 "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 =20 ________________________________ From: Pat Thaler [mailto:pthaler@broadcom.com]=20 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 =09 =09 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. =20 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 =09 =09 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 =09 =20 ________________________________ 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 =09 =09 Arkady, =20 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 =09 =20 ________________________________ From: arkady kanevsky [mailto:arkady.kanevsky@gmail.com]=20 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 =09 =09 David,=20 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, wrote: =09 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. =09 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: =09 https://www.ietf.org/mailman/listinfo/storm =09 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. =09 Thanks, --David =09 ---------------------------------------------------- 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 =09 ---------------------------------------------------- =09 =09 _______________________________________________ rddp mailing list rddp@ietf.org =09 https://www.ietf.org/mailman/listinfo/rddp =09 =09 --=20 Cheers, Arkady Kanevsky =09 ------_=_NextPart_001_01C9EDF2.85F8DD12 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hmm .. I=20 read:
 
"but not limited to TCP = with MPA=20 markers and SCTP" as being = motivated
by non-IP uses, e.g., InfiniBand = and=20 FC.  Arkady?

Thanks,
--David

 

From: Pat Thaler = [mailto:pthaler@broadcom.com]=20
Sent: Monday, June 15, 2009 3:17 PM
To: Black, = David;=20 arkady.kanevsky@gmail.com
Cc: imss@ietf.org; ips@ietf.org;=20 rddp@ietf.org; storm@ietf.org
Subject: RE: [rddp] STORM = proposed=20 charter - 31 May 2009 version

Did you mean "are not based on TCP" rather = than "are not=20 based on IP"?
Arkady was asking about connection setup for = SCTP which=20 the former fits but not the latter.
 
Regards,
Pat

From: ips-bounces@ietf.org=20 [mailto:ips-bounces@ietf.org] On Behalf Of=20 Black_David@emc.com
Sent: Monday, June 15, 2009 11:53=20 AM
To: Black_David@emc.com; = arkady.kanevsky@gmail.com
Cc:=20 imss@ietf.org; ips@ietf.org; storm@ietf.org; = rddp@ietf.org
Subject:=20 Re: [Ips] [rddp] STORM proposed charter - 31 May 2009=20 version

And here's=20 what I just did to that bullet ...

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

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

Thanks,
--David

 

From: rddp-bounces@ietf.org=20 [mailto:rddp-bounces@ietf.org] On Behalf Of=20 Black_David@emc.com
Sent: Monday, June 15, 2009 2:46=20 PM
To: arkady.kanevsky@gmail.com
Cc: = imss@ietf.org;=20 ips@ietf.org; rddp@ietf.org; storm@ietf.org
Subject: Re: = [rddp]=20 STORM proposed charter - 31 May 2009 version

Arkady,
 
I'll=20 beef up the bullet, but probably not with that
degree=20 of specifics.  Thanks for pointing this = out,
and I=20 apologize for the delay in responding.

Thanks,
--David

 

From: arkady kanevsky=20 [mailto:arkady.kanevsky@gmail.com]
Sent: Tuesday, June = 02, 2009=20 5:26 PM
To: Black, David
Cc: storm@ietf.org;=20 imss@ietf.org; ips@ietf.org; rddp@ietf.org
Subject: Re: = [rddp]=20 STORM proposed charter - 31 May 2009 version

David,=20
The description of RDDP MPA bullet is too narrow.
(5) RDDP MPA: Good support for MPI applications requires a=20 small
update to=20 MPA startup functionality to allow either end
of the=20 connection to initiate.

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

How about:
(5) RDDP Connection Setup: Good support for MPI applications = requires=20 a small
update to=20 MPA startup functionality to allow either end
of the=20 connection to initiate. Add RDMA Read credits to RDDP = Connection
        Setup. Make RDDP connection = setup to=20 be applicable for any message based
        protocols, including but not = limited=20 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>=20 wrote:
What=20 I believe is the final draft of the proposed charter
for the = STORM WG=20 is attached; I've done a bunch of editing
and added the info = about=20 T10 and T11 doc access.  This is
about to go out for = wider=20 review.

Also, a reminder that STORM discussion will stop=20 cc:'ing
other mailing lists soon.  If you're interested = in=20 STORM
work, please subscribe to the storm@ietf.org mailing = list:
https://www.ietf.org/mailman/listinfo/storm

Fi= nally=20 - this is a near-final reminder that the rddp@ietf.org
mailing list = will be=20 closing soon - all discussion of RDDP
protocols will move to = the storm@ietf.org mailing=20 = list.

Thanks,
--David
--------------------------------------= --------------
David=20 L. Black, Distinguished Engineer
EMC Corporation, 176 South = St.,=20 Hopkinton, MA  01748
+1 (508) 293-7953     =  =20       FAX: +1 (508) 293-7786
black_david@emc.com =    =20    Mobile: +1 (978)=20 = 394-7754
----------------------------------------------------

_= ______________________________________________
rddp=20 mailing list
rddp@ietf.org
https://www.ietf.org/mailman/listinfo/rddp



--
Cheers,
Arkady=20 = Kanevsky
------_=_NextPart_001_01C9EDF2.85F8DD12-- From Black_David@emc.com Mon Jun 15 13:38:06 2009 Return-Path: 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 6C1C428C147; Mon, 15 Jun 2009 13:38:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.338 X-Spam-Level: X-Spam-Status: No, score=-6.338 tagged_above=-999 required=5 tests=[AWL=0.260, 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 Fx5J7o1Dailx; Mon, 15 Jun 2009 13:38:05 -0700 (PDT) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 0E5B73A67AF; Mon, 15 Jun 2009 13:38:04 -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 n5FKcE8M022883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 16:38:14 -0400 Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si01.isus.emc.com (Tablus Interceptor); Mon, 15 Jun 2009 16:38:06 -0400 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n5FKc2Ho003347; Mon, 15 Jun 2009 16:38:06 -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 16:38:03 -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_01C9EDF9.2E0E815E" Date: Mon, 15 Jun 2009 16:38:02 -0400 Message-ID: <9FA859626025B64FBC2AF149D97C944A02F622D6@CORPUSMX80A.corp.emc.com> In-Reply-To: <517c62fb0906151332y9a3c71ak479167fdd7a2d841@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rddp] STORM proposed charter - 31 May 2009 version Thread-Index: Acnt+HZKrejIqU2BReqy/0Md1ZQimQAAKpaA References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> <517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> <517c62fb0906151332y9a3c71ak479167fdd7a2d841@mail.gmail.com> From: To: X-OriginalArrivalTime: 15 Jun 2009 20:38:03.0646 (UTC) FILETIME=[2E50D9E0:01C9EDF9] X-EMM-EM: Active Cc: imss@ietf.org, ips@ietf.org, rddp@ietf.org, storm@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 20:38:06 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9EDF9.2E0E815E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ok, I'll fix it. Thanks, --David =20 ________________________________ From: arkady kanevsky [mailto:arkady.kanevsky@gmail.com]=20 Sent: Monday, June 15, 2009 4:33 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 =09 =09 David, I was not proposing to extend it beyond IP based protocols. Specifically I am trying to ensure that new spec can support TCP/MPA and SCTP. Other protocols that are not IP based or not even Ethernet based, in my view, are outside the scope of IETF. =20 In essense, it is RDMA connection setup on top of message based protocol. So It be done on top of TCP/MPA, or SCTP or maybe some other message based protocols that use IP. Thanks, Arkady =09 =09 On Mon, Jun 15, 2009 at 2:45 PM, wrote: =09 Arkady, =20 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 =09 =20 ________________________________ From: arkady kanevsky [mailto:arkady.kanevsky@gmail.com]=20 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 =09 =09 David,=20 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, wrote: =09 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. =09 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: =09 https://www.ietf.org/mailman/listinfo/storm =09 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. =09 Thanks, --David =09 ---------------------------------------------------- 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 =09 ---------------------------------------------------- =09 =09 _______________________________________________ rddp mailing list rddp@ietf.org =09 https://www.ietf.org/mailman/listinfo/rddp =09 =09 --=20 Cheers, Arkady Kanevsky =09 --=20 Cheers, Arkady Kanevsky =09 ------_=_NextPart_001_01C9EDF9.2E0E815E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Ok, I'll fix=20 it.

Thanks,
--David

 

From: arkady kanevsky=20 [mailto:arkady.kanevsky@gmail.com]
Sent: Monday, June 15, = 2009 4:33=20 PM
To: Black, David
Cc: storm@ietf.org; = imss@ietf.org;=20 ips@ietf.org; rddp@ietf.org
Subject: Re: [rddp] STORM = proposed=20 charter - 31 May 2009 version

David,
I was not proposing to extend it beyond IP based protocols.
Specifically I am trying to ensure that new spec can = support
TCP/MPA and SCTP. Other protocols that are not IP based
or not even Ethernet based, in my view, are outside the scope of=20 IETF.
 
In essense, it is RDMA connection setup on top of message
based protocol. So It be done on top of TCP/MPA, or SCTP or
maybe some other message based protocols that use IP.
Thanks,
Arkady

On Mon, Jun 15, 2009 at 2:45 PM, <Black_David@emc.com> = wrote:
Arkady,
 
I'll beef up the = bullet, but=20 probably not with that
degree of = specifics.  Thanks=20 for pointing this out,
and I apologize for = the delay in=20 responding.

Thanks,
--David

 

From: arkady kanevsky = [mailto:arkady.kanevsky@gmail.com]
Sent: = Tuesday,=20 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=20 proposed charter - 31 May 2009 version

David,=20
The description of RDDP MPA bullet is too narrow.
(5) RDDP MPA: Good support for MPI applications requires a=20 small
update to MPA startup = functionality to allow either end
of the connection to=20 initiate.

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

How about:
(5) RDDP Connection Setup: Good support for MPI applications = requires=20 a small
update to MPA startup = functionality to allow either end
of the connection to = initiate.=20 Add RDMA Read credits to RDDP Connection
        Setup. Make RDDP connection = setup to=20 be applicable for any message based
        protocols, including but not = limited=20 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=20 I believe is the final draft of the proposed charter
for the = STORM WG=20 is attached; I've done a bunch of editing
and added the info = about=20 T10 and T11 doc access.  This is
about to go out for = wider=20 review.

Also, a reminder that STORM discussion will stop=20 cc:'ing
other mailing lists soon.  If you're interested = in=20 STORM
work, please subscribe to the storm@ietf.org mailing list:
https://www.ietf.org/mailman/listinfo/storm

Fi= nally=20 - this is a near-final reminder that the rddp@ietf.org
mailing list will be = closing soon -=20 all discussion of RDDP
protocols will move to the storm@ietf.org mailing=20 = list.

Thanks,
--David
--------------------------------------= --------------
David=20 L. Black, Distinguished Engineer
EMC Corporation, 176 South = St.,=20 Hopkinton, MA  01748
+1 (508) 293-7953     =  =20       FAX: +1 (508) 293-7786
black_david@emc.com=20        Mobile: +1 (978)=20 = 394-7754
----------------------------------------------------

_= ______________________________________________
rddp=20 mailing list
rddp@ietf.org
https://www.ietf.org/mailman/listinfo/rddp



--
Cheers,
Arkady=20 = Kanevsky

<= BR=20 clear=3Dall>

--
Cheers,
Arkady = Kanevsky
------_=_NextPart_001_01C9EDF9.2E0E815E-- From arkady.kanevsky@gmail.com Mon Jun 15 13:32:36 2009 Return-Path: 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 4462528C0FF; Mon, 15 Jun 2009 13:32:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 dTK8rvHK1vbv; Mon, 15 Jun 2009 13:32:35 -0700 (PDT) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by core3.amsl.com (Postfix) with ESMTP id C0B193A6D0E; Mon, 15 Jun 2009 13:32:34 -0700 (PDT) Received: by yxe11 with SMTP id 11so108678yxe.29 for ; Mon, 15 Jun 2009 13:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8chRVAEhG8m6jMYpgp2MIIO03pqFmi0mbL7UHlgfvm8=; b=QaBi8pWg4T+6yaXfY25TrvWnNXYQX+FJyQFQg/m0VKj5fu9m5qE1wLbB2iJlQD0Eya pkZtrY1OjJ5e2Mo23lWlmCTPQoPktGBWTCexDPyVK7pOgOW/yZ0ADgghzA/NvfOs8lpl ZxlHGbcdlKzXgcMARO6W+oL8GEmW+X3HBAatE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ROmi3IxWeqrDJoLrgKXViyGepCLnh5SKZW1dyrTuAOzanQENdFtTjzzk/+siagRQJq A79KI/CTMZlhWl5JQzUl/h1UwiNbh+/mONq+7BSalfzjScCEuQrFZnMS2zqgv8rGr3vN /tOBOJSzwh6ZM1orQVyZioLI3u13OkFFVNjoo= MIME-Version: 1.0 Received: by 10.151.101.8 with SMTP id d8mr14011981ybm.256.1245097964985; Mon, 15 Jun 2009 13:32:44 -0700 (PDT) In-Reply-To: <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> References: <9FA859626025B64FBC2AF149D97C944A02D37D4F@CORPUSMX80A.corp.emc.com> <517c62fb0906021425y6e4db28cm6b34a29eb497cd13@mail.gmail.com> <9FA859626025B64FBC2AF149D97C944A02F621B2@CORPUSMX80A.corp.emc.com> Date: Mon, 15 Jun 2009 16:32:44 -0400 Message-ID: <517c62fb0906151332y9a3c71ak479167fdd7a2d841@mail.gmail.com> From: arkady kanevsky To: Black_David@emc.com Content-Type: multipart/alternative; boundary=00151751138ee9ded0046c68f5ab X-Mailman-Approved-At: Tue, 16 Jun 2009 08:03:12 -0700 Cc: imss@ietf.org, ips@ietf.org, rddp@ietf.org, storm@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 20:32:36 -0000 --00151751138ee9ded0046c68f5ab Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit David, I was not proposing to extend it beyond IP based protocols. Specifically I am trying to ensure that new spec can support TCP/MPA and SCTP. Other protocols that are not IP based or not even Ethernet based, in my view, are outside the scope of IETF. In essense, it is RDMA connection setup on top of message based protocol. So It be done on top of TCP/MPA, or SCTP or maybe some other message based protocols that use IP. Thanks, Arkady On Mon, Jun 15, 2009 at 2:45 PM, wrote: > 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, 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 > > -- Cheers, Arkady Kanevsky --00151751138ee9ded0046c68f5ab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
David,
I was not proposing to extend it beyond IP based protocols.
Specifically I am trying to ensure that new spec can support
TCP/MPA and SCTP. Other protocols that are not IP based
or not even Ethernet based, in my view, are outside the scope of IETF.=
=A0
In essense, it is RDMA connection setup on top of message
based protocol. So It be done on top of TCP/MPA, or SCTP or
maybe some other message based protocols that use IP.
Thanks,
Arkady

On Mon, Jun 15, 2009 at 2:45 PM, <Black_David@emc.com> wrote:
Arkady,
=A0
I'll beef up the bulle= t, but probably not with that
degree of specifics.=A0 Th= anks for pointing this out,
and I apologize for the de= lay in responding.

Thanks,
--David

=A0

From: arkady kanevsky [mailto:arkady.kanevsky@g= mail.com]
Sent: Tuesday, June 02, 2009 5:26 PM
To:= Black, David
Cc: storm@ietf.o= rg; imss@ietf.org; ips@ietf.org; rddp@ietf.org
Subject: Re: [rddp] STORM proposed charter - 31 May 2009 version
=
David,=20
The description of RDDP MPA bullet is too narrow.
(5) RDDP MPA: Good support for MPI applications requires a small
update to MPA startup function= ality 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=A0primarily=A0for TCP stream markers. This bullet should= provide
RDDP connection setup for both TCP and SCTP and for any message based<= /div>
protocol.

How about:
(5) RDDP Connection Setup: Good support for MPI applications requires = a small
update to MPA startup function= ality to allow either end
of the connection to initiate.= Add RDMA Read credits to RDDP Connection
=A0=A0 =A0 =A0 =A0Setup. Make RDDP connection setup to be applicable f= or any message based
=A0=A0 =A0 =A0 =A0protocols, 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 draf= t 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. =A0This is
about to go = out for wider review.

Also, a reminder that STORM discussion will st= op cc:'ing
other mailing lists soon. =A0If you're interested in = STORM
work, please subscribe to the storm@ietf.org mailing list:
https://www.ietf.org/mailman/list= info/storm

Finally - this is a near-final reminder that the rddp@ietf.org
mailing list will be clos= ing 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 =A001748
+1 (508) 293-7953 =A0 =A0 =A0 =A0 =A0 =A0 F= AX: +1 (508) 293-7786
black_david@emc.co= m =A0 =A0 =A0 =A0Mobile: +1 (978) 394-7754
-------------------------= ---------------------------

________________________________________= _______
rddp mailing list
rdd= p@ietf.org
https://www.ietf.org/mailman/listinfo/rddp




--
Cheers,
Arkady Kanevsky
=



--
Cheers,
Arkady Kanevsky
--00151751138ee9ded0046c68f5ab-- From arne.redlich@googlemail.com Mon Jun 22 10:24:16 2009 Return-Path: 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 D6DF028C12E for ; Mon, 22 Jun 2009 10:24:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.98 X-Spam-Level: X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619] 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 vmRv3kX9TUDj for ; Mon, 22 Jun 2009 10:24:16 -0700 (PDT) Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by core3.amsl.com (Postfix) with ESMTP id BC0B63A69C4 for ; Mon, 22 Jun 2009 10:24:15 -0700 (PDT) Received: by ewy6 with SMTP id 6so4878327ewy.37 for ; Mon, 22 Jun 2009 10:24:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=015EWMrts6qMfZ7kICoRJW0rMNGgpBNrSxsrwfbhj6E=; b=pULcDDmakgVlwRXhtlqyFqt06zLjlMKVDo542U/1/5DYARedqSZEzVSiYBuQcSkRJU ZXKmP0H70+TiSkdLxINT+IhQaQDUXaQYLxypPJenQ2oVRhDlqIt6pARAyqii2Zxy0knt dn5ugO8hTBGHc/dPwz98kgbmfOwXioW+RJAhk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:reply-to:to:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; b=enjz1MaMg6aAYR0AtqJ6cgC12D2SpKPy26cqU/eEcOW/C6gwH5buAVcCCcT8bsCkUx tN9hPU3OZdTC++ypep7ZILTg60qvvBoav3VpRaOdjT58ieu6BbJfJ6aRFFXhEZ4HQH9S SschKLtixJSzORsFYKge+MZe6o0LMo6CK18Os= Received: by 10.210.141.19 with SMTP id o19mr7687620ebd.54.1245691467808; Mon, 22 Jun 2009 10:24:27 -0700 (PDT) Received: from ?192.168.11.2? (lo-0.caesar2.telehouse.ddkom.net [212.80.224.243]) by mx.google.com with ESMTPS id 26sm13501415ewy.83.2009.06.22.10.24.25 (version=SSLv3 cipher=RC4-MD5); Mon, 22 Jun 2009 10:24:27 -0700 (PDT) From: Arne Redlich To: ips@ietf.org Content-Type: text/plain Date: Mon, 22 Jun 2009 19:24:18 +0200 Message-Id: <1245691458.4513.269.camel@blackadder> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Subject: [Ips] iSER Data-in clarification X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: arne.redlich@gmail.com List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2009 18:34:43 -0000 Hi, I'm unclear on the granularity with which an iSER target is supposed to transfer Data-In via RDMA writes. Here's the pieces of information I'm trying to tie together: (1) The iSER spec replaces the initiator's MaxRecvDataSegmentLength with InitiatorMaxRecvDSL, but this only applies to control type PDUs (2) MaxBurstLength limits the size of Data-{In,Out} sequences, however, the iSER spec is silent about Data-In sequences. (3) RFC 5046, 7.3.5 (SCSI Data-In): "2. It MUST generate and send an RDMA Write Message containing the read data to the initiator [...] c. It MUST use DataSegmentLength from the SCSI Data-in PDU to determine the amount of data to be sent in the RDMA Write Message." What is the iSCSI layer at the target supposed to use as DataSegmentLength? MaxBurstLength? The full Data-In length? Thanks in advance, Arne