rfc1739.txt

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

      PROMPT-ON-CONNECT             PUSH
      PUT                           PWD
      QUIT                          QUOTE
      RECEIVE                       REMOTE-HELP
      REMOVE-DIRECTORY              RENAME
      RETAIN                        RM
      RMDIR                         SEND
      SHOW-DIRECTORY                SITE
      SPAWN                         STATISTICS
      STATUS                        STREAM



Kessler & Shepard                                              [Page 12]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


      STRUCTURE                     TAKE
      TENEX                         TYPE
      USER                          VERBOSE
      VERSION

   ** WIRETAP.SPIES.COM> HELP TYPE
      The TYPE command changes the FTP transfer type.  The possible
      arguments to the TYPE command are ASCII, IMAGE, BACKUP, and
      LOGICAL-BYTE ASCII type is used for transferring ASCII text files.
      IMAGE type is used for transferring binary files.  BACKUP type is
      used for transferring VAX/VMS backup savesets with 2048 byte block
      size.

   ** WIRETAP.SPIES.COM> DIR
      <Opening ASCII mode data connection for /bin/ls.
      total 25
      drwxr-xr-x  2 9013     daemon      512 Jul  1  1993 .cap
      drwxr-xr-x  4 9013     daemon      512 Jul  1  1993 About
      -rw-r--r--  1 9013     daemon      791 Apr  6  1993 About_Gopher
      drwxr-xr-x  3 9013     daemon      512 Jul 12  1993 Books
      drwxr-xr-x 13 9013     daemon      512 Jul  1  1993 Clinton
      lrwxrwxrwx  1 root     daemon       12 Feb 26 07:02 Economic_Plan
      -> Gov/Economic
      drwxr-xr-x  4 9013     daemon      512 Jul  1  1993 Etext
      lrwxrwxrwx  1 root     daemon       13 Feb 26 07:01 GAO_Reports ->
      Gov/GAO-Trans
      drwxr-xr-x 29 9013     daemon     1024 Feb  3 00:15 Gov
      drwxr-xr-x 16 9013     daemon      512 Jul  1  1993 Library
      lrwxrwxrwx  1 root     daemon        9 Feb 26 06:56 NAFTA ->
      Gov/NAFTA
      drwxr-xr-x  2 9013     daemon      512 Jul  1  1993 Other
      drwxr-xr-x  3 9013     daemon     3072 Apr  7 20:59 alt.etext
      drwxr-xr-x  8 root     42          512 Jul  1  1993 ba.internet
      dr-xr-xr-x  2 bin      wheel       512 Jul  1  1993 bin
      drwxr-xr-x  2 root     daemon      512 Feb 15 06:14 dev
      drwxr-xr-x  3 root     wheel       512 Jul  1  1993 etc
      drwxr-xr-x 11 9038     daemon      512 Dec 17 05:37 game_archive
      drwx-wx-wx  3 root     daemon     1024 Apr 18 02:09 incoming
      drwxr-xr-x  3 root     ftp         512 Oct 29 02:35 pub
      drwxr-xr-x  2 root     daemon      512 Jul  1  1992 tmp
      drwxr-xr-x  3 root     daemon      512 Jul  1  1993 usr
      drwxr-xr-x  3 9013     42         1024 Jul  1  1993 waffle
      <Transfer complete.
      1490 bytes transferred at 4966 bps.
      Run time = 10. ms, Elapsed time = 2400. ms.

   ** WIRETAP.SPIES.COM> CD Gov
      <CWD command successful.



Kessler & Shepard                                              [Page 13]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


   ** WIRETAP.SPIES.COM> SHOW
      <"/Gov" is current directory.

   ** WIRETAP.SPIES.COM> DIR *.act
      <Opening ASCII mode data connection for /bin/ls.
      -rw-r--r--  1 9013     42        32695 Dec 10 21:37 brady.act
      -r--r--r--  1 9013     42       168649 Mar 26  1993 disable.act
      -r--r--r--  1 9013     42        62602 Mar 30  1993 ecpa.act
      -r--r--r--  1 9013     42        29519 Mar 30  1993 faircredit.act
      -r--r--r--  1 9013     42        57206 Mar 30  1993 privacy.act
      -r--r--r--  1 9013     42        16261 Mar 26  1993 warpower.act
      <Transfer complete.
      401 bytes transferred at 7638 bps.
      Run time = 0. ms, Elapsed time = 420. ms.

   ** WIRETAP.SPIES.COM> GET faircredit.act FAIRCRDT.TXT
      <Opening ASCII mode data connection for faircredit.act (29519
      bytes).
      <Transfer complete.
      30132 bytes transferred at 39976 bps.
      Run time = 40. ms, Elapsed time = 6030. ms.

   ** WIRETAP.SPIES.COM> QUIT
      <Goodbye.
      SMCVAX$
      ================================================================

2.6. TELNET

   TELNET [17] is TCP/IP's virtual terminal protocol.  Using TELNET, a
   user connected to one host can login to another host, appearing like
   a directly-attached terminal at the remote system; this is TCP/IP's
   definition of a "virtual terminal."  The general form of the TELNET
   command is:

        TELNET  [IP_address | host_name]  [port]

   As shown, a TELNET connection is initiated when the user enters the
   "TELNET" command and supplies either a "host_name" or "IP_address";
   if neither are given, TELNET will ask for one once the application
   begins.

   In the example below, a user logged onto a PC on a LAN will use
   TELNET to attach to the remote host "smcvax.smcvt.edu".   Once logged
   in via TELNET, the user can do anything on the remote host that they
   could do if they were on a directly-connected terminal or had dialed-
   up by modem.  The commands that are used are those available on the
   remote system to which the user is attached.  In the sample dialogue



Kessler & Shepard                                              [Page 14]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


   below, the user attached to SMCVAX will use basic VAX/VMS commands:

   o  The "dir" command lists the files having a "COM" file extension.
   o  The "mail" command enters the MAIL system (there are no messages).
   o  "Pinging" the home host shows that it is alive!

   When finished, "logout" logs the user off the remote host; TELNET
   automatically closes the connection to the remote host and returns
   control to the local system.

   It is important to note that TELNET is a very powerful tool, one that
   may provide users with access to many Internet utilities and services
   that might not be otherwise available.  Many of these features are
   accessed by specifying a port number with the TELNET command, in
   addition to a host's address, and knowledge of port numbers provides
   another mechanism for users to access information with Telnet.

   This guide discusses several TCP/IP and Internet utilities that
   require local client software, such as Finger, Whois, Archie, and
   Gopher.  But what if your software does not include a needed client?
   In some cases, Telnet may be used to access a remote client and
   provide the same functionality.

   This is done by specifying a port number with the TELNET command.
   Just as TCP/IP hosts have a unique IP address, applications on the
   host are associated with an address, called a "port".  Finger, for
   example, is associated with the well-known port number 79.  In the
   absence of a Finger client, TELNETing to port 79 at a remote host may
   provide the same information.  You can "finger" another host with
   TELNET by using a command like:

                              TELNET host_name 79

   Other well-known TCP/IP port numbers include 20 (FTP data transfer),
   21 (FTP control), 25 (SMTP), 43 (whois), 70 (Gopher), and 185
   (KNOWBOT).

   Some services are available on the Internet using TELNET and special
   port numbers.  A geographical information database, for example, may
   be accessed by TELNETing to port 3000 at host
   "martini.eecs.umich.edu"; current weather information is available at
   port 3000 at hosts "downwind.sprl.umich.edu" and
   "wind.atmos.uah.edu".








Kessler & Shepard                                              [Page 15]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


   ==================================================================
** C:\> TELNET SMCVAX.SMCVT.EDU
   FTP Software PC/TCP tn 2.31 01/07/94 12:38
   Copyright (c) 1986-1993 by FTP Software, Inc. All rights reserved

   - Connected to St. Michael's College -

** Username: KUMQUAT
** Password:

   St. Michael's College VAX/VMS System.
   Node SMCVAX.

       Last interactive login on Thursday,  9-JUN-1994 11:55
       Last non-interactive login on Thursday,  9-JUN-1994 08:20

   Good Afternoon User KUMQUAT.  Logged in on 12-JUN-1994 at 3:27 PM.

   User [GUEST,KUMQUAT] has 4292 blocks used, 5708 available,
   of 10000 authorized and permitted overdraft of 100 blocks on $1$DIA2

** SMCVAX$ DIR *.COM
   Directory $1$DIA2:[GUEST.KUMQUAT]

   BACKUP.COM;24         24  16-JUL-1990 16:22:46.68  (RWED,RWED,RE,)
   DELTREE.COM;17         3  16-JUL-1990 16:22:47.58  (RWED,RWED,RE,)
   EXPANDZ.COM;7          2  22-FEB-1993 10:00:04.35  (RWED,RWED,RE,)
   FTSLOGBLD.COM;3        1  16-JUL-1990 16:22:48.57  (RWED,RWED,RE,)
   FTSRRR.COM;2           1  16-JUL-1990 16:22:48.73  (RWED,RWED,RE,)
   LOGIN.COM;116          5   1-DEC-1993 09:33:21.61  (RWED,RWED,RE,)
   SNOOPY.COM;6           1  16-JUL-1990 16:22:52.06  (RWED,RWED,RE,)
   SYLOGIN.COM;83         8  16-JUL-1990 16:22:52.88  (RWED,RWED,RE,RE)
   SYSHUTDWN.COM;1        0  16-JUL-1990 16:22:53.04  (RWED,RWED,RE,)
   SYSTARTUP.COM;88      15  16-JUL-1990 16:22:53.21  (RWED,RWED,RE,)
   WATCH_MAIL.COM;1     173  10-MAY-1994 09:59:52.65  (RWED,RWED,RE,)

   Total of 11 files, 233 blocks.

** SMCVAX$ MAIL
** MAIL> EXIT

** SMCVAX$ PING HILL.COM /N=5
   PING HILL.COM (199.182.20.4): 56 data bytes
   64 bytes from 199.182.20.4: icmp_seq=0 time=290 ms
   64 bytes from 199.182.20.4: icmp_seq=1 time=260 ms
   64 bytes from 199.182.20.4: icmp_seq=2 time=260 ms
   64 bytes from 199.182.20.4: icmp_seq=3 time=260 ms
   64 bytes from 199.182.20.4: icmp_seq=4 time=260 ms



Kessler & Shepard                                              [Page 16]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


   ----HILL.COM PING Statistics----
   5 packets transmitted, 5 packets received, 0% packet loss
   round-trip (ms)  min/avg/max = 260/266/290

** SMCVAX$ LOGOUT
     KUMQUAT      logged out at 12-JUN-1994 15:37:04.29

   Connection #0 closed

   C:\>
   ==================================================================

2.7. User Database Lookup Tools

2.7.1. WHOIS/NICNAME

   WHOIS and NICNAME are TCP/IP applications that search databases to
   find the name of network and system administrators, RFC authors,
   system and network points-of-contact, and other individuals who are
   registered in appropriate databases.  The original NICNAME/WHOIS
   protocol is described in RFC 954 [4].

   WHOIS may be accessed by TELNETing to an appropriate WHOIS server and
   logging in as "WHOIS" (no password is required); the most common
   Internet name server is located at the Internet Network Information
   Center (InterNIC) at "rs.internic.net".  This specific database, in
   particular, only contains INTERNET domains, IP network numbers, and
   points of contact; policies governing the InterNIC database are
   described in RFC 1400 [19].  The MILNET database resides at
   "nic.ddn.mil" and PSI's White Pages pilot service is located at
   "psi.com".

   Many software packages contain a WHOIS/NICNAME client that
   automatically establishes the TELNET connection to a default name
   server database, although users can usually specify any name server
   database that they want.

   The accompanying dialogues shows several types of WHOIS/NICNAME
   information queries.  In the session below, we request information
   about an individual (Denis Stratford) by using WHOIS locally, a
   specific domain (hill.com) by using NICNAME locally, and a high-level
   domain (edu) using TELNET to a WHOIS server.









Kessler & Shepard                                              [Page 17]

RFC 1739           Primer on Internet & TCP/IP Tools       December 1994


      ==================================================================
   ** SMCVAX$ WHOIS STRATFORD, DENIS
      Stratford, Denis (DS378)      denis@@SMCVAX.SMCVT.EDU
         St. Michael's College
         Jemery Hall, Room 274
         Winooski Park
         Colchester, VT 05439
         [phone]

         Record last updated on 02-Nov-92.
      SMCVAX$

   ** C:\> NICNAME HILL.COM
      Hill Associates (HILL-DOM)
         17 Roosevelt Highway
         Colchester, VT 05446

         Domain Name: HILL.COM

         Administrative Contact:
            Kessler, Gary C.  (GK34)  [e-mail]
            [phone]
         Technical Contact, Zone Contact:
            Monaghan, Carol A.  (CAM4)  [e-mail]
            [phone]

         Record last updated on 15-Jun-94.

         Domain servers in listed order:

         NETCOMSV.NETCOM.COM   192.100.81.101
         NS.NETCOM.COM              192.100.81.105