Subject: T10/07-469r9 iADT Posted
Date: Tue, 7 Oct 2008 00:31:15 -0600
From: "Paul Suhler" <Paul.Suhler@Quantum.Com>
To: <t10@t10.org>
X-Message-Number: 9181
Formatted message: HTML-formatted message

I have posted the latest revision of 07-469 for discussion at the Wednesday
morning teleconference.  The changes from the previous version include:
*	Incorporated changes from 8 September 2008 meeting, minutes in
T10/08-372r0 <http://www.t10.org/ftp/t10/document.08/08-372r0.pdf>; .
*	Deleted retirement to send a Close event to Port state machine upon
connection close.
*	Removed requirement to have Sensea/Sensed asserted to establish a
connection.
*	Incorporated comments from IBM's T10/08-392r0
<http://www.t10.org/ftp/t10/document.08/08-392r0.pdf>;  and from an IBM e-mail
about the Sockets API.	This includes a new informative subclause 6.4.6.
*	Renamed Close service request and Closed service indication to
Disconnect and Disconnected.
*	Added ADT Port argument to protocol services to identify the ADT
port.
*	Deleted service responses that are generated only in response to
invalid requests, e.g., coding errors like NULL arguments.  Added subclause
6.2.11 and Table w indicating possible causes of other errors and recovery
procedures.
*	Deleted some of the detailed renumbering instructions; the editor is
capable of doing this himself.
http://www.t10.org/ftp/t10/document.07/07-469r9.pdf
Thanks to IBM for providing detailed comments.
Paul
___________________________________
Paul A. Suhler | Firmware Engineer | Quantum Corporation | Office:
949.856.7748 | paul.suhler@quantum.com
___________________________________
Disregard the Quantum Corporation confidentiality notice below.  The
information contained in this transmission is not confidential.  Permission
is hereby explicitly granted to disclose, copy, and further distribute to any
individual(s) or organization(s), without restriction.
-----------------------------------------------------------
The information contained in this transmission may be 
confidential. Any disclosure, copying, or further 
distribution of confidential information is not permitted 
unless such privilege is explicitly granted in writing by 
Quantum Corporation. Furthermore, Quantum Corporation is not 
responsible for the proper and complete transmission of the 
substance of this communication or for any delay in its 
receipt.
------------------------------------------------------------