RFC 5667 on Network File System (NFS) Direct Data Placement
RFC Editor <rfc-editor@rfc-editor.org> Tue, 19 January 2010 18:53 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 66D5528C10D for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[AWL=-0.113, 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 swcZ5y5uagvx for <ietf-announce@core3.amsl.com>; Tue, 19 Jan 2010 10:53:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id ACFB228C10C for <ietf-announce@ietf.org>; Tue, 19 Jan 2010 10:53:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 74DDBE0686; Tue, 19 Jan 2010 10:53:20 -0800 (PST)
Date: Tue, 19 Jan 2010 10:53:20 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: RFC 5667 on Network File System (NFS) Direct Data Placement
Message-ID: <20100119185320.GH14300@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:53:24 -0000
Resending. ----- Forwarded message from rfc-editor@rfc-editor.org ----- To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 5667 on Network File System (NFS) Direct Data Placement From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, nfsv4@ietf.org Date: Thu, 14 Jan 2010 23:08:28 -0800 (PST) A new Request for Comments is now available in online RFC libraries. RFC 5667 Title: Network File System (NFS) Direct Data Placement Author: T. Talpey, B. Callaghan Status: Standards Track Date: January 2010 Mailbox: tmtalpey@gmail.com, brentc@apple.com Pages: 10 Characters: 83728 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nfsv4-nfsdirect-08.txt URL: http://www.rfc-editor.org/rfc/rfc5667.txt This document defines the bindings of the various Network File System (NFS) versions to the Remote Direct Memory Access (RDMA) operations supported by the RPC/RDMA transport protocol. It describes the use of direct data placement by means of server-initiated RDMA operations into client-supplied buffers for implementations of NFS versions 2, 3, 4, and 4.1 over such an RDMA transport. [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 -----