rfc1913.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   gets a query which has a term requesting a field not in this list for
   this template, the polling server will treat that term as a 'hit'.
   If the value is False, the pollee is indicating that there are no
   other fields for this template which should be treated as a hit. This
   field is required because the basic model for the WHOIS++ query
   syntax requires that the results of each search term be 'and'ed
   together. This field allows polled servers to export data only for
   non-sensitive fields, yet still get referrals of queries which
   contain sensitive terms.

   IMPORTANT: The data listed in the centroid must be in the ISO-8859-1
   character set in this version of the indexing protocol. Use of any
   other character set is a violation of the protocol. Note that the
   base-level server is also specified to use ISO-8859-1 [Deutsch, et



Weider, et al               Standards Track                    [Page 11]

RFC 1913       Architecture of the Whois++ Index Service   February 1996


   al, 1995].

# CENTROID-CHANGES
 Version-number: // version number of pollee's index software, used to
                 // insure compatibility
 Start-time: // change list starting time, GMT
 End-time: // change list ending time, GMT
 Server-handle: // IANA unique identifier of the responding server
 Case-sensitive: // states whether data is case sensitive or case
                 // insensitive. values are TRUE or FALSE
 Authentication-type: // Type of authentication used by pollee, or NONE
 Authentication-data: // Data for authentication
 Compression-type: // Type of compression used on the data, or NONE
 Size-of-compressed-data: // size of compressed data if compression
                          // is used
 Operation: // One of 3 keywords: ADD, DELETE, FULL
            // ADD - add these entries to the centroid for this server
            // DELETE - delete these entries from the centroid of this
            // server
            // FULL - the full centroid as of end-time follows
{ // The multiply occurring template block starts here
# BEGIN TEMPLATE
 Template: // a standard whois++ template name
 Any-field: // TRUE or FALSE. See beginning of 6.3 for explanation.
 { // the template contains multiple field blocks
# BEGIN FIELD
 Field: // a field name within that template
 Data: // Either the keyword *ANY*, or
       // the word list itself, one per line, cr/lf terminated,
       // each line starting with a dash character ('-').
# END FIELD
  } // the field ends with END FIELD
# END TEMPLATE
} // the template block ends with END TEMPLATE
# END CENTROID-CHANGES // This line must be used to terminate the
                         // centroid change report

   For each template, all fields must be listed, or queries will not be
   referred correctly.

Required/Optional table

Version-number  REQUIRED, value is 1.0
Start-time      REQUIRED (even if the centroid type is FULL)
End-time        REQUIRED (even if the centroid type is FULL)
Server-handle   REQUIRED
Case-Sensitive  OPTIONAL
Authentication-Type     OPTIONAL



Weider, et al               Standards Track                    [Page 12]

RFC 1913       Architecture of the Whois++ Index Service   February 1996


Authentication-Data     OPTIONAL
Compression-type        OPTIONAL
Size-of-compressed-data OPTIONAL (even if compression is used)
Operation     OPTIONAL, if used, upport for all three values is required
Tokenization-type       OPTIONAL
#BEGIN TEMPLATE REQUIRED
Template        REQUIRED
Any-field       REQUIRED
#BEGIN FIELD    REQUIRED
Field           REQUIRED
Data            REQUIRED
#END FIELD      REQUIRED
#END TEMPLATE   REQUIRED
#END CENTROID-CHANGES REQUIRED

Example:

# CENTROID-CHANGES
 Version-number: 1.0
 Start-time: 197001010000
 End-time: 199503012336
 Server-handle: BUNYIP01
# BEGIN TEMPLATE
 Template: USER
 Any-field: TRUE
# BEGIN FIELD
 Field: Name
 Data: Patrik
-Faltstrom
-Malin
-Linnerborg
#END FIELD
#BEGIN FIELD
 Field: Email
 Data: [e-mail]
[e-mail]
# END FIELD
# END TEMPLATE
# END CENTROID-CHANGES

6.4 QUERY and POLLEES responses

   The response to a QUERY command is done in WHOIS++ format.








Weider, et al               Standards Track                    [Page 13]

RFC 1913       Architecture of the Whois++ Index Service   February 1996


6.5. Query referral

   When referrals are included in the body of a response to a query,
   each referral is listed in a separate SERVER-TO-ASK block as shown
   below.

# SERVER-TO-ASK
 Version-number: // version number of index software, used to insure
                 // compatibility
 Body-of-Query: // the original query goes here
 Server-Handle: // WHOIS++ handle of the referred server
 Host-Name: // DNS name or IP address of the referred server
 Port-Number: // Port number to which to connect, if different from the
                // WHOIS++ port number

# END

Required/Optional table

Version-number REQUIRED, value should be 1.0
Body-of-query OPTIONAL
Server-Handle REQUIRED
Host-Name REQUIRED
Port-Number OPTIONAL, must be used if different from port 63

Example:

# SERVER-TO-ASK
 Version-Number: 1.0
 Server-Handle: SUNETSE01
 Host-Name: sunic.sunet.se
 Port-Number: 63
# END

7: Reply Codes

   In addition to the reply codes listed in [Deutsch 95] for the basic
   WHOIS++ client/server interaction, the following reply codes are used
   in version 1.0 of this protocol.

113 Requested method not available      Unable to provide a requested
                                        compression method. Contacted
                                        server will send requested
                                        data in different format.

227 Update request acknowledged         A DATA-CHANGED transmission
                                        has been accepted and logged
                                        for further action.



Weider, et al               Standards Track                    [Page 14]

RFC 1913       Architecture of the Whois++ Index Service   February 1996


503 Required attribute missing          A REQUIRED attribute is
                                        missing in an interaction.

504 Desired server unreachable          The desired server is
                                        unreachable.

505 Desired server unavailable          The desired server fails to
                                        respond to requests, but host
                                        is still reachable.

8. References

[Deutsch 95] Deutsch, et al., "Architecture of the WHOIS++ service",
             RFC 1835, August 1995.


[Faltstrom 95] Faltstrom, P., et al., "How to Interact with a WHOIS++
               Mesh, RFC 1914, February 1996.

9. Security Considerations

   Security issues are not discussed in this memo.





























Weider, et al               Standards Track                    [Page 15]

RFC 1913       Architecture of the Whois++ Index Service   February 1996


10. Authors' Addresses

   Chris Weider
   Bunyip Information Systems, Inc.
   310 St. Catherine St. West
   Montreal, PQ H2X 2A1
   CANADA

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Jim Fullton
   MCNC Center for Communications
   Post Office Box 12889
   3021 Cornwallis Road
   Research Triangle Park
   North Carolina 27709-2889

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Simon Spero
   EMail: [e-mail]
























Weider, et al               Standards Track                    [Page 16]