RFC 5666 on Remote Direct Memory Access Transport for Remote Procedure Call

RFC Editor <rfc-editor@rfc-editor.org> Tue, 19 January 2010 18:52 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A82128C101 for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level:
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-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 CkEP9frQVVAA for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:52:49 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9CCB728C0FF for <ietf-announce@ietf.org>; Tue, 19 Jan 2010 10:52:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 60BC2E0686; Tue, 19 Jan 2010 10:52:46 -0800 (PST)
Date: Tue, 19 Jan 2010 10:52:46 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: RFC 5666 on Remote Direct Memory Access Transport for Remote Procedure Call
Message-ID: <20100119185246.GG14300@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2010 18:52:50 -0000

Resending.

----- Forwarded message from rfc-editor@rfc-editor.org -----

Delivered-To: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5666 on Remote Direct Memory Access Transport for Remote Procedure Call
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, nfsv4@ietf.org
Date: Thu, 14 Jan 2010 23:08:16 -0800 (PST)


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5666

        Title:      Remote Direct Memory Access Transport 
                    for Remote Procedure Call 
        Author:     T. Talpey, B. Callaghan
        Status:     Standards Track
        Date:       January 2010
        Mailbox:    tmtalpey@gmail.com, 
                    brentc@apple.com
        Pages:      34
        Characters: 83728
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nfsv4-rpcrdma-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5666.txt

This document describes a protocol providing Remote Direct Memory Access
(RDMA) as a new transport for Remote Procedure Call (RPC).  The
RDMA transport binding conveys the benefits of efficient, bulk-data
transport over high-speed networks, while providing for minimal
change to RPC applications and with no required revision of the
application RPC protocol, or the RPC protocol itself.  [STANDARDS TRACK]

This document is a product of the Network File System Version 4 Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


----- End forwarded message -----