rfc1714.txt

中、英文RFC文档大全打包下载完全版 .

                                 information used to authenticate
                                 the person sending the registration
                                 information.  The method used must
                                 be identified using the -private
                                 directive.  Work must be done to
                                 identify usable authentication
                                 methods for unsupervised
                                 delegation.  This is beyond the
                                 scope of this document.  However,
                                 the authors have made an effort to
                                 allow flexibility in the
                                 implementation of an authentication
                                 system.

   Example of use:

   -register on add [e-mail]
   Object-type:referral
   Referral:netman1.netsol.com:4343
   Domain-Name:netsol.com
   IP-Network:192.153.247.0
   IP-Network:198.41.0.0
   -register off

2.3.13 object

   RWhois data is a collection of objects with defined attributes.  The
   attributes for an object can be acquired by issuing the -schema
   directive.  Each object must at a minimum define the attribute
   object-type.  This attribute identifies the name of the object that



Williamson & Kosters                                           [Page 14]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   will be displayed in response to the -object directive.  This
   directive can be used by a client to verify that a server contains
   the desired object.  Another possible use may be to gather all of the
   objects contained on a server and display them to the user in the
   form of a menu for selection.

   Format for use:

   -object<SP>[object]

   [object]{%s}   This optional argument identifies the object
                  requested.  If no argument is sent, all objects
                  contained in the server will be returned.

   Example of use:

   -object domain

2.3.14 define

   Format strings describing the format of an object's attribute may
   include format macros.  More information about definitions of format
   macros can be found in Section 6.  The -define directive allows the
   client to request the definition of a format macro.

   Format for use:

   -define<SP>[macro name]

   [macro name]{%s}    This optional argument identifies the name of
                       the macro to display.  If no arguments are
                       sent, the server must return the definition
                       of all macros contained in the server.

   Example of use:

   -define server

2.3.15 private

   The -private directive allows the client to identify the
   authentication method to be used.  More research needs to be done
   with respect to client authentication.  This directive will allow
   more experimentation.







Williamson & Kosters                                           [Page 15]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   Format for use:

   -private<SP><action><SP><method><SP>[data]

   <action>{auth|encr} This required argument identifies the action
                       the directive is taking.  Currently the value
                       for this argument can be auth for
                       authentication or encr for encryption.

   <method>{%s}        This required argument contains the name of
                       the method to be used.  The value must be
                       recognized by the server or an error will be
                       sent.  It is beyond the scope of this
                       document to identify the possible method to
                       be used.

   [data]{%s}          This optional argument must be supplied if
                       required by the method identified in the
                       previous argument.

   Example of use:

   -private auth pass1 xxjdk998uu

   The above example is a simple password exchange.  It is beyond the
   scope of this document to determine the authentication technique that
   would best suit this protocol.  Development is underway to determine
   the authentication needs and to experiment with potential solutions.

2.3.16 X-

   This directive is the preface to extended directives, mutually agreed
   to between the client and server.  The client and server must have
   knowledge of the extended directives to use.  Extension can
   accommodate other uses such as NetHelp, white pages, and many others.
   If the extensions are public, they should be documented in an RFC and
   available through the -directive directive.














Williamson & Kosters                                           [Page 16]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   Format for use:

   -X-<directive name><SP>[directive arguments]

   <directive name>{%s}     This required argument identifies the
                            name of the directive being issued.

   [directive arguments]{?} This optional argument is dependent upon
                            the required or optional arguments of
                            the extended directive.  There may be
                            multiple directive arguments.

   Example of use:

   -X-date

2.3.17 directive

   Directives allowed by a server may vary.  The client can issue the
   -directive directive to determine if the server allows a specific
   directive or to obtain a list of all acceptable directives for that
   server.

   Format for use:

   -directive<SP>[directive]

   [directive][%s]   This optional argument identifies the directive
                     being requested.  If no arguments are sent, all
                     of the directives accepted by the server must
                     be sent.

   Example of use:

   -directive X-date

2.3.18 display

   The -display directive is used to set the display mode of the server
   or to identify display modes the client is capable of.  If this
   directive is sent without arguments, the server will return all
   available display methods.









Williamson & Kosters                                           [Page 17]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   Format for use:

   -display<SP>[action]<SP>[method]

   [action]{activate|capable}
                       The `activate' setting enables a certain
                       display mode, while a `capable' setting sends
                       the display mode the client is capable of.

   [method]{%s}        This optional argument indicates the display
                       method desired by the client.

   Example of use:

   -display swip
   -display mime

2.3.19 language

   The -language directive is used to set the language mode of the
   server or to identify language modes the client is capable of.  If
   this directive is sent without arguments, the server will return all
   available languages.

   Format for use:

   -language<SP>[language]

   [language]{%s}      This optional argument indicates the language
                       desired by the client.

   Example of use:

   -language german

2.4  RWhois Client Model

   Server <-------> Client

   START:
   <------ Connection (record time to connect)
           If no server type...Wait up to specified
            time for------> "%RWhois" response
            (recommend wait of at least 5 seconds)

   if  "%RWhois" is not received from server, assume that it is
    not an RWhois server
       goto QUERY:



Williamson & Kosters                                           [Page 18]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   else if "%RWhois" is received from server
       <------- send "-RWhois -VX.X"
       --------> receive "%ok"
       DIRECTIVE: if directive for server
                  <------- send directive
                  -------> receive server response
                  if "%ok" received
                    goto DIRECTIVE:
                  if "%error" received
                    process error then goto DIRECTIVE:
                else if no more commands for server
                   goto QUERY:
   QUERY:
       <-------- send query
       --------> Receive and display response
       PROCESS: if "%referral" received
                   if first referral
                      restart server list
                   else
                      add to server list
               if "%see-also" received
                   insert server into server list
               if in holdconnection mode
                   goto DIRECTIVE:
               if no directive (%)
                   goto END:
               goto PROCESS:
   END:
   server will disconnect
   if more servers on Queue and multi or referral mode active
       goto START:

   Every time the RWhois client receives a %referral or %see-also
   response from the RWhois server it must compare the host:port:query
   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
   prototype RWhois client maintains a server trail and compares each
   new directive with the entire list.  If a recursive act is about to
   occur, the client will notify the user and exit.  The original Whois
   client opens a TCP connection, sends the query, and displays the
   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
   directives and receiving responses.  All of these features have been
   incorporated into the experimental RWhois client.





Williamson & Kosters                                           [Page 19]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


3.  RWhois Server Model

   This section describes the functionality of the RWhois server.

3.1  Output Display and Restriction Keywords

   The RWhois server will behave similarly to the original whois server
   in terms of display formats and restrictions.  The following are
   required in the RWhois server.

   Display Format Keywords

   EXPand (*)          Expand

   ~                   no sub displays

   SUBdisplay (%)      sub displays

   SUMmary ($)         Give a short summary for the query on one to
                       many hits (defaults on multiple hits).

   Full (=)            Give the full record output on one to many
                       hits (defaults on one hit only).

   The following was added to whois post RFC 954 [RFC-954] and is part
   of the RWhois requirements:

   dump (#)            Display the record in a parsable format.

   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
   requested by post fixing a `*' or `.' at the end of the search item
   for unknown characters.  This capability is required for an RWhois
   server.

      Example: last-name=williamson and first-name=scott

      Data Restriction Format Keywords












Williamson & Kosters                                           [Page 20]

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


      The following restriction keywords are found in the RFC 954
      [RFC-954] whois server: