[storm] Proposed Agenda for STORM RDMA/IP Mini-BOF Vancouver

Tom Talpey <ttalpey@microsoft.com> Fri, 25 October 2013 20:43 UTC

Return-Path: <ttalpey@microsoft.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B25A011E81B8 for <storm@ietfa.amsl.com>; Fri, 25 Oct 2013 13:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1muHPksYYGNa for <storm@ietfa.amsl.com>; Fri, 25 Oct 2013 13:43:03 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3FB6411E81D1 for <storm@ietf.org>; Fri, 25 Oct 2013 13:43:02 -0700 (PDT)
Received: from BY2PR03CA028.namprd03.prod.outlook.com ( by BY2PR03MB286.namprd03.prod.outlook.com ( with Microsoft SMTP Server (TLS) id 15.0.785.10; Fri, 25 Oct 2013 20:43:00 +0000
Received: from BY2FFO11FD014.protection.gbl (2a01:111:f400:7c0c::194) by BY2PR03CA028.outlook.office365.com (2a01:111:e400:2c2c::21) with Microsoft SMTP Server (TLS) id 15.0.800.7 via Frontend Transport; Fri, 25 Oct 2013 20:43:00 +0000
Received: from mail.microsoft.com ( by BY2FFO11FD014.mail.protection.outlook.com ( with Microsoft SMTP Server (TLS) id 15.0.805.12 via Frontend Transport; Fri, 25 Oct 2013 20:43:00 +0000
Received: from TK5EX14MBXC284.redmond.corp.microsoft.com ([]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([]) with mapi id 14.03.0158.002; Fri, 25 Oct 2013 20:42:16 +0000
From: Tom Talpey <ttalpey@microsoft.com>
To: "storm@ietf.org" <storm@ietf.org>
Thread-Topic: Proposed Agenda for STORM RDMA/IP Mini-BOF Vancouver
Thread-Index: Ac7RnF/D4oVQbWoASV6HK2KhNbSHCg==
Date: Fri, 25 Oct 2013 20:42:15 +0000
Message-ID: <614F550557B82C44AC27C492ADA391AA25576CE7@TK5EX14MBXC284.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(74876001)(76796001)(15975445006)(46102001)(33656001)(77096001)(76786001)(51856001)(74366001)(56816003)(20776003)(65816001)(63696002)(47776003)(53806001)(81542001)(54356001)(76176001)(47446002)(31966008)(80976001)(79102001)(74662001)(74502001)(23726002)(76482001)(50986001)(4396001)(47736001)(47976001)(49866001)(83072001)(80022001)(77982001)(59766001)(55846006)(56776001)(54316002)(81686001)(50466002)(15202345003)(6806004)(81816001)(85806002)(74706001)(19580395003)(83322001)(85306002)(66066001)(44976005)(69226001)(81342001)(46406003); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB286; H:mail.microsoft.com; CLIP:; FPR:; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0010D93EFE
X-OriginatorOrg: DuplicateDomain-a84fc36a-4ed7-4e57-ab1c-3e967bcbad48.microsoft.com
Subject: [storm] Proposed Agenda for STORM RDMA/IP Mini-BOF Vancouver
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 20:43:11 -0000

The following updated proposed agenda has been posted for the IETF-88 STORM WG. Feedback or comments welcome. See you in Vancouver!

STORM WG, IETF-88 Vancouver Canada
1300-1500 Thursday Nov 7, Regency B

Blue Sheets, Introduction and Agenda Bashing - David Black - 5 min

RDMA Ecosystem - Tom Talpey - 20 min
       What is RDMA
       Previous IETF work
       Upper layers using RDMA
            iSER, NFS/RDMA, SMB3, SCSI RDMA Protocol (SRP),
               High Performance/Scientific/Financial Computing, Experimental
            RDMA requirements of each
       RDMA layers
            iWARP, InfiniBand, RDMA over Converged Ethernet (RoCE)
       Lower layers used by RDMA
            TCP, SCTP, Ethernet L2, Infiniband
       RDMA trends and development
       Virtualization, encapsulation
       Fabrics, infrastructure, bandwidths

iWARP trends - Brian Hausauer - 15 min+discussion
       Protocol status
       Extensions status
       Work in Progress

RoCE trends - TBA - 15 min+discussion
       Protocol status
       Related standards org(s)
       Work in Progress

Fabric trends - Pat Thaler - 10 min+discussion
       RoCE dependencies from (Ethernet) fabric
       Data Center Bridging (DCB) including Priority Flow Control (PFC)

General discussion - 1 hour, also included above
       Future work within IETF
       Related work within IETF
       Relationship to external standards org(s)
       Protocol alternatives, e.g. iWARP, RoCE
       Identification of areas to investigate

Wrapup and next step(s)              


Additional background:

The STORM (STORage Maintenance) working group's responsibilities include
maintenance and development of various IETF RDMA specifications, and interest
and activity is rising in these. Many RDMA device and RDMA-aware upper layer
implementations already use IETF-standard protocols, and others are moving
toward using IP networks, by defining new IP-family layering. Use of the iWARP
family is already in place for three broadly implemented storage protocols
(iSCSI, NFS, SMB), as well as for High Performance Computing. The Infiniband
Trade Association, which defines the InfiniBand and RDMA over Converged Ethernet
(RoCE) transports, is also addressing these. Additional extensions to the IETF
RDMA RFCs are in progress in the STORM working group.

A BOF is scheduled for the upcoming meeting to review the status of the various
RDMA-related efforts, and the requirements of upper layers. With these at front
of mind, a discussion will be held to determine interest and desire to proceed
with next steps in the IETF, and coordination with external standards efforts.
In addition to determining possible future IETF work, the discussion will
explore the role IETF may play in external specifications.

Example RDMA-capable Transports:
	iWARP (RFC5040-5044) and draft-ietf-storm-rdmap-ext
	RoCE (www.infinibandta.org)
	InfiniBand (www.infinibandta.org)

Example Upper layers using RDMA:
	NFS/RDMA (RFC5666-5667)
	iSER (RFC5046) and draft-ietf-storm-iser
	SMB3 and SMB Direct (MS-SMB2 and MS-SMBD http://msdn.microsoft.com/en-us/library/jj712081.aspx)
	MPI (http://en.wikipedia.org/wiki/Message_Passing_Interface)

Additional implementations/use:
	iWARP extensions (continued)
	Routable RoCE
	Shared memory (draft-fox-tcpm-shared-memory-rdma)
	Further use by storage upper layers
	Applicability to new storage technologies e.g. flash, nonvolatile memory, etc.