rfc801.txt

RFC 相关的技术文档

RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


   Suppose a user on a NCP-only non-SMTP host wishes to send a message
   to a user on an TCP-only host.  Suppose the destination user is
   "Smith" and the host is "ABC-X".

      1)  Use the local mail composition program to prepare the message.
          Address the message to "Smith.ABC-X@FORWARDER".  Tell the
          composition program to queue the message.

      2)  The background mailer-daemon finds my queued message.  It
          sends the message to host FORWARDER using the old FTP/NCP mail
          procedure.

      3)  The special forwarder host converts the "user name" supplied
          by the FTP/NCP mail procedure (in the MAIL or MLFL command) to
          "Smith@ABC-X" (in the SMTP RCTP command) and queues the
          message to be processed by the SMTP mailer-daemon program on
          this same host.  No conversion of the mailbox addresses in
          made in thr message header or body.

      4)  The SMTP mailer-daemon program on the forwarder host finds
          this queued message and checks the destination host name in a
          table to find the internet address.  It finds the destination
          address and send the mail using the SMTP procedure.

         +---------+          +---------+          +---------+
         |         |   FTP    |         |   SMTP   |         |
         | Source  |<-------->|Forwarder|<-------->|  Dest.  |
         |  Host   |   NCP    |   Host  |   TCP    |   Host  |
         +---------+          +---------+          +---------+






















Postel                                                         [Page 15]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


APPENDIX D.  IP/TCP Implementation Status

   Please note that the information in this section may become quickly
   dated.  Current information on the status of IP and TCP
   implementations can be obtained from the file
   <INTERNET-NOTEBOOK>TCP-IP-STATUS.TXT on ISIF.

   BBN C70 UNIX

      Date:  18 Nov 1981
      From:  Rob Gurwitz <gurwitz at BBN-RSM>

      The C/70 processor is a BBN-designed system with a native
      instruction set oriented toward executing the C language.  It
      supports UNIX Version 7 and provides for user processes with a
      20-bit address space.  The TCP/IP implementation for the C/70 was
      ported from the BBN VAX TCP/IP, and shares all of its features.

      This version of TCP/IP is running experimentally at BBN, but is
      still under development.  Performance tuning is underway, to make
      it more compatible with the C/70's memory management system.

   BBN GATEWAYS

      Date:  19 Nov 1981
      From:  Alan Sheltzer <sheltzer at BBN-UNIX>

      In an effort to provide improved service in the gateways
      controlled by BBN, a new gateway implementation written in
      macro-11 instead of BCPL is being developed.  The macro-11 gateway
      will provide users with internet service that is functionally
      equivalent to that provided by the current BCPL gateways with some
      performance improvements.

         ARPANET/SATNET gateway at BBN (10.3.0.40),
         ARPANET/SATNET gateway at NDRE (10.3.0.41),
         Comsat DCN Net/SATNET gateway at COMSAT (4.0.0.39),
         SATNET/UCL Net/RSRE Net gateway at UCL (4.0.0.60),
         PR Net/RCC Net gateway at BBN (3.0.0.62),
         PR Net/ARPANET gateways at SRI (10.3.0.51, 10.1.0.51),
         PR Net/ARPANET gateway at Ft. Bragg (10.0.0.38).










Postel                                                         [Page 16]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


   BBN H316 and C/30 TAC

      Date:  18 November 1981
      From:  Bob Hinden <Hinden@BBN-UNIX>

      The Terminal Access Controller (TAC) is user Telnet host that
      supports TCP/IP and NCP host to host protocols.  It runs in 32K
      H-316 and 64K C/30 computers.  It supports up to 63 terminal
      ports.  It connects to a network via an 1822 host interface.

      For more information on the TAC's design, see IEN-166.

   BBN HP-3000

      Date:  14 May 1981
      From:  Jack Sax <sax@BBN-UNIX>

      The HP3000 TCP code is in its final testing stages.  The code
      includes under the MPE IV operating system as a special high
      priority process.  It is not a part of the operating system kernel
      because MPE IV has no kernel.  The protocol process includes TCP,
      IP, 1822 and a new protocol called HDH which allows 1822 messages
      to be sent over HDLC links.  The protocol process has about 8k
      bytes of code and at least 20k bytes of data depending on the
      number of buffers allocated.

      In addition to the TCP the HP3000 has user and server TELNET as
      well as user FTP.  A server FTP may be added later.

      A complete description of the implementation software can be found
      in IEN-167.

   BBN PDP-11 UNIX

      Date:  14 May 1981
      From:  Jack Haverty <haverty@BBN-UNIX>

      This TCP implementation was written in C.  It runs as a user
      process in version 6 UNIX, with modifications added by BBN for
      network access.  It supports user and server Telnet.

      This implementation was done under contract to DCEC.  It is
      installed currently on several PDP-11/70s and PDP-11/44s.  Contact
      Ed Cain at DCEC <cain@EDN-UNIX> for details of further
      development.






Postel                                                         [Page 17]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


   BBN TENEX & TOPS20

      Date:  23 Nov 1981
      From:  Charles Lynn <CLynn@BBNA>

      TCP4 and IP4 are available for use with the TENEX operating system
      running on a Digital KA10 processor with BBN pager.  TCP4 and IP4
      are also available as part of TOPS20 Release 3A and Release 4 for
      the Digital KL10 and KL20 processors.

      Above the IP layer, there are two Internet protocols within the
      monitor itself (TCP4 and GGP).  In addition up to eight (actually
      a monitor assembly parameter) protocols may be implemented by
      user-mode programs via the "Internet User Queue" interface. The
      GGP or Gateway-Gateway Protocol is used to receive advice from
      Internet Gateways in order to control message flow.  The GGP code
      is in the process of being changed and the ICMP protocol is being
      added.

      TCP4 is the other monitor-supplied protocol and it has two types
      of connections -- normal data connections and "TCP Virtual
      Terminal" (TVT) connections.  The former are used for bulk data
      transfers while the latter provide terminal access for remote
      terminals.

      Note that TVTs use the standard ("New") TELNET protocol.  This is
      identical to that used on the ARPANET with NCP and in fact, is
      largely implemented by the same code.

      Performance improvements, support for the new address formats, and
      User and Server FTP processes above the TCP layer are under
      development.

   BBN VAX UNIX

      Date:  18 Nov 1981
      From:  Rob Gurwitz <gurwitz at BBN-RSM>

      The VAX TCP/IP implementation is written in C for Berkeley 4.1BSD
      UNIX, and runs in the UNIX kernel.  It has been run on VAX 11/780s
      and 750s at several sites, and is due to be generally available in
      early 1982.

      The implementation conforms to the TCP and IP specifications (RFC
      791, 793).  The implementation supports the new extended internet
      address formats, and both GGP and ICMP.  It also supports multiple
      network access protocols and device drivers.  Aside from ARPANET
      1822 and the ACC LH/DH-11 driver, experimental drivers have also
      been developed for ETHERNET.  There are user interfaces for


Postel                                                         [Page 18]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


      accessing the IP and local network access layers independent of
      the TCP.

      Higher level protocol services include user and server TELNET,
      MTP, and FTP, implemented as user level programs.  There are also
      tools available for monitoring and recording network traffic for
      debugging purposes.

      Continuing development includes performance enhancements.  The
      implementation is described in IEN-168.

   COMSAT

      Date:  30 Apr 1980
      From:  Dave Mills <Mills@ISIE>
      

      The TCP/IP implementation here runs in an LSI-11 with a homegrown
      operating system compatible in most respects to RT-11. Besides the
      TCP/IP levels the system includes many of the common high-level
      protocols used in the ARPANET community, such as TELNET, FTP and
      XNET.

   DCEC PDP-11 UNIX

      Date:  23 Nov 1981
      From:  Ed Cain <cain@EDN-UNIX>

      This TCP/IP/ICMP implementation runs as a user process in version
      6 UNIX, with modifications obtained from BBN for network access.
      IP reassembles fragments into datagrams, but has no separate IP
      user interface.  TCP supports user and server Telnet, echo,
      discard, internet mail, and a file transfer service. ICMP
      generates replies to Echo Requests, and sends Source-Quench when
      reassembly buffers are full.

      Hardware - PDP-11/70 and PDP-11/45 running UNIX version 6, with
      BBN IPC additions.  Software - written in C, requiring 25K
      instruction space, 20K data space.  Supports 10 connections.












Postel                                                         [Page 19]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


   DTI VAX

      Date:  15 May 1981
      From:  Gary Grossman <grg@DTI)>

      Digital Technology Incorporated (DTI) IP/TCP for VAX/VMS

      The following describes the IP and TCP implementation that DTI
      plans to begin marketing in 4th Quarter 1981 as part of its
      VAX/VMS network software package.

      Hardware:  VAX-11/780 or /750.  Operating System:  DEC standard
      VAX/VMS Release 2.0 and above.  Implementation Language:   Mostly
      C, with some MACRO.  Connections supported:  Maximum of 64.

      User level protocols available:  TELNET, FTP, and MTP will be
      available. (The NFE version uses AUTODIN II protocols.)

   MIT MULTICS

      Date:  13 May 1981
      From:  Dave Clark <Clark@MIT-Multics>

      Multics TCP/IP is implemented in PL/1 for the HISI 68/80. It has
      been in experimental operation for about 18 months; it can be
      distributed informally as soon as certain modifications to the
      system are released by Honeywell.  The TCP and IP package are
      currently being tuned for performance, especially high throughput
      data transfer.

      Higher level services include user and server telnet, and a full
      function MTP mail forwarding package.

      The TCP and IP contain good logging and debugging facilities,
      which have proved useful in the checkout of other implementations.
      Please contact us for further information.

   SRI LSI-11

      Date:  15 May 1981
      From:  Jim Mathis <mathis.tscb@Sri-Unix>

      The IP/TCP implementation for the Packet Radio terminal interface
      unit is intended to run on an LSI-11 under the MOS real-time
      operating system.  The TCP is written in MACRO-11 assembler
      language.  The IP is currently written in assembler language; but
      is being converted into C. There are no plans to convert the TCP
      from assembler into C.



Postel                                                         [Page 20]


RFC 801                                                    November 1981
                                                 NCP/TCP Transition Plan


      The TCP implements the full specification.  The TCP appears to be
      functionally compatible with all other major implementations.  In
      particular, it is used on a daily basis to provide communications
      between users on the Ft. Bragg PRNET and ISID on the ARPANET.

      The IP implementation is reasonably complete, providing
      fragmentation and reassembly; routing to the first gateway; and a
      complete host-side GGP process.

      A measurement collection mechanism is currently under development
      to collect TCP and IP statistics and deliver them to a measurement
      host for data reduction.

   UCLA IBM

      Date:  13 May 1981
      From:  Bob Braden <Braden@ISIA>

      Hardware:  IBM 360 or 370, with a "Santa Barbara" interface to the
      IMP.

      Operating System:  OS/MVS with ACF/VTAM.  An OS/MVT version is
      also available.  The UCLA NCP operates as a user job, with its own
      internal multiprogramming and resource management mechanisms.

      Implementation Language:  BAL (IBM's macro assembly language)

      User-Level Protocols Available:  User and Server Telnet























Postel                                                         [Page 21]