SPC-4 late letter ballot comment

[Knight, Frederick]

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1303069_f.htm">HTML-formatted message</a>

There is no information in the Asymmetric Access state model that
describes how asymmetric access states are reported.  This late
letter ballot comments adds that description.
Create a new:
5.16.2.4.x Target port asymmetric access state reporting
Target port asymmetric access state information is reported in a target
port descriptor (see table 306 - Target port group descriptor format in
6.37) in response to a REPORT TARGET PORT GROUPS command.  The response
for each REPORT TARGET PORT GROUPS command is independent (e.g., the device
server may return different states for the same target port in the responses
to multiple REPORT TARGET PORT GROUPS commands).
The information returned in the target port group descriptor that contains
a target port descriptor with a relative target port identifier that
matches the relative target port identifier of the target port to which the
REPORT TARGET PORTS GROUP command is sent shall be the current information.
Example: If the application client sends two REPORT TARGET PORT GROUPS
commands; the first, called command "A", via the target port with relative
target port identifier 100 and the second, called command "B", via the
target port with relative target port identifier 101 then the information
returned by the device server in the target port group descriptor that
contains relative target port identifier 100 in response to command "A" is
current information and the information returned by the device server in
the target port group descriptor that contains relative target port
identifier 100 in the response to command "B" may not be current information.
The information returned by the device server in the target port
group descriptor that contains relative target port identifier 101 in
the response to command "B" is current information and the information
returned by the device server in the target port group descriptor that
contains relative target port identifier 101 in the response to command
"A" may not be current information.
If an application client detects more than one set of information for a
target port (i.e., both current information and information that may not
be current), then the application client should use the current information.