[T13] [T13] [T13] [T13] Integrating zone attribute ideas from T13 ZAC call

[Joe Breher]

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

inline...
On May 21, 2015, at 2:14 PM, Gerry Houlder
<gerry.houlder at seagate.com> wrote:
OK, so then that would lead to wording examples like "If the Zone Condition
attribute is set to Empty, then ..." or "A Zone Condition attribute value of
Empty indicates ...". Is this what you had in mind Joe?
Yes, I believe those would work. We might even shorthand it to 'if the Zone
Condition (see w.x.y.z) is set to, then...', though I personally would prefer
'Zone Condition zone attribute' -- at least until such time as we might
create a Zone class.
We may not need to employ this attribute in places other than:
a) where we are defining what to return for the ZONE CONDITION field within
the REPORT ZONES parameter data, and
b) where we are updating the attribute value upon any zone condition state
machine transition
as this attribute is only necessary in order to bridge from the
unreferenceable state machine to the ephemeral REPORT ZONES command.
Are we OK with having a Zone Condition Attribute and a ZONE CONDITION field?
Ralph was intentionally make the wording a little different for these two to
reduce the chance of confusing them. Maybe there wouldn't be any confusion
since one is always follows by "attribute" and the other always followed by
"field".
Well, for completeness, we have the ZONE CONDITION field, and we have the
'zone condition' which is the value within the ZONE CONDITION field, right?
Accordingly, the camel cap of Zone Condition can be used to discriminate the
attribute from the field or the value in the field. This might be too fine a
distinction for comfort. 'Zone Condition zone attribute' makes this
distinction abundantly clear, but gets back to the verbosity to which you
seem to be disinclined.
Fortunately, the possible enumerated values of this particular attribute
could be made to have a 1:1 relationship with the values that can be
represented in the ZONE CONDITION field, and also to the states of the state
machine. We still need to tread carefully, however, as future uses of this
newly invented bald attribute may not be so constrained -- this seems to set
a new precedent.
Joe Breher
Storage Architecture Technologist
Standards Setting Organization
San Jose Research Center
HGST, a Western Digital company
(478) 2-Breher
(478) 227-3437
This e-mail may contain confidential or legally privileged information of
HGST. If you are not the intended recipient, please notify us immediately by
responding to this e-mail and then deleting it from your system.