[tcpm] Fw: New Version Notification for draft-fox-tcpm-shared-memory-rdma-00.txt

Mike Fox <mjfox@us.ibm.com> Mon, 09 July 2012 21:46 UTC

Return-Path: <mjfox@us.ibm.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DF511E8102 for <tcpm@ietfa.amsl.com>; Mon, 9 Jul 2012 14:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xL6Eo6xnCN50 for <tcpm@ietfa.amsl.com>; Mon, 9 Jul 2012 14:46:30 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 9965111E80F2 for <tcpm@ietf.org>; Mon, 9 Jul 2012 14:46:28 -0700 (PDT)
Received: from /spool/local by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <tcpm@ietf.org> from <mjfox@us.ibm.com>; Mon, 9 Jul 2012 15:46:54 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 9 Jul 2012 15:46:52 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 934D03E40054 for <tcpm@ietf.org>; Mon, 9 Jul 2012 21:46:21 +0000 (WET)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q69LkLhk287712 for <tcpm@ietf.org>; Mon, 9 Jul 2012 15:46:21 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q69LkLFf001805 for <tcpm@ietf.org>; Mon, 9 Jul 2012 15:46:21 -0600
Received: from d03nm118.boulder.ibm.com (d03nm118.boulder.ibm.com [9.63.40.219]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q69LkLir001802 for <tcpm@ietf.org>; Mon, 9 Jul 2012 15:46:21 -0600
To: tcpm@ietf.org
MIME-Version: 1.0
X-KeepSent: 63CD4C49:784B3B30-85257A36:0077294A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
From: Mike Fox <mjfox@us.ibm.com>
X-MIMETrack: S/MIME Sign by Notes Client on Mike Fox/Raleigh/IBM(Release 8.5.3|September 15, 2011) at 07/09/2012 05:46:17 PM, Serialize by Notes Client on Mike Fox/Raleigh/IBM(Release 8.5.3|September 15, 2011) at 07/09/2012 05:46:17 PM, Serialize complete at 07/09/2012 05:46:17 PM, S/MIME Sign failed at 07/09/2012 05:46:17 PM: The cryptographic key was not found, Serialize by Router on D03NM118/03/M/IBM(Release 8.5.3 ZX853HP5|January 12, 2012) at 07/09/2012 15:46:21, Serialize complete at 07/09/2012 15:46:21
Message-ID: <OF63CD4C49.784B3B30-ON85257A36.0077294A-85257A36.00779871@us.ibm.com>
Date: Mon, 09 Jul 2012 17:46:19 -0400
Content-Type: multipart/alternative; boundary="=_alternative 0077983D85257A36_="
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12070921-7606-0000-0000-000001DD902B
Subject: [tcpm] Fw: New Version Notification for draft-fox-tcpm-shared-memory-rdma-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 09 Jul 2012 21:46:31 -0000

The submitted internet draft describes a new protocol that exploits RDMA 
over CEE (RoCE) transparently for TCP sockets based applications. This 
protocol (Shared Memory Communications over RDMA or SMC-R for short) 
achieves this transparency by using normal TCP connection establishment 
flows but allows each end point to dynamically negotiate the use of SMC-R 
via TCP experimental options as proposed in 
draft-ietf-tcpm-experimental-options-01.txt. When both end points agree to 
use the SMC-R protocol, all data flows across the two TCP endpoints take 
place using out of band RDMA Write operations to pre-defined memory 
regions allocated by the two peers. The goal of the SMC-R protocol is to 
achieve this transparently for TCP socket applications which means 
supporting the same socket API semantics and simulating the behavior of 
the TCP protocol as observed by the application layer. As such, SMC-R 
includes provisions for handling TCP specific features such as urgent 
data. The hybrid nature of the SMC-R protocol allows it to maintain many 
of the qualities of service associated with TCP/IP communications while 
providing the performance benefits of leveraging RDMA technology for 
moving data on Ethernet networks capable of RDMA. 

Any review and comments on this draft would be very much appreciated. 

Thank you,
Mike Fox



> A new version of I-D, draft-fox-tcpm-shared-memory-rdma-00.txt
> has been successfully submitted by Mike Fox and posted to the
> IETF repository.
>
> Filename:               draft-fox-tcpm-shared-memory-rdma
> Revision:               00
> Title:                                  Shared Memory Communications 
over RDMA
> Creation date:                  2012-07-09
> WG ID:                                  Individual Submission
> Number of pages: 133
> URL:             
http://www.ietf.org/internet-drafts/draft-fox-tcpm-shared-memory-rdma-00.txt

> Status:          
http://datatracker.ietf.org/doc/draft-fox-tcpm-shared-memory-rdma
> Htmlized:        
http://tools.ietf.org/html/draft-fox-tcpm-shared-memory-rdma-00
>
>
> Abstract:
>   This document describes the Shared Memory Communications over RDMA
>   (SMC-R) protocol.  This protocol provides RDMA communications to TCP
>   endpoints in a manner that is transparent to socket applications.  It
>   further provides for dynamic discovery of partner RDMA capabilities
>   and dynamic setup of RDMA connections, transparent high availability
>   and load balancing when redundant RDMA network paths are available,
>   and it maintains many of the traditional TCP/IP qualities of service
>   such as filtering that enterprise users demand, as well as TCP socket
>   semantics such as urgent data.
>
>  
>
>
> The IETF Secretariat