query
Click on the red underlined text to get to the source
... is part of the block 198.41.0.0/16 which is part of the block
198.0.0.0/8) The InterNIC may not have the information, but will at
least be able to reduce the query and point or refer the users closer
to their goal. This has led to the development of a referral whois,
and the corresponding RWhois protocol.
...
...
In this case, the client should only send the query. We realize that
the server identification feature may mean that the identity of an
...
... of these servers in building the RWhois structure.
The RWhois server must remain connected until a query is received.
If the client wishes to make multiple queries ...
... query is received.
If the client wishes to make multiple queries it must send the
-holdconnect directive. In this mode, once the client has sent the
...
... -holdconnect directive. In this mode, once the client has sent the
last query and received either an answer or the error code indicating
that no records were found, it must issue the -quit directive. If
...
... compatibility with older Whois clients, the
query is not prefaced with the `-' character. Only after the client
is certain that the server is an RWhois server should these
...
... lt;query> ...
...
The query is generally the final directive sent to the server. It is
the only directive that does not start with a `-'. The query ...
... query is generally the final directive sent to the server. It is
the only directive that does not start with a `-'. The query is the
question that the client wants the server to answer. The qualifiers
...
... question that the client wants the server to answer. The qualifiers
that may proceed the query are addressed in Section 3.1 - Output
Display and Restriction Keywords.
...
... query>
[Display format]{%s} This optional pre-query directive allows
the requester to select the format of
the returned data. Details of the
...
... 3.1.
[Query restriction]{%s} This optional pre-query directive allows
the requester to limit the area in which
...
...
[Query restriction]{%s} This optional pre-query directive allows
the requester to limit the area in which
the servers search ...
... The -load directive allows the client to make a quick decision about
presenting the query to the current server. If the client determines
that another server can better serve the query ...
... query to the current server. If the client determines
that another server can better serve the query, then control may be
transferred to the server with the lower load and better connection.
...
... X.500 was the requirement to know the
schema of an object before making a query. RWhois allows the client
to request the schema for an object without knowledge of the object
...
... The RWhois server must close the connection after the response to a
query has been received. The query is the final exchange between the
client and server ...
... connection after the response to a
query has been received. The query is the final exchange between the
client and server. However, this characteristic can be modified with
...
... client, expecting the client to redirect
the query to the server identified in the response. If the client is
located behind a firewall ...
... located behind a firewall or is poorly connected, having a server
make the query may improve query performance or allow a query ...
... firewall or is poorly connected, having a server
make the query may improve query performance or allow a query to be
...
... query may improve query performance or allow a query to be
satisfied. The -forward directive will instruct the server to
operate as a forwarding server. Whether or not this directive should
...
... authority area in question. It is not considered a
bad referral if the server does not have an answer to
the query, but responds positively to the -soa area
directive. This merely means that there is not an
answer to the query ...
... query, but responds positively to the -soa area
directive. This merely means that there is not an
answer to the query. When a -badref is sent to the
referring server; it should log the bad referral so the
administrator ...
... if it is no longer correct. This action should only be
taken after receiving a negative response to the query
and the SOA request.
...
... update list.
<information>{action=badref|recurref <<server>:<query>>
action=inssec|delsec|update
...
... or has data that changed.
<query>{%s} This required argument identifies the query
that was sent to the server that gave a
...
...
<query>{%s} This required argument identifies the query
that was sent to the server that gave a
recursive or bad referral.
...
... if "%RWhois" is not received from server, assume that it is
not an RWhois server
goto QUERY:
else if "%RWhois" is received from server
...
... QUERY:
<-------- send query
--------> Receive and display response
PROCESS: if "%referral" received
...
... response from the RWhois server it must compare the host:port:query
with those already executed. If the client discovers that it is
...
... with those already executed. If the client discovers that it is
being directed to repeat the same query to a server that it has
already visited, it must not repeat that query. As an example, the
...
... being directed to repeat the same query to a server that it has
already visited, it must not repeat that query. As an example, the
prototype RWhois client maintains a server trail and compares each
...
... client opens a TCP connection, sends the query, and displays the
response. The RWhois client must be more robust in order to handle
...
... response. The RWhois client must be more robust in order to handle
multiple server queries, servers that do not exist, and recursive
referrals. The client must also remain connected while sending
...
... SUBdisplay (%) sub displays
SUMmary ($) Give a short summary for the query on one to
many hits (defaults on multiple hits).
...
...
In addition to the above, the RWhois server must accept additional
pre-query directives such as Boolean queries and attribute=value
query ...
... In addition to the above, the RWhois server must accept additional
pre-query directives such as Boolean queries and attribute=value
query combinations. The capability to perform partial matches are
...
... query directives such as Boolean queries and attribute=value
query combinations. The capability to perform partial matches are
requested by post fixing a `*' or `.' at the end of the search item
...
... Query on Handle only
mailbox Query on all records for person
person Query on User records only
...
...
The %referral response instructs the client to query another server
(which could be a whois, RWhois, or whois++ server). Referrals are
cumulative. The first referral received during a session ...
... response format below, the
authority area equals the reduced query. There are three types of
referral. The type can be determined by the client evaluating the
...
... If the authority area received from a referral response is equal to
the original query, then it is a link type referral. If the
authority ...
... link type referral. If the
authority area is not equal to the query, then it is a reduction type
referral. If no authority area is sent, then it is a punt type
...
... referral. (Punt means the server is not a root and cannot answer the
query and therefore is referring the client to a level up the tree or
...
... client to a level up the tree or
to a server that can better answer the query.) [NOTE: the punt type
referral may be used to direct a client into the whois++ mesh ...
...
The client may receive multiple referrals from a single query. If
the SOA for each of these referrals is the same, then the first
referral is the primary server and all subsequent servers are
...
... authority area that caused the referral for
the query in question. Using this value as
the argument for the -soa directive to
the referral server should result in a
...
... The %see-also response instructs the client to contact another server
for additional information about the current query. See-also servers
should be inserted into the server list just after the current
server. If multiple see-alsos are received from a single query ...
... query. See-also servers
should be inserted into the server list just after the current
server. If multiple see-alsos are received from a single query, each
subsequent see-also should be inserted after any other see-alsos
previously received. See-alsos should be additional information
...
... subsequent see-also should be inserted after any other see-alsos
previously received. See-alsos should be additional information
related to the current query.
One example use for the see-also response is to display autonomous
system ...
... non-RWhois.
<query>{%s} This required argument sets the query that
must be sent to the referred server. The
...
...
<query>{%s} This required argument sets the query that
must be sent to the referred server. The
query ...
... query that
must be sent to the referred server. The
query may be different from the original
query sent to the referring server.
...
... query may be different from the original
query sent to the referring server.
<url>{%Murl} This required argument defines the Uniform
Resource ...
... Query Reduction ...
... The critical component of the RWhois server is the ability to reduce
the query to find a server that is closer to the data. The search
algorithm ...
... algorithm of the server is the following:
1) accept a query
2) find any local matches - display them
3) find any referrals - display them
...
... 2) find any local matches - display them
3) find any referrals - display them
4) if no local or referral hits, reduce the query and goto step 3
Here is an example of the query ...
... query ietf.cnri.reston.va.us:
1) query whois for ietf.cnri.reston.va.us
2) search rs.internic.net for information (no hits).
...
... lt;QUERY> ...
...
These responses may occur following a query:
<answer>
...
... will have a `6' in the second position of the code.
100 Get Peer Name query failed
120 Registration not processed... will process hours:<hours>
...
... 333 Not SOA for requested authority area
334 Pre-query directive not implemented
335 System's load not available
336 Object not defined
...
... only wishes to ask one question. A separate document will describe
the UDP facility for RWhois. Adjustments to the query must be made
to make this a practical option. The only function allowed while
utilizing UDP ...
... to make this a practical option. The only function allowed while
utilizing UDP is a single query.
...