[T11.3] FC-LS/FCP-4: Proposed REC behavior

Roger Hathorn rhathorn at us.ibm.com
Wed Aug 30 13:53:18 PDT 2006


Formatted message: <A HREF="r0608303_f.htm">HTML-formatted message</A>
Attachment #1: <A HREF="r0608303_graycol.gif">graycol.gif</A>
Attachment #2: <A HREF="r0608303_pic14651.gif">pic14651.gif</A>
Attachment #3: <A HREF="r0608303_ecblank.gif">ecblank.gif</A>

I suggest that the proposed text:
A Read Exchange Consise Request shall only be accepted if the Originator
Nx_Port or the Responder Nx_Port of the target Exchange makes the request
be changed to:
"A Read Exchange Consise Request shall only be issued by the Originator
Nx_Port or the Responder Nx_Port of the target Exchange."
to allow existing implementations to remain compliant.	 The text, as
proposed, indicated that the recipient has to somehow check this.
Roger G. Hathorn
Senior Engineer, Storage Systems Development
IBM Systems and Technology Group
Tel: 520-799-5950 (T/L: 321-5950)
Pager: 520-446-2741 or
http://www.arch.com/cgi-bin/wwwpreproc.exe?PIN=5204462741
	     "David Peterson"					       
	     <David.Peterson at m					       
	     cdata.com> 						To
	     Sent by:		       <t10 at t10.org>, <t11_3 at mail.t11.org>
	     t11_3-bounces at lis						cc
	     tserve.com 					       
								   Subject
				       [T11.3] FC-LS/FCP-4: Proposed REC
	     08/30/2006 10:29	       behavior 		       
	     AM 						       
Howdy,
To remove the ability for a third party to issue an REC, here is the
proposed text for FC-LS:
4.2.42.1 Description
This ELS shall be used only for purposes specific to an FC-4. The REC (Read
Exchange Concise) Extended Link Service requests an Nx_Port to return
Exchange information for the RX_ID and OX_ID originated by the S_ID
specified in the Payload of the request Sequence. The S_ID specified in the
Payload of the request Sequence may differ from address identifiers of both
the source and destination of the REC request itself. A Read Exchange
Consise Request shall only be accepted if the Originator Nx_Port or the
Responder Nx_Port of the target Exchange makes the request. The
specification of OX_ID and RX_ID shall be provided for the destination
Nx_Port to locate the status information requested. A Responder destination
Nx_Port shall use the RX_ID and verify that the OX_ID is consistent, unless
the RX_ID is unassigned (i.e., RX_ID = FFFFh). If the RX_ID is unassigned
in the request, the Responder shall identify the Exchange by means of the
S_ID specified in the Payload of the request Sequence and OX_ID. An
Originator Nx_Port shall use the OX_ID and verify that the RX_ID is
consistent.
Please review the proposed text and be ready for a vote at the October T11
FC-LS working group meeting.
Thanks...Dave
(no disclaimer)
_______________________________________________
T11_3 mailing list
http://mailman.listserve.com/listmanager/listinfo/t11_3



More information about the T10 mailing list