H.2.3 Referenced Standards

H.2.3 Referenced Standards (Current)
Prev	H.2 DNS Service Discovery	Next

RFC2136 DNS Dynamic Updates http://tools.ietf.org/html/rfc2136

RFC2181 Clarifications to the DNS Specification http://tools.ietf.org/html/rfc2181

RFC2219 Use of DNS Aliases for Network Services http://tools.ietf.org/html/rfc2219

RFC2782 A DNS RR for specifying the location of services (DNS SRV) http://tools.ietf.org/html/rfc2782

RFC6762 Multicast DNS http://tools.ietf.org/html/rfc6762

RFC6763 DNS-Based Service Discovery http://tools.ietf.org/html/rfc6763

DNS Self-Discovery http://www.dns-sd.org/

The name to be used in the DNS SRV to advertise DICOM Association Acceptors, regardless of the SOP Class(es) supported, shall be

"dicom" for unsecured DICOM communication
"dicom-tls" for the Basic TLS Secure Transport Connection Profile
"dicom-iscl" for ISCL Transport Connection Profile
"dicomweb" for DICOM web services over unsecured http
"dicomweb-tls" for DICOM web services over https

Note

These choices are consistent with the names registered with IANA to define the mapping of IP ports to services, which is conventional for this usage. The choice "dicom" is used rather than the "acr-nema" alternative for clarity. There is no implied port choice by the usage in the DNS SRV Service Type, since the port is explicitly conveyed.

The DNS TXT record may contain the following parameters:

AET= <application entity title>, where the value <application entity title>is to be used as the Called Application Entity Title when initiating Associations to the device
PrimaryDeviceType= <primary device type>, where the value <primary device type>is as defined Table H.1-2 Attributes of Device Object
DICOMWebPath= <service>, where the value <service> is the path component of the DICOM Web Service root as defined in PS3.18

In the absence of a DNS TXT record, or the AET parameter of the DNS TXT record, then the Instance Name preceding the Service Type in the DNS SRV record used for DICOM service discovery shall be the AET.

Note

Further parameters are not specified, for example to indicate the SOP Classes supported or other information, since the size of DNS records encoded as UDP datagrams is strictly limited, and furthermore, the envisaged multicast usage encourages the exchange of the minimal information necessary. The existing DICOM association negotiation mechanism can be used to explore the SOP Classes offered once the IP address, port number and AET are known. The primary device type is supplied because it is useful to indicate to users the type of device, which is not conveyed during association establishment.

Prev	Up	Next
H.2.2 Use Case Roles	Home	H.2.4 Examples