DICOM PS3.3 2022d - Information Object Definitions

P.2.2 Protocol

The non-DICOM file access protocol used in the Inventory URI link is not constrained by this Standard. The Conformance Statement for the implementation shall specify the protocol(s) in its description of conformance to the Inventory SOP Class. Some common protocols are listed in Table P.2-1.

Note

  1. Conformance specification may be facilitated by reference to IANA-registered schemes (http://www.iana.org/assignments/uri-schemes/).

  2. Several protocols are layered on HTTP. While the specific protocol should be specified in the Conformance Statement, the only feature required is the ability to read an object, which is generally implemented simply as an HTTP GET in such protocols, and may be implemented with only a URI.

  3. An access protocol will support technical means for access control and transport security, which must be used in accordance with institutional security policies and procedures. See Section YYYY.6.1 “Access Control and Secure Transport” in PS3.17.

Table P.2-1. Common Non-DICOM File Access Protocols (Informative)

IANA-registered Scheme

Protocol

Further Specification

nfs

NFS

[RFC7530]

smb

SMB

http://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-smb2

https

HTTP GET

[RFC7230], [RFC7231] Includes various cloud storage implementations


DICOM PS3.3 2022d - Information Object Definitions