15 citations found. Retrieving documents...
A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Internet Engineering Task Force, Feb. 2000. RFC 2782.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
The Globe Infrastructure Directory Service - Kuz, van Steen, Sips (2001)   (1 citation)  (Correct)

....domains do represent proximity (e.g. the top level country domains) that part of the hierarchy can be used directly. The DNS servers at the leaves of the hierarchy contain mappings from base region names to corresponding RSD addresses. These mappings are stored in DNS SRV records. An SRV record [5] is a service record and is used to specify the location of named network services. This enhances DNS by identifying the specific services provided at a particular domain name, allowing different services to share a logical domain name but be hosted on different physical servers. A particular ....

A. Gulbrandsen and P. Vixie. A DNS RR for specifying the location of services (DNS SRV), Feb. 2000. RFC 2728.


OTP in Server Farms - Snyder, Bruening, Logan (2002)   (Correct)

....on each node, maintaining local data corresponding to the description above. The local data is kept in ets tables. There is a chicken and egg problem associated with resource discovery: how do new nodes find the resource discovery system A new OTP node starting up uses DNS to look for SRV records[3] for the OTP cluster to which it belongs . Static configuration for the node is thus limited to 1) the server s resolv.conf file, and 2) the name of the cluster. 2.4 Logging The main purpose of logging on the platform is to assist in diagnosing problems. Other systems exist for collection of ....

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). RFC 2782, Internet Engineering Task Force, Feb. 2000, http://www.ietf.org/rfc/rfc2782.txt.


A Waypoint Service Approach to Connect Heterogeneous.. - Ng, Stoica, Zhang (2001)   (1 citation)  (Correct)

....the same service (e.g. no two reusable IP host can simultaneously support port 22 ssh login) thus unacceptable connectivity is provided. Tedious per application manual configurations are also required. A related technique is to take advantage of a new type of DNS resource record proposed in [9], called the SRV resource record, which can specify the port number of a service. When both the service provider and the client support DNS SRV, the client can retrieve both the IP address of the host that is offering the service and the exact port number it should use to use the service. Suppose ....

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV), February 2000. RFC-2782.


Towards Junking the PBX: Deploying IP Telephony - Jiang, Lennox, Schulzrinne.. (2001)   (Correct)

....the host portion and then the user name portion. For example, the domain portion, erlang.cs.columbia.edu is canonicalized to cs.columbia.edu. This is done by matching the domain portion of the request URI against a regular expression. For example, cs.columbia.edu) 128.59. 1[6 9] 2[0 3]) 0 9] maps all host names and IP addresses from 128.59.16.0 to 128.59.23.255 in the CS domain to the canonical server address of cs.columbia.edu. If the canonicalized host name does not match, the server is being used as an outbound proxy server and just routes the request to the SIP server ....

....components in our environment allows putting more components to meet the needs of a largescale user base. For example, multiple conference servers can be installed, with each running only tens of active conferences. For scaling proxy servers, we make use of the DNS SRV capability in SIP. A DNS SRV [3] resource record lists a set of servers, ordered by priority, for each service and domain. For example, example.com sip. udp 0 40 a.example.com 0 40 b.example.com 0 20 c.example.com 1 0 backup.somewhere.com indicates that the servers a, b, c should be used if possible, with ....

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Request for Comments 2782, Internet Engineering Task Force, Feb. 2000.


The Globe Infrastructure Directory Service - Kuz, van Steen, Sips (2001)   (1 citation)  (Correct)

....domains do represent proximity (e.g. the top level country domains) that part of the hierarchy can be used directly. The DNS servers at the leaves of the hierarchy contain mappings from base region names to corresponding RSD addresses. These mappings are stored in DNS SRV records. An SRV record [5] is a service record and is used to specify the location of named network services. This enhances DNS by identifying the speci c services provided at a particular domain name, allowing di erent services to share a logical domain name but be hosted on di erent physical servers. A particular service ....

A. Gulbrandsen and P. Vixie. A DNS RR for specifying the location of services (DNS SRV), Feb. 2000. RFC 2728.


The Globe Infrastructure Directory Service - Kuz, van Steen, Sips (2001)   (1 citation)  (Correct)

....domains do represent proximity (e.g. the top level country domains) that part of the hierarchy can be used directly. The DNS servers at the leaves of the hierarchy contain mappings from base region names to corresponding RSD addresses. These mappings are stored in DNS SRV records. An SRV record [5] is a service record and 8 is used to specify the location of named network services. This enhances DNS by identifying the specific services provided at a particular domain name, allowing different services to share a logical domain name but be hosted on different physical servers. A particular ....

A. Gulbrandsen and P. Vixie. A DNS RR for specifying the location of services (DNS SRV), Feb. 2000. RFC 2728.


A Waypoint Service Approach to Connect Heterogeneous.. - Ng, Stoica, Zhang (2001)   (1 citation)  (Correct)

....host. With this work around, al though more than one reusable IP host is reachable, no two reusable IP hosts can offer the same service (e.g. no two reusable IP host can simultaneously support ssh login) A related technique is to take advantage of a new type of DNS resource record proposed in [11], called the SRV resource record, which can specify the port number of a service. When both the service provider and the client support DNS SRV, the client can retrieve both the IP address of the host that is offering the service and the exact port number it should use to use the service. Suppose ....

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV), February 2000. RFC-2782.


Session Invitation Protocol - Handley, Schooler (1996)   (3 citations)  (Correct)

....checks if the user address is location specific. If so, then that is the address used for the remote user agent. If not, the requesting client looks up the domain part of the user address in the DNS. This provides one or more records giving IP addresses. If a new service (SRV) resource record [5] is returned giving a conference address server, then that is the address to contact next. If no relevant resource record is returned, but an A record is returned, then that is the address to contact next. If neither a resource record or an A record is returned, but an MX record is returned, then ....

A. Gulbrandsen, P. Vixie, "A DNS RR for specifying the location of services" Internet Draft draftgulbrandsen -dns-rr-srvcs-02.txt, Work in Progress, Jan 1996. Mark Handley/Eve Schooler [Page 17]


Personal Mobility for Multimedia Services in the Internet - Schulzrinne, Oertel, Zahl (1995)   (9 citations)  (Correct)

....a host name to one or more Internet addresses, while mail exchange (MX) records [13] as mentioned, map a domain name to the host name of its mail exchange host. Rather than using MX records and thus forcing MUCS servers to be co located with mail exchangers, a new service (SRV) resource record [14] can be used, once it is implemented more widely. However, using the mail host as a MUCS server has practical advantages. Due to the importance of electronic mail, it is likely to be well cared for and reliable. It is also often the only host that resides outside a corporate firewall. If no ....

A. Gulbrandsen and P. Vixie, "A DNS RR for specifying the location of services," Internet Draft, Internet Engineering Task Force, Mar. 1995. Work in progress.


Scalability in an Intentional Naming System - Lilley (2000)   (7 citations)  (Correct)

....named domainname, and then dsr:domainname. Thus, the request for cameras:lcs:mit:edu is routed to dsr:lcs:mit:edu. There are other possible approaches to nd the correct DSR for a virtual space. The alternate solution that we most carefully considered was using the SRV Resource 40 Record in DNS [11] rather than relying on the dsr pre x. The SRV record, which is a recent 1 addition to DNS, is intended for applications such as INS that wish to embed specialized information in DNS without requiring a new Resource Record type. But, due to the newness of the SRV Resource Record, the lack of ....

.... subdomain within lcs, the latter check makes it possible. The well known port currently assumed for a DSR is 5678. Since this functionality is abstracted to a single procedure, the lookup process could be straightforwardly extended to include additional means such as the DNS SRV Resource Record [11], which is intended for putting application speci c data such as this in DNS. After this, it is important for the INR to know which incoming virtual spaces are local and to maintain its internal structures consistently. If an incoming packet is addressed to the cameras:localdomain virtual space, ....

A. Gulbranssen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Internet Engineering Task Force, February 2000. RFC 2782.


An Architecture for Internet Data Transfer - Niraj Tolia Michael (2006)   (Correct)

No context found.

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Internet Engineering Task Force, Feb. 2000. RFC 2782.


In Proceedings of the 3rd Symposium on Networked Systems.. - Niraj Tolia Michael (2006)   (Correct)

No context found.

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Internet Engineering Task Force, Feb. 2000. RFC 2782.


An Architecture for Internet Data Transfer - Michael (2006)   (Correct)

No context found.

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). Internet Engineering Task Force, Feb. 2000. RFC 2782.


Service Discovery Solutions' Federation: A Service Broker Approach - Koponen (2002)   (Correct)

No context found.

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). RFC 2782, IETF, February 2000.


Use Authentication and Remote Execution Across Administrative.. - Kaminsky (2004)   (Correct)

No context found.

A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV). RFC 2782, Network Working Group, February 2000.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC