2. Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC2119, March 1997.
3. [SAM-2] ANSI NCITS. Weber, Ralph O., editor. SCSI Architecture
Model -2 (SAM-2). T10 Project 1157-D. rev 23, 16 Mar 2002.
4. [SPC-2] ANSI NCITS. Weber, Ralph O., editor. SCSI Primary
Commands 2 (SPC-2). T10 Project 1236-D. rev 20, 18 July
2001.
5. [CAM-3] ANSI NCITS. Dallas, William D., editor. Information
Technology - Common Access Method - 3 (CAM-3)). X3T10 Project
990D. rev 3, 16 Mar 1998.
6. [99-245r8] Hafner, Jim. A Detailed Proposal for Access
Controls. T10/99-245 revision 9, 26 Apr 2000.
7. [SPI-X] ANSI NCITS. SCSI Parallel Interface - X.
8. [FCP] ANSI NCITS. SCSI-3 Fibre Channel Protocol [ANSI
X3.269:1996].
9. [FCP-2] ANSI NCITS. SCSI-3 Fibre Channel Protocol - 2
[T10/1144-D].
10. Paxon, V. End-to-end internet packet dynamics, IEEE Transactions
on Networking 7,3 (June 1999) pg 277-292.
11. Stone J., Partridge, C. When the CRC and TCP checksum disagree,
ACM Sigcomm (Sept. 2000).
12. Malkin, G. and A. Harkin, "TFTP Blocksize Option", RFC2348, May
1998.
13. Floyd, S., "Congestion Control Principles", BCP 14, RFC2914,
September 2000.
12. Acknowledgements
Special thanks to Julian Satran, IBM and David Black, EMC for their
extensive review comments.
13. Author's Addresses
Address comments to:
Marjorie Krueger
Hewlett-Packard Corporation
8000 Foothills Blvd
Roseville, CA 95747-5668, USA
Phone: +1 916 785-2656
EMail: marjorie_krueger@hp.com
Randy Haagens
Hewlett-Packard Corporation
8000 Foothills Blvd
Roseville, CA 95747-5668, USA
Phone: +1 916 785-4578
EMail: Randy_Haagens@hp.com
Costa Sapuntzakis
Stanford University
353 Serra Mall Dr #407
Stanford, CA 94305
Phone: 650-723-2458
EMail: csapuntz@stanford.edu
Mark Bakke
Cisco Systems, Inc.
6450 Wedgwood Road
Maple Grove, MN 55311
Phone: +1 763 398-1054
EMail: mbakke@cisco.com
14. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFCEditor function is currently provided by the
Internet Society.