RFC 3958:Domain-Based Application Service Location...
RFC-Ref

address


Click on the red underlined text to get to the source

... host for a given application service are limited in terms of the use cases supported. To address some of the limitations, this document defines a DDDS Application to ...
... map service+protocol+domain to specific server addresses by using both NAPTR [5 ...


... and normal SRV processing is applied. In the case of an "A" flag, an address record is sought for the REPLACEMENT field target (and the default protocol port ...


... services with particular domain names (e.g., e-mail addresses, SIP addresses, etc). A non-goal ...
... e-mail addresses, SIP addresses, etc). A non-goal is having all manner of label mapped into domain names ...
... domain names in order to use this. This document does not address how to select the domain for which the service ...


... 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 organizations. ...
... 8. The client gets the A record with the IP address for backup.em.example.com from example.com's NS. ...
... 9. The client connects to that IP address, on port 10001 (from the SRV record ...


... o the purpose of SRV is to address individual server administration issues, not to provide application naming: As stated in [3], "The ...
... SRV to say that the next lookup could be something other than an address record, but this is more complex than is necessary for most applications of SRV ...


... of the Rule is a domain name and should be used to lookup address records for that domain. ...


... Authors' Addresses ...


... copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. ...



Google
Web
RFC-Ref