rfc899.txt

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

RFC 899                                                         May 1984


866     Postel       May 83      Active Users

   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet that choose to implement an Active Users
   Protocol are expected to adopt and implement this standard.  The
   Active Users service simply sends a list of the currently active
   users on the host without regard to the input.

865     Postel       May 83      Quote of the Day Protocol

   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet that choose to implement a Quote of the Day
   Protocol are expected to adopt and implement this standard.   The
   Quote of the Day service simply sends a short message without regard
   to the input.

864     Postel       May 83      Character Generator Protocol

   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet that choose to implement a Character Generator
   Protocol are expected to adopt and implement this standard.  The
   Character Generator service simply sends data without regard to the
   input.

863     Postel       May 83      Discard Protocol

   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet that choose to implement a Discard Protocol are
   expected to adopt and implement this standard.  The Discard service
   simply throws away any data it receives.

862     Postel       May 83      Echo Protocol

   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet that choose to implement a Echo Protocol are
   expected to adopt and implement this standard.  The Echo service
   simply sends back to the originating source any data it receives.

861     Postel       May 83      Telnet Extended Options - List Option

   This Telnet Option provides a mechanism for extending the set of
   possible options.  This RFC specifies a standard for the ARPA
   Internet community.  Hosts on the ARPA Internet are expected to adopt
   and implement this standard.  Obsoletes NIC 16239.








Postel & Westine                                                [page 7]



RFC 899                                                         May 1984


860     Postel       May 83      Telnet Timing Mark Option

   This Telnet Option provides a way to check the roundtrip path between
   two Telnet modules.  This RFC specifies a standard for the ARPA
   Internet community.  Hosts on the ARPA Internet are expected to adopt
   and implement this standard.  Obsoletes NIC 16238.

859     Postel       May 83      Telnet Status Option

   This Telnet Option provides a way to determine the other Telnet
   module's view of the status of options.  This RFC specifies a
   standard for the ARPA Internet community.  Hosts on the ARPA Internet
   are expected to adopt and implement this standard.  Obsoletes RFC 651
   (NIC 31154).

858     Postel       May 83      Telnet Suppress Go Ahead Option

   This Telnet Option disables the exchange of go-ahead signals between
   the Telnet modules.  This RFC specifies a standard for the ARPA
   Internet community.  Hosts on the ARPA Internet are expected to adopt
   and implement this standard.  Obsoletes NIC 15392.

857     Postel       May 83      Telnet Echo Option

   This Telnet Option enables remote echoing by the other Telnet module.
   This RFC specifies a standard for the ARPA Internet community.  Hosts
   on the ARPA Internet are expected to adopt and implement this
   standard.  Obsoletes NIC 15390.

856     Postel       May 83      Telnet Binary Transmission

   This Telnet Option enables a binary data mode between the Telnet
   modules.  This RFC specifies a standard for the ARPA Internet
   community.  Hosts on the ARPA Internet are expected to adopt and
   implement this standard.  Obsoletes NIC 15389.

855     Postel       May 83      Telnet Option Specifications

   This memo specifies the general form for Telnet options and the
   directions for their specification.  This RFC specifies a standard
   for the ARPA Internet community.  Hosts on the ARPA Internet are
   expected to adopt and implement this standard.  Obsoletes RFC 651,
   NIC 18640.









Postel & Westine                                                [page 8]



RFC 899                                                         May 1984


854     Postel       May 83      Telnet Protocol Specifications

   This is the specification of the Telnet protocol used for remote
   terminal access in the ARPA Internet.  The purpose of the TELNET
   Protocol is to provide a fairly general, bi-directional, eight-bit
   byte oriented communications facility.  Its primary goal is to allow
   a standard method of interfacing terminal devices and
   terminal-oriented processes to each other.  It is envisioned that the
   protocol may also be used for terminal-terminal communication
   ("linking") and process-process communication (distributed
   computation).   This RFC specifies a standard for the ARPA Internet
   community.  Hosts on the ARPA Internet are expected to adopt and
   implement this standard.  Obsoletes NIC 18639.

853     Not issued yet.

852     Malis        Apr 83      The ARPANET Short Blocking Feature

   This RFC specifies the ARPANET Short Blocking Feature, which will
   allow ARPANET  hosts to optionally shorten the IMP's host blocking
   timer.  This Feature is a replacement of the ARPANET non-blocking
   host interface, which was never implemented, and will be available to
   hosts using either the 1822 or 1822L Host Access Protocol.  This RFC
   is also being presented as a solicitation of comments on the Short
   Blocking Feature, especially from host network software implementers
   and maintainers.

851     Malis        Apr 83      The ARPANET 1822L Host Access Protocol

   This RFC specifies the ARPANET 1822L Host Access Protocol, which is a
   successor to the existing 1822 Host Access Protocol.  1822L allows
   ARPANET hosts to use logical names as well as 1822's physical port
   locations to address each other.  This RFC is also being presented as
   a solicitation of comments on 1822L, especially from host network
   software implementers and maintainers.  Obsoletes RFC 802.

850     Horton       Jun 83      Standard for Interchange of USENET
                                 Messages

   This memo is distributed as an RFC only to make this information
   easily accessible to researchers in the ARPA community.  It does not
   specify an Internet standard.  This RFC defines the standard format
   for interchange of Network News articles among USENET sites.  It
   describes the format for articles themselves, and gives partial
   standards for transmission of news.  The news transmission is not
   entirely standardized in order to give a good deal of flexibility to
   the individual hosts to choose transmission hardware and software,
   whether to batch news and so on.




Postel & Westine                                                [page 9]



RFC 899                                                         May 1984


849     Crispin      May 83      Suggestions for Improved Host Table
                                 Distribution

   This RFC actually is a request for comments.  The issue dealt with is
   that of a naming registry update procedure, both as exists currently
   and what could exist in the future.  None of the proposed solutions
   are intended as standards at this time; rather it is hoped that a
   general consensus will emerge as the appropriate solution, leaving
   eventually to the adoption of standards.

848     Smallberg    Mar 83      Who provides the "Little" TCP Services?

   This RFC lists those hosts which provide any of these "little" TCP
   services:  The list of hosts were taken from the NIC hostname table
   of 24-Feb-83.  The tests were run on February 23 and 24, and March 3
   and 5 from ISI-VAXA.ARPA.

847     Westine      Feb 83      Summary of Smallberg Surveys

   This is a summary of the surveys of Telnet, FTP and Mail (SMTP)
   servers conducted by David Smallberg in December 1982, January and
   February 1983 as reported in RFC 832-843, 845-846.  This memo
   extracts the number of hosts that accepted the connection to their
   server for each of Telnet, FTP, and SMTP, and compares it to the
   total host in the Internet (not counting TACs or ECHOS).

846     Smallberg    Feb 83      Who Talks TCP? -- Survey of 22 February
                                 1983

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 18-Feb-83.  The tests were run on 22-Feb-83
   from ISI-VAXA.ARPA.

845     Smallberg    Feb 83      Who Talks TCP? -- Survey of 15 February
                                 1983

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 3-Feb-83.  The tests were run on 15-Feb-83
   from ISI-VAXA.ARPA.











Postel & Westine                                               [page 10]



RFC 899                                                         May 1984


844     Clements    Feb 83      Who Talks ICMP, too?  Survey of 18
                                 February 1983

   This survey determines how many hosts are able to respond to TELENET
   connections from a user at a class C site.  This requires, in
   addition to IP and TCP, participation in gateway routing via ICMP and
   handling of Class C addresses.  The list of hosts was taken from RFC
   843, extracting only those hosts which are listed there as accepting
   TELNET connection.  The tests were run on 18-Feb-83.

843     Smallberg    Feb 83      Who Talks TCP? -- Survey of 8 February
                                 1983

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 3-Feb-83.  The tests were run on 8-Feb-83
   and on 9-Feb-83 from ISI-VAXA.ARPA.

842     Smallberg    Feb 83      Who Talks TCP? -- Survey of 1 February
                                 1983

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 28-Jan-83.  The tests were run on 1-Feb-83
   and on 2-Feb-83 ISI-VAXA.ARPA.

841     FIPS PUB 98  Jan 83      Specification for Message Format for
                                 Computer Based Message Systems

   This RFC is FIPS 98.  The purpose of distributing this document as an
   RFC is to make it easily accessible to the ARPA research community.
   This RFC does not specify a standard for the ARPA Internet.
   Obsoletes RFC 806.

840     Postel       Apr 83      Official Protocols

   This RFC has been revised, see RFC 880.

839     Smallberg    Jan 83      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 31-Dec-82.  The tests were run on
   25-Jan-83.








Postel & Westine                                               [page 11]



RFC 899                                                         May 1984


838     Smallberg    Jan 83      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 31-Dec-82.  The tests were run on
   18-Jan-83.

837     Smallberg    Jan 83      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 31-Dec-82.  The tests were run on
   11-Jan-83.

836     Smallberg    Jan 83      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 20-Dec-82.  The tests were run on 4-Jan-83
   through 5-Jan-83.

835     Smallberg    Dec 82      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 2-Dec-82.  The tests were run on 28-Dec-82
   through 5-Jan-83.

834     Smallberg    Dec 82      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 2-Dec-82.  The tests were run on 22-Dec-82.

833     Smallberg    Dec 82      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 2-Dec-82.  The tests were run on 14-Dec-82.

832     Smallberg    Dec 82      Who Talks TCP?

   This RFC is a survey of hosts to identify the implementation status
   of Telnet, FTP, and Mail on TCP.  The list of hosts was taken from
   the NIC hostname table of 2-Dec-82.  The tests were run on 7-Dec-82.







Postel & Westine                                               [page 12]