CA2562639C - Method and apparatus for facilitating long-lived dns queries - Google Patents
Method and apparatus for facilitating long-lived dns queries Download PDFInfo
- Publication number
- CA2562639C CA2562639C CA2562639A CA2562639A CA2562639C CA 2562639 C CA2562639 C CA 2562639C CA 2562639 A CA2562639 A CA 2562639A CA 2562639 A CA2562639 A CA 2562639A CA 2562639 C CA2562639 C CA 2562639C
- Authority
- CA
- Canada
- Prior art keywords
- llq
- client
- name server
- response
- data items
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4541—Directories for service discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Abstract
One embodiment of the present invention provides a system that implements a long-lived query (LLQ) at a name server. During operation, the system receives an LLQ from a client at the name server, wherein the LLQ requests information related to one or more data items stored on the name server. In response to the LLQ, the system informs the client of updates to the one or more data items.
Description
METHOD AND APPARATUS FOR
FACILITATING LONG-LIVED DNS QUERIES
Inventor: Kiren Sekar and Stuart D. Cheshire BACKGROUND
Field of the Invention [0001] The present invention relates to computer networks. More specifically, the present invention relates to a method and an apparatus that facilitates long-lived domain name service (DNS) queries.
Related Art [0002] It is presently common for a client to use a variety of services over a network. For example, a computer running Apple's iPhotoTM may share another computer's iPhotoTM album over a network. One prerequisite for using a service over a network is that, prior to using the service, a client needs to identify a specific instance of that service, for example by obtaining the service's host address and port number. It is therefore important for a client to obtain and maintain accurate and updated information for services in a network.
FACILITATING LONG-LIVED DNS QUERIES
Inventor: Kiren Sekar and Stuart D. Cheshire BACKGROUND
Field of the Invention [0001] The present invention relates to computer networks. More specifically, the present invention relates to a method and an apparatus that facilitates long-lived domain name service (DNS) queries.
Related Art [0002] It is presently common for a client to use a variety of services over a network. For example, a computer running Apple's iPhotoTM may share another computer's iPhotoTM album over a network. One prerequisite for using a service over a network is that, prior to using the service, a client needs to identify a specific instance of that service, for example by obtaining the service's host address and port number. It is therefore important for a client to obtain and maintain accurate and updated information for services in a network.
[0003] Clients typically become aware of a service through some type of service discovery mechanism. Although a service discovery mechanism can be provided through different network protocols, it is typically impractical to use underlying protocols that are not readily available. The existing domain name service (DNS) protocol, because of its ubiquity and extendibility, has proven to be an effective protocol for local-area service discovery, and is an excellent candidate for providing wide-area service discovery beyond the local network. In particular, the Internet Engineering Task Force (IETF) Request for Comments (RFC) 2761 specifies an extension to DNS (EDNSO), which allows a DNS message to deliver resource records (RRs) that carry service meta-information.
[0004] Unfortunately, while the extended DNS allows a name server to provide service information, it does not enable a name server to deliver continuously updated service information to the clients. A service update occurs when a service instance appears or disappears, or when the state of a service changes. Such updates are becoming progressively more frequent, as networks become more dynamic, and services become more versatile and mobile.
[0005] A traditional DNS query is "one-shot" - a name server answers a query only once, and returns only results available at that moment. Thus, when a client queries a name server, it only obtains infonnation for a service instance at a specific point in time. To maintain up-to-date service infonmation, a client has to periodically po11 the name server. This solution has drawbacks, because a low polling rate can leave the client with stale information, and a high polling rate can have an adverse impact on network and server performance.
[0006] Hence, what is needed is a method and an apparatus that facilitates long-lived DNS queries which allow a client to obtain updated service information without polling the name server.
SUMMARY
SUMMARY
[0007] One embodiment of the present invention provides a system that implements a long-lived query (LLQ) at a name server. During operation, the system receives an LLQ from a client at the name server, wherein the LLQ requests infon.nation related to one or more data items stored on the name server. In response to the LLQ, the system informs the client of updates to the one or more data items.
[0008] In a variation of this embodiment, receiving the LLQ involves a two-way handshake process, a three-way handshake process, or a four-way handshake process.
[0009] In a further variation, during a four-way handshake process, the system first receives an initial LLQ setup request from the client, which includes a desired lease life. To avoid potential spoofing, the system then sends a challenge to the client in response to the LLQ setup request, wherein the challenge includes a random LLQ
identifier (LLQ-ID) and a granted lease life. Next, the system receives a challenge response from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID. The system then sends an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
identifier (LLQ-ID) and a granted lease life. Next, the system receives a challenge response from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID. The system then sends an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
[0010] In a variation of this embodiment, to subsequently inform the client of updates to the one or more data items, the system monitors the state of the one or more data items specified by the LLQ. If the state of the one or more data items changes, the system communicates the changes to the client in one or more gratuitous responses.
[0011] In a further variation, a gratuitous response message may include multiple data items corresponding to a single LLQ, unless the size of the gratuitous response message exceeds a packet-size limitation.
[0012] In a variation of this embodiment, the system receives a refresh request for one or more LLQs from a client. In response to the refresh request, the system allows the one or more LLQs to remain active for a period of time.
[0013] In a further variation, the system updates the address or listening port associated with the client upon receiving a refresh request, which indicates a change of the client's address or listening port.
[0014] In a further variation, the system sends an acknowledgement to the client in response to the refresh request.
[0015] In a variation of this embodiment, the system receives a terminate request for one or more LLQs from a client. In response to the terminate request, the system terminates the one or more LLQs specified in the refresh request.
[0016] In a variation of this embodiment, the system receives an LLQ from a client at an intermediate LLQ proxy, which communicates directly with the client, and which communicates with the name server on behalf of one or more clients.
[0017] One embodiment of the present invention provides a system that discovers a service in a network. During operation, the system maintains state information for one or more services in the network on a name server. Upon a request from a host, the system communicates from the name server subsequent updates of the service to the requesting host. The system stops communication of the subsequent updates to the requesting host after a period of time following receipt of the request.
100181 One embodiment of the present invention provides a system that implements a long-lived query (LLQ). During operation, the system sends an LLQ
to a name server from a client, wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time. The system then receives subsequent updates of the one or more data items at the client from the name server.
[0019] In a variation of this embodiment, the system sends a refresh request before the LLQ expires so that the LLQ remains active.
[0020] One embodiment of the present invention provides a system that discovers a service in a network. During operation, the system communicates a query from a client to a name server, wherein the name server maintains state information for one or more services in the network. The system then receives subsequent updates of the service at the client from the name server.
[0021] In a variation of this embodiment, the system communicates a refresh request to the name server before the query expires, so that the query remains active.
[0021a] In a further aspect, the present invention provides a method for operating a name server to implement a long-lived query LLQ thereat, comprising:
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ
requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
4a [0021b] In a further aspect, the present invention provides a method for operating a client to implement a long-lived query, LLQ at a name server, comprising:
sending a setup request for an LLQ to a name server from the client, wherein the LLQ
requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
[0021c] In a still further aspect, the present invention provides a computer-readable storage medium storing computer-readable instnzctions that when executed by a computer cause the computer to perform a method for operating a name server to implement a long-lived query, LLQ, the method comprising: receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests infonnation related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ
and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
[0021d] In a still further aspect, the present invention provides a computer-readable storage medium storing computer readable instructions that when executed by a computer cause the computer to perform a method for operating a client to implement a long-lived query, LLQ, at a name server, the method comprising: sending a setup request for an LLQ to a name server from the client wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ
remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
[0021e] In a further aspect, the present invention provides a name server for implementing a long-lived query, LLQ, configured to: receive a setup request for an LLQ
from a client, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in 4b response to the LLQ, to connnunicate to the client a current state of the one or more data items, andsubsequently inform the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
BRIEF DESCRIPTION OF THE FIGURES
[0022] FIG.1 illustrates a network containing a name server that supports LLQs in accordance with an embodiment of the present invention.
[0023] FIG. 2 illustrates a DNS message format that supports LLQs in accordance with an embodiment of the present invention.
[0024] FIG. 3 presents a time-space diagram and a flowchart illustrating a four-way handshake process for setting up an LLQ in accordance with an embodiment of the present invention.
[0025] FIG. 4 presents a flowchart illustrating the process of sending network service updates to a client in accordance with an embodiment of the present invention.
(0026] FIG. 5A presents a flowchart illustrating the process of sending a refresh request from a client to refresh the lease lives of one or more LLQs in accordance with an embodiment of the present invention.
[0027] FIG. 5B presents a flowchart illustrating the process of sending a 5 refresh request from a client to update its address or listening port in accordance with an embodiment of the present invention.
[0028] FIG. 6 illustrates a network containing a DNS cache acting as an LLQ
proxy which handles LLQs in accordance with an embodiment of the present invention.
DETAILED DESCRIPTION
[0029] The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
[0030] The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.
Networks Supaorting Long-lived Oueries [00311 FIG. I illustrates a network containing a name server that supports LLQs in accordance with an embodiment of the present invention. As shown in FIG:
1, network 100 contains a name server 120, computer systems 102 and 104, printers 106 and 108, and a scanner 110. Note that network 100 may be a local-area network or a wide-area network, such as the Internet. In this example, both printers 106 and 108 provide printing services over network 100.
[0032] When client computer 104 needs a printing service, it sets up an LLQ
at name server 120. Name server 120 maintains updated state information for both printers 106 and 108. In this example, printer 106's printing service is available and printer 108's printing service is not available when computer 102's LLQ is set up.
Hence, name server 120 sends computer 104 the current information about the printing service offered by printer 106.
[0033] During the lease life granted by name server 120 to computer 104's LLQ regarding this particular service (printing service by printer 106), name server 120 automatically updates computer 104 with the latest changes of this service through gratuitous responses. For example, when printer 106 is offline or out of paper, name server 120 sends a gratuitous response which notifies computer 102 of this change of the service. In addition, if printer 108's service becomes available, name server 120 also notifies computer 102 that additional service by printer 108 is now available.
[0034] FIG. 2 illustrates a DNS message format that supports LLQs in accordance with an embodiment of the present invention. A typical DNS message includes a header 210, a question field 212, an answer field 214, an authority field 216, and an additional information field 218. Question field 212 is used to send a query from a client to the name server. Answer field 214, authority field 216, and additional information field 218 include "resource records" (RRs) that share a common RR format. Note that each of these fields may be include one or more RRs.
[0035] Referring to FIG. 2, a resource record includes a NAME field 220, a TYPE field 222, a CLASS field 224, a time-to-live (TTL) field 226, a resource data length (RDLEN) field 228, and resource data (RDATA) field 230. One approach to implement LLQ is to use option (OPT) pseudo-RR as specified in IETF RFC 2671.
Encoding an LLQ request in an OPT RR allows for implementation of LLQ with minimal modification to a name server's front-end, and causes servers that do not implement LLQ to return an appropriate error automatically.
[0036] Accordingly, NAME field 220 is the name to which the following resource data corresponds, which in this case is the root domain of the service. TYPE
field 222 has the value of OPT to indicate that this is an OPT RR. CLASS field indicates, as per RFC 2671, the sender's user datagram protocol (UDP) payload size.
However, clients and servers are not required to determine their reassembly buffer size or path maximum transmission unit (MTU) to support an LLQ. Thus, the sender of an LLQ request or response may set CLASS field 224 to zero. The recipient ignores the CLASS field if it is set to zero. TTL field 226 indicates the number of seconds that the RR can be cached by the client. Here, TTL field 226 can be set to zero to indicate that the RR does not contain resource record data to be cached.
RDLEN field 228 specifies the length of the RDATA field 230.
[0037] RDATA field 230 contains the following fields to carry LLQ
information: OPTION-CODE field 232 is used to indicate that the following fields carry LLQ information. OPTION-LENGTH field 234 indicates the length of following fields. VERSION field 236 indicates the version of LLQ protocol implemented. LLQ-OPCODE field 238 identifies an LLQ operation (e.g., setup or refresh). ERROR field 240 indicates LLQ errors. LLQ-ID field 242 contains an identifier for a specific LLQ. LEASE LIFE field 244 indicates a requested or granted life of LLQ, in seconds. This data format, comprising of (OPTION-CODE, OPTION-LEN, LLQ-Metadata) tuples, may be repeated an arbitrary number of times in the RDATA field, with a properly set RDLEN field.
LLO Setup [0038] FIG. 3 presents a time-space diagram and a flowchart illustrating a four-way handshake process for setting up an LLQ in accordance with an embodiment of the present invention. Typically, a client initiates an LLQ, and completes the LLQ
setup via a four-way handshake process with the name server. This process provides a reliable setup and reduces the risk of denial of service attacks.
100391 As shown in FIG. 3, the system in a name server starts by receiving an LLQ setup request from a client (step 310). An LLQ setup request is formatted like a standard DNS query, with an OPT RR containing LLQ metadata in its additional information field. LLQ setup requests are identified by the LLQ-SETUP OPCODE
and a zero-valued LLQ-ID. An LLQ setup request may contain multiple questions to set up multiple LLQs, each of which is contained in an LLQ metadata section.
An LLQ setup request may also request a lease life, during which the LLQ remain valid at the name server.
100401 In response to the LLQ setup request, the system sends an LLQ
challenge back to the client (step 320). An LLQ challenge is a DNS response, with its DNS message ID matching that of the request, and with all questions in the request present in the question field. The challenge contains an OPT-RR with an LLQ
metadata section for each LLQ request, indicating the success or failure of each request. The challenge also contains an LLQ-ID and a granted lease life for each successfully requested LLQ. An LLQ-ID can be a unique random number generated by the name server. The name server discards an LLQ when its lease life expires, unless the client refreshes the LLQ in time.
[0041] Next, the system receives an LLQ challenge response sent by the client in response to the challenge (step 330). This LLQ challenge response can be a DNS
request with a single OPT-RR in the additional information field, with the OPT-RR
RDATA identical to the OPT-RR RDATA contained in the LLQ challenge (i.e., echoing, for each set of fields, the LLQ-ID and the granted lease life).
[00421 The system then sends out an acknowledgement acknowledging the LLQ challenge response (step 340). This acknowledgement contains all available answers to the question(s) contained in the original LLQ setup request, along with all additional RRs appropriate for those answers in the additional information field. It also contains an OPT-RR that repeats the assigned LLQ-ID and lease life.
[00431 Note that the four-way handshake process described above is just one embodiment of the present invention. It mainly targets to prevent spoofing which could lead to denial-of-service attacks. Alternatively, a two-way, three-way, or n-way handshake process may be used to set up an LLQ. In general, the actual mechanism of how an LLQ is set up does not affect the basic operation of an LLQ.
[0044] In a two-way handshake process, for example, a client first sends an LLQ setup request to the name server. Upon receiving the LLQ setup request, the name server responds with all available answers to the question(s) contained in the LLQ setup request. In the same response, the name server also assigns an LLQ-ID
and a lease life for the LLQ.
[0045] In a three-way handshake process, for example, a client first sends an LLQ setup request to the name server. Upon receiving the LLQ setup request, the name server responds with all available answers to the question(s) contained in the LLQ setup request. In the same response, the name server also assigns an LLQ-ID
and a lease life for the LLQ. After receiving the response, the client sends an acknowledgement back to the server to confirm successful receipt of the response.
Gratuitous Responses [0046] FIG. 4 presents a flowchart illustrating the process of sending network service updates to a client in accordance with an embodiment of the present invention.
When the state of services changes in a name server's zone, the server checks whether the updated resource records answer any LLQs whose lease lives have not expired. If so, the name server sends the updated RRs in the form of a gratuitous DNS
response to the LLQ requestor client.
[0047] The name server may aggregate gratuitous responses for a single LLQ, such that a single message contains multiple RRs. However, aggregation is not desirable if it would cause a message that would otherwise fit in a single packet to be truncated, or would introduce undue latency.
[0048] After sending a gratuitous response, the name server waits for an acknowledgement from the client. If the client does not respond, the server can re-send the response a number of times, waiting for a period between each re-transmission, terminating the LLQ if no acknowledgement is received.
[0049] The flow chart in FIG. 4 illustrates this event notification process.
The system in a name server starts by monitoring the state of services and determines whether there is any RR update (step 410). If not, the system continues monitoring. If so, the system determines whether the updated RR answers any unexpired LLQs (step 420). If not, the system continues monitoring the services. If so, the system sends a gratuitous response to the client with the updated RR (step 430). The system then 5 determines whether it has received any acknowledgement from the client within a period of time (step 440). An acknowledgement indicates that the client has successfully received the gratuitous response, and the system continues its monitoring of the services. If not, the system re-sends the gratuitous response to the client (step 450), and waits for acknowledgement (step 460). If the system eventually receives an 10 acknowledgement, the gratuitous response is successful and the system goes back to the monitoring state. If not, the system terminates the LLQ (step 470). Note that the system may re-send the gratuitous response for a number of times, and may wait for progressively longer periods between the re-sends.
LLORefreshine [0050] FIG. 5A presents a flowchart illustrating the process of sending a refresh request from a client to refresh the lease lives of one or more LLQs in accordance with an embodiment of the present invention. If a client desires to maintain an LLQ beyond the duration specified in the assigned lease life, the client may send a refresh request. A refresh request is similar to an LLQ setup response, with the LLQ-OPCODE set to LLQ-REFRESH. Unlike an LLQ setup response, a refresh request returns no answers. In addition, a client may aggregate a number of LLQs in one refresh request message to reduce network traffic.
[0051] As illustrated in FIG. 5A, the client starts by determining whether the lease life of an LLQ is about to expire (step 510). If so, it sends a refresh request to the name server (step 520). It then waits for an acknowledgement from the name server (step 530). If it receives an acknowledgement, the refresh process is successful and hence complete. If it does not receive an acknowledgement after a certain period of time, it may re-transmit the refresh request to the name server (step 520).
If the client determines that the name server is down because no acknowledgement is received, the client may re-establish the LLQ.
[0052] FIG. 5B presents a flowchart illustrating the process of sending a refresh request from a client to update its address or listening port in accordance with an embodiment of the present invention. If a client's address or listening port changes, the client may send an LLQ refresh request to the name server from the new address or port. Upon receiving the refresh request, the name server updates the address or port number associated with the client, and renews the lease life of the LLQ
belonging to the client.
[0053] As illustrated in FIG. 5B, the client starts by determining whether there is a change in its address or listening port (step 540). If not, it continues monitoring its address and listening port. If so, the client sends a refresh request to the name server (step 550). It then waits for an acknowledgement from the name server (step 560). If it receives an acknowledgement, the refresh process is successful and hence complete. If it does not receive an acknowledgement after a certain period of time, it may re-transmit the refresh request to the name server (step 550). If the client determines that the name server is down because no acknowledgement is received, the client may re-establish the LLQ.
DNS CachinQ and LLO Proxy [00541 FIG. 6 illustrates a network containing a DNS cache acting as an LLQ
proxy which handles LLQs in accordance with an embodiment of the present invention. Computer 102 may send LLQ setup request and control messages to an intermediate DNS cache 610. If DNS cache 610 serves as an intermediate LLQ
proxy, it can communicate directly with computer 102 and with name server 660 on behalf of one or more clients.
[0055) If DNS cache 610 does not implement LLQ proxying, computer 102 needs to determine the address and port number of the name server to which it can send LLQ messages. To identify the name server that handles LLQ messages, computer 102 first sends a standard DNS query for the name of the LLQ, with type SOA (start of authority). If the SOA record exists, the name server answers with that SOA record in the answer field of its response message. If not, the name server answers with an SOA record for that name's zone in the authority field of its response message. For example, a query for _ftp._tcp.apple.com. may return an SOA
record named apple.com. in the authority field of the response if there is no SOA
record named _ftp._tcp.apple.com. Computer 102 then constructs and sends an SRV
(service location) query for the name _dns-llq._udp.<soa-name>, which in this example is _dsn-llq._udp.apple.com. In response, a name server implementing LLQ answers with an SRV record for this name. The SRV RDATA indicates the port to which LLQ requests are to be sent.
[0056] The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the.present invention to the forms disclosed.
Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.
100181 One embodiment of the present invention provides a system that implements a long-lived query (LLQ). During operation, the system sends an LLQ
to a name server from a client, wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time. The system then receives subsequent updates of the one or more data items at the client from the name server.
[0019] In a variation of this embodiment, the system sends a refresh request before the LLQ expires so that the LLQ remains active.
[0020] One embodiment of the present invention provides a system that discovers a service in a network. During operation, the system communicates a query from a client to a name server, wherein the name server maintains state information for one or more services in the network. The system then receives subsequent updates of the service at the client from the name server.
[0021] In a variation of this embodiment, the system communicates a refresh request to the name server before the query expires, so that the query remains active.
[0021a] In a further aspect, the present invention provides a method for operating a name server to implement a long-lived query LLQ thereat, comprising:
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ
requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
4a [0021b] In a further aspect, the present invention provides a method for operating a client to implement a long-lived query, LLQ at a name server, comprising:
sending a setup request for an LLQ to a name server from the client, wherein the LLQ
requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
[0021c] In a still further aspect, the present invention provides a computer-readable storage medium storing computer-readable instnzctions that when executed by a computer cause the computer to perform a method for operating a name server to implement a long-lived query, LLQ, the method comprising: receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests infonnation related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ
and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
[0021d] In a still further aspect, the present invention provides a computer-readable storage medium storing computer readable instructions that when executed by a computer cause the computer to perform a method for operating a client to implement a long-lived query, LLQ, at a name server, the method comprising: sending a setup request for an LLQ to a name server from the client wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ
remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
[0021e] In a further aspect, the present invention provides a name server for implementing a long-lived query, LLQ, configured to: receive a setup request for an LLQ
from a client, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in 4b response to the LLQ, to connnunicate to the client a current state of the one or more data items, andsubsequently inform the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
BRIEF DESCRIPTION OF THE FIGURES
[0022] FIG.1 illustrates a network containing a name server that supports LLQs in accordance with an embodiment of the present invention.
[0023] FIG. 2 illustrates a DNS message format that supports LLQs in accordance with an embodiment of the present invention.
[0024] FIG. 3 presents a time-space diagram and a flowchart illustrating a four-way handshake process for setting up an LLQ in accordance with an embodiment of the present invention.
[0025] FIG. 4 presents a flowchart illustrating the process of sending network service updates to a client in accordance with an embodiment of the present invention.
(0026] FIG. 5A presents a flowchart illustrating the process of sending a refresh request from a client to refresh the lease lives of one or more LLQs in accordance with an embodiment of the present invention.
[0027] FIG. 5B presents a flowchart illustrating the process of sending a 5 refresh request from a client to update its address or listening port in accordance with an embodiment of the present invention.
[0028] FIG. 6 illustrates a network containing a DNS cache acting as an LLQ
proxy which handles LLQs in accordance with an embodiment of the present invention.
DETAILED DESCRIPTION
[0029] The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
[0030] The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.
Networks Supaorting Long-lived Oueries [00311 FIG. I illustrates a network containing a name server that supports LLQs in accordance with an embodiment of the present invention. As shown in FIG:
1, network 100 contains a name server 120, computer systems 102 and 104, printers 106 and 108, and a scanner 110. Note that network 100 may be a local-area network or a wide-area network, such as the Internet. In this example, both printers 106 and 108 provide printing services over network 100.
[0032] When client computer 104 needs a printing service, it sets up an LLQ
at name server 120. Name server 120 maintains updated state information for both printers 106 and 108. In this example, printer 106's printing service is available and printer 108's printing service is not available when computer 102's LLQ is set up.
Hence, name server 120 sends computer 104 the current information about the printing service offered by printer 106.
[0033] During the lease life granted by name server 120 to computer 104's LLQ regarding this particular service (printing service by printer 106), name server 120 automatically updates computer 104 with the latest changes of this service through gratuitous responses. For example, when printer 106 is offline or out of paper, name server 120 sends a gratuitous response which notifies computer 102 of this change of the service. In addition, if printer 108's service becomes available, name server 120 also notifies computer 102 that additional service by printer 108 is now available.
[0034] FIG. 2 illustrates a DNS message format that supports LLQs in accordance with an embodiment of the present invention. A typical DNS message includes a header 210, a question field 212, an answer field 214, an authority field 216, and an additional information field 218. Question field 212 is used to send a query from a client to the name server. Answer field 214, authority field 216, and additional information field 218 include "resource records" (RRs) that share a common RR format. Note that each of these fields may be include one or more RRs.
[0035] Referring to FIG. 2, a resource record includes a NAME field 220, a TYPE field 222, a CLASS field 224, a time-to-live (TTL) field 226, a resource data length (RDLEN) field 228, and resource data (RDATA) field 230. One approach to implement LLQ is to use option (OPT) pseudo-RR as specified in IETF RFC 2671.
Encoding an LLQ request in an OPT RR allows for implementation of LLQ with minimal modification to a name server's front-end, and causes servers that do not implement LLQ to return an appropriate error automatically.
[0036] Accordingly, NAME field 220 is the name to which the following resource data corresponds, which in this case is the root domain of the service. TYPE
field 222 has the value of OPT to indicate that this is an OPT RR. CLASS field indicates, as per RFC 2671, the sender's user datagram protocol (UDP) payload size.
However, clients and servers are not required to determine their reassembly buffer size or path maximum transmission unit (MTU) to support an LLQ. Thus, the sender of an LLQ request or response may set CLASS field 224 to zero. The recipient ignores the CLASS field if it is set to zero. TTL field 226 indicates the number of seconds that the RR can be cached by the client. Here, TTL field 226 can be set to zero to indicate that the RR does not contain resource record data to be cached.
RDLEN field 228 specifies the length of the RDATA field 230.
[0037] RDATA field 230 contains the following fields to carry LLQ
information: OPTION-CODE field 232 is used to indicate that the following fields carry LLQ information. OPTION-LENGTH field 234 indicates the length of following fields. VERSION field 236 indicates the version of LLQ protocol implemented. LLQ-OPCODE field 238 identifies an LLQ operation (e.g., setup or refresh). ERROR field 240 indicates LLQ errors. LLQ-ID field 242 contains an identifier for a specific LLQ. LEASE LIFE field 244 indicates a requested or granted life of LLQ, in seconds. This data format, comprising of (OPTION-CODE, OPTION-LEN, LLQ-Metadata) tuples, may be repeated an arbitrary number of times in the RDATA field, with a properly set RDLEN field.
LLO Setup [0038] FIG. 3 presents a time-space diagram and a flowchart illustrating a four-way handshake process for setting up an LLQ in accordance with an embodiment of the present invention. Typically, a client initiates an LLQ, and completes the LLQ
setup via a four-way handshake process with the name server. This process provides a reliable setup and reduces the risk of denial of service attacks.
100391 As shown in FIG. 3, the system in a name server starts by receiving an LLQ setup request from a client (step 310). An LLQ setup request is formatted like a standard DNS query, with an OPT RR containing LLQ metadata in its additional information field. LLQ setup requests are identified by the LLQ-SETUP OPCODE
and a zero-valued LLQ-ID. An LLQ setup request may contain multiple questions to set up multiple LLQs, each of which is contained in an LLQ metadata section.
An LLQ setup request may also request a lease life, during which the LLQ remain valid at the name server.
100401 In response to the LLQ setup request, the system sends an LLQ
challenge back to the client (step 320). An LLQ challenge is a DNS response, with its DNS message ID matching that of the request, and with all questions in the request present in the question field. The challenge contains an OPT-RR with an LLQ
metadata section for each LLQ request, indicating the success or failure of each request. The challenge also contains an LLQ-ID and a granted lease life for each successfully requested LLQ. An LLQ-ID can be a unique random number generated by the name server. The name server discards an LLQ when its lease life expires, unless the client refreshes the LLQ in time.
[0041] Next, the system receives an LLQ challenge response sent by the client in response to the challenge (step 330). This LLQ challenge response can be a DNS
request with a single OPT-RR in the additional information field, with the OPT-RR
RDATA identical to the OPT-RR RDATA contained in the LLQ challenge (i.e., echoing, for each set of fields, the LLQ-ID and the granted lease life).
[00421 The system then sends out an acknowledgement acknowledging the LLQ challenge response (step 340). This acknowledgement contains all available answers to the question(s) contained in the original LLQ setup request, along with all additional RRs appropriate for those answers in the additional information field. It also contains an OPT-RR that repeats the assigned LLQ-ID and lease life.
[00431 Note that the four-way handshake process described above is just one embodiment of the present invention. It mainly targets to prevent spoofing which could lead to denial-of-service attacks. Alternatively, a two-way, three-way, or n-way handshake process may be used to set up an LLQ. In general, the actual mechanism of how an LLQ is set up does not affect the basic operation of an LLQ.
[0044] In a two-way handshake process, for example, a client first sends an LLQ setup request to the name server. Upon receiving the LLQ setup request, the name server responds with all available answers to the question(s) contained in the LLQ setup request. In the same response, the name server also assigns an LLQ-ID
and a lease life for the LLQ.
[0045] In a three-way handshake process, for example, a client first sends an LLQ setup request to the name server. Upon receiving the LLQ setup request, the name server responds with all available answers to the question(s) contained in the LLQ setup request. In the same response, the name server also assigns an LLQ-ID
and a lease life for the LLQ. After receiving the response, the client sends an acknowledgement back to the server to confirm successful receipt of the response.
Gratuitous Responses [0046] FIG. 4 presents a flowchart illustrating the process of sending network service updates to a client in accordance with an embodiment of the present invention.
When the state of services changes in a name server's zone, the server checks whether the updated resource records answer any LLQs whose lease lives have not expired. If so, the name server sends the updated RRs in the form of a gratuitous DNS
response to the LLQ requestor client.
[0047] The name server may aggregate gratuitous responses for a single LLQ, such that a single message contains multiple RRs. However, aggregation is not desirable if it would cause a message that would otherwise fit in a single packet to be truncated, or would introduce undue latency.
[0048] After sending a gratuitous response, the name server waits for an acknowledgement from the client. If the client does not respond, the server can re-send the response a number of times, waiting for a period between each re-transmission, terminating the LLQ if no acknowledgement is received.
[0049] The flow chart in FIG. 4 illustrates this event notification process.
The system in a name server starts by monitoring the state of services and determines whether there is any RR update (step 410). If not, the system continues monitoring. If so, the system determines whether the updated RR answers any unexpired LLQs (step 420). If not, the system continues monitoring the services. If so, the system sends a gratuitous response to the client with the updated RR (step 430). The system then 5 determines whether it has received any acknowledgement from the client within a period of time (step 440). An acknowledgement indicates that the client has successfully received the gratuitous response, and the system continues its monitoring of the services. If not, the system re-sends the gratuitous response to the client (step 450), and waits for acknowledgement (step 460). If the system eventually receives an 10 acknowledgement, the gratuitous response is successful and the system goes back to the monitoring state. If not, the system terminates the LLQ (step 470). Note that the system may re-send the gratuitous response for a number of times, and may wait for progressively longer periods between the re-sends.
LLORefreshine [0050] FIG. 5A presents a flowchart illustrating the process of sending a refresh request from a client to refresh the lease lives of one or more LLQs in accordance with an embodiment of the present invention. If a client desires to maintain an LLQ beyond the duration specified in the assigned lease life, the client may send a refresh request. A refresh request is similar to an LLQ setup response, with the LLQ-OPCODE set to LLQ-REFRESH. Unlike an LLQ setup response, a refresh request returns no answers. In addition, a client may aggregate a number of LLQs in one refresh request message to reduce network traffic.
[0051] As illustrated in FIG. 5A, the client starts by determining whether the lease life of an LLQ is about to expire (step 510). If so, it sends a refresh request to the name server (step 520). It then waits for an acknowledgement from the name server (step 530). If it receives an acknowledgement, the refresh process is successful and hence complete. If it does not receive an acknowledgement after a certain period of time, it may re-transmit the refresh request to the name server (step 520).
If the client determines that the name server is down because no acknowledgement is received, the client may re-establish the LLQ.
[0052] FIG. 5B presents a flowchart illustrating the process of sending a refresh request from a client to update its address or listening port in accordance with an embodiment of the present invention. If a client's address or listening port changes, the client may send an LLQ refresh request to the name server from the new address or port. Upon receiving the refresh request, the name server updates the address or port number associated with the client, and renews the lease life of the LLQ
belonging to the client.
[0053] As illustrated in FIG. 5B, the client starts by determining whether there is a change in its address or listening port (step 540). If not, it continues monitoring its address and listening port. If so, the client sends a refresh request to the name server (step 550). It then waits for an acknowledgement from the name server (step 560). If it receives an acknowledgement, the refresh process is successful and hence complete. If it does not receive an acknowledgement after a certain period of time, it may re-transmit the refresh request to the name server (step 550). If the client determines that the name server is down because no acknowledgement is received, the client may re-establish the LLQ.
DNS CachinQ and LLO Proxy [00541 FIG. 6 illustrates a network containing a DNS cache acting as an LLQ
proxy which handles LLQs in accordance with an embodiment of the present invention. Computer 102 may send LLQ setup request and control messages to an intermediate DNS cache 610. If DNS cache 610 serves as an intermediate LLQ
proxy, it can communicate directly with computer 102 and with name server 660 on behalf of one or more clients.
[0055) If DNS cache 610 does not implement LLQ proxying, computer 102 needs to determine the address and port number of the name server to which it can send LLQ messages. To identify the name server that handles LLQ messages, computer 102 first sends a standard DNS query for the name of the LLQ, with type SOA (start of authority). If the SOA record exists, the name server answers with that SOA record in the answer field of its response message. If not, the name server answers with an SOA record for that name's zone in the authority field of its response message. For example, a query for _ftp._tcp.apple.com. may return an SOA
record named apple.com. in the authority field of the response if there is no SOA
record named _ftp._tcp.apple.com. Computer 102 then constructs and sends an SRV
(service location) query for the name _dns-llq._udp.<soa-name>, which in this example is _dsn-llq._udp.apple.com. In response, a name server implementing LLQ answers with an SRV record for this name. The SRV RDATA indicates the port to which LLQ requests are to be sent.
[0056] The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the.present invention to the forms disclosed.
Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.
Claims (32)
1. A method for operating a name server to implement a long-lived query LLQ
thereat, comprising:
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ
and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
thereat, comprising:
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ
and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
2. The method of claim 1, wherein receiving the LLQ involves a two-way handshake process, a three-way handshake process, or a four-way handshake process.
3. The method of claim 2, wherein the four-way handshake process involves:
receiving an initial LLQ setup request from the client, which includes a desired lease life; sending a challenge to the client in response to the LLQ setup request, wherein the challenge includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receiving a challenge reply from the client in response to the challenge, wherein the challenge reply echoes the LLQ-ID; and sending an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
receiving an initial LLQ setup request from the client, which includes a desired lease life; sending a challenge to the client in response to the LLQ setup request, wherein the challenge includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receiving a challenge reply from the client in response to the challenge, wherein the challenge reply echoes the LLQ-ID; and sending an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
4. The method of claim 1, wherein a gratuitous response message may include multiple data items corresponding to a single LLQ, unless the size of the gratuitous response message exceeds a packet- size limitation.
5. The method of claim 1, further comprising:
receiving a refresh request for one or more LLQs from a client; and allowing the one or more LLQs to remain active for a period of time in response to the refresh request.
receiving a refresh request for one or more LLQs from a client; and allowing the one or more LLQs to remain active for a period of time in response to the refresh request.
6. The method of claim 5, further comprising updating the address or listening port associated with the client upon receiving a refresh request, which indicates a change of the client's address or listening port.
7. The method of claim 5, further comprising sending an acknowledgement to the client in response to the refresh request.
8. The method of claim 1, further comprising:
receiving a terminate request for one or more LLQs from a client; and terminating the one or more LLQs specified in the terminate request.
receiving a terminate request for one or more LLQs from a client; and terminating the one or more LLQs specified in the terminate request.
9. The method of claim 1, further comprising receiving an LLQ from a client at an intermediate LLQ proxy, which communicates directly with the client, and which communicates with the name server on behalf of one or more clients.
10. The method of claim 1, further comprising:
maintaining state information for one or more services in the network on the name server;
upon a request from a host, communicating from the name server subsequent updates of the service to the requesting host; and stopping communication of the subsequent updates to the requesting host after a period of time following receipt of the request.
maintaining state information for one or more services in the network on the name server;
upon a request from a host, communicating from the name server subsequent updates of the service to the requesting host; and stopping communication of the subsequent updates to the requesting host after a period of time following receipt of the request.
11. A method for operating a client to implement a long-lived query, LLQ
at a name server, comprising:
sending a setup request for an LLQ to a name server from the client, wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
at a name server, comprising:
sending a setup request for an LLQ to a name server from the client, wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
12. The method of claim 11, further comprising sending a refresh request before the LLQ expires so that the LLQ remains active.
13. A computer-readable storage medium storing computer readable instructions that when executed by a computer cause the computer to perform a method for operating a name server to implement a long-lived query, LLQ, the method comprising:
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
receiving a setup request for an LLQ from a client at the name server, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, informing the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
14. The computer-readable storage medium of claim 13, wherein the method step of receiving the LLQ involves a two-way handshake process, a three-way handshake process, or a four-way handshake process.
15. The computer-readable storage medium of claim 14, wherein the four-way handshake process involves:
receiving an initial LLQ setup request from the client, which includes a desired lease life; sending a challenge to the client in response to the LLQ setup request, wherein the challenge includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receiving a challenge reply from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID; and sending an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
receiving an initial LLQ setup request from the client, which includes a desired lease life; sending a challenge to the client in response to the LLQ setup request, wherein the challenge includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receiving a challenge reply from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID; and sending an acknowledgement to the client in response to the challenge response, along with the information related to the one or more data items as requested by the LLQ.
16. The computer-readable storage medium of claim 13, wherein a gratuitous response message may include multiple data items corresponding to a single LLQ, unless the size of the gratuitous response message exceeds a packet-size limitation.
17 17. The computer-readable storage medium of claim 13, wherein the method further comprises:
receiving a refresh request for one or more LLQs from a client; and allowing the one or more LLQs to remain active for a period of time in response to the refresh request.
receiving a refresh request for one or more LLQs from a client; and allowing the one or more LLQs to remain active for a period of time in response to the refresh request.
18. The computer-readable storage medium of claim 17, wherein the method further comprises updating the address or listening port associated with the client upon receiving a refresh request, which indicates a change of the client's address or listening port.
19. The computer-readable storage medium of claim 17, wherein the method further comprises sending an acknowledgement to the client in response to the refresh request.
20. The computer-readable storage medium of claim 17, the method further comprises terminating the one or more LLQs specified in the refresh request if the refresh request specifies a zero-valued lease life.
21. The computer-readable storage medium of claim 13, wherein the method further comprises:
receiving a terminate request for one or more LLQs from a client; and terminating the one or more LLQs specified in the terminate request.
receiving a terminate request for one or more LLQs from a client; and terminating the one or more LLQs specified in the terminate request.
22. The computer-readable storage medium of claim 13, wherein the method further comprises:
maintaining state information for one or more services in the network on the name server upon a request from a host, communicating from the name server subsequent updates of the service to the requesting host; and stopping communication of the subsequent updates to the requesting host after a period of time following receipt of the request.
maintaining state information for one or more services in the network on the name server upon a request from a host, communicating from the name server subsequent updates of the service to the requesting host; and stopping communication of the subsequent updates to the requesting host after a period of time following receipt of the request.
23. A computer-readable storage medium storing computer readable instructions that when executed by a computer cause the computer to perform a method for operating a client to implement a long-lived query, LLQ, at a name server, the method comprising:
sending a setup request for an LLQ to a name server from the client wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
sending a setup request for an LLQ to a name server from the client wherein the LLQ requests information related to one or more data items stored on the name server, and wherein the LLQ remains active for a period of time; and receiving subsequent updates of the one or more data items specified by the LLQ at the client from the name server.
24. The computer-readable storage medium of claim 23, the method further comprising sending a refresh request before the LLQ expires so that the LLQ
remains active.
remains active.
25. A name server for implementing a long-lived query, LLQ, configured to:
receive a setup request for an LLQ from a client, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, to communicate to the client a current state of the one or more data items, and subsequently inform the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
receive a setup request for an LLQ from a client, wherein the LLQ requests information related to one or more data items stored on the name server and wherein the LLQ remains active for a period of time; and in response to the LLQ, to communicate to the client a current state of the one or more data items, and subsequently inform the client of updates to the one or more data items by monitoring the state of the one or more data items specified by the LLQ and, if the state of the one or more data items changes, communicating the changes to the client in one or more gratuitous responses.
26. The name server of claim 25, wherein while receiving the LLQ, the name server is configured to:
receive an initial LLQ setup request from the client, which includes a desired lease life; send a challenge to the client in response to the LLQ setup request, wherein the acknowledgement includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receive a challenge response from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID; and to send an acknowledgement to the client in response to the challenge response, along with answers to the question.
receive an initial LLQ setup request from the client, which includes a desired lease life; send a challenge to the client in response to the LLQ setup request, wherein the acknowledgement includes a random LLQ identifier, LLQ-ID, and a granted lease life;
receive a challenge response from the client in response to the challenge, wherein the challenge response echoes the LLQ-ID; and to send an acknowledgement to the client in response to the challenge response, along with answers to the question.
27. The name server of claim 25, wherein a gratuitous response message may include multiple data items corresponding to a single LLQ, unless the size of the gratuitous response message exceeds a packet-size limitation.
28. The name server of claim 25, wherein the name server is further configured to:
receive a refresh request for one or more LLQs from a client; and if the refresh request specifies a non-zero lease life, to renew the lease lives of the one or more LLQs in response to the refresh request.
receive a refresh request for one or more LLQs from a client; and if the refresh request specifies a non-zero lease life, to renew the lease lives of the one or more LLQs in response to the refresh request.
29. The name server of claim 28, wherein the name server is further configured to update the address or listening port associated with the client upon receiving a refresh request, which indicates a change of the client's address or listening port.
30. The name server of claim 28, the name server is further configured to terminate the one or more LLQs specified in the refresh request if the refresh request specifies a zero-valued lease life.
31. The name server of claim 28, wherein the name server is further configured to send an acknowledgement to the client in response to the refresh request.
32. A system including the name server of claim 25 and an intermediate long-lived query proxy, LLQ proxy, said proxy configured to:
receive a setup request for an LLQ from a client;
communicate directly with the client; and to communicate with the name server on behalf of one or more clients.
receive a setup request for an LLQ from a client;
communicate directly with the client; and to communicate with the name server on behalf of one or more clients.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/877,518 | 2004-06-25 | ||
US10/877,518 US8161184B2 (en) | 2004-06-25 | 2004-06-25 | Method and apparatus for facilitating long-lived DNS queries |
PCT/US2005/004305 WO2006011909A1 (en) | 2004-06-25 | 2005-02-10 | Method and apparatus for facilitating long-lived dns queries |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2562639A1 CA2562639A1 (en) | 2006-02-02 |
CA2562639C true CA2562639C (en) | 2010-05-04 |
Family
ID=34960597
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2562639A Active CA2562639C (en) | 2004-06-25 | 2005-02-10 | Method and apparatus for facilitating long-lived dns queries |
Country Status (9)
Country | Link |
---|---|
US (1) | US8161184B2 (en) |
EP (1) | EP1759517B1 (en) |
JP (1) | JP4594380B2 (en) |
AT (1) | ATE429771T1 (en) |
AU (1) | AU2005267597B2 (en) |
CA (1) | CA2562639C (en) |
DE (1) | DE602005014106D1 (en) |
HK (1) | HK1102948A1 (en) |
WO (1) | WO2006011909A1 (en) |
Families Citing this family (85)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7113980B2 (en) * | 2001-09-06 | 2006-09-26 | Bea Systems, Inc. | Exactly once JMS communication |
US20060218303A1 (en) * | 2005-03-25 | 2006-09-28 | The Go Daddy Group, Inc. | Creation of a database storing domain names and business operational areas |
US20060218151A1 (en) * | 2005-03-25 | 2006-09-28 | The Go Daddy Group, Inc. | Use of a database storing domain names and business operational areas |
US7870265B2 (en) * | 2005-06-30 | 2011-01-11 | Oracle International Corporation | System and method for managing communications sessions in a network |
CN101346634B (en) * | 2005-11-04 | 2012-10-24 | 甲骨文国际公司 | System and method for a gatekeeper in a communications network |
US8171466B2 (en) | 2006-05-16 | 2012-05-01 | Oracle International Corporation | Hitless application upgrade for SIP server architecture |
US8112525B2 (en) * | 2006-05-16 | 2012-02-07 | Oracle International Corporation | Engine near cache for reducing latency in a telecommunications environment |
US8001250B2 (en) * | 2006-05-16 | 2011-08-16 | Oracle International Corporation | SIP and HTTP convergence in network computing environments |
US8219697B2 (en) | 2006-05-17 | 2012-07-10 | Oracle International Corporation | Diameter protocol and SH interface support for SIP server architecture |
US7661027B2 (en) * | 2006-10-10 | 2010-02-09 | Bea Systems, Inc. | SIP server architecture fault tolerance and failover |
US20080086567A1 (en) * | 2006-10-10 | 2008-04-10 | Bea Systems, Inc. | SIP server architecture for improving latency in message processing |
US20080147551A1 (en) * | 2006-12-13 | 2008-06-19 | Bea Systems, Inc. | System and Method for a SIP Server with Online Charging |
US8078737B2 (en) * | 2006-12-13 | 2011-12-13 | Oracle International Corporation | System and method for efficient storage of long-lived session state in a SIP server |
US9667430B2 (en) * | 2006-12-13 | 2017-05-30 | Oracle International Corporation | System and method for a SIP server with offline charging |
US8028090B2 (en) | 2008-11-17 | 2011-09-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
US7991910B2 (en) | 2008-11-17 | 2011-08-02 | Amazon Technologies, Inc. | Updating routing information based on client location |
US7895475B2 (en) * | 2007-07-11 | 2011-02-22 | Oracle International Corporation | System and method for providing an instrumentation service using dye injection and filtering in a SIP application server environment |
US8321568B2 (en) | 2008-03-31 | 2012-11-27 | Amazon Technologies, Inc. | Content management |
US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
US7970820B1 (en) | 2008-03-31 | 2011-06-28 | Amazon Technologies, Inc. | Locality based content distribution |
US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
US7962597B2 (en) | 2008-03-31 | 2011-06-14 | Amazon Technologies, Inc. | Request routing based on class |
US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US8122098B1 (en) * | 2008-11-17 | 2012-02-21 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US8782236B1 (en) | 2009-06-16 | 2014-07-15 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US8397073B1 (en) | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
US10467042B1 (en) | 2011-04-27 | 2019-11-05 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
US9231903B2 (en) * | 2011-12-30 | 2016-01-05 | Time Warner Cable Enterprises Llc | System and method for resolving a DNS request using metadata |
US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9160809B2 (en) | 2012-11-26 | 2015-10-13 | Go Daddy Operating Company, LLC | DNS overriding-based methods of accelerating content delivery |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
US9369333B1 (en) * | 2013-05-10 | 2016-06-14 | Google Inc. | System and method for centralizing outbound communications between an email system and a third party service |
US9712485B2 (en) | 2014-07-30 | 2017-07-18 | Cisco Technology, Inc. | Dynamic DNS-based service discovery |
US10057208B2 (en) * | 2014-10-31 | 2018-08-21 | Cisco Technology, Inc. | Visibility control for domain name system service discovery |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10305934B2 (en) * | 2016-05-26 | 2019-05-28 | Cisco Technology, Inc. | Identity based domain name system (DNS) caching with security as a service (SecaaS) |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
US10742593B1 (en) | 2017-09-25 | 2020-08-11 | Amazon Technologies, Inc. | Hybrid content request routing system |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US11271846B2 (en) | 2018-10-22 | 2022-03-08 | Oracle International Corporation | Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs) |
US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
US11308522B2 (en) * | 2018-12-14 | 2022-04-19 | Anagog Ltd. | Utilizing browsing history while preserving user-privacy |
US11252093B2 (en) | 2019-06-26 | 2022-02-15 | Oracle International Corporation | Methods, systems, and computer readable media for policing access point name-aggregate maximum bit rate (APN-AMBR) across packet data network gateway data plane (P-GW DP) worker instances |
US11159359B2 (en) | 2019-06-26 | 2021-10-26 | Oracle International Corporation | Methods, systems, and computer readable media for diameter-peer-wide egress rate limiting at diameter relay agent (DRA) |
US11323413B2 (en) | 2019-08-29 | 2022-05-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints |
US11082393B2 (en) | 2019-08-29 | 2021-08-03 | Oracle International Corporation | Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 5G and non-5G service endpoints |
US11224009B2 (en) | 2019-12-30 | 2022-01-11 | Oracle International Corporation | Methods, systems, and computer readable media for enabling transport quality of service (QoS) in 5G networks |
US11528334B2 (en) | 2020-07-31 | 2022-12-13 | Oracle International Corporation | Methods, systems, and computer readable media for preferred network function (NF) location routing using service communications proxy (SCP) |
US11290549B2 (en) | 2020-08-24 | 2022-03-29 | Oracle International Corporation | Methods, systems, and computer readable media for optimized network function (NF) discovery and routing using service communications proxy (SCP) and NF repository function (NRF) |
US11483694B2 (en) * | 2020-09-01 | 2022-10-25 | Oracle International Corporation | Methods, systems, and computer readable media for service communications proxy (SCP)-specific prioritized network function (NF) discovery and routing |
US11570262B2 (en) | 2020-10-28 | 2023-01-31 | Oracle International Corporation | Methods, systems, and computer readable media for rank processing for network function selection |
US11470544B2 (en) | 2021-01-22 | 2022-10-11 | Oracle International Corporation | Methods, systems, and computer readable media for optimized routing of messages relating to existing network function (NF) subscriptions using an intermediate forwarding NF repository function (NRF) |
US11589298B2 (en) | 2021-03-05 | 2023-02-21 | Oracle International Corporation | Methods, systems, and computer readable media for selecting multiple network function types using a single discovery request |
US11496954B2 (en) | 2021-03-13 | 2022-11-08 | Oracle International Corporation | Methods, systems, and computer readable media for supporting multiple preferred localities for network function (NF) discovery and selection procedures |
US11888946B2 (en) | 2021-06-02 | 2024-01-30 | Oracle International Corporation | Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests |
US11895080B2 (en) | 2021-06-23 | 2024-02-06 | Oracle International Corporation | Methods, systems, and computer readable media for resolution of inter-network domain names |
US11950178B2 (en) | 2021-08-03 | 2024-04-02 | Oracle International Corporation | Methods, systems, and computer readable media for optimized routing of service based interface (SBI) request messages to remote network function (NF) repository functions using indirect communications via service communication proxy (SCP) |
US11930083B2 (en) | 2021-08-09 | 2024-03-12 | Oracle International Corporation | Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations |
US11871309B2 (en) | 2021-09-28 | 2024-01-09 | Oracle International Corporation | Methods, systems, and computer readable media for network function discovery using preferred-locality information |
US11849506B2 (en) | 2021-10-08 | 2023-12-19 | Oracle International Corporation | Methods, systems, and computer readable media for routing inter-public land mobile network (inter-PLMN) messages related to existing subscriptions with network function (NF) repository function (NRF) using security edge protection proxy (SEPP) |
US11888957B2 (en) | 2021-12-07 | 2024-01-30 | Oracle International Corporation | Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing |
US11917720B2 (en) | 2021-12-14 | 2024-02-27 | Oracle International Corporation | Methods, systems, and computer readable media for enabling forwarding of subsequent network function subscription updates |
US11652895B1 (en) | 2022-02-15 | 2023-05-16 | Oracle International Corporation | Methods, systems, and computer readable media for dynamic optimized network function discovery for consumer network functions |
US11855956B2 (en) | 2022-02-15 | 2023-12-26 | Oracle International Corporation | Methods, systems, and computer readable media for providing network function (NF) repository function (NRF) with configurable producer NF internet protocol (IP) address mapping |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5878212A (en) * | 1995-07-31 | 1999-03-02 | At&T Corp. | System for updating mapping or virtual host names to layer-3 address when multimedia server changes its usage state to busy or not busy |
US6778651B1 (en) * | 1997-04-03 | 2004-08-17 | Southwestern Bell Telephone Company | Apparatus and method for facilitating service management of communications services in a communications network |
US6108330A (en) * | 1997-09-26 | 2000-08-22 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem that selects among a plurality of DNS servers for responding to a DNS query |
US7237036B2 (en) * | 1997-10-14 | 2007-06-26 | Alacritech, Inc. | Fast-path apparatus for receiving data corresponding a TCP connection |
US6016512A (en) * | 1997-11-20 | 2000-01-18 | Telcordia Technologies, Inc. | Enhanced domain name service using a most frequently used domain names table and a validity code table |
US6654786B1 (en) * | 1998-04-30 | 2003-11-25 | Openwave Systems Inc. | Method and apparatus for informing wireless clients about updated information |
US6701353B1 (en) * | 1999-05-13 | 2004-03-02 | Avaya Inc. | System for responding to new message polling from clients |
US6845393B1 (en) * | 1999-06-14 | 2005-01-18 | Sun Microsystems, Inc. | Lookup discovery service in a distributed system having a plurality of lookup services each with associated characteristics and services |
US6438594B1 (en) * | 1999-08-31 | 2002-08-20 | Accenture Llp | Delivering service to a client via a locally addressable interface |
US6332163B1 (en) * | 1999-09-01 | 2001-12-18 | Accenture, Llp | Method for providing communication services over a computer network system |
US6799202B1 (en) * | 1999-12-16 | 2004-09-28 | Hachiro Kawaii | Federated operating system for a server |
US20020163889A1 (en) * | 2000-02-02 | 2002-11-07 | Yechiam Yemini | Method and apparatus for providing services on a dynamically addressed network |
US6633867B1 (en) * | 2000-04-05 | 2003-10-14 | International Business Machines Corporation | System and method for providing a session query within the context of a dynamic search result set |
US6898618B1 (en) * | 2000-05-09 | 2005-05-24 | Sun Microsystems, Inc. | Client-specified display services in a distributed computing environment |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7016875B1 (en) * | 2000-08-04 | 2006-03-21 | Enfotrust Networks, Inc. | Single sign-on for access to a central data repository |
US6944167B1 (en) * | 2000-10-24 | 2005-09-13 | Sprint Communications Company L.P. | Method and apparatus for dynamic allocation of private address space based upon domain name service queries |
US6862627B1 (en) * | 2000-12-12 | 2005-03-01 | Apple Computer, Inc. | Method and system for preventing a timeout from reaching a network host |
US7080132B2 (en) * | 2001-01-19 | 2006-07-18 | Apple Computer, Inc. | Presentation during network address acquisition |
WO2002057917A2 (en) * | 2001-01-22 | 2002-07-25 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
US6775661B1 (en) * | 2001-03-21 | 2004-08-10 | Lycos, Inc. | Querying databases using database pools |
EP1410258A4 (en) * | 2001-06-22 | 2007-07-11 | Inc Nervana | System and method for knowledge retrieval, management, delivery and presentation |
US7222187B2 (en) * | 2001-07-31 | 2007-05-22 | Sun Microsystems, Inc. | Distributed trust mechanism for decentralized networks |
US7289462B1 (en) * | 2001-12-26 | 2007-10-30 | Nortel Networks Limited | Method and apparatus for network-initiated context activation using dynamic DNS updates |
EA200400873A1 (en) * | 2001-12-28 | 2005-12-29 | Джеффри Джэймс Джонас | REAL-TIME DATA STORAGE |
US9998321B2 (en) * | 2002-03-19 | 2018-06-12 | Apple Inc. | Method and apparatus for supporting duplicate suppression when issuing multicast queries using DNS-format message packets |
KR100424613B1 (en) * | 2002-04-22 | 2004-03-27 | 삼성전자주식회사 | Method for spoofing domain name system in local network and local network system thereof |
JP2004062441A (en) * | 2002-07-26 | 2004-02-26 | Ntt Docomo Inc | Service management system and method, server management device, communication terminal, and server device |
US7206934B2 (en) * | 2002-09-26 | 2007-04-17 | Sun Microsystems, Inc. | Distributed indexing of identity information in a peer-to-peer network |
US7072800B1 (en) * | 2002-09-26 | 2006-07-04 | Computer Associates Think, Inc. | Application response monitor |
JP2004171495A (en) * | 2002-11-22 | 2004-06-17 | Ntt Docomo Inc | Service performance monitoring system, service performance monitoring node, communication terminal, communication terminal program and service performance monitoring method |
US7350077B2 (en) * | 2002-11-26 | 2008-03-25 | Cisco Technology, Inc. | 802.11 using a compressed reassociation exchange to facilitate fast handoff |
JP3703457B2 (en) * | 2003-01-21 | 2005-10-05 | キヤノン株式会社 | Address notification method, program, and apparatus |
JP4161758B2 (en) * | 2003-03-19 | 2008-10-08 | 日本電気株式会社 | Network information detection apparatus and method |
US20050278237A1 (en) * | 2004-06-12 | 2005-12-15 | Globaltec Solutions, Llp | System, apparatus and method for performing a multiple condition investment transaction |
US20090141692A1 (en) * | 2007-11-30 | 2009-06-04 | Mika Kasslin | Optimized ad hoc networking |
-
2004
- 2004-06-25 US US10/877,518 patent/US8161184B2/en active Active
-
2005
- 2005-02-10 DE DE602005014106T patent/DE602005014106D1/en active Active
- 2005-02-10 EP EP05713326A patent/EP1759517B1/en active Active
- 2005-02-10 JP JP2007507311A patent/JP4594380B2/en active Active
- 2005-02-10 AT AT05713326T patent/ATE429771T1/en not_active IP Right Cessation
- 2005-02-10 CA CA2562639A patent/CA2562639C/en active Active
- 2005-02-10 AU AU2005267597A patent/AU2005267597B2/en active Active
- 2005-02-10 WO PCT/US2005/004305 patent/WO2006011909A1/en not_active Application Discontinuation
-
2007
- 2007-07-09 HK HK07107333.4A patent/HK1102948A1/en not_active IP Right Cessation
Also Published As
Publication number | Publication date |
---|---|
WO2006011909A1 (en) | 2006-02-02 |
JP4594380B2 (en) | 2010-12-08 |
AU2005267597B2 (en) | 2008-07-17 |
EP1759517A1 (en) | 2007-03-07 |
ATE429771T1 (en) | 2009-05-15 |
AU2005267597A1 (en) | 2006-02-02 |
JP2007531949A (en) | 2007-11-08 |
US8161184B2 (en) | 2012-04-17 |
CA2562639A1 (en) | 2006-02-02 |
EP1759517B1 (en) | 2009-04-22 |
HK1102948A1 (en) | 2007-12-07 |
US20060010224A1 (en) | 2006-01-12 |
DE602005014106D1 (en) | 2009-06-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2562639C (en) | Method and apparatus for facilitating long-lived dns queries | |
US7685288B2 (en) | Ad-hoc service discovery protocol | |
Cheshire et al. | Multicast dns | |
AU2005267596B2 (en) | Method and apparatus for looking up configuration information for a network node | |
US9998321B2 (en) | Method and apparatus for supporting duplicate suppression when issuing multicast queries using DNS-format message packets | |
US20060077940A1 (en) | Communication system and method with mobile devices | |
Cheshire et al. | Rfc 6762: Multicast dns | |
WO2005041489A1 (en) | Formtext handover method in dhcpv4, handover apparatus and medium having instructions for performing the method | |
CA2562900C (en) | Method and apparatus for updating resource records in a name-server database | |
US20190021065A1 (en) | Reducing Time Required for Location Lookup When Downlink Packets Arrive By Assisting Preloading of a Location of a Wireless Device Into the IP Advertisement Point (IAP) | |
CN105340247B (en) | Method for network change tolerant service discovery in computer networks | |
US11070513B2 (en) | DNS-based method of transmitting data | |
US20110235641A1 (en) | Communication apparatus, method of controlling the communication apparatus,and program | |
EP3811592A1 (en) | Communication protocol discover method in constrained application protocol (coap) | |
Cheshire et al. | RFC 8764 Apple's DNS Long-Lived Queries Protocol | |
JP4242752B2 (en) | Address table management method and terminal | |
Cheshire | RFC 8766: Discovery Proxy for Multicast DNS-Based Service Discovery | |
Wasserman | IPv6 Neighbor Discovery Optimizations for Wired and Wireless Networks draft-chakrabarti-nordmark-6man-efficient-nd-05 | |
Stillman et al. | Network Working Group R. Stewart Internet-Draft Cisco Systems, Inc. Expires: April 14, 2005 Q. Xie Motorola, Inc. | |
Rahman et al. | CoRE Working Group A. Castellani Internet-Draft University of Padova Intended status: Informational S. Loreto Expires: October 29, 2012 Ericsson | |
Rahman et al. | CoRE Working Group A. Castellani Internet-Draft University of Padova Intended status: Informational S. Loreto Expires: September 13, 2012 Ericsson |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |