draft-ietf-nfsv4-pnfs-block-disk-protection-01.txt   draft-ietf-nfsv4-pnfs-block-disk-protection-02.txt 
NFSv4 Working Group D. Black NFSv4 Working Group D. Black
Internet-Draft EMC Corporation Internet-Draft EMC Corporation
Intended status: draft J. Glasgow Intended status: Proposed Standard J. Glasgow
Expires: May 22, 2012 Google Expires: November 23, 2012 Google
Updates: 5663 S. Faibish Updates: 5663 S. Faibish
Intended Status: Proposed Standard EMC Corporation EMC Corporation
November 21, 2011 May 22, 2012
pNFS block disk protection pNFS block disk protection
draft-ietf-nfsv4-pnfs-block-disk-protection-01 draft-ietf-nfsv4-pnfs-block-disk-protection-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 22, 2012. This Internet-Draft will expire on November 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 16 skipping to change at page 2, line 16
Abstract Abstract
Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to
enable direct client access to file data on storage, bypassing the enable direct client access to file data on storage, bypassing the
NFSv4 server. This can increase both performance and parallelism, NFSv4 server. This can increase both performance and parallelism,
but requires additional client functionality, some of which depends but requires additional client functionality, some of which depends
upon the type of storage used. The pNFS specification for block upon the type of storage used. The pNFS specification for block
storage (RFC 5663) describes how clients can identify the volumes storage (RFC 5663) describes how clients can identify the volumes
used for pNFS, but this mechanism requires communication with the used for pNFS, but this mechanism requires communication with the
NFSv4 server. This document adds a mechanism to RFC 5663 that NFSv4 server. This document updates RFC 5663 to add a mechanism that
enables identification of block storage devices used by pNFS file enables identification of block storage devices used by pNFS file
systems without communicating with the server. This enables clients systems without communicating with the server. This enables clients
to control access to pNFS block devices when the client initially to control access to pNFS block devices when the client initially
boots, as opposed to waiting until the client can communicate with boots, as opposed to waiting until the client can communicate with
the NFSv4 server. the NFSv4 server.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Conventions used in this document..............................4 2. Conventions used in this document..............................4
3. GPT Partition Table Entry......................................4 3. GPT Partition Table Entry......................................4
4. Security Considerations........................................5 4. Security Considerations........................................5
5. IANA Considerations............................................5 5. IANA Considerations............................................5
6. Conclusions....................................................5 6. Conclusions....................................................5
7. References.....................................................5 7. References.....................................................6
7.1. Normative References......................................5 7.1. Normative References......................................6
7.2. Informative References....................................6 7.2. Informative References....................................6
Acknowledgements..................................................6 Acknowledgements..................................................6
Authors' Addresses................................................6 Authors' Addresses................................................7
1. Introduction 1. Introduction
Figure 1 shows the overall architecture of a Parallel NFS (pNFS) Figure 1 shows the overall architecture of a Parallel NFS (pNFS)
system: system:
+-----------+ +-----------+
|+-----------+ +-----------+ |+-----------+ +-----------+
||+-----------+ | | ||+-----------+ | |
||| | NFSv4.1 + pNFS | | ||| | NFSv4.1 + pNFS | |
skipping to change at page 4, line 43 skipping to change at page 4, line 43
3. GPT Partition Table Entry 3. GPT Partition Table Entry
The following mechanism enables pNFS clients to identify pNFS block The following mechanism enables pNFS clients to identify pNFS block
storage devices without contacting the server: storage devices without contacting the server:
- Each block storage device dedicated to pNFS includes a GUID - Each block storage device dedicated to pNFS includes a GUID
partition table (GPT) [GPT]. partition table (GPT) [GPT].
- The pNFS Block Storage partitions are identified in the GPT with - The pNFS Block Storage partitions are identified in the GPT with
GUID e5b72a69-23e5-4b4d-b176-16532674fc34. This GUID has been GUID e5b72a69-23e5-4b4d-b176-16532674fc34. This GUID has been
generated by one of the draft authors for this purpose. generated by one of the draft authors for this purpose. GPT
GUID usage is well understood and implemented. This document
provides a definition for this GUID and its usage. A central
registration mechanism does not exist for GPT GUIDs, or GUIDs in
general by design, see [RFC4122].
This mechanism enables an operating system to prevent non-pNFS access This mechanism enables an operating system to prevent non-pNFS access
to pNFS block storage immediately upon boot. Servers that support to pNFS block storage immediately upon boot. Servers that support
pNFS block layouts SHOULD use the GPT and this GUID for all pNFS pNFS block layouts SHOULD use the GPT and this GUID for all pNFS
block storage devices. block storage devices.
A pNFS client operating system that supports block layouts SHOULD A pNFS client operating system that supports block layouts SHOULD
recognize this GUID and use its presence to prevent data access to recognize this GUID and use its presence to prevent data access to
pNFS block devices until a layout that includes the device is pNFS block devices until a layout that includes the device is
received from the MDS. received from the MDS.
skipping to change at page 5, line 25 skipping to change at page 5, line 27
that could otherwise corrupt stored pNFS data. that could otherwise corrupt stored pNFS data.
As of November 2011, many current operating system versions support As of November 2011, many current operating system versions support
the GPT, including FreeBSD, Linux and Solaris [GPT-W]. the GPT, including FreeBSD, Linux and Solaris [GPT-W].
4. Security Considerations 4. Security Considerations
The pNFS block layout security considerations in [RFC5663] apply to The pNFS block layout security considerations in [RFC5663] apply to
this document. this document.
The security considerations in [RFC4122] apply to the GUID specified
in this document.
5. IANA Considerations 5. IANA Considerations
There are no IANA considerations in this document. There are no IANA considerations in this document.
6. Conclusions 6. Conclusions
This document specifies an identification mechanism for pNFS block This document specifies an identification mechanism for pNFS block
storage devices that can be used to protect those devices during storage devices that can be used to protect those devices during
operating system boot before the pNFS meta data server can be operating system boot before the pNFS meta data server can be
contacted. contacted.
skipping to change at page 6, line 7 skipping to change at page 6, line 21
September 2011, available from http://www.uefi.org . September 2011, available from http://www.uefi.org .
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5663] Black, D., Glasgow, J., Fridella, S., "Parallel NFS (pNFS) [RFC5663] Black, D., Glasgow, J., Fridella, S., "Parallel NFS (pNFS)
Block/Volume Layout", RFC 5663, January 2010. Block/Volume Layout", RFC 5663, January 2010.
7.2. Informative References 7.2. Informative References
[GPT-W] http://en.wikipedia.org/wiki/GUID_Partition_Table [GPT-W] http://en.wikipedia.org/wiki/GUID_Partition_Table
[RFC4122] Leach, P., Mealling, M., Salz, R., "A Universally Unique
IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
Acknowledgements Acknowledgements
This document was produced by the IETF NFSv4 Working Group. Review This document was produced by the IETF NFSv4 Working Group. Review
comments from members of the working group improved this document and comments from members of the working group improved this document and
are gratefully acknowledged. The authors would like to thank Tom are gratefully acknowledged. The authors would like to thank Tom
Talpey for helpful comments on this document, and Alex Burlyga for Talpey and Martin Stiemerling for helpful comments on this document,
providing an appropriate reference for the format of the GPT. and also Alex Burlyga for providing an appropriate reference for the
format of the GPT.
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
Authors' Addresses Authors' Addresses
David L. Black (editor) David L. Black (editor)
EMC Corporation EMC Corporation
176 South Street 176 South Street
Hopkinton, MA 01748 Hopkinton, MA 01748
US US
 End of changes. 12 change blocks. 
15 lines changed or deleted 26 lines changed or added

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