Requirements for pNFS Layout Types
draft-ietf-nfsv4-layout-types-11
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (nfsv4 WG) | |
| Author | Thomas Haynes | ||
| Last updated | 2018-04-19 (latest revision 2018-02-27) | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats | pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Spencer Shepler | ||
| Shepherd write-up | Show (last changed 2018-01-14) | ||
| IESG | IESG state | IESG Evaluation::AD Followup | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Needs 4 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Spencer Dawkins | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
NFSv4 T. Haynes
Internet-Draft Primary Data
Updates: 5661 (if approved) April 19, 2018
Intended status: Standards Track
Expires: October 21, 2018
Requirements for pNFS Layout Types
draft-ietf-nfsv4-layout-types-11.txt
Abstract
This document defines the requirements which individual pNFS layout
types need to meet in order to work within the parallel NFS (pNFS)
framework as defined in RFC5661. In so doing, it aims to clearly
distinguish between requirements for pNFS as a whole and those
specifically directed to the pNFS File Layout. The lack of a clear
separation between the two set of requirements has been troublesome
for those specifying and evaluating new Layout Types. In this
regard, this document updates RFC5661.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 21, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Haynes Expires October 21, 2018 [Page 1]
Internet-Draft Layout Types April 2018
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Use of the Terms "Data Server" and "Storage Device" . . . 5
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 6
3. The Control Protocol . . . . . . . . . . . . . . . . . . . . 6
3.1. Control Protocol Requirements . . . . . . . . . . . . . . 8
3.2. Previously Undocumented Protocol Requirements . . . . . . 9
3.3. Editorial Requirements . . . . . . . . . . . . . . . . . 10
4. Specifications of Original Layout Types . . . . . . . . . . . 11
4.1. File Layout Type . . . . . . . . . . . . . . . . . . . . 11
4.2. Block Layout Type . . . . . . . . . . . . . . . . . . . . 12
4.3. Object Layout Type . . . . . . . . . . . . . . . . . . . 13
5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 16
Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
The concept of layout type has a central role in the definition and
implementation of Parallel Network File System (pNFS) (see
[RFC5661]). Clients and servers implementing different layout types
behave differently in many ways while conforming to the overall pNFS
framework defined in [RFC5661] and this document. Layout types may
differ as to:
o The method used to do I/O operations directed to data storage
devices.
o The requirements for communication between the metadata server
(MDS) and the storage devices.
o The means used to ensure that I/O requests are only processed when
the client holds an appropriate layout.
Haynes Expires October 21, 2018 [Page 2]
Internet-Draft Layout Types April 2018
o The format and interpretation of nominally opaque data fields in
pNFS-related NFSv4.x data structures.
Show full document text