Implementations conforming to the Storage Commitment Service shall support the transactions listed as Required in Table 13.2-1.

Implementations conforming to the Storage Commitment Service shall specify their role in their Conformance Statement (see PS3.2): origin server, user agent or both.

In addition, for each supported transaction they shall specify:

An origin server conforming to the Storage Commitment Service shall implement the Retrieve Capabilities Transaction, specifying its role (see Section 8.9 and Annex H).

Implementation-specific warning and error codes shall be included in the Conformance Statement.

An origin server implementation defines how it provides its commitment to storage. Certain origin servers may commit to permanently store the SOP Instances (e.g., an archive system) while other origin servers may commit to provide storage of the SOP Instances for a limited amount of time. The origin server shall document in its Conformance Statement the nature of its commitment to storage (e.g., duration of storage, retrieve capabilities and latency, capacity).

Once the origin server has committed to store the SOP Instances, the user agent may decide that it is appropriate to delete its copies of the SOP Instances. These types of behaviors are outside the scope of this Standard; however, the user agent shall document the types of behaviors it is able to provide in its Conformance Statement.

An origin server implementation shall specify in its Conformance Statement how long the result of a Request will be available for the user agent.