rfc1099.txt

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

Network Working Group                                        J. Reynolds
Request for Comments: 1099                                           ISI
                                                           December 1991


                      Request for Comments Summary

                         RFC Numbers 1000-1099

Status of This Memo

   This memo is a slightly annotated list of the 100 RFCs from RFC 1000
   through RFCs 1099.  This is a status report on these RFCs.  This memo
   provides information for the Internet community.  It does not specify
   an Internet standard.  Distribution of this memo is unlimited.

RFC     Author       Date      Title
---     ------       ----      -----

1099    Reynolds     Dec 91    Requests For Comments Summary

This memo.


1098    Case         Apr 89    A Simple Network Management
                               Protocol (SNMP)

This RFC is a re-release of RFC 1067, with a changed "Status of this
Memo" section.  This memo 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.


1097    Miller       Apr 89    Telnet Subliminal-Message Option

This RFC specifies a standard for the Internet community.  Hosts on the
Internet that display subliminal messages within the Telnet protocol are
expected to adopt and implement this standard.


1096    Marcy        Mar 89    Telnet X Display Location Option

This RFC specifies a standard for the Internet community.  Hosts on the
Internet that transmit the X display location within the Telnet protocol



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


are expected to adopt and implement this standard.


1095    Warrier      Apr 89    The Common Management Information
                               Services and Protocol over TCP/IP
                               (CMOT)

This memo defines a network management architecture that uses the
International Organization for Standardization's (ISO) Common Management
Information Services/Common Management Information Protocol (CMIS/CMIP)
in a TCP/IP environment.  This architecture provides a means by which
control and monitoring information can be exchanged between a manager
and a remote network element.  In particular, this memo defines the
means for implementing the Draft International Standard (DIS) version of
CMIS/CMIP on top of Internet transport protocols for the purpose of
carrying management information defined in the Internet-standard
management information base.  DIS CMIS/CMIP is suitable for deployment
in TCP/IP networks while CMIS/CMIP moves toward becoming an
International Standard.  Together with the relevant ISO standards and
the companion RFCs that describe the initial structure of management
information and management information base, these documents provide the
basis for a comprehensive architecture and system for managing TCP/IP-
based internets, and in particular the Internet.


1094    Sun          Mar 89    NFS: Network File System
                               Protocol Specification

This RFC describes a protocol that Sun Microsystems, Inc., and others
are using.  A new version of the protocol is under development, but
others may benefit from the descriptions of the current protocol, and
discussion of some of the design issues.


1093    Braun        Feb 89    The NSFNET Routing Architecture

This document describes the routing architecture for the NSFNET centered
around the new NSFNET Backbone, with specific emphasis on the interface
between the backbone and its attached networks.


1092    Rekhter      Feb 89    EGP and Policy Based Routing
                               in the New NSFNET Backbone

This memo discusses implementation decisions for routing issues in the
NSFNET, especially in the NSFNET Backbone.  Of special concern is the
restriction of routing information to advertize the best route as
established by a policy decision.



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


1091    VanBokkelen  Feb 89    Telnet Terminal-Type Option

This RFC specifies a standard for the Internet community.  Hosts on the
Internet that exchange terminal type information within the Telnet
protocol are expected to adopt and implement this standard.

This standard supersedes RFC 930.  A change is made to permit cycling
through a list of possible terminal types and selecting the most
appropriate


1090    Ullmann      Feb 89    SMTP on X.25

This memo proposes a standard for SMTP on the virtual circuit facility
provided by the X.25 standard of the CCITT.


1089    Schoffstall  Feb 89    SNMP over Ethernet

This memo describes an experimental method by which the Simple Network
Management Protocol (SNMP) can be used over Ethernet MAC layer framing
instead of the Internet UDP/IP protocol stack.  This specification is
useful for LAN based network elements that support no higher layer
protocols beyond the MAC sub-layer.


1088    McLaughlin   Feb 89    A Standard for the Transmission of IP
                               Datagrams over NetBIOS Networks

This document specifies a standard method of encapsulating the Internet
Protocol (IP) datagrams on NetBIOS networks.


1087    IAB          Jan 89    Ethics and the Internet

This memo is a statement of policy by the Internet Activities Board
(IAB) concerning the proper use of the resources of the Internet.


1086    Onions       Dec 88    ISO-TP0 bridge between TCP and X.25

This memo proposes a standard for the Internet community.  Hosts on the
Internet that choose to implement ISO TP0 transport connectivity between
TCP and X.25 based hosts are expected to experiment with this proposal.
TCP port 146 is reserved for this proposal.






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


1085    Rose         Dec 88    ISO Presentation Services
                               on top of TCP/IP-based internets

RFC 1006 describes a mechanism for providing the ISO transport service
on top of TCP/IP.  Once this method is applied, one may implement "real"
ISO applications on top of TCP/IP-based internets, by simply
implementing OSI session, presentation, and application services on top
of the transport service access point which is provided on top of the
TCP.  Although straight-forward, there are some environments in which
the richness provided by the OSI application layer is desired, but it is
nonetheless impractical to implement the underlying OSI infrastructure
(i.e., the presentation, session, and transport services on top of the
TCP).

This memo describes an approach for providing "stream-lined" support of
OSI application services on top of TCP/IP-based internets for such
constrained environments.  This memo proposes a standard for the
Internet community.


1084    Reynolds     Dec 88      BOOTP Vendor Information Extensions

This RFC is a slight revision and extension of RFC-1048 by Philip
Prindeville.  This memo will be updated as additional tags are are
defined.  This edition introduces Tag 13 for Boot File Size.  Comments
and suggestions for improvements are sought.


1083    IAB          Dec 88      IAB Official Protocol Standards

This memo describes the state of standardization of protocols used in
the Internet as determined by the Internet Activities Board (IAB).  An
overview of the standards procedures is presented first, followed by
discussions of the standardization process and the RFC document series,
then the explanation of the terms is presented, the lists of protocols
in each stage of standardization follows, and finally pointers to
references and contacts for further information.

This memo is issued quarterly, please be sure the copy you are reading
is dated within the last three months.


1082    Rose         Nov 88      Post Office Protocol - Version 3
                                 Extended Service Offerings

This memo suggests a simple method for workstations to dynamically
access mail from a discussion group server, as an extension to an
earlier memo which dealt with dynamically accessing mail from a mailbox



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


server using the Post Office Protocol - Version 3 (POP3).  This RFC
specifies a proposed protocol for the Internet community, and requests
discussion and suggestions for improvements.  All of the extensions
described in this memo to the POP3 are OPTIONAL.


1081    Rose         Nov 88      Post Office Protocol - Version 3

This memo suggests a simple method for workstations to dynamically
access mail from a mailbox server.  This RFC specifies a proposed
protocol for the Internet community, and requests discussion and
suggestions for improvements.


1080    Hedrick      Dec 88      Telnet Remote Flow Control Option

This RFC specifies a standard for the Internet community.  Hosts on the
Internet that do remote flow control within the Telnet protocol are
expected to adopt and implement this standard.


1079    Hedrick      Dec 88      Telnet Terminal Speed Option

This RFC specifies a standard for the Internet community.  Hosts on the
Internet that exchange terminal speed information within the Telnet
protocol are expected to adopt and implement this standard.


1078    Lottor       Nov 88      TCP Port Service Multiplexer (TCPMUX)

This RFC proposes an Internet standard which can be used by future TCP
services instead of using 'well-known ports'.


1077    Leiner       Nov 88      Critical Issues in High Bandwidth
                                 Networking

This memo presents the results of a working group on High Bandwidth
Networking.  This RFC is for your information and you are encouraged to
comment on the issues presented.


1076    Trewitt      Nov 88      HEMS Monitoring and Control Language

This RFC specifies a query language for monitoring and control of
network entities.  This RFC supercedes RFC 1023, extending the query
language and providing more discussion of the underlying issues.




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


This language is a component of the High-Level Entity Monitoring System
(HEMS) described in RFC 1021 and RFC 1022.  Readers may wish to consult
these RFCs when reading this memo.  RFC 1024 contains detailed
assignments of numbers and structures used in this system.  Portions of
RFC 1024 that define query language structures are superceded by
definitions in this memo.  This memo assumes a knowledge of the ISO data
encoding standard, ASN.1.


1075    Waitzman     Nov 88      Distance Vector Multicast Routing
                                 Protocol

This RFC describes a distance-vector-style routing protocol for routing
multicast datagrams through an internet.  It is derived from the Routing
Information Protocol (RIP), and implements multicasting as described in
RFC-1054.  This is an experimental protocol, and its implementation is
not recommended at this time.


1074    Rekhter      Oct 88      The NSFNET Backbone SPF based Interior
                                 Gateway Protocol

This RFC is an implementation description of the standard ANSI IS-IS and