URI
Click on the red underlined text to get to the source
... 7] application to allow
mapping of domain names to URIs for particular application services
and protocols. This allows the "lookup ...
... S-NAPTR DDDS Application). However, that also rules
out the possibility of providing a URI as the target of DDDS
...
... U-NAPTR is effectively a modest extension to S-NAPTR, to
accommodate the use of URIs as targets, without allowing the full
range ...
... Straightforward URI-Enabled NAPTR (U-NAPTR) ...
... described below, and the result of the regular expression evaluation
will be a URI that is the result of the DDDS resolution.
...
... U-NAPTR permits regular expressions of a form that does a complete
replacement of the matched string with a URI, expressed as a constant
string. This is essentially a dodge around the fact that the
REPLACEMENT field in NAPTR ...
... REPLACEMENT field in NAPTR is required to produce only a fully
qualified domain name (and, therefore, cannot be used for a URI).
The specific allowed syntax for U-NAPTR ...
... to connect to authoritative server(s) (host, port, protocol, or URI)
for an application service within a given domain ...
...
This DDDS Application uses only 3 of the Flags defined for the URI/
URN Resolution Application [5 ...
... records for that domain. "U" means that the output of the Rule is a
URI that should be resolved in order to obtain access to the
described service.
...
...
Note that this is similar to, but not the same as the syntax used in
the URI DDDS application [5]. The DDDS ...
... The syntax here is expanded to allow the characters that are valid in
any URI scheme name (see [8]). Since "+" (the separator used in the
RFC3404prop ...
... RFC3404prop service parameter string) is an allowed character for URI
scheme names, ":" is chosen as the separator here.
...
... following syntax (i.e., a regular expression to replace the domain
name with a URI):
u-naptr-regexp = "!.*!"<URI ...
... The defining RFC may also include further application-specific
restrictions, such as limitations on the types of URIs that may be
returned for the application service.
...
... 2]. U-NAPTR has the additional consideration that
resolving URIs (from the result of the DDDS resolution) has its own
set of security implications ...
... DDDS resolution) has its own
set of security implications, covered in the URI specification (in
particular, Section 7 of [8]). In essence, using DNSSEC ...
... 8]). In essence, using DNSSEC, client
software can be confident that the URI obtained using U-NAPTR is
indeed the one specified by the administrator ...
... validity of the service reached by
resolving that URI is a matter of URI resolution security practices.
...
... Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404prop, October 2002. ...
... Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", RFC 3986std66, STD ...