rfc1099.txt

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

ISO ES-IS routing protocols within the NSFNET backbone network.


1073    Waitzman     Oct 88      Telnet Window Size Option

This RFC describes a proposed Telnet option to allow a client to convey
window size to a Telnet server.


1072    Jacobson     Oct 88      TCP Extensions for Long-Delay Paths

This RFC proposes a set of extensions to the TCP protocol to provide
efficient operation over a path with a high bandwidth*delay product.
These extensions are not proposed as an Internet standard at this time.
Instead, they are intended as a basis for further experimentation and
research on transport protocol performance.


1071    Braden       Aug 88      Computing the Internet Checksum

This RFC summarizes techniques and algorithms for efficiently computing
the Internet checksum.  It is not a standard, but a set of useful
implementation techniques.





Reynolds                                                        [Page 6]

RFC 1099                  Summary of 1000-1099             December 1991


1070    Hagens       Feb 89      Use of the Internet as a Subnetwork
                                 for Experimentation with the OSI
                                 Network Layer

This RFC proposes a scenario for experimentation with the International
Organization for Standardization (ISO) Open Systems Interconnection
(OSI) network layer protocols over the Internet and requests discussion
and suggestions for improvements to this scenario.  This RFC also
proposes the creation of an experimental OSI internet.  To participate
in the experimental OSI internet, a system must abide by the agreements
set forth in this RFC.


1069    Callon       Feb 89      Guidelines for the use of Internet-IP
                                 addresses in the ISO Connectionless-
                                 Mode Network Protocol

This RFC suggests an addressing scheme for use with the ISO
Connectionless Network Protocol (CLNP) in the Internet.  This is a
solution to one of the problems inherent in the use of "ISO-grams" in
the Internet.  This memo is a revision of RFC 986.  This RFC suggests a
proposed protocol for the Internet community, and requests discussion
and suggestions for improvements.


1068    DeSchon      Aug 88      Background File Transfer Program
                                 (BFTP)

This RFC describes an Internet background file transfer service that is
built upon the third-party transfer model of FTP.  No new protocols are
involved.  The purpose of this memo is to stimulate discussions on new
Internet service modes.


1067    Case         Aug 88      A Simple Network Management Protocol

This RFC defines a simple protocol by which management information for a
network element may be inspected or altered by logically remote users.
In particular, together with its companion memos which describe the
structure of management information along with the initial management
information base, these documents provide a simple, workable
architecture and system for managing TCP/IP-based internets and in
particular, the Internet.

This memo specifies a draft standard for the Internet community. TCP/IP
implementations in the Internet which are network manageable are
expected to adopt and implement this specification.




Reynolds                                                        [Page 7]

RFC 1099                  Summary of 1000-1099             December 1991


1066    McCloghrie    Aug 88      Management Information Base for Network
                                  Management of TCP/IP-based internets

This RFC provides the initial version of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based
internets in the short-term.  In particular, together with its companion
memos which describe the structure of management information along with
the initial network management protocol, these documents provide a
simple, workable architecture and system for managing TCP/IP-based
internets, and in particular, the Internet.

This memo specifies a draft standard for the Internet community.  TCP/IP
implementations in the Internet which are network manageable are
expected to adopt and implement this specification.


1065    Rose          Aug 88      Structure and Identification of
                                  Management Information for
                                  TCP/IP-based internets

This RFC provides the common definitions for the structure and
identification of management information for TCP/IP-based internets.  In
particular, together with its companion memos, which describe the
initial management information base along with the initial network
management protocol, these documents provide a simple, working
architecture and system for managing TCP/IP-based internets and in
particular, the Internet.

This memo specifies a draft standard for the Internet community.  TCP/IP
implementation in the Internet which are network manageable are expected
to adopt and implement this specification.


1064    Crispin       Jul 88      Interactive Mail Access Protocol -
                                  Version 2

This memo suggests a method for workstations to dynamically access mail
from a mailbox server ("respository").  This RFC specifies a standard
for the SUMEX-AIM community and a proposed experimental protocol for the
Internet community.  Discussion and suggestions for improvement are
requested.


1063    Mogul         Jul 88      IP MTU Discovery Options

A pair of IP options that can be used to learn the minimum MTU of a path
through an internet is described, along with its possible uses.  This is
a proposal for an Experimental protocol.



Reynolds                                                        [Page 8]

RFC 1099                  Summary of 1000-1099             December 1991


1062    Romano        Aug 88      Internet Numbers

This memo is an official status report on the network numbers and
gateway autonomous system numbers used in the Internet community.


1061    Never issued.


1060    Reynolds      Mar 90      Assigned Numbers

This memo is a status report on the parameters (i.e., numbers and
keywords) used in protocols in the Internet community.  Distribution of
this memo is unlimited.


1059    Mills         Jul 88      Network Time Protocol (Version 1)
                                  Specification and Implementation

This memo describes the Network Time Protocol (NTP), specifies its
formal structure and summarizes information useful for its
implementation.  NTP provides the mechanisms to synchronize time and
coordinate time distribution in a large, diverse internet operating at
rates from mundane to lightwave.  It uses a returnable-time design in
which a distributed subnet of time servers operating in a self-
organizing, hierarchical master-slave configuration synchronizes logical
clocks within the subnet and to national time standards via wire or
radio.  The servers can also redistribute reference time via local
routing algorithms and time daemons.

The NTP architectures, algorithms and protocols which have evolved over
several years of implementation and refinement are described in this
document.  The prototype system, which has been in regular operation in
the Internet for the last two years, is described in an Appendix along
with performance data which shows that timekeeping accuracy throughout
most portions of the Internet can be ordinarily maintained to within a
few tens of milliseconds, even the cases of failure or disruption of
clocks, time servers or nets. This is a Draft Standard for an Elective
protocol.


1058    Hedrick       Jun 88      Routing Information Protocol

This RFC describes an existing protocol for exchanging routing
information among gateways and other hosts.  It is intended to be used
as a basis for developing gateway software for use in the Internet
community.




Reynolds                                                        [Page 9]

RFC 1099                  Summary of 1000-1099             December 1991


1057    Sun           Jun 88       RPC: Remote Procedure Call Protocol
                                   Specification Version 2

This RFC describes a standard that Sun Microsystems and others are
using, and is one we wish to propose for the Internet's consideration.
This memo is not an Internet standard at this time.


1056    Lambert       Jun 88   PCMAIL: A Distributed Mail System
                               for Personal Computers

This memo is a discussion of the Pcmail workstation based distributed
mail system.  It is identical to the discussion in RFC-993, save that a
new, much simpler mail transport protocol is described.  The new
transport protocol is the result of continued research into ease of
protocol implementation and use issues.


1055    Romkey         Jun 88    A Nonstandard for Transmission of
                                 IP Datagrams over Serial Lines: SLIP

The TCP/IP protocol family runs over a variety of network media: IEEE
802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite
links, and serial lines.  There are standard encapsulations for IP
packets defined for many of these networks, but there is no standard for
serial lines.  SLIP, Serial Line IP, is a currently a de facto standard,
commonly used for point-to-point serial connections running TCP/IP.  It
is not an Internet standard.


1054    Deering        May 88      Host Extensions for IP Multicasting

This memo specifies the extensions required of a host implementation of
the Internet Protocol (IP) to support multicasting.  IP multicasting is
the transmission of an IP datagram to a "host group", a set hosts
identified by a single IP destination address.  A multicast datagram is
delivered to all members of its destination host group with the same
"best-efforts" reliability as regular unicast IP datagrams.  It is
proposed as a standard for IP multicasting in the Internet.  This
specification is a major revision of RFC-988.


1053    Levy           Apr 88       Telnet X.3 PAD Option

This RFC proposes a new option to Telnet for the Internet community, and
requests discussion and suggestions for improvements.





Reynolds                                                       [Page 10]

RFC 1099                  Summary of 1000-1099             December 1991


1052    Cerf           Apr 88      IAB Recommendations for the
                                   Development of Internet Network
                                   Management Standards

This RFC is intended to convey to the Internet community and other
interested parties the recommendations of the Internet Activities Board
(IAB) for the development of network management protocols for use in the
TCP/IP environment.  This memo does NOT, in and of itself, define or
propose an Official Internet Protocol.  It does reflect, however, the
policy of the IAB with respect to further network management development
in the short and long term.


1051    Prindeville     Mar 88     A Standard for the Transmission of IP
                                   Datagrams and ARP Packets over ARCNET
                                   Networks

This memo specifies a standard method of encapsulating Internet Protocol
(IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET.  This
RFC is a standard protocol for the Internet community.


1050    Sun             Apr 88      RPC: Remote Procedure Call
                                    Protocol Specification

This memo specifies a message protocol used in implementing Sun's Remote
Procedure Call (RPC) package.  This RFC describes a standard that Sun
Microsystems and others are using and is one they wish to propose for
the Internet's consideration.  It is not an Internet standard at this
time.


1049    Sirbu           Mar 88      A Content-Type Header Field for
                                    Internet Messages

This memo suggests proposed additions to the Internet Mail Protocol,
RFC-822, for the Internet community, and requests discussion and
suggestions for improvements.


1048    Prindeville     Feb 88      BOOTP Vendor Information Extensions

This memo proposes an addition to the Bootstrap Protocol (BOOTP).
Comments and suggestions for improvements are sought.







Reynolds                                                       [Page 11]