--- 1/draft-ietf-nfsv4-nfsdirect-04.txt 2007-05-09 01:12:14.000000000 +0200 +++ 2/draft-ietf-nfsv4-nfsdirect-05.txt 2007-05-09 01:12:14.000000000 +0200 @@ -1,17 +1,19 @@ -Internet-Draft Tom Talpey -Expires: April 2007 Brent Callaghan - -Document: draft-ietf-nfsv4-nfsdirect-04 October, 2007 +NFSv4 Working Group Tom Talpey +Internet-Draft Network Appliance, Inc. +Intended status: Standards Track Brent Callaghan +Expires: November 8, 2007 Apple Computer, Inc. + May 7, 2007 NFS Direct Data Placement + draft-ietf-nfsv4-nfsdirect-05 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -48,39 +50,39 @@ 3. Transfers from NFS Server to NFS Client . . . . . . . . . . 3 4. NFS Versions 2 and 3 Mapping . . . . . . . . . . . . . . . . 4 5. NFS Version 4 Mapping . . . . . . . . . . . . . . . . . . . 5 6. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 9. Normative References . . . . . . . . . . . . . . . . . . . . 8 10. Informative References . . . . . . . . . . . . . . . . . . 9 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . 9 12. Intellectual Property and Copyright Statements . . . . . 10 - Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10 + Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . 10 Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 1. Introduction The RDMA Transport for ONC RPC [RPCRDMA] allows an RPC client application to post buffers in a Chunk list for specific arguments and results from an RPC call. The RDMA transport header conveys this list of client buffer addresses to the server where the application can associate them with client data and use RDMA operations to transfer the results directly to and from the posted buffers on the client. The client and server must agree on a consistent mapping of posted buffers to RPC. This document details the mapping for each - version of the NFS protocol [RFC1831] [RFC1832] [RFC1094] [RFC1813] + version of the NFS protocol [RFC1831] [RFC4506] [RFC1094] [RFC1813] [RFC3530] [NFSv4.1]. 2. Transfers from NFS Client to NFS Server The RDMA Read list, in the RDMA transport header, allows an RPC client to marshal RPC call data selectively. Large chunks of data, such as the file data of an NFS WRITE request, MAY be referenced by an RDMA Read list and be moved efficiently and directly-placed by an RDMA READ operation initiated by the server. @@ -354,24 +356,24 @@ Levels", Best Current Practice, BCP 14, RFC 2119, March 1997. [RFC1831] R. Srinivasan, "RPC: Remote Procedure Call Protocol Specification Version 2", Standards Track RFC, http://www.ietf.org/rfc/rfc1831.txt - [RFC1832] - R. Srinivasan, "XDR: External Data Representation Standard", + [RFC4506] + M. Eisler, Ed., "XDR: External Data Representation Standard", Standards Track RFC, - http://www.ietf.org/rfc/rfc1832.txt + http://www.ietf.org/rfc/rfc4506.txt [RFC1094] "NFS: Network File System Protocol Specification", (NFS version 2) Informational RFC, http://www.ietf.org/rfc/rfc1094.txt [RFC1813] B. Callaghan, B. Pawlowski, P. Staubach, "NFS Version 3 Protocol Specification", Informational RFC, http://www.ietf.org/rfc/rfc1813.txt @@ -421,28 +424,45 @@ Brent Callaghan Apple Computer, Inc. MS: 302-4K 2 Infinite Loop Cupertino, CA 95014 USA EMail: brentc@apple.com 12. Intellectual Property and Copyright Statements -Intellectual Property Statement +Full Copyright Statement + + Copyright (C) The IETF Trust (2007). + + This document is subject to the rights, licenses and restrictions + contained in BCP 78, and except as set forth therein, the authors + retain all their rights. + + This document and the information contained herein are provided on + an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE + REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE + IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL + WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY + WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE + ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS + FOR A PARTICULAR PURPOSE. +Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. + Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. @@ -445,33 +465,13 @@ of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. -Disclaimer of Validity - - This document and the information contained herein are provided on - an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE - REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND - THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, - EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT - THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR - ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A - PARTICULAR PURPOSE. - -Copyright Statement - - Copyright (C) The Internet Society (2006). - - This document is subject to the rights, licenses and restrictions - contained in BCP 78, and except as set forth therein, the authors - retain all their rights. - -Acknowledgement - - Funding for the RFC Editor function is currently provided by the - Internet Society. +Acknowledgment + Funding for the RFC Editor function is provided by the IETF + Administrative Support Activity (IASA).