rfc999.txt

RFC 相关的技术文档

   Domain Specific Part (DSP) of an NSAP address.  This RFC specifies the
   way in which the DSP may be constructed so as to facilitate efficient
   address assignment.  This RFC is for informational purposes only and its
   distribution is unlimited and does not specify a standard of the
   ARPA-Internet.

981     Mills        Mar 86      An Experimental Multiple-Path Routing
                                 Algorithm

   This document introduces wiretap algorithms, a class of experimental,
   multiple routing algorithms that compute quasi-optimum routes for
   stations sharing a packet-radio broadcast channel.  The primary route (a
   minimum-distance path), and additional paths ordered by distance, which
   serve as alternate routes should the primary route fail, are computed.
   This prototype is presented as an example of a class of routing
   algorithms and data-base management techniques that may find wider
   application in the Internet community.  Discussions and suggestions for
   improvements are welcomed.

980     Jacobsen     Mar 86      Protocol Document Order Information

   This RFC indicates how to obtain various protocol documents used in the
   DARPA research community.  Included is an overview of the new 1985 DDN
   Protocol Handbook and available sources for obtaining related documents
   (such as DOD, ISO, and CCITT).



9

9Westine & Postel                                                [Page 5]

RFC 999                                                       March 1987


979     Malis        Mar 86      PSN End-to-End Functional Specification

   This memo is an updated version of BBN Report 5775, "End-to-End
   Functional Specification and describes important changes to the
   functionality of the interface between a Host and the PSN, and should be
   carefully reviewed by anyone involved in supporting a host on either the
   ARPANET or MILNET".  The new End-to-End protocol (EE) is being developed
   in order to correct a number of deficiencies in the old EE, to improve
   its performance and overall throughput, and to better equip the Packet
   Switch Node (PSN, also known as the IMP) to support its current and
   anticipated host population.

978     Reynolds     Feb 86      Voice File Interchange Protocol (VFIP)

   The purpose of the Voice File Interchange Protocol (VFIP) is to permit
   the interchange of various types of speech files between different
   systems in the ARPA-Internet community.  Suggestions for improvement are
   encouraged.

977     Kantor       Feb 86      Network News Transfer Protocol

   NNTP specifies a protocol for the distribution, inquiry, retrieval, and
   posting of news articles using a reliable stream-based transmission of
   news among the ARPA-Internet community.  NNTP is designed so that news
   articles are stored in a central database allowing a subscriber to
   select only those items he wishes to read.  Indexing, cross-referencing,
   and expiration of aged messages are also provided. This RFC suggests a
   proposed protocol for the ARPA-Internet community, and requests
   discussion and suggestions for improvements.

976     Horton       Feb 86      UUCP Mail Interchange Format Standard

   This document defines the standard format for the transmission of mail
   messages between computers in the UUCP Project.  It does not however,
   address the format for storage of messages on one machine, nor the lower
   level transport mechanisms used to get the date from one machine to the
   next.  It represents a standard for conformance by hosts in the UUCP
   zone.

975     Mills        Feb 86      Autonomous Confederations

   This RFC proposes enhancements to the Exterior Gateway Protocol (EGP) to
   support a simple, multiple-level routing capability while preserving the
   robustness features of the current EGP model.  The enhancements
   generalize the concept of core system to include multiple communities of
   autonomous systems, called autonomous confederations.  Discussion and
   suggestions for improvement are requested.







Westine & Postel                                                [Page 6]

RFC 999                                                       March 1987


974     Partridge    Jan 86      Mail Routing and the Domain System

   This RFC presents a description of how mail systems on the Internet are
   expected to route messages based on information from the domain system.
   This involves a discussion of how mailers interpret MX RRs, which are
   used for message routing.

973     Mockapetris  Jan 86      Domain System Changes and Observations

   This RFC documents updates to Domain Name System specifications RFC-882
   and RFC-883, suggests some operational guidelines, and discusses some
   experiences and problem areas in the present system.

972     Wancho       Jan 86      Password Generator Protocol

   This RFC specifies a standard for the ARPA Internet community.  The
   Password Generator Service (PWDGEN) provides a set of six randomly
   generated eight-character "words" with a reasonable level of
   pronounceability, using a multi-level algorithm.  Hosts on the ARPA
   Internet that choose to implement a password generator service are
   expected to adopt and implement this standard.

971     DeSchon      Dec 85      A Survey of Data Representation
                                 Standards

   This RFC is a comparison of several data representation standards that
   are currently in use.  The standards discussed are the CCITT X.409
   recommendation, the NBS Computer Based Message System (CBMS) standard,
   DARPA Multimedia Mail system, the Courier remote procedure call
   protocol, and the SUN Remote Procedure Call package.  No proposals in
   this document are intended as standards for the ARPA-Internet at this
   time.  Rather, it is hoped that a general consensus will emerge as to
   the appropriate approach to a data representation standard, leading
   eventually to the adoption of an ARPA-Internet standard.

970     Nagle        Dec 85      On Packet Switches With Infinite
                                 Storage

   The purpose of this RFC is to focus discussion on a particular problem
   in the ARPA-Internet and possible methods of solution.  Most prior work
   on congestion in datagram systems focuses on buffer management.  In this
   memo the case of a packet switch with infinite storage is considered.
   Such a packet switch can never run out of buffers.  It can, however,
   still become congested.  The meaning of congestion in an
   infinite-storage system is explored.  An unexpected result is found that
   shows a datagram network with infinite storage, first-in-first-out
   queuing, at least two packet switches, and a finite packet lifetime
   will, under overload, drop all packets.  By attacking the problem of
   congestion for the infinite-storage case, new solutions applicable to
   switches with finite storage may be found.  No proposed solutions this
   document are intended as standards for the ARPA-Internet at this time.



Westine & Postel                                                [Page 7]

RFC 999                                                       March 1987


969     Clark        Dec 85      NETBLT: A Bulk Data Transfer Protocol

   This RFC suggests a proposed protocol for the ARPA-Internet community,
   and requests discussion and suggestions for improvements.  This is a
   preliminary discussion of the Network Block Transfer (NETBLT) protocol.
   NETBLT is intended for the rapid transfer of a large quantity of data
   between computers.  It provides a transfer that is reliable and flow
   controlled, and is structured to provide maximum throughput over a wide
   variety of networks.  This description is published for discussion and
   comment, and does not constitute a standard.  As the proposal may
   change, implementation of this document is not advised.  See RFC-998.

968     Cerf         Dec 85      'Twas the Night Before Start-up'

   This memo discusses problems that arise and debugging techniques used in
   bringing a new network into operation.

967     Padlipsky    Dec 85      All Victims Together

   This RFC proposes a new set of RFCs on how the networking code is
   integrated with various operating systems.  It appears that this topic
   has not received enough exposure in the literature. Comments and
   suggestions are encouraged.

966     Deering      Dec 85      A Multicast Extension to the Internet
                                 Protocol

   This RFC defines a model of service for Internet multicasting and
   proposes an extension to the Internet Protocol (IP) to support such a
   multicast service.  Discussion and suggestions for improvements are
   requested.  See RFC-988.

965     Aguilar      Dec 85      A Format for a Graphical Communication
                                 Protocol

   This RFC describes the requirements for a graphical format on which to
   base a graphical on-line communication protocol, and proposes an
   Interactive Graphical Communication Format using the GKSM session
   metafile.  We hope this contribution will encourage the discussion of
   multimedia data exchange and the proposal of solutions.

964     Sidhu        Nov 85      Some Problems with the Specification of
                                 the Military Standard Transmission
                                 Control Protocol

   The purpose of this RFC is to provide helpful information on the
   Military Standard Transmission Control Protocol (MIL-STD-1778) so that
   one can obtain a reliable implementation of this protocol standard.
   This note points out three errors with this specification.  This note
   also proposes solutions to these problems.




Westine & Postel                                                [Page 8]

RFC 999                                                       March 1987


963     Sidhu        Nov 85      Some Problems with the Specification of
                                 the Military Standard Internet Protocol

   The purpose of this RFC is to provide helpful information on the
   Military Standard Internet Protocol (MIL-STD-1777) so that one can
   obtain a reliable implementation of this protocol.  This paper points
   out several problems in this specification.  This note also proposes
   solutions to these problems.

962     Padlipsky    Nov 85      TCP-4 Prime

   This memo is in response to Bob Braden's call for a transaction oriented
   protocol (RFC-955), and continues the discussion of a possible
   transaction oriented transport protocol.  This memo does not propose a
   standard.

961     Reynolds     Dec 85      Official ARPA-Internet Protocols

   This memo identifies the documents specifying the official protocols
   used in the Internet, and comments on any revisions or changes planned.
   This edition of the Official Protocols updates and obsoletes RFC-944.
   This memo is an official status report on the protocols used in the
   ARPA-Internet community.  See RFC-991.

960     Reynolds     Dec 85      Assigned Numbers

   This memo documents the currently assigned values from several series of
   numbers used in network protocol implementations.  This edition of
   Assigned Numbers updates and obsoletes RFC-943.  This memo is an
   official status report on the numbers used in protocols in the
   ARPA-Internet community.  See RFC-990 and 997.

959     Postel       Oct 85      File Transfer Protocol (FTP)

   This memo is the official specification of the File Transfer Protocol
   (FTP) for the DARPA Internet community.  The primary intent is to
   clarify and correct the documentation of the FTP specification, not to
   change the protocol.  The following new optional commands are included
   in this edition of the specification:  Change to Parent Directory
   (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory
   (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST).
   Note that this specification is compatible with the previous edition.

958     Mills        Sep 85      Network Time Protocol (NTP)

   This document describes the Network Time Protocol (NTP), a protocol for
   synchronizing a set of network clocks using a set of distributed clients