port
Click on the red underlined text to get to the source
... application protocol
dynamically to target server and port.
As discussed in section 5, existing approaches to using DNS records ...
... address record is sought for the REPLACEMENT field target (and the
default protocol port is assumed).
...
...
o the designated remote server (host and port) fails to provide
appropriate security credentials ...
... 9. The client connects to that IP address, on port 10001 (from the
SRV record), by using ProtB over tcp.
...
... resource records to determine the host and port providing the server.
This enables a distinction between naming an application service
...
... SRV records provide mappings from protocol
names to host and port. The use cases described herein require an
additional layer -- from some service ...
... for a client to connect to authoritative server(s) (host, port,
protocol) for a particular application service within a given domain ...
...
port = -1
...
... pseudocode in Appendix A is crafted to find the first, most
preferred host-port pair for a particular application service and
protocol. If, for any reason, that host ...
... service and
protocol. If, for any reason, that host-port pair did not work
(connection refused, application-level ...
... NAPTR processing if the application code fails to connect to a
located host-port pair;
o use callbacks for the S-NAPTR ...