Network Working Group The Internet Society
Internet-Draft Sun Microsystems
March 1998
An agreement between the Internet Society,
the IETF and Sun Microsystems, Inc.
in the matter of NFS V.4 protocols
<draft-isoc-sun-nfs-agreement-00.txt>
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
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.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract
This Request for Comments records an agreement between Sun
Microsystems, Inc. and the Internet Society to permit the flow of
Sun's Network File System specifications into the Internet Standards
process conducted by the Internet Engineering Task Force.
Note:
This RFC is NOT a standard. It is an official public record of an
agreement between Sun Microsystems and the Internet Society. The
referenced RFCs 1094 dated March 1989 ("NFS: Network File System
Protocol Specification") and 1813 dated June 1995 ("NFS Version 3
Protocol Specification") are not attached to the document below, but
are incorporated by reference.
ISOC & Sun [Page 1]
Internet-Draft ISOC / Sun agreement on NFS March 1998
AGREEMENT BETWEEN THE INTERNET SOCIETY,
THE IETF AND SUN MICROSYSTEMS, INC.
IN THE MATTER OF NFS V.4 PROTOCOLS
This Agreement is made this 3rd day of March, 1998 by and between Sun
Microsystems, Inc. ("Donor") and the Internet Society. In
consideration of the mutual covenants and conditions set forth below,
the parties hereto agree as follows:
1. License Grant. For good and valuable consideration, receipt and
sufficiency of which is hereby acknowledged, and solely for the
purpose specified in Paragraph 2 below, Donor hereby grants to the
Internet Society ("Licensees" which, for the purposes of this
Agreement, shall include the Internet Engineering Task Force
("IETF"), the IETF Secretariat, and their respective members,
officers, employees, contractors and participating individuals) a
cost-free, perpetual, non-exclusive, worldwide right and license
under any copyrights owned or otherwise licensable by Donor, under
any Sun patent rights that are essential to practice the
Specification, and any other Sun intellectual property rights to use,
reproduce, distribute, perform, display and prepare derivative works
of the Specification, and to authorize others to do so. For the
purposes of this Agreement, "Specification" means the technical
specification described more fully in Exhibit A, which Donor will
make available as the initial point for development of the
specification for NFS Version 4 as described hereunder, together with
any technical specifications based thereon developed by Licensees.
2. Statement of Purpose. The licenses granted in Section 1 are
granted for the sole purpose of seeking to make the Specification an
Internet standard.
3. Evolution of the Specification. Donor further grants to Licensees
a worldwide right and license to further evolve, develop and modify
the Specification for the purpose of making the Specification an
Internet Standard through the Internet Standardization Process (as
specified in RFC 2026); Donor may not grant a license involving the
Specification to any other party, including any standards group, that
would authorize such party to evolve, develop, modify or promote the
Specification as a standard. In particular, Donor acknowledges that
if it performs any evolution, development or modification of the
Specification outside of the Internet Standardization Process, that
this should be clearly indicated as being a non-standard development,
and that no reference to the Internet Standards Process is allowed
for any such Specification developed outside of the Internet
Standards Process.
4. Non-Confidentiality. Donor hereby acknowledges that Licensees
ISOC & Sun [Page 2]
Internet-Draft ISOC / Sun agreement on NFS March 1998
assume no obligation to maintain any confidentiality with respect to
the Specification licensed hereunder. Licensees acknowledge that any
rights not expressly granted herein are reserved by Donor. Donor
represents that, to the best of its knowledge, there are no
infringement claims against the Specification.
5. Future License. Donor hereby acknowledges that Licensees have no
duty to publish or otherwise use or disseminate the Specification,
including, in particular, an obligation to raise the Specification to
the Internet standards-track. Provided that the Specification is
elevated to "Proposed Standard" level within 24 months of the
execution of this Agreement, Donor hereby agrees to license the
Specification to others at no charge and otherwise under
substantially similar terms as those granted to Licensee herein (with
the exception that such use of the Specification by such Licensees
shall be for purposes of implementing and complying with the Standard
rather than for making the Specification an Internet Standard), so
long as such licensees of the Specification implement and comply with
the Internet standard. In the event the Specification is not
elevated to "Proposed Standard" level within 24 months of the
execution of this Agreement, then the license granted in Section 3 of
this agreement shall terminate.
6. DISCLAIMER OF WARRANTY. THE SPECIFICATION IS PROVIDED TO
LICENSEES "AS IS", AND ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY
AND NONINFRINGEMENT ARE HEREBY DISCLAIMED.
7. LIMITATION OF LIABILITY. IN NO EVENT WILL DONOR BE LIABLE FOR ANY
LOST REVENUE, PROFITS OR DATA, OR FOR DIRECT, SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THEORY OF LIABILITY ARISING OUT OF THE USE OR INABILITY
TO USE THE SPECIFICATION, EVEN IF DONOR HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
8. Acknowledgment. Donor agrees to permit Licensees to use Donor's
name and address to indicate the original source of the
Specification.
9. Miscellaneous. This Agreement constitutes the entire agreement
between the parties concerning its subject matter, and supersedes all
prior written or oral agreements and discussions. All additions or
modifications to this agreement must be made in writing and must be
signed by an authorized representative of each party. If any term or
condition of this Agreement is declared void or unenforceable as
provided herein or by a court of competent jurisdiction, the
remaining provisions shall remain in full force and effect. The
parties agree to comply strictly with all applicable export control
ISOC & Sun [Page 3]
Internet-Draft ISOC / Sun agreement on NFS March 1998
laws and regulations. Where no U.S. Federal law governs, this
agreement will be governed by the law of the State of California
without reference to its conflict of laws provision.
IN WITNESS WHEREOF, the parties hereto have caused this Agreement to
be executed by their duly authorized representatives.
Signature /S/ Rich Green Date 3 March 1998
Name Rich Green
Title VP Solaris
SunSoft, Inc.
Signature /S/ Donald M. Heath Date 6 March 1998
Name Donald M. Heath
Title President and CEO of the Internet Society
Exhibit A The specifications embodied in RFCs 1094 and 1813, minus
the portions of RFCs 1094 and 1813 that assume that NFS Version 2 and
Version 3 operate over XDR and ONC RPC.* The control of ONC RPC
program number 100003 (NFS) for the purpose of generating Version
numbers 4 and onward.
*Note: ISOC already has a license to use XDR and ONC RPC (see IETF
RFC 1790), and thus may determine whether or not to create an NFS
Version 4 that uses XDR and/or ONC RPC.
Security Considerations Since this document records an agreement
rather than describes a technology security is not directly effected
but, that said, one of the aims of an IETF NFS working group should
be to ensure that a standards track NFS protocol has adequate
security.
Editor's Address
Scott Bradner
Harvard University
1350 Mass Ave. Rm 876
Cambridge, MA 02138
phone - +1 617 495 3864
email - sob@harvard.edu
ISOC & Sun [Page 4]