draft-ietf-nfsv4-layout-types-12.txt   draft-ietf-nfsv4-layout-types-13.txt 
NFSv4 T. Haynes NFSv4 T. Haynes
Internet-Draft Hammerspace Internet-Draft Hammerspace
Updates: 5661 (if approved) April 19, 2018 Updates: 5661 (if approved) April 25, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: October 21, 2018 Expires: October 27, 2018
Requirements for pNFS Layout Types Requirements for pNFS Layout Types
draft-ietf-nfsv4-layout-types-12.txt draft-ietf-nfsv4-layout-types-13.txt
Abstract Abstract
This document defines the requirements which individual pNFS layout This document defines the requirements which individual pNFS layout
types need to meet in order to work within the parallel NFS (pNFS) 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 framework as defined in RFC5661. In so doing, it aims to clearly
distinguish between requirements for pNFS as a whole and those distinguish between requirements for pNFS as a whole and those
specifically directed to the pNFS File Layout. The lack of a clear specifically directed to the pNFS File Layout. The lack of a clear
separation between the two set of requirements has been troublesome separation between the two set of requirements has been troublesome
for those specifying and evaluating new Layout Types. In this for those specifying and evaluating new Layout Types. In this
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 21, 2018. This Internet-Draft will expire on October 27, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 17 skipping to change at page 2, line 17
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Use of the Terms "Data Server" and "Storage Device" . . . 5 2.1. Use of the Terms "Data Server" and "Storage Device" . . . 5
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 6 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 6
3. The Control Protocol . . . . . . . . . . . . . . . . . . . . 6 3. The Control Protocol . . . . . . . . . . . . . . . . . . . . 6
3.1. Control Protocol Requirements . . . . . . . . . . . . . . 8 3.1. Control Protocol Requirements . . . . . . . . . . . . . . 8
3.2. Previously Undocumented Protocol Requirements . . . . . . 9 3.2. Previously Undocumented Protocol Requirements . . . . . . 10
3.3. Editorial Requirements . . . . . . . . . . . . . . . . . 10 3.3. Editorial Requirements . . . . . . . . . . . . . . . . . 10
4. Specifications of Original Layout Types . . . . . . . . . . . 11 4. Specifications of Original Layout Types . . . . . . . . . . . 11
4.1. File Layout Type . . . . . . . . . . . . . . . . . . . . 11 4.1. File Layout Type . . . . . . . . . . . . . . . . . . . . 11
4.2. Block Layout Type . . . . . . . . . . . . . . . . . . . . 12 4.2. Block Layout Type . . . . . . . . . . . . . . . . . . . . 13
4.3. Object Layout Type . . . . . . . . . . . . . . . . . . . 13 4.3. Object Layout Type . . . . . . . . . . . . . . . . . . . 14
5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . 16 8.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 16 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 16
Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 16 Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
The concept of layout type has a central role in the definition and The concept of layout type has a central role in the definition and
implementation of Parallel Network File System (pNFS) (see implementation of Parallel Network File System (pNFS) (see
[RFC5661]). Clients and servers implementing different layout types [RFC5661]). Clients and servers implementing different layout types
behave differently in many ways while conforming to the overall pNFS behave differently in many ways while conforming to the overall pNFS
framework defined in [RFC5661] and this document. Layout types may framework defined in [RFC5661] and this document. Layout types may
differ as to: differ as to:
skipping to change at page 6, line 27 skipping to change at page 6, line 27
protocols (such as NFS) are not data servers. protocols (such as NFS) are not data servers.
Since a given storage device may support multiple layout types, a Since a given storage device may support multiple layout types, a
given device can potentially act as a data server for some set of given device can potentially act as a data server for some set of
storage protocols while simultaneously acting as a storage device for storage protocols while simultaneously acting as a storage device for
others. others.
2.2. Requirements Language 2.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
This document differs from most standards-track documents in that it This document differs from most standards-track documents in that it
specifies requirements for those defining future layout types rather specifies requirements for those defining future layout types rather
than defining the requirements for implementations directly. This than defining the requirements for implementations directly. This
document makes clear whether: document makes clear whether:
(1) any particular requirement applies to implementations. (1) any particular requirement applies to implementations.
(2) any particular requirement applies to those defining layout (2) any particular requirement applies to those defining layout
types. types.
skipping to change at page 15, line 47 skipping to change at page 16, line 10
7. IANA Considerations 7. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, <https://www.rfc-editor.org/info/
rfc2119>.
[RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File [RFC5661] Shepler, S., Ed., Eisler, M., Ed., and D. Noveck, Ed.,
System (NFS) Version 4 Minor Version 1 Protocol", RFC "Network File System (NFS) Version 4 Minor Version 1
5661, January 2010. Protocol", RFC 5661, DOI 10.17487/RFC5661, January 2010,
<https://www.rfc-editor.org/info/rfc5661>.
[RFC5663] Black, D., Fridella, S., and J. Glasgow, "pNFS Block/ [RFC5663] Black, D., Fridella, S., and J. Glasgow, "Parallel NFS
Volume Layout", RFC 5663, January 2010. (pNFS) Block/Volume Layout", RFC 5663, DOI 10.17487/
RFC5663, January 2010, <https://www.rfc-editor.org/info/
rfc5663>.
[RFC5664] Halevy, B., Welch, B., and J. Zelenka, "Object-Based [RFC5664] Halevy, B., Welch, B., and J. Zelenka, "Object-Based
Parallel NFS (pNFS) Operations", RFC 5664, January 2010. Parallel NFS (pNFS) Operations", RFC 5664, DOI 10.17487/
RFC5664, January 2010, <https://www.rfc-editor.org/info/
rfc5664>.
[RFC8154] Hellwig, C., "Parallel NFS (pNFS) Small Computer System [RFC8154] Hellwig, C., "Parallel NFS (pNFS) Small Computer System
Interface (SCSI) Layout", RFC 8154, DOI 10.17487/RFC8154, Interface (SCSI) Layout", RFC 8154, DOI 10.17487/RFC8154,
May 2017, <http://www.rfc-editor.org/info/rfc8154>. May 2017, <https://www.rfc-editor.org/info/rfc8154>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[FlexFiles] [FlexFiles]
Halevy, B. and T. Haynes, "Parallel NFS (pNFS) Flexible Halevy, B. and T. Haynes, "Parallel NFS (pNFS) Flexible
File Layout", draft-ietf-nfsv4-flex-files-16 (Work In File Layout", draft-ietf-nfsv4-flex-files-16 (Work In
Progress), January 2018. Progress), January 2018.
[Lustre] Faibish, S. and P. Tao, "Parallel NFS (pNFS) Lustre Layout [Lustre] Faibish, S. and P. Tao, "Parallel NFS (pNFS) Lustre Layout
Operations", draft-faibish-nfsv4-pnfs-lustre-layout-07 Operations", draft-faibish-nfsv4-pnfs-lustre-layout-07
 End of changes. 14 change blocks. 
21 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/