idnits 2.17.1 draft-cel-nfsv4-comp-stor-reqs-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (March 25, 2019) is 1856 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network File System Version 4 C. Lever 3 Internet-Draft Oracle 4 Intended status: Informational March 25, 2019 5 Expires: September 26, 2019 7 Network File System Requirements for Computational Storage 8 draft-cel-nfsv4-comp-stor-reqs-00 10 Abstract 12 This document introduces an architecture for supporting Computational 13 Storage on Network File System version 4 (NFS) servers and clients. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on September 26, 2019. 32 Copyright Notice 34 Copyright (c) 2019 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 1. Introduction 49 Computational storage is more than providing compute offload. True 50 computational storage conforms to one or both of the following 51 criteria: 53 o Compute resources co-located with data storage leverages a high 54 bandwidth link between storage and local compute. 56 o Compute resources co-located with data storage reduces interrupt 57 or data bandwidth needed between storage and host. 59 For NFS, the focus of computational storage techniques is on reducing 60 network utilization between a server and its clients. NFSv4.2 [3] 61 already applies this approach: new features include copy offload and 62 file initialization (ALLOCATE). 64 There are two broad types of computation offloaded to storage: 66 Search: Examples include SQL offload, or performing a "find" 67 operation without pulling a filesystem's data to a client. 69 Filtering: Also known as data transformation. Examples include 70 compression, transcoding, encryption, or integrity checking. 72 The purpose of the current document is to provide a framework for 73 reasoning about computational storage relative to the NFS protocol. 75 1.1. Requirements Language 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 79 "OPTIONAL" in this document are to be interpreted as described in BCP 80 14 [1] [2] when, and only when, they appear in all capitals, as shown 81 here. 83 2. Parameters 85 For various reasons, we do not want to require changes to the NFS 86 protocol to expose computational resources. Instead, an NFS server 87 host can advertise alternate RPC programs which allow NFS clients 88 access to the server's computational services in a structured 89 fashion. The underlying assumption is that such computation runs 90 faster on a host that can access file data directly rather than via 91 NFS. 93 An important class of input and output parameters for these remote 94 procedures are objects (e.g. files and directories) that exist in a 95 filesystem that is shared via NFS. Such objects are referenced by 96 filehandle and optionally a range of bytes. 98 Serialization is necessary to prevent an offload agent from colliding 99 with access by NFS clients. Open state or a delegation might be 100 appropriate for this purpose. 102 3. Security Considerations 104 A trust relationship must exist between clients and servers. For 105 example, how would clients be certain that the server has actually 106 encrypted a file's content? 108 There will need to be a mechanism for authorizing offload agents to 109 access file data. 111 4. IANA Considerations 113 This document requests no action from IANA. 115 5. References 117 5.1. Normative References 119 [1] Bradner, S., "Key words for use in RFCs to Indicate 120 Requirement Levels", BCP 14, RFC 2119, 121 DOI 10.17487/RFC2119, March 1997, 122 . 124 [2] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 125 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 126 May 2017, . 128 5.2. Informative References 130 [3] Haynes, T., "Network File System (NFS) Version 4 Minor 131 Version 2 Protocol", RFC 7862, DOI 10.17487/RFC7862, 132 November 2016, . 134 Acknowledgments 136 Special thanks go to Transport Area Director Magnus Westerlund, NFSV4 137 Working Group Chairs Spencer Shepler and Brian Pawlowski, and NFSV4 138 Working Group Secretary Thomas Haynes for their support. 140 Author's Address 142 Charles Lever 143 Oracle Corporation 144 United States of America 146 Email: chuck.lever@oracle.com