RFC 3832:Remote Service Discovery in the Service L...
RFC-Ref

DNS SRV


Click on the red underlined text to get to the source

... Service Location Protocol (SLP) [RFC2608] via DNS SRV [RFC2782]. We consider remote service discovery ...
... multicast). DNS SRV provides good support for remote service discovery. However, if multiple servers are discovered via DNS SRV ...
... DNS SRV provides good support for remote service discovery. However, if multiple servers are discovered via DNS SRV for a service, only priority ...
... service properties (such as cost, speed and service quality) need to be considered in the selection process, DNS SRV becomes insufficient. We propose that using SLP ...
... We propose that using SLP and DNS SRV together can provide better support for remote service discovery. First, a UA ...
... support for remote service discovery. First, a UA uses DNS SRV to find SLP DAs at a remote DNS ...
... services. In this way, we can avoid the limitations in using SLP and DNS SRV separately. On one hand, without DNS SRV, an SLP ...
... SLP and DNS SRV separately. On one hand, without DNS SRV, an SLP UA needs to depend on static ...
... administrative domain. On the other hand, without SLP, DNS SRV has limited support for service selection. ...
... service selection. In this document, we first define the DNS SRV Resource Records (RRs) ...
... domain. Then, we discuss various issues in using SLP and DNS SRV together for remote service discovery. Finally, we give the steps ...


... The DNS SRV RRs for SLP DA ...
... According to RFC 2782prop [RFC2782], the DNS SRV RRs for SLP DA ...
... DA. Please refer to [RFC2782] for detailed explanation of each field in DNS SRV RRs. ...
... RRs. Next we show an example of using DNS SRV RRs to map a given DNS ...
... SRV. Then the UA will receive a list of DNS SRV RRs in a DNS reply, which gives ...


... Remote Service Discovery in SLP via DNS SRV ...
... SLP DAs can be discovered in two ways: (1) using the mechanisms described in RFC 2608, and (2) using DNS SRV RRs as described in this document. The second approach is useful for UAs ...
... Using DNS SRV RRs to discover SLP DAs requires knowledge of the ...
... UA uses remote DAs according to these prioritized rules: (1) using DAs which it has been configured with, and (2) using DAs which it has discovered via DNS SRV. ...
... service MUST be registered in the "default" scope, but it MAY be registered in other scopes at the same time. Similarly, all DAs advertised via DNS SRV MUST serve the "default" scope, but they MAY serve other scopes at the same time. As a result, users wishing to discover services ...


... IN, and QTYPE=SRV. Then, U gets a list of DNS SRV RRs (referred to as L) in a DNS reply, which ...


... queries that are not in the "default" scope. In addition, the security considerations for DNS SRV [RFC2782] apply to this document. Also, the DNS security extensions ...


... This specification describes remote service discovery in SLP via DNS SRV. It facilitates discovering services at a remote DNS domain ...
... Users should be aware of two constraints in using DNS SRV to discover SLP DAs: (1) they SHOULD only use DNS SRV ...
... DNS SRV to discover SLP DAs: (1) they SHOULD only use DNS SRV to discover DAs in the "default" scope, and (2) an administrator may choose to register ...
... administrator may choose to register only a subset of all DAs in the "default" scope via DNS SRV. Thus, to discover local DAs, implementations MUST use the standard SLP ...
... mechanisms per RFC 2608. In addition, implementations supporting this specification MAY use DNS SRV to discover local DAs in the "default" scope. ...
... Note that the services discovered via DNS SRV and remote SLP DAs may not necessarily be remotely accessible. ...


... In the DNS SRV RRs for SLP DA ...


... DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...



Google
Web
RFC-Ref