domain
Click on the red underlined text to get to the source
... service
naming that allows service location without relying on rigid domain
naming conventions (so-called name hacks). The proposal defines a
Dynamic Delegation Discovery System ...
... DDDS -- see [4]) Application to
map domain name, application service name, and application protocol
...
... DDDS Application to
map service+protocol+domain to specific server addresses by using
both NAPTR ...
... NAPTR records are used to store application
service+protocol information for a given domain. Following the DDDS
standard, these records are looked up, and the rewrite rules
...
... NAPTR records associated with the target
domain name (example.com, above). These are to be sorted in terms of
increasing ORDER and increasing PREF within each ORDER.
...
... queries for the NAPTR RRs for the domain
of a named application service. The first DNS query ...
... NAPTR records
(i.e., those for the target named domain). However, the chosen
protocol MUST be listed in that first NAPTR RR ...
... Note that this approach is intended specifically for use when it
makes sense to associate services with particular domain names (e.g.,
e-mail addresses, SIP ...
... addresses, etc). A non-goal is having all
manner of label mapped into domain names in order to use this.
This document does not address ...
...
This document does not address how to select the domain for which the
service+protocol is being sought. Other conventions will have to
...
... service+protocol is being sought. Other conventions will have to
define how this might be used (e.g., new messaging standards can
define what domain to use from their URIs or how to step down from
foobar.example.com to example.com, if applicable).
...
... identify the server as being authoritative for the original target
domain is always considered a failure condition.
...
... Guidelines for Domain Administrators ...
...
o Service discovery within a domain. For example, this can be used
to find the "authoritative" server for some type of service within
...
... to find the "authoritative" server for some type of service within
a domain (see the specific example in section 4.2).
o Multiple protocols. This is already common today as new
...
... o Remote hosting. Each of the above use cases applies within the
administration of a single domain. However, one domain operator
may elect to engage another organization to provide an application
...
... Remote hosting. Each of the above use cases applies within the
administration of a single domain. However, one domain operator
may elect to engage another organization to provide an application
service ...
... Service Discovery within a Domain ...
... "authoritative" server for a given application service within a
domain. This is "discovery", as there is no a priori knowledge as to
whether or where the service is offered; it is therefore important to
...
... certificates associated with
particular application (servers) operated in (or for) a particular
domain. The following is a hypothetical case for storing application
key or certificate data for a given domain ...
... domain. The following is a hypothetical case for storing application
key or certificate data for a given domain: the premise is that a
credentials registry ...
... node service holding the keys/certs for the servers operated by (or
for) the domain. It is assumed that more than one protocol is
available to provide the service for a particular domain ...
... domain. It is assumed that more than one protocol is
available to provide the service for a particular domain. This
DDDS-based approach is used to find the CredReg server that holds the
...
...
Note that the application service might be offered in another domain
using a different set of application protocols:
...
...
2. Extensible messaging servers are likely to be operated out of a
different domain than that of the extensible messaging address,
and servers of different protocols may be offered by independent
...
... service's SRV records in the thinkingcat.example domain.
A better approach is to have one NAPTR ...
... NAPTR RR in the thinkingcat.example
domain point to all the hosted services. The hosting domain ...
... domain point to all the hosted services. The hosting domain has
NAPTR records for each service ...
... service
available (via S-NAPTR) per domain. Often, this will not be the
case. Assuming that thinkingcat.example had the CredReg service set
...
... client to reach the final server for a "ProtB"
service for EM for the thinkingcat.example domain is as follows:
Client ...
...
Increasingly, application protocol standards use domain names to
identify server targets and stipulate that clients ...
... SRV records can be used to map from a specific
service name and protocol for a specific domain to a specific server,
SRV records are limited to one layer ...
... SRV record is located, this proposal requires only a subset of
NAPTR strictly bound to domain names, without making use of the
REGEXP field of NAPTR ...
... SRV RR allows administrators to use several servers for a single
domain, to move services from host to host ...
... Target servers by "service" (e.g., "ldap") and "protocol" (e.g.,
"tcp") in a given domain. The definition of these terms implies
specific things (e.g., that protocol should be one of UDP or TCP ...
... layer -- from some service label to servers that may in be
hosted within different administrative domains. We could tweak SRV
to say that the next lookup ...
...
The Application Unique String is domain label for which an
authoritative server for a particular service is sought.
...
... First Well-Known Rule" is identity -- that is, the output of the
rule is the Application-Unique String, the domain label for which the
authoritative server for a particular service is sought.
...
... lookups. This means that the Rule is the last
one and that the flag determines what the next stage should be. The
"S" flag means that the output of this Rule is a domain label for
which one or more SRV [3 ...
... SRV [3] records exist. "A" means that the output
of the Rule is a domain name and should be used to lookup address
...
... NAPTR DNS resource
record contain the rewrite rules. The Keys for this database are
encoded as domain-names.
The First Well-Known Rule ...
...
The First Well-Known Rule produces a domain name, and this is the Key
used for the first look up. The NAPTR records for that domain ...
... domain name, and this is the Key
used for the first look up. The NAPTR records for that domain are
requested.
...
... Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403prop ...
... Newton, A. and M. Sanz, "IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS ...
... Atkins, D. and R. Austein, "Threat Analysis Of The Domain Name System", Work in Progress, April 2004. ...
... for the required application service and protocol from the
originating domain and that provides them in a sorted order for
the application to try.
...