FIBRE CHANNEL - T11

TR-xx-1998 Fibre Channel Tape Rev 1.07 August 7, 1998
The relationship between use (specified in this document) and support (implemented by a product) is
subtle. If this document specifies that a feature must be used, then a compliant adapter must support
it. In some cases, the specification is asymmetric: to ensure interoperability when an optional feature
is used, this document mandates support for the infrastructure required to use the feature without
specifying that the feature actually be used when conforming to this profile.
The requirements of this document are a proper subset of the various relevant standards. They prohibit
use of many features and options in these standards; and interoperability is not guaranteed if
these features are used. This document does not prohibit implementation of features, only their use.
Functions that are mandatory in the appropriate base standard are assumed to be implemented. Implementations
may support features whose use is prohibited by this document and such prohibited
features may be required for compliance with the relevant standards or other Profiles or applications
not covered by this document.
In the event of conflicts between this profile and other profile documents, the resolution of those conflicts
is beyond the scope of this document.
3.5 Definitions and abbreviations used in Feature Set tables
The following definitions are used to define usage of reference features or options provided by the
applicable standards.
Prohibited: If a feature is Prohibited, it means that it shall not be used between FC-TAPE compliant
implementations. An implementation may use the feature to communicate with non-compliant implementations.
This document does not prohibit the implementation of features, only their use between
FC-TAPE compliant implementations. However, interoperability is not guaranteed if Prohibited features
are used when communicating with devices conforming to this profile.
Required: If a feature or parameter value is Required, it means that it shall be used between all FC-
TAPE compliant implementations. FC-TAPE compliant implementations are required to implement
the feature. An implementation may use the feature to communicate with non-compliant implementations.
Interoperability with devices conforming to this profile is not guaranteed if Required features
are not implemented.
Allowed: If a feature or parameter value is Allowed, it means that it may be used between FC-TAPE
compliant implementations. FC-TAPE compliant implementations are not required to implement the
feature, but if they do, the feature shall be implemented as described in the applicable standard. Typically,
the potential user of a feature may determine if the potential recipient supports that feature via
a Required discovery process or a minimal response by the recipient.
Invokable: If a feature or parameter value is Invokable, it means that it may be used between FC-
TAPE compliant implementations. FC-TAPE compliant implementations are required to implement
the feature, and make available the use of the feature. Invokable is different than Allowable or Required
in that an originator may invoke the feature if needed, but the originator is not required to invoke
it, and may never need to. The recipient shall support Invokable features or provide a response
that it is not implemented as defined by the appropriate standard. In each case, this profile shall state
whether the recipient is Required to support the feature or function.
Features in this document are summarized in the form of Feature Set tables. These tables indicate
whether the feature is Required, Prohibited, Invokable, or Allowed for FC-TAPE compliance with this
report; or whether a parameter is Required to be a particular value for compliance with this document.
Features or parameters that are not listed do not affect interoperability of Private NL_Ports.
The following legend is used for table entries in these clauses:
7