RE: Response Fence Flag

I need a little tutorial here.  Note that this is an architectural hack
that
is very "un-SCSI" and is not required if the response is qualified with
identification
information associated with the original request.  I know that such
qualification
exists for commands, but does it exist for task management requests in
iSCSI?  
 
I know that it does exist for parallel SCSI (which is strictly
interlocked)
and for SAS and Fibre Channel SCSI, making such "fences" unrequired by
those technologies.
 
Note that Rob's previous revision of 06-341 is available on www.t10.org.
 
I would hate to see such a hack creep into the SCSI architecture.
 
Bob
 

________________________________

From: Elliott, Robert (Server Storage) [mailto:[email protected]] 
Sent: Wednesday, January 03, 2007 1:56 PM
To: [email protected]
Subject: RE: [Ips] Response Fence Flag


If T10 agrees, T10 proposal 06-341 will add it to SAM-4.
 
-- 
Rob Elliott, [email protected] 
Hewlett-Packard Industry Standard Server Storage Advanced Technology 
https://ecardfile.com/id/RobElliott 



________________________________

	From: Eddy Quicksall [mailto:[email protected]] 
	Sent: Wednesday, January 03, 2007 2:00 PM
	To: [email protected]
	Subject: [Ips] Response Fence Flag
	
	
	Section 3.3.1 talks about a Response Fence Flag:
	 
	SCSI protocol layer instructs the SCSI transport layer of a 
	"Response Fence" associated with the response in question when 
	the "Send Command Complete" protocol data service (SAM-2, clause

	5.4.2) ...
	 
	But I don't see any reference to that in SAM-2.
	 
	Is this strictly an iSCSI flag? Where is the flag specified?
	 
	Eddy

_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips