rfc899.txt

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

RFC 899                                                         May 1984


831     Braden       Dec 82      Backup Access to the European Side of
                                 SATNET

   The purpose of this RFC is to focus discussion on a particular
   Internet problem:  a backup path for software maintenance of the
   European sector of the Internet, for use when SATNET is partitioned.
   We propose a mechanism, based upon the Source Routing option of IP,
   to reach European Internet sites via the VAN Gateway and UCL.  This
   proposal is not intended as a standard at this time.

830     Zaw-Sing Su  Oct 82      A Distributed System for Internet Name
                                 Service

   This RFC proposes a distributed name service for DARPA Internet.  Its
   purpose is to focus discussion on the subject.  It is hoped that a
   general consensus will emerge leading eventually to the adoption of
   standards.

829     Cerf         Oct 82      Packet Satellite Technology Reference
                                 Sources

   This RFC describes briefly the packet satellite technology developed
   by the Defense Advanced Research Projects Agency and several other
   participating organizations in the U.K. and Norway and provides a
   bibliography of relevant papers for researchers interested in
   experimental and operational experience with this dynamic
   satellite-sharing technique.

828     Owen         Aug 82      Data Communications:  IFIP's
                                 International "Network" of Experts

   This RFC is distributed to inform the ARPA Internet community of the
   activities of the IFIP technical committee on Data Communications,
   and to encourage participation in those activities.

827     Rosen        Oct 82      Exterior Gateway Protocol (EGP)

   This RFC is proposed to establish a standard for Gateway to Gateway
   procedures that allow the Gateways to be mutually suspicious.  This
   document is a DRAFT for that standard.  Your comments are strongly
   encouraged.

826     Plummer      Nov 82      An Ethernet Address Resolution Protocol

   The purpose of this RFC is to present a method of Converting Protocol
   Addresses (e.g., IP addresses) to Local Network Addresses (e.g.,
   Ethernet addresses).  This is an issue of general concern in the ARPA
   Internet Community at this time.  The method proposed here is
   presented for your consideration and comment.  This is not the
   specification of an Internet Standard.


Postel & Westine                                               [page 13]



RFC 899                                                         May 1984


825     Postel       Nov 82      Request for Comments on Requests for
                                 Comments

   This RFC is intended to clarify the status of RFCs and to provide
   some guidance for the authors of RFCs in the future.  It is in a
   sense a specification for RFCs.

824     MacGregor    Aug 82      The Cronus Virtual Local Network

   The purpose of this note is to describe the CRONUS Virtual Local
   Network, especially the addressing related features.  These features
   include a method for mapping between Internet Addresses and Local
   Network addresses.  This is a topic of current concern in the ARPA
   Internet community.  This note is intended to stimulate discussion.
   This is not a specification of an Internet Standard.

823     Hinden       Sep 82      The DARPA Internet Gateway

   This RFC is a status report on the Internet Gateway developed by BBN.
   It describes the Internet Gateway as of September 1982.  This memo
   presents detailed descriptions of message formats and gateway
   procedures, however, this is not an implementation specification, and
   such details are subject to change.

822     Crocker      Aug 82      Standard for the Format of ARPA
                                 Internet Text Messages

   This document revises the specifications in RFC 733, in order to
   serve the needs of the larger and more complex ARPA Internet.  Some
   of RFC 733's features failed to gain adequate acceptance.  In order
   to simplify the standard and the software that follows it, these
   features have been removed.  A different addressing scheme is used,
   to handle the case of internetwork mail; and the concept of
   re-transmission has been introduced.  Obsoletes RFC 733, NIC 41952.

821     Postel       Aug 82      Simple Mail Transfer Protocol

   The objective of Simple Mail Transfer Protocol (SMTP) is to transfer
   mail reliably and efficiently.  SMTP is independent of the particular
   transmission subsystem and requires only a reliable ordered data
   stream channel.  Obsoletes RFC 788, 780, and 772.

820     Postel       Jan 82      Assigned Numbers

   This RFC is an old version, see RFC 870.







Postel & Westine                                               [page 14]



RFC 899                                                         May 1984


819     Zaw-Sing Su  Aug 82      The Domain Naming Convention for
                                 Internet User Applications

   This RFC is an attempt to clarify the generalization of the Domain
   Naming Convention, the Internet Naming Convention, and to explore the
   implications of its adoption for Internet name service and user
   applications.

818     Postel       Nov 82      The Remote User Telnet Service

   This RFC is the specification of an application protocol.  Any host
   that implements this application level service must follow this
   protocol.

817     Clark        Jul 82      Modularity and Efficiency in Protocol
                                 Implementation

   This RFC will discuss some of the commonly encountered reasons why
   protocol implementations seem to run slowly.

816     Clark        Jul 82      Fault Isolation and Recovery

   This RFC describes the portion of fault isolation and recovery which
   is the responsibility of the host.

815     Clark        Jul 82      IP Datagram Reassembly Algorithms

   This RFC describes an alternate approach of dealing with reassembly
   which reduces the bookkeeping problem to a minimum, and requires only
   one buffer for storage equal in size to the final datagram being
   reassembled, which can reassemble a datagram from any number of
   fragments arriving in any order with any possible pattern of overlap
   and duplication, and which is appropriate for almost any sort of
   operating system.

814     Clark        Jul 82      Name, Addresses, Ports, and Routes

   This RFC gives suggestions and guidance for the design of the tables
   and algorithms necessary to keep track of these various sorts of
   identifiers inside a host implementation of TCP/IP.

813     Clark        Jul 82      Window and Acknowledgement Strategy in
                                 TCP

   This RFC describes implementation strategies to deal with two
   mechanisms in TCP, the window and the acknowledgement.  It also
   presents a particular set of algorithms which have received testing
   in the field, and which appear to work properly with each other.
   With more experience, these algorithms may become part of the formal
   specification, until such time their use is recommended.


Postel & Westine                                               [page 15]



RFC 899                                                         May 1984


812     Harrenstien   Mar 82     NICNAME/WHOIS

   This RFC gives a description of what the NICNAME/WHOIS Server is and
   how to access it.  This server together with the corresponding
   Identification Data Base provides online directory look-up equivalent
   to the ARPANET Directory.

811     Harrenstien   Mar 82      Hostnames Server

   This RFC gives a description of what the Hostnames Server is and how
   to access it.  The function of this particular server is to deliver
   machine-readable name/address information describing networks,
   gateways, hosts, and eventually domains, within the internet
   environment.

810     Feinler      Mar 82      DoD Internet Host Table Specification

   This RFC specifies a new host table format applicable to both ARPANET
   and Internet needs.  In addition to host name to host address
   translation and selected protocol information, we have also included
   network and gateway name to address correspondence, and host
   operating system information.  This RFC obsoletes the host table
   described in RFC 608.

809     Chang        Feb 82      UCL Facsimile System

   This RFC describes the features of the computerised facsimile system
   developed in the Department of Computer Science at UCL.  First its
   functions are considered and the related experimental work are
   reported.  Then the disciplines for system design are discussed.
   Finally, the implementation of the system are described, while
   detailed description are given as appendices.

808     Postel       Mar 82      Summary of Computer Mail Services
                                 Meeting Held at BBN on 10 January 1979

   This RFC is a very belated attempt to document a meeting that was
   held three years earlier to discuss the state of computer mail in the
   ARPA community and to reach some conclusions to guide the further
   development of computer mail systems such that a coherent total mail
   service would continue to be provided.

807     Postel       Feb 82      Multimedia Mail Meeting Notes

   This RFC consists of notes from a meeting held at USC Information
   Sciences Institute on the 12th of January to discuss common interests
   in multimedia computer mail issues and to agree on some specific
   initial experiments.




Postel & Westine                                               [page 16]



RFC 899                                                         May 1984


806     NBS          Sep 81      Specification for Message Format for
                                 Computer Based Message Systems

   This RFC deals with Computer Based Message systems which provides a
   basis for interaction between different CBMS by defining the format
   of messages passed between them.  This RFC is replaced by RFC 841.

805     Postel       Feb 82      Computer Mail Meeting Notes

   This RFC consists of notes from a meeting that was held at USC
   Information Sciences Institute on 11 January 1982, to discuss
   addressing issues in computer mail. The major conclusion reached at
   the meeting is to extend the "username@hostname" mailbox format to
   "[e-mail]", where the domain itself can be further
   strutured.

804     CCITT        Jan 82      CCITT Draft Recommendation T.4

   This is the CCITT standard for group 3 facsimile encoding.  This is
   useful for data compression of bit map data.

803     Agarwal      Nov 81      Dacom 450/500 Facsimile Data
                                 Transcoding

   The first part of this RFC describes in detail the Dacom 450 data
   compression algorithms and is an update and correction to an earlier
   memorandum.  The second part of this RFC describes briefly the Dacom
   500 data compression algorithm as used by the INTELPOST
   electronic-mail network under development by the US Postal Service
   and several foreign administrators.

802     Malis        Nov 81      The ARPANET 1822L Host Access Protocol

   This document proposed two major changes to the current ARPANET host
   access protocol.  The first change will allow hosts to use logical
   addressing (i.e., host addresses that are independent of their
   physical location on the ARPANET) to communicate with each other, and
   the second will allow a host to shorten the amount of time that it
   may be blocked by its IMP after it presents a message to the network
   (currently, the IMP can block further input from a host for up to 15
   seconds).  See RFCs 852 and 851.

801     Postel       Nov 81      NCP/TCP Transition Plan

   This RFC discusses the conversion of hosts from NCP to TCP.  And
   making available the principle services:  Telnet, File Transfer, and
   Mail.  These protocols allow all hosts in the ARPA community to share
   a common interprocess communication environment.




Postel & Westine                                               [page 17]



RFC 899                                                         May 1984


800     Postel       Nov 82      Requests for Comments Summary

   This RFC is a slightly annotated list of the 100 RFCs from RFC 700
   through RFC 799.  This is a status report on these RFCs.
















































Postel & Westine                                               [page 18]