draft-ietf-nfsv4-rfc3530bis-dot-x-13.txt   draft-ietf-nfsv4-rfc3530bis-dot-x-14.txt 
NFSv4 T. Haynes, Ed. NFSv4 T. Haynes, Ed.
Internet-Draft NetApp Internet-Draft NetApp
Intended status: Standards Track D. Noveck, Ed. Intended status: Standards Track D. Noveck, Ed.
Expires: May 14, 2013 EMC Expires: July 21, 2013 EMC
November 10, 2012 January 17, 2013
Network File System (NFS) Version 4 Network File System (NFS) Version 4
External Data Representation Standard (XDR) Description External Data Representation Standard (XDR) Description
draft-ietf-nfsv4-rfc3530bis-dot-x-13.txt draft-ietf-nfsv4-rfc3530bis-dot-x-14.txt
Abstract Abstract
The Network File System (NFS) version 4 is a distributed filesystem The Network File System (NFS) version 4 is a distributed filesystem
protocol which owes heritage to NFS protocol version 2, RFC 1094, and protocol which owes heritage to NFS protocol version 2, RFC 1094, and
version 3, RFC 1813. Unlike earlier versions, the NFS version 4 version 3, RFC 1813. Unlike earlier versions, the NFS version 4
protocol supports traditional file access while integrating support protocol supports traditional file access while integrating support
for file locking and the mount protocol. In addition, support for for file locking and the mount protocol. In addition, support for
strong security (and its negotiation), compound operations, client strong security (and its negotiation), compound operations, client
caching, and internationalization have been added. Of course, caching, and internationalization have been added. Of course,
attention has been applied to making NFS version 4 operate well in an attention has been applied to making NFS version 4 operate well in an
Internet environment. Internet environment.
This document, together with RFC3530bis replaces RFC 3530 as the RFC3530bis is formally obsoleting RFC 3530. But this document,
definition of the NFS version 4 protocol. together with RFC3530bis replaces RFC 3530 as the definition of the
NFS version 4 protocol.
Requirements Language 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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). 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 July 21, 2013.
This Internet-Draft will expire on May 14, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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 respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 12 skipping to change at page 3, line 12
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. XDR Description of NFSv4.0 . . . . . . . . . . . . . . . . . . 4 1. XDR Description of NFSv4.0 . . . . . . . . . . . . . . . . . . 4
2. Security Considerations . . . . . . . . . . . . . . . . . . . 37 2. Security Considerations . . . . . . . . . . . . . . . . . . . 37
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
4. Normative References . . . . . . . . . . . . . . . . . . . . . 37 4. Normative References . . . . . . . . . . . . . . . . . . . . . 37
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 37 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 37
Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 37 Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38
1. XDR Description of NFSv4.0 1. XDR Description of NFSv4.0
This document contains the XDR ([2]) description of NFSv4.0 protocol This document contains the XDR ([RFC4506]) description of NFSv4.0
([3]). protocol ([I-D.ietf-nfsv4-rfc3530bis]).
The XDR description is provided in this document in a way that makes The XDR description is provided in this document in a way that makes
it simple for the reader to extract into ready to compile form. The it simple for the reader to extract into ready to compile form. The
reader can feed this document in the following shell script to reader can feed this document in the following shell script to
produce the machine readable XDR description of NFSv4.0: produce the machine readable XDR description of NFSv4.0:
#!/bin/sh #!/bin/sh
grep "^ *///" | sed 's?^ */// ??' | sed 's?^ *///$??' grep "^ *///" | sed 's?^ */// ??' | sed 's?^ *///$??'
I.e. if the above script is stored in a file called "extract.sh", and I.e. if the above script is stored in a file called "extract.sh", and
skipping to change at page 4, line 31 skipping to change at page 4, line 31
sh extract.sh < spec.txt > nfs4_prot.x sh extract.sh < spec.txt > nfs4_prot.x
The effect of the script is to remove leading white space from each The effect of the script is to remove leading white space from each
line, plus a sentinel sequence of "///". line, plus a sentinel sequence of "///".
The XDR description, with the sentinel sequence follows: The XDR description, with the sentinel sequence follows:
/// /* /// /*
/// * This file was machine generated for /// * This file was machine generated for
/// * draft-ietf-nfsv4-rfc3530bis- /// * draft-ietf-nfsv4-rfc3530bis-
/// * Last updated Sat Nov 10 17:52:19 CST 2012 /// * Last updated Thu Jan 17 16:51:53 CST 2013
/// */ /// */
/// /* /// /*
/// * Copyright (C) The IETF Trust (2009-2011) /// * Copyright (C) The IETF Trust (2009-2011)
/// * All Rights Reserved. /// * All Rights Reserved.
/// * /// *
/// * Copyright (C) The Internet Society (1998-2011). /// * Copyright (C) The Internet Society (1998-2011).
/// * All Rights Reserved. /// * All Rights Reserved.
/// */ /// */
/// ///
/// /* /// /*
skipping to change at page 37, line 21 skipping to change at page 37, line 21
/// version NFS_CB { /// version NFS_CB {
/// void /// void
/// CB_NULL(void) = 0; /// CB_NULL(void) = 0;
/// CB_COMPOUND4res /// CB_COMPOUND4res
/// CB_COMPOUND(CB_COMPOUND4args) = 1; /// CB_COMPOUND(CB_COMPOUND4args) = 1;
/// } = 1; /// } = 1;
/// } = 0x40000000; /// } = 0x40000000;
2. Security Considerations 2. Security Considerations
See the Security Considerations section of [3]. See the Security Considerations section of
[I-D.ietf-nfsv4-rfc3530bis].
3. IANA Considerations 3. IANA Considerations
See the IANA Considerations section of [3]. This document does not have an IANA considerations.
4. Normative References 4. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [I-D.ietf-nfsv4-rfc3530bis]
Levels", March 1997. Haynes, T. and D. Noveck, "NFS Version 4 Protocol",
draft-ietf-nfsv4-rfc3530bis-21 (work in progress),
November 2012.
[2] Eisler, M., "XDR: External Data Representation Standard", [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
STD 67, RFC 4506, May 2006. Requirement Levels", March 1997.
[3] Haynes, T. and D. Noveck, "NFS Version 4 Protocol", [RFC4506] Eisler, M., "XDR: External Data Representation Standard",
draft-ietf-nfsv4-rfc3530bis-04 (work in progress), July 2010. STD 67, RFC 4506, May 2006.
Appendix A. Acknowledgments Appendix A. Acknowledgments
David Quigley tested the extraction of the .x file from this document David Quigley tested the extraction of the .x file from this document
and corrected the two resulting errors. and corrected the two resulting errors.
Appendix B. RFC Editor Notes Appendix B. RFC Editor Notes
[RFC Editor: please remove this section prior to publishing this [RFC Editor: please remove this section prior to publishing this
document as an RFC] document as an RFC]
[RFC Editor: prior to publishing this document as an RFC, please [RFC3530bis should be replaced by the RFC number of
replace all occurences of RFC3530bis with RFCxxxx where xxxx is the draft-ietf-nfsv4-rfc3530bis in this draft.]
RFC number assigned to the XDR document.]
[RFC Editor: Please note that there is also a reference entry that [RFC Editor: Please note that there is also a reference entry that
needs to be modified for the companion document.] needs to be modified for the companion document.]
Authors' Addresses Authors' Addresses
Thomas Haynes (editor) Thomas Haynes (editor)
NetApp NetApp
9110 E 66th St 9110 E 66th St
Tulsa, OK 74133 Tulsa, OK 74133
 End of changes. 15 change blocks. 
24 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/