draft-ietf-nfsv4-minorversion1-dot-x-11.txt   draft-ietf-nfsv4-minorversion1-dot-x-12.txt 
NFSv4 S. Shepler NFSv4 S. Shepler
Internet-Draft M. Eisler Internet-Draft M. Eisler
Intended status: Standards Track D. Noveck Intended status: Standards Track D. Noveck
Expires: June 7, 2009 Editors Expires: June 18, 2009 Editors
December 04, 2008 December 15, 2008
NFSv4 Minor Version 1 XDR Description NFSv4 Minor Version 1 XDR Description
draft-ietf-nfsv4-minorversion1-dot-x-11.txt draft-ietf-nfsv4-minorversion1-dot-x-12.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of 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.
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."
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 June 7, 2009. This Internet-Draft will expire on June 18, 2009.
Copyright Notice
Copyright (c) 2008 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
to this document.
Abstract Abstract
This Internet-Draft provides the XDR description for NFSv4 minor This Internet-Draft provides the XDR description for NFSv4 minor
version one. version one.
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 [1].
Table of Contents Table of Contents
1. Code Components Licensing Notice . . . . . . . . . . . . . . . 3 1. Code Components Licensing Notice . . . . . . . . . . . . . . . 3
2. XDR Description of NFSv4.1 . . . . . . . . . . . . . . . . . . 3 2. XDR Description of NFSv4.1 . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 71 3. Security Considerations . . . . . . . . . . . . . . . . . . . 71
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 71 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 72
5. Normative References . . . . . . . . . . . . . . . . . . . . . 71 5. Normative References . . . . . . . . . . . . . . . . . . . . . 72
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 71 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 72
Intellectual Property and Copyright Statements . . . . . . . . . . 73 Appendix B. RFC Editor Notes . . . . . . . . . . . . . . . . . . 72
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 73
1. Code Components Licensing Notice 1. Code Components Licensing Notice
The XDR description and scripts for extracting the XDR description The XDR description and scripts for extracting the XDR description
are Code Components as described in Section 4 of "Legal Provisions are Code Components as described in Section 4 of "Legal Provisions
Relating to IETF Documents" [2]. These Code Components are licensed Relating to IETF Documents" [2].
according to the terms of Section 4 of "Legal Provisions Relating to
IETF Documents".
2. XDR Description of NFSv4.1 2. XDR Description of NFSv4.1
This document contains the XDR ([3]) description of NFSv4.1 protocol This document contains the XDR ([3]) description of NFSv4.1 protocol
([4]). In order to facilitate implementations that support both ([4]). In order to facilitate implementations that support both
NFSv4.0 and NFSv4.1, the description includes operations, and other NFSv4.0 and NFSv4.1, the description includes operations, and other
features of NFSv4.0 that do not apply to NFSv4.1. features of NFSv4.0 that do not apply to NFSv4.1.
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.1: produce the machine readable XDR description of NFSv4.1:
<CODE BEGINS> <CODE BEGINS>
#!/bin/sh #!/bin/sh
grep "^ *///" | sed 's?^ */// ??' | sed 's?^ *///$??' grep '^ *///' | sed 's?^ */// ??' | sed 's?^ *///$??'
<CODE ENDS> <CODE ENDS>
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
this document is in a file called "spec.txt", then the reader can do: this document is in a file called "spec.txt", then the reader can do:
<CODE BEGINS> <CODE BEGINS>
sh extract.sh < spec.txt > nfs4_prot.x sh extract.sh < spec.txt > nfs4_prot.x
<CODE ENDS> <CODE ENDS>
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:
<CODE BEGINS> <CODE BEGINS>
/// /* /// /*
/// * Copyright (c) 2008 IETF Trust and the persons identified
/// * as the document authors. All rights reserved.
/// *
/// * The document authors are identified in [RFC3530] and
/// * [draft-ietf-nfsv4-minorversion1-xx.txt].
/// *
/// * Redistribution and use in source and binary forms, with
/// * or without modification, are permitted provided that the
/// * following conditions are met:
/// *
/// * o Redistributions of source code must retain the above
/// * copyright notice, this list of conditions and the
/// * following disclaimer.
/// *
/// * o Redistributions in binary form must reproduce the above
/// * copyright notice, this list of conditions and the
/// * following disclaimer in the documentation and/or other
/// * materials provided with the distribution.
/// *
/// * o Neither the name of Internet Society, IETF or IETF
/// * Trust, nor the names of specific contributors, may be
/// * used to endorse or promote products derived from this
/// * software without specific prior written permission.
/// *
/// * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
/// * AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
/// * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
/// * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
/// * FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
/// * EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
/// * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
/// * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
/// * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
/// * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
/// * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
/// * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
/// * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
/// * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
/// * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
/// */
/// /*
/// * This code was derived from [RFC3530]. Please
/// * reproduce this note if possible.
/// *
/// * This file was machine generated for /// * This file was machine generated for
/// * draft-ietf-nfsv4-minorversion1-28 /// * draft-ietf-nfsv4-minorversion1-29
/// * Last updated Thu Dec 4 11:05:51 PST 2008 /// * Last updated Mon Dec 15 11:26:38 PST 2008
/// */ /// */
/// /* /// /*
/// * nfs4_prot.x /// * nfs4_prot.x
/// */ /// */
/// ///
/// %#ifndef _AUTH_SYS_DEFINE_FOR_NFSv41 /// %#ifndef _AUTH_SYS_DEFINE_FOR_NFSv41
/// %#define _AUTH_SYS_DEFINE_FOR_NFSv41 /// %#define _AUTH_SYS_DEFINE_FOR_NFSv41
/// %#include <rpc/auth_sys.h> /// %#include <rpc/auth_sys.h>
/// %typedef struct authsys_parms authsys_parms; /// %typedef struct authsys_parms authsys_parms;
/// %#endif _AUTH_SYS_DEFINE_FOR_NFSv41 /// %#endif _AUTH_SYS_DEFINE_FOR_NFSv41
skipping to change at page 71, line 19 skipping to change at page 72, line 15
4. IANA Considerations 4. IANA Considerations
See the IANA Considerations section of [4]. See the IANA Considerations section of [4].
5. Normative References 5. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", March 1997. Levels", March 1997.
[2] IETF Trust, "Legal Provisions Relating to IETF Documents", [2] IETF Trust, "Legal Provisions Relating to IETF Documents",
URL http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf,
November 2008. November 2008.
[3] Eisler, M., "XDR: External Data Representation Standard", [3] Eisler, M., "XDR: External Data Representation Standard",
STD 67, RFC 4506, May 2006. STD 67, RFC 4506, May 2006.
[4] Shepler, S., Eisler, M., and D. Noveck, "NFS Version 4 Minor [4] Shepler, S., Eisler, M., and D. Noveck, "NFS Version 4 Minor
Version 1", draft-ietf-nfsv4-minorversion1-28 (work in Version 1", draft-ietf-nfsv4-minorversion1-29 (work in
progress), Dec 2008. progress), Dec 2008.
Appendix A. Acknowledgements
The authors are grateful to Lars Eggert for navigating the
intellectual property issues of this document.
Appendix B. RFC Editor Notes
o [RFC Editor: please delete this section before publishing]
o [RFC Editor: after the appearance of,
* This code was derived from [RFC3530]. Please
* reproduce this note if possible.
please add this text with the three leading forward slashes on
each line of text (so that the text shows up in the self-
extracting Code Component):
* This code was derived from [RFCTBD1]. Please
* reproduce this note if possible.
where TBD1 is replaced with the number of the RFC that will
replace draft-ietf-nfsv4-minorversion1-xx.txt [4].]
o [RFC Editor: please replace these lines,
*
* This file was machine generated for
* draft-ietf-nfsv4-minorversion1-xx
* Last updated
with this text with the three leading forward slashes on each line
of text (so that the text shows up in the Code Component):
*
* This file was machine generated for RFCTBD1
where TBD1 is replaced with the RFC number of
draft-ietf-nfsv4-minorversion1-xx.txt [4].]
o [RFC Editor: please replace the entry in the "Normative
References" section that identifies
draft-ietf-nfsv4-minorversion1-xx.txt with an entry that describes
RFCTBD1, where TBD1 is replaced with the number of the RFC that
will replace draft-ietf-nfsv4-minorversion1-xx.txt. ]
o [RFC Editor: please replace all appearances of
draft-ietf-nfsv4-minorversion1-xx.txt with RFCTBD1, where TBD1 is
the number of the RFC that will replace
draft-ietf-nfsv4-minorversion1-xx.txt.]
Authors' Addresses Authors' Addresses
Spencer Shepler Spencer Shepler
Storspeed, Inc. Storspeed, Inc.
7808 Moonflower Drive 7808 Moonflower Drive
Austin, TX 78750 Austin, TX 78750
USA USA
Phone: +1-512-402-5811 ext 8530 Phone: +1-512-402-5811 ext 8530
Email: shepler@storspeed.com Email: shepler@storspeed.com
skipping to change at page 73, line 4 skipping to change at line 3473
Phone: +1-719-599-9026 Phone: +1-719-599-9026
Email: mike@eisler.com Email: mike@eisler.com
David Noveck David Noveck
NetApp NetApp
1601 Trapelo Road, Suite 16 1601 Trapelo Road, Suite 16
Waltham, MA 02454 Waltham, MA 02454
USA USA
Phone: +1-781-768-5347 Phone: +1-781-768-5347
Email: dnoveck@netapp.com Email: dnoveck@netapp.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 13 change blocks. 
20 lines changed or deleted 122 lines changed or added

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