Revisions to final responses for transition of FCP from 007a to 008, PLEASE REVIEW
Bob.Snively at eng.sun.com
Mon Jan 17 20:41:58 PST 1994
REVISIONS TO PROPOSED RESOLUTIONS
FCP REV 007A TO FCP REV 008
The following items were resolved in a way different than originally proposed.
001 E Correct cover references
... If noticed by X3, there could be
objection to the title FC Working Group Chair since the procedures
specifically prohibit the concept of any standing working groups.
>> Dal Allan is re-labeled as: Fibre Channel Leader
003 E Editorial fixes
protocol in "Fibre Channel protocol" and consider deleting "requirements".
The last sentence of the abstract is instead modified to say: "This standard
describes the frame format and protocol definitions required to
transfer commands and data between a SCSI (Small Computer System Interface)
Initiatior and Target using the Fibre Channel Physical and Signaling
012 E FC-PH levels
In 3.1.16 I question the usage of FC-2 here ... since
I recall the Fibre Channel levels being poorly documented within
FC-PH. Has the ambiguity in the level content been rectified in
The levels remain poorly defined in FC-PH. In section 3.1.15 (rev 007a) I will
change the text to indicate Fibre Channel service interface instead of FC-2.
014 E Logical Unit Number
In 3.1.26 the definition is watered down from SAM. Citing
the equivalence to the Entity Address is not very helpful since
that definition of Entity Address is not included in 3.1.
The entity address is renamed as the logical unit number throughout the
033 E Other PRLI parameters
Note FC-4 issue in 6.1. Does the paragraph they are in imply
that FCP requires items in FC-SB and other unamed FC documents
besides PRLI or is it a throw away paragraph other than the portion
that is redundant to the second sentence of 6?
The original proposal suggested listing the common service parameters
in FCP for reference. After observing that this description occupies
13 pages in SB, I elected to leave the definitions in SB, Annex A.
5) The Fibre Channel implementation of Abort Task has an interesting characteristic.
After an Abort, data may still continue flowing into a host adapter. The
data may have been transmitted and be passing through the fabric, or it may
be part of a sequence that has been committed to hardware in the target and
will continue being transferred for some time. As a result, the host adapter
still has to expect some data to come through. The FC-PH places the
data under control of the Recovery Qualifier until the initiator emits a
Reinstate Recovery Qualifier command. Thus data will either be dropped in the
bit bucket or routed to memory and ignored. In either case, certain resources
(the Exchange resources and perhaps the memory resources) cannot be freed until
the RRQ command is passed. The result is that the Abort command's completion
indication (required by SAM) may not be able to be presented immediately.
A sentence is installed in section 7.1.2 to say: "To be compliant
with FC-PH, the ABORT TASK may not immediately release all
exchange resources, since a Recovery Qualifier may be established to
allow for the mangement of information that may already have
been delivered to the switching fabric."
More information about the T10