domain
Click on the red underlined text to get to the source
... services in given
remote DNS domains, and local service discovery as discovering
desired services ...
... service discovery as discovering
desired services within the local administrative domain.
SLP ...
... UAs) discover desired services in
the local administrative domain by querying all Service Agents (SAs)
...
... DA
discovery are not generally applicable beyond the local
administrative domain. On the other hand, without SLP, DNS SRV has
...
... DA services, which are used to map a given DNS domain to
remotely accessible (i.e., accessible from the Internet) DAs in that
...
... remotely accessible (i.e., accessible from the Internet) DAs in that
domain. Then, we discuss various issues in using SLP and DNS SRV
...
... services, the Proto
field is either "tcp" or "udp", and the Target field is the domain
name of an SLP DA. Please refer to [RFC2782 ...
... RRs to map a given DNS
domain to remotely accessible DAs in that domain. To discover
remotely accessible DAs in a remote domain ...
... DNS
domain to remotely accessible DAs in that domain. To discover
remotely accessible DAs in a remote domain (say, example.com), a UA ...
... domain to remotely accessible DAs in that domain. To discover
remotely accessible DAs in a remote domain (say, example.com), a UA
makes a DNS query ...
... RRs in a DNS reply, which gives
all remotely accessible DAs in the domain example.com, such as:
;; Priority Weight Port Target ...
... UAs to acquire service
information for remote DNS domains. For example, a mobile node
visiting a network ...
... RRs to discover SLP DAs requires knowledge of the
domain where SLP DAs are registered. For remote service discovery,
...
... service discovery,
it is assumed that the DNS domain of interest is known via a priori
knowledge. For example, a UA is configured with a domain name ...
... domain of interest is known via a priori
knowledge. For example, a UA is configured with a domain name or the
user provides the domain name manually.
...
... UA is configured with a domain name or the
user provides the domain name manually.
Note that there is no implied "search ...
... Note that there is no implied "search order" of DNS domains in
finding remote DAs. For instance, if a UA is looking for remote DAs
...
... finding remote DAs. For instance, if a UA is looking for remote DAs
in the domain foo.bar.example.com, it SHOULD only look for
_slp._tcp.foo.bar.example.com (or _slp._udp.foo.bar.example.com), and
MUST NOT fall back to look for _slp._tcp.bar.example.com,
...
... UA discovers desired services in a given remote DNS domain by
unicasting requests to DAs in that domain. The UA ...
... DNS domain by
unicasting requests to DAs in that domain. The UA uses remote DAs
according to these prioritized rules: (1) using DAs which it has been
...
...
As SLP scopes are intended to be used only within one administrative
domain, they are likely incomprehensible to users outside of the
administrative domain. Thus, any remotely accessible service ...
... SLP scopes are intended to be used only within one administrative
domain, they are likely incomprehensible to users outside of the
administrative domain. Thus, any remotely accessible service MUST be
registered in the "default" scope, but it MAY be registered in other
...
...
To support remote service discovery, a domain exposes its service
information to the Internet. Standard SLP ...
... DNS
SRV. It facilitates discovering services at a remote DNS domain if
the domain name is known via a priori knowledge. However, it does
...
... DNS domain if
the domain name is known via a priori knowledge. However, it does
not intend to solve the problem of Internet-wide service discovery.
...
... As SLP scopes are not intended to be used outside the local
administrative domain, all remote service discovery in SLP SHOULD be
...
... Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034std13, November 1987. ...
... Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035std13, November 1987. ...
... Eastlake 3rd, D., "Domain Name System Security Extensions", RFC 2535(-> 4035prop | 4034prop | 4033prop), March 1999. ...