rfc2345.txt

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


RFC 2345        Domain Names and Company Name Retrieval         May 1998


   If 10 or more entries are found in the database for the query, only
   the top 10 will be returned in the response.

   For the purposes of this demonstration, there is no provision for
   submitting additions or changes to the database. The authors and the
   sponsoring companies are not responsible for the accuracy of the data
   provided by this prototype. Our apologies if your company is not
   listed.

6.2  Client

6.2.1 Download Location:

   A demonstration client for the Windows 95/Nt platforms is available
   for public download through anonymous ftp at:
   ftp.mci.net/pub/ietf/company/demo.exe, or via the web:
   ftp://ftp.mci.net/pub/ietf/company/demo.exe
   File size is approximately 1.9 MB.

6.2.2 Setup Instructions:

   a) Download the client installation software from the site mentioned
      above to a local 32 bit Windows computer. The client installation
      software has been compressed using the self-extracting archive
      application from InstallShield The default name for the download
      is "demo.exe".

   b) Double click on the file through File Explorer or run the program
      through the START menu.

   c) Select "Setup" to allow InstallShield to uncompress the files
      needed to install the demonstration client to a temporary
      directory. InstallShield will then automatically launch the main
      application Setup program.

   d) The main setup program will install the demo application files and
      make the necessary additions to the Windows Registry. No user
      action is required.

   e) Upon completion of installation you will be prompted to run the
      application or to exit setup.










Klensin, et. al.              Experimental                      [Page 8]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


6.2.3 Paranoia:

   What did you just do to my computer?

   Files Copied:

   companyname.exe    Main program executable
   whois.ocx          WhoIs module from Mabry Software
   led.ocx            LED module from Mabry Software
   msvbvm50.dll       Microsoft Visual Basic 5.0 runtime file
   stdole2.tlb        Microsoft Visual Basic 5.0 runtime file
   oleaut32.dll       Microsoft Visual Basic 5.0 runtime file
   olepro32.dll       Microsoft Visual Basic 5.0 runtime file
   comcat.dll         Microsoft Visual Basic 5.0 runtime file
   asyncfilt.dll      Microsoft Visual Basic 5.0 runtime file
   crtl3d32.dll       Installshield control used for installation only

   Registry Changes:

   Created key under HKEY_CLASSES_ROOT called Who

   This entry is used to enable the Microsoft Internet Explorer's
   pluggable protocol handler. The key contains several sub-entries that
   list the path and command to the companyname executable. The
   pluggable protocol hander provides the necessary hooks to launch the
   companyname application whenever the WHO:// URL is submitted in the
   address line of Internet Explorer.

6.2.4 Using the Program

6.2.4.1 Standalone Operation:

   From the Start Menu, select the Programs \ Companyname \ companyname.
   Alternatively, it can be launched from Start:
     Run c:\windows\companyname.exe

   Enter the name of the company that you are attempting to locate and
   press OK.

   A status box will be displayed while the client is communicating with
   the server until a response is returned. The possible returns are:

      a) Message box saying that,  "Your request was not found."
         This means that the company information that was submitted was
         not found in the database.






Klensin, et. al.              Experimental                      [Page 9]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


      b) A list box containing 2 - 10 company names sorted high to
         low by score. Highlight one of the names and press the launch
         button. The program will launch the default web browser for
         your computer and navigate to the site.

      c) The default web browser launches and navigates to a site.
         This means that only one match was found in the database and
         that match is opened directly without user intervention.

6.2.4.2 Within Internet Explorer

   From the Address Line within the web browser, enter "WHO://" followed
   by the name of the company that you wish to search for and press the
   enter key.

      Note:  Since the company name is entered within the URL space
             of the browser, it can not contain spaces.

   If you wish to send a search string that contains spaces, enter
   "WHO://" with no company information.  The application will display
   the dialogue window as described in standalone mode for you to enter
   the search criteria.

   A status box will be displayed while the client is communicating with
   the server until a response is returned. The possible returns are:

      a) Message box saying that,  "Your request was not found."
         This means that the company information that was submitted was
         not found in the database.

      b) A list box containing 2 - 10 company names sorted high to
         low by score. Highlight one of the names and press the launch
         button. The program will launch the default web browser for
         your computer and navigate to the site.

      c) The default web browser launches and navigates to a site.
         This means that only one match was found in the database and
         that match is opened directly without user intervention.

6.2.5 Client Customization

   The name of the Whois server is hardcoded within the application to
   "companies.mci.net". No initialization file or registry keys are
   needed for the default configuration.  Realizing  that some testers
   may have proxy servers on their corporate systems and that others may
   wish to test the client against a different Whois server, the client
   supports a mechanism for changing the default server.  To enable the
   server customization, follow these steps:



Klensin, et. al.              Experimental                     [Page 10]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


      a) Create a new directory in the root of the
         C: Drive called "companyname"

      b) Using Notepad or any text editor create a new file
         called "whois.ini"

      c) Add a new line to the file beginning with
         "SERVER= <server name>". Do not include the double quotes
         around the tag. <server name> would be the IP Address or DNS
         name of the new Whois or proxy server.

      d) End the line with a carriage return.

      e) Save the file as a plain text file back to
         "c:\companyname\whois.ini"

6.2.6 Client Limitations:

   The demonstration software and database are provided "as is". No
   warranties are stated or implied. Use at your own risk.

   The demonstration client is supported only on 32 bit Intel Windows
   platforms. It has been tested on  Windows 95, Windows NT 4.0 and
   Windows 98 beta RC0.

   Use of the WHO:// URL moniker from within the web browser is
   supported only under Microsoft Internet Explorer.

   TCP Port 43 must be cleared through firewalls for client to
   communicate with the server. Refer to the section on client
   customization if you need to utilize a proxy server to traverse a
   firewall.

   When using the Address Line entry method within Microsoft Internet
   Explorer, spaces are not permitted within the search string.

7. References

   [ABNF]  Crocker, D., and P. Overell, Eds., "Augmented BNF for Syntax
   Specifications: ABNF",  RFC 2234, November 1997.

   [RFC1591]  Postel, J., "Domain Name System Structure and Delegation",
   RFC 1591, March 1994.

   [GOPHER] Anklesaria, F., McCahill, M., Lindner, P., Johnson, D.,
   John, D., Torrey, D., and B. Alberti, "The Internet Gopher Protocol
   (a distributed document search and retrieval protocol)", RFC 1436,
   March 1993.



Klensin, et. al.              Experimental                     [Page 11]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


   [LDAP]  Yeong, W., Howes, T., and S. Kille, "Lightweight Directory
   Access Protocol", RFC 1777, March 1995.

   [RWHOIS]   Williamson, S., and M. Kosters, "Referral Whois Protocol
   (RWhois)", RFC 1714, December 1994.

   [URL]   Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
   Resource Locators (URL)", RFC 1738, December 1994.

   [WHOIS] Feinler, E., Harrenstien, K., and M. Stahl, "NICNAME/WHOIS",
   RFC 954, October 1985.

   [WHOIS++]  Deutsch, P., Schoultz, R., Faltstrom, P., and C. Weider,
   "Architecture of the WHOIS++ service", RFC 1835, August 1995.

   [X500]  Wright, R., Getchell, A., Howes, T., Sataluri, S., Yee, P.,
   and W. Yeong, "Recommendations for an X.500 Production Directory
   Service", RFC 1803, June 1995.

   [Z39.50]  Lynch, C., "Using the Z39.50 Information Retrieval Protocol
   in the Internet Environment", RFC 1729, December 1994.

8. Security Considerations

   This suggested use of the WHOIS protocol adds no significant security
   risks to those of traditional applications of the protocol which is
   one of the most widely-deployed applications on the Internet.  As
   usual, servers should expect to use the string sent to them as an
   information retrieval key, not as a function to be executed in some
   way.  A more significant risk would arise if the server supporting
   the translation function were somehow spoofed; in that case, an
   incorrect URL might be returned for a particular company. As with the
   possibility of finding an incorrect page using naming conventions,
   the best protection against the risks that could then occur is
   careful attention to certificates, signatures, and other
   authenticity-indicating information.

9.  IANA Considerations

   As provided in section 3.3, above, this experiment requests that IANA
   maintain a registry of query variation forms and that the registry be
   initialized with the two values specified in that section.









Klensin, et. al.              Experimental                     [Page 12]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


10. Acknowledgements

   This memo was inspired by a many discussions over the last few years
   about the status and uses of the domain name system, information
   location using conventions about domain names, exposure of URLs to
   end users, and convergence of directory and search protocols.  While
   the people involved are too numerous to attempt to list, the authors
   would like to acknowledge their contributions and comments.

   Martin Hamilton, Keith Moore, Tom Thornbury and Ed Trembicki-Guy made
   important suggestions that have contributed to the revision of this
   memo.

11. Authors' Addresses

   John C. Klensin
   MCI Internet Architecture
   800 Boylston St, 7th floor
   Boston, MA 02199
   USA

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


   Ted Wolf, Jr.
   Electronic Commerce
   Dun & Bradstreet Information Services
   3 Sylvan Way
   Parsippany, NJ 07054
   USA

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


   Gary W. Oglesby
   MCI Internet Architecture
   842 N. Ahoy Dr.
   Gilbert, AZ 85234
   USA

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







Klensin, et. al.              Experimental                     [Page 13]

RFC 2345        Domain Names and Company Name Retrieval         May 1998


12.  Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
























Klensin, et. al.              Experimental                     [Page 14]