| 1 |
<pre>Network Working Group The Internet Society |
| 2 |
Request for Comments: 2339 Sun Microsystems |
| 3 |
Category: Informational May 1998 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">An Agreement Between the Internet Society,</span> |
| 7 |
<span class="h1">the IETF, and Sun Microsystems, Inc.</span> |
| 8 |
<span class="h1">in the matter of NFS V.4 Protocols</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. It does |
| 13 |
not specify an Internet standard of any kind. Distribution of this |
| 14 |
memo is unlimited. |
| 15 |
|
| 16 |
Copyright Notice |
| 17 |
|
| 18 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 19 |
|
| 20 |
Abstract |
| 21 |
|
| 22 |
This Request for Comments records an agreement between Sun |
| 23 |
Microsystems, Inc. and the Internet Society to permit the flow of |
| 24 |
Sun's Network File System specifications into the Internet Standards |
| 25 |
process conducted by the Internet Engineering Task Force. |
| 26 |
|
| 27 |
Note: |
| 28 |
|
| 29 |
This RFC is NOT a standard. It is an official public record of an |
| 30 |
agreement between Sun Microsystems and the Internet Society. The |
| 31 |
referenced RFCs 1094 dated March 1989 ("NFS: Network File System |
| 32 |
Protocol Specification") and 1813 dated June 1995 ("NFS Version 3 |
| 33 |
Protocol Specification") are not attached to the document below, but |
| 34 |
are incorporated by reference. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">ISOC & Sun Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2339">RFC 2339</a> ISOC / Sun agreement on NFS May 1998</span> |
| 55 |
|
| 56 |
|
| 57 |
AGREEMENT BETWEEN THE INTERNET SOCIETY, |
| 58 |
THE IETF, AND SUN MICROSYSTEMS, INC. |
| 59 |
IN THE MATTER OF NFS V.4 PROTOCOLS |
| 60 |
|
| 61 |
|
| 62 |
This Agreement is made this 3rd day of March, 1998 by and between Sun |
| 63 |
Microsystems, Inc. ("Donor") and the Internet Society. In |
| 64 |
consideration of the mutual covenants and conditions set forth below, |
| 65 |
the parties hereto agree as follows: |
| 66 |
|
| 67 |
1. License Grant. For good and valuable consideration, receipt and |
| 68 |
sufficiency of which is hereby acknowledged, and solely for the |
| 69 |
purpose specified in Paragraph 2 below, Donor hereby grants to the |
| 70 |
Internet Society ("Licensees" which, for the purposes of this |
| 71 |
Agreement, shall include the Internet Engineering Task Force |
| 72 |
("IETF"), the IETF Secretariat, and their respective members, |
| 73 |
officers, employees, contractors and participating individuals) a |
| 74 |
cost-free, perpetual, non-exclusive, worldwide right and license |
| 75 |
under any copyrights owned or otherwise licensable by Donor, under |
| 76 |
any Sun patent rights that are essential to practice the |
| 77 |
Specification, and any other Sun intellectual property rights to use, |
| 78 |
reproduce, distribute, perform, display and prepare derivative works |
| 79 |
of the Specification, and to authorize others to do so. For the |
| 80 |
purposes of this Agreement, "Specification" means the technical |
| 81 |
specification described more fully in Exhibit A, which Donor will |
| 82 |
make available as the initial point for development of the |
| 83 |
specification for NFS Version 4 as described hereunder, together with |
| 84 |
any technical specifications based thereon developed by Licensees. |
| 85 |
|
| 86 |
2. Statement of Purpose. The licenses granted in <a href="#section-1">Section 1</a> are |
| 87 |
granted for the sole purpose of seeking to make the Specification an |
| 88 |
Internet standard. |
| 89 |
|
| 90 |
3. Evolution of the Specification. Donor further grants to Licensees |
| 91 |
a worldwide right and license to further evolve, develop and modify |
| 92 |
the Specification for the purpose of making the Specification an |
| 93 |
Internet Standard through the Internet Standardization Process (as |
| 94 |
specified in <a href="./rfc2026">RFC 2026</a>); Donor may not grant a license involving the |
| 95 |
Specification to any other party, including any standards group, that |
| 96 |
would authorize such party to evolve, develop, modify or promote the |
| 97 |
Specification as a standard. In particular, Donor acknowledges that |
| 98 |
if it performs any evolution, development or modification of the |
| 99 |
Specification outside of the Internet Standardization Process, that |
| 100 |
this should be clearly indicated as being a non-standard development, |
| 101 |
and that no reference to the Internet Standards Process is allowed |
| 102 |
for any such Specification developed outside of the Internet |
| 103 |
Standards Process. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">ISOC & Sun Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2339">RFC 2339</a> ISOC / Sun agreement on NFS May 1998</span> |
| 111 |
|
| 112 |
|
| 113 |
4. Non-Confidentiality. Donor hereby acknowledges that Licensees |
| 114 |
assume no obligation to maintain any confidentiality with respect to |
| 115 |
the Specification licensed hereunder. Licensees acknowledge that any |
| 116 |
rights not expressly granted herein are reserved by Donor. Donor |
| 117 |
represents that, to the best of its knowledge, there are no |
| 118 |
infringement claims against the Specification. |
| 119 |
|
| 120 |
5. Future License. Donor hereby acknowledges that Licensees have no |
| 121 |
duty to publish or otherwise use or disseminate the Specification, |
| 122 |
including, in particular, an obligation to raise the Specification to |
| 123 |
the Internet standards-track. Provided that the Specification is |
| 124 |
elevated to "Proposed Standard" level within 24 months of the |
| 125 |
execution of this Agreement, Donor hereby agrees to license the |
| 126 |
Specification to others at no charge and otherwise under |
| 127 |
substantially similar terms as those granted to Licensee herein (with |
| 128 |
the exception that such use of the Specification by such Licensees |
| 129 |
shall be for purposes of implementing and complying with the Standard |
| 130 |
rather than for making the Specification an Internet Standard), so |
| 131 |
long as such licensees of the Specification implement and comply with |
| 132 |
the Internet standard. In the event the Specification is not |
| 133 |
elevated to "Proposed Standard" level within 24 months of the |
| 134 |
execution of this Agreement, then the license granted in <a href="#section-3">Section 3</a> of |
| 135 |
this agreement shall terminate. |
| 136 |
|
| 137 |
6. DISCLAIMER OF WARRANTY. THE SPECIFICATION IS PROVIDED TO |
| 138 |
LICENSEES "AS IS", AND ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR |
| 139 |
IMPLIED, INCLUDING FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY |
| 140 |
AND NONINFRINGEMENT ARE HEREBY DISCLAIMED. |
| 141 |
|
| 142 |
7. LIMITATION OF LIABILITY. IN NO EVENT WILL DONOR BE LIABLE FOR ANY |
| 143 |
LOST REVENUE, PROFITS OR DATA, OR FOR DIRECT, SPECIAL, INDIRECT, |
| 144 |
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND |
| 145 |
REGARDLESS OF THEORY OF LIABILITY ARISING OUT OF THE USE OR INABILITY |
| 146 |
TO USE THE SPECIFICATION, EVEN IF DONOR HAS BEEN ADVISED OF THE |
| 147 |
POSSIBILITY OF SUCH DAMAGES. |
| 148 |
|
| 149 |
8. Acknowledgment. Donor agrees to permit Licensees to use Donor's |
| 150 |
name and address to indicate the original source of the |
| 151 |
Specification. |
| 152 |
|
| 153 |
9. Miscellaneous. This Agreement constitutes the entire agreement |
| 154 |
between the parties concerning its subject matter, and supersedes all |
| 155 |
prior written or oral agreements and discussions. All additions or |
| 156 |
modifications to this agreement must be made in writing and must be |
| 157 |
signed by an authorized representative of each party. If any term or |
| 158 |
condition of this Agreement is declared void or unenforceable as |
| 159 |
provided herein or by a court of competent jurisdiction, the |
| 160 |
remaining provisions shall remain in full force and effect. The |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">ISOC & Sun Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2339">RFC 2339</a> ISOC / Sun agreement on NFS May 1998</span> |
| 167 |
|
| 168 |
|
| 169 |
parties agree to comply strictly with all applicable export control |
| 170 |
laws and regulations. Where no U.S. Federal law governs, this |
| 171 |
agreement will be governed by the law of the State of California |
| 172 |
without reference to its conflict of laws provision. |
| 173 |
|
| 174 |
IN WITNESS WHEREOF, the parties hereto have caused this Agreement to |
| 175 |
be executed by their duly authorized representatives. |
| 176 |
|
| 177 |
Signature /S/ Rich Green Date 3 March 1998 |
| 178 |
Name Rich Green |
| 179 |
Title VP Solaris |
| 180 |
SunSoft, Inc. |
| 181 |
|
| 182 |
Signature /S/ Donald M. Heath Date 6 March 1998 |
| 183 |
Name Donald M. Heath |
| 184 |
Title President and CEO of the Internet Society |
| 185 |
|
| 186 |
Exhibit A The specifications embodied in RFCs 1094 and 1813, minus |
| 187 |
the portions of RFCs 1094 and 1813 that assume that NFS Version 2 and |
| 188 |
Version 3 operate over XDR and ONC RPC.* The control of ONC RPC |
| 189 |
program number 100003 (NFS) for the purpose of generating Version |
| 190 |
numbers 4 and onward. |
| 191 |
|
| 192 |
*Note: ISOC already has a license to use XDR and ONC RPC (see IETF |
| 193 |
<a href="./rfc1790">RFC 1790</a>), and thus may determine whether or not to create an NFS |
| 194 |
Version 4 that uses XDR and/or ONC RPC. |
| 195 |
|
| 196 |
Security Considerations |
| 197 |
|
| 198 |
Since this document records an agreement rather than describes a |
| 199 |
technology security is not directly effected but, that said, one of |
| 200 |
the aims of an IETF NFS working group should be to ensure that a |
| 201 |
standards track NFS protocol has adequate security. |
| 202 |
|
| 203 |
Editor's Address |
| 204 |
|
| 205 |
Scott Bradner |
| 206 |
Harvard University |
| 207 |
1350 Mass Ave. Rm 876 |
| 208 |
Cambridge, MA 02138 |
| 209 |
|
| 210 |
Phone: +1 617 495 3864 |
| 211 |
EMail: [email protected] |
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">ISOC & Sun Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2339">RFC 2339</a> ISOC / Sun agreement on NFS May 1998</span> |
| 223 |
|
| 224 |
|
| 225 |
Full Copyright Statement |
| 226 |
|
| 227 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 228 |
|
| 229 |
This document and translations of it may be copied and furnished to |
| 230 |
others, and derivative works that comment on or otherwise explain it |
| 231 |
or assist in its implementation may be prepared, copied, published |
| 232 |
and distributed, in whole or in part, without restriction of any |
| 233 |
kind, provided that the above copyright notice and this paragraph are |
| 234 |
included on all such copies and derivative works. However, this |
| 235 |
document itself may not be modified in any way, such as by removing |
| 236 |
the copyright notice or references to the Internet Society or other |
| 237 |
Internet organizations, except as needed for the purpose of |
| 238 |
developing Internet standards in which case the procedures for |
| 239 |
copyrights defined in the Internet Standards process must be |
| 240 |
followed, or as required to translate it into languages other than |
| 241 |
English. |
| 242 |
|
| 243 |
The limited permissions granted above are perpetual and will not be |
| 244 |
revoked by the Internet Society or its successors or assigns. |
| 245 |
|
| 246 |
This document and the information contained herein is provided on an |
| 247 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 248 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 249 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 250 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 251 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 252 |
|
| 253 |
|
| 254 |
|
| 255 |
|
| 256 |
|
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
ISOC & Sun Informational [Page 5] |
| 277 |
</pre> |