URI
Click on the red underlined text to get to the source
... to a resource identified by a SIP or SIPS (secure SIP) URI. This URI
can identify the desired resource to which the request is targeted
...
... SIP or SIPS (secure SIP) URI. This URI
can identify the desired resource to which the request is targeted
(in which case, the URI ...
... URI
can identify the desired resource to which the request is targeted
(in which case, the URI is found in the Request-URI), or it can
identify an intermediate hop towards that resource (in which case,
...
... can identify the desired resource to which the request is targeted
(in which case, the URI is found in the Request-URI), or it can
identify an intermediate hop towards that resource (in which case,
the URI ...
... Request-URI), or it can
identify an intermediate hop towards that resource (in which case,
the URI is found in the Route header). The procedures defined here
...
... Route header). The procedures defined here
in no way affect this URI (i.e., the URI is not rewritten with the
result of the DNS lookup ...
... header). The procedures defined here
in no way affect this URI (i.e., the URI is not rewritten with the
result of the DNS lookup), they only result in an IP address ...
... 3261prop [1]
provides guidelines on determining which URI needs to be resolved in
DNS to determine the host ...
... 1], the request can be sent to a
specific intermediate proxy not identified by a SIP URI, but rather,
by a hostname or numeric IP address. In that case, a temporary URI ...
... SIP URI, but rather,
by a hostname or numeric IP address. In that case, a temporary URI,
used for purposes of this specification, is constructed. That URI is
...
... IP address. In that case, a temporary URI,
used for purposes of this specification, is constructed. That URI is
of the form sip:<proxy>, where <proxy ...
... proxy. As a result, in all cases, the
problem boils down to resolution of a SIP or SIPS URI in DNS to
determine the IP address ...
...
We define TARGET as the value of the maddr parameter of the URI, if
present, otherwise, the host value of the hostport component of the
...
... present, otherwise, the host value of the hostport component of the
URI. It identifies the domain to be contacted. A description of the
SIP ...
... domain to be contacted. A description of the
SIP and SIPS URIs and a definition of these parameters can be found
in [1].
...
... SIP URI, and TCP
for a SIPS URI. Similarly, if no transport protocol is specified,
and the TARGET ...
... UDP for a SIP URI, and TCP for a SIPS URI. This is
because UDP is the only mandatory transport ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) [6], and thus
the only one guaranteed to be interoperable for a SIP URI. It was
also specified as the default transport in RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) when no transport
was present in the SIP URI. However, another transport, such as TCP,
...
...
First, a client resolving a SIPS URI MUST discard any services that
do not contain "SIPS" as the protocol in the service field ...
... service field. The
converse is not true, however. A client resolving a SIP URI SHOULD
retain records with "SIPS" as the protocol, if the client supports
...
... SRV records are found, the client SHOULD use TCP for a SIPS
URI, and UDP for a SIP URI. However, another transport protocol ...
... IP address, but a port is present in
the URI, the client performs an A or AAAA record lookup ...
... IP addresses, each of which can
be contacted at the specific port from the URI and transport protocol
...
... identifier "_sips" for SIPS URIs. For a
SIP URI, if the client wishes to use TLS, it also uses the service ...
...
In many cases, an element needs to construct a SIP URI for inclusion
in a Contact header in a REGISTER ...
... INVITE. According to RFC 3261prop [1], these URIs have to have the
property that they resolve to the specific element that inserted
...
... (indicating the preferred choice), and this record points to the
specific element that constructed the URI. However, there are
additional records with higher values of the priority field that
...
... is in fact available and preferred.
This is partially mitigated by the presence of the sips URI scheme,
which is always sent only over TLS. An attacker ...
... DNS records. In the worst
case, they can prevent communication from occurring by deleting all
records. A sips URI itself is generally exchanged within a secure
context, frequently on a business card or secure web page, or within
...
... 3261prop
[1] for details. The sips URI is therefore preferred when security
is truly needed, but we allow TLS ...
... is truly needed, but we allow TLS to be used for requests resolved by
a SIP URI to allow security that is better than no TLS at all.
...
... Transport Determination Application, and its goal is to
map an incoming SIP or SIPS URI to a set of SRV records for the
various servers that can handle the URI ...
... SIPS URI to a set of SRV records for the
various servers that can handle the URI.
The following is the information that DDDS ...
... the input to the resolution service. For this application, it
is the URI to resolve.
First Well Known Rule: The first well known rule extracts a key
...