As per Relevance of the word information, we have this rfc below:
Network Working Group J.
Request for Comments: 1099
December 1991
Request for Comments
RFC Numbers 1000-1099
Status of This
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
provides information for the Internet community. It does not
an Internet standard. Distribution of this memo is unlimited
RFC Author Date
--- ------ ---- -----
1099 Reynolds Dec 91 Requests For Comments
This memo
1098 Case Apr 89 A Simple Network
Protocol (SNMP
This RFC is a re-release of RFC 1067, with a changed "Status of
Memo" section. This memo defines a simple protocol by which
information for a network element may be inspected or altered
logically remote users. In particular, together with its
memos which describe the structure of management information along
the initial management information base, these documents provide
simple, workable architecture and system for managing TCP/IP-
internets and in particular the Internet
1097 Miller Apr 89 Telnet Subliminal-Message
This RFC specifies a standard for the Internet community. Hosts on
Internet that display subliminal messages within the Telnet protocol
expected to adopt and implement this standard
1096 Marcy Mar 89 Telnet X Display Location
This RFC specifies a standard for the Internet community. Hosts on
Internet that transmit the X display location within the Telnet
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
Services and Protocol over TCP/
(CMOT
This memo defines a network management architecture that uses
International Organization for Standardization's (ISO) Common
Information Services/Common Management Information Protocol (CMIS/CMIP
in a TCP/IP environment. This architecture provides a means by
control and monitoring information can be exchanged between a
and a remote network element. In particular, this memo defines
means for implementing the Draft International Standard (DIS) version
CMIS/CMIP on top of Internet transport protocols for the purpose
carrying management information defined in the Internet-
management information base. DIS CMIS/CMIP is suitable for
in TCP/IP networks while CMIS/CMIP moves toward becoming
International Standard. Together with the relevant ISO standards
the companion RFCs that describe the initial structure of
information and management information base, these documents provide
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
Protocol
This RFC describes a protocol that Sun Microsystems, Inc., and
are using. A new version of the protocol is under development,
others may benefit from the descriptions of the current protocol,
discussion of some of the design issues
1093 Braun Feb 89 The NSFNET Routing
This document describes the routing architecture for the NSFNET
around the new NSFNET Backbone, with specific emphasis on the
between the backbone and its attached networks
1092 Rekhter Feb 89 EGP and Policy Based
in the New NSFNET
This memo discusses implementation decisions for routing issues in
NSFNET, especially in the NSFNET Backbone. Of special concern is
restriction of routing information to advertize the best route
established by a policy decision
Reynolds [Page 2]
RFC 1099 Summary of 1000-1099 December 1991
1091 VanBokkelen Feb 89 Telnet Terminal-Type
This RFC specifies a standard for the Internet community. Hosts on
Internet that exchange terminal type information within the
protocol are expected to adopt and implement this standard
This standard supersedes RFC 930. A change is made to permit
through a list of possible terminal types and selecting the
1090 Ullmann Feb 89 SMTP on X.25
This memo proposes a standard for SMTP on the virtual circuit
provided by the X.25 standard of the CCITT
1089 Schoffstall Feb 89 SNMP over
This memo describes an experimental method by which the Simple
Management Protocol (SNMP) can be used over Ethernet MAC layer
instead of the Internet UDP/IP protocol stack. This specification
useful for LAN based network elements that support no higher
protocols beyond the MAC sub-layer
1088 McLaughlin Feb 89 A Standard for the Transmission of
Datagrams over NetBIOS
This document specifies a standard method of encapsulating the
Protocol (IP) datagrams on NetBIOS networks
1087 IAB Jan 89 Ethics and the
This memo is a statement of policy by the Internet Activities
(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
Internet that choose to implement ISO TP0 transport connectivity
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
on top of TCP/IP-based
RFC 1006 describes a mechanism for providing the ISO transport
on top of TCP/IP. Once this method is applied, one may implement "real
ISO applications on top of TCP/IP-based internets, by
implementing OSI session, presentation, and application services on
of the transport service access point which is provided on top of
TCP. Although straight-forward, there are some environments in
the richness provided by the OSI application layer is desired, but it
nonetheless impractical to implement the underlying OSI
(i.e., the presentation, session, and transport services on top of
TCP).
This memo describes an approach for providing "stream-lined" support
OSI application services on top of TCP/IP-based internets for
constrained environments. This memo proposes a standard for
Internet community
1084 Reynolds Dec 88 BOOTP Vendor Information
This RFC is a slight revision and extension of RFC-1048 by
Prindeville. This memo will be updated as additional tags are
defined. This edition introduces Tag 13 for Boot File Size.
and suggestions for improvements are sought
1083 IAB Dec 88 IAB Official Protocol
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Activities Board (IAB).
overview of the standards procedures is presented first, followed
discussions of the standardization process and the RFC document series
then the explanation of the terms is presented, the lists of
in each stage of standardization follows, and finally pointers
references and contacts for further information
This memo is issued quarterly, please be sure the copy you are
is dated within the last three months
1082 Rose Nov 88 Post Office Protocol - Version 3
Extended Service
This memo suggests a simple method for workstations to
access mail from a discussion group server, as an extension to
earlier memo which dealt with dynamically accessing mail from a
Reynolds [Page 4]
RFC 1099 Summary of 1000-1099 December 1991
server using the Post Office Protocol - Version 3 (POP3). This
specifies a proposed protocol for the Internet community, and
discussion and suggestions for improvements. All of the
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
access mail from a mailbox server. This RFC specifies a
protocol for the Internet community, and requests discussion
suggestions for improvements
1080 Hedrick Dec 88 Telnet Remote Flow Control
This RFC specifies a standard for the Internet community. Hosts on
Internet that do remote flow control within the Telnet protocol
expected to adopt and implement this standard
1079 Hedrick Dec 88 Telnet Terminal Speed
This RFC specifies a standard for the Internet community. Hosts on
Internet that exchange terminal speed information within the
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
services instead of using 'well-known ports'.
1077 Leiner Nov 88 Critical Issues in High
This memo presents the results of a working group on High
Networking. This RFC is for your information and you are encouraged
comment on the issues presented
1076 Trewitt Nov 88 HEMS Monitoring and Control
This RFC specifies a query language for monitoring and control
network entities. This RFC supercedes RFC 1023, extending the
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
(HEMS) described in RFC 1021 and RFC 1022. Readers may wish to
these RFCs when reading this memo. RFC 1024 contains
assignments of numbers and structures used in this system. Portions
RFC 1024 that define query language structures are superceded
definitions in this memo. This memo assumes a knowledge of the ISO
encoding standard, ASN.1.
1075 Waitzman Nov 88 Distance Vector Multicast
This RFC describes a distance-vector-style routing protocol for
multicast datagrams through an internet. It is derived from the
Information Protocol (RIP), and implements multicasting as described
RFC-1054. This is an experimental protocol, and its implementation
not recommended at this time
1074 Rekhter Oct 88 The NSFNET Backbone SPF based
Gateway
This RFC is an implementation description of the standard ANSI IS-IS
ISO ES-IS routing protocols within the NSFNET backbone network
1073 Waitzman Oct 88 Telnet Window Size
This RFC describes a proposed Telnet option to allow a client to
window size to a Telnet server
1072 Jacobson Oct 88 TCP Extensions for Long-Delay
This RFC proposes a set of extensions to the TCP protocol to
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
research on transport protocol performance
1071 Braden Aug 88 Computing the Internet
This RFC summarizes techniques and algorithms for efficiently
the Internet checksum. It is not a standard, but a set of
implementation techniques
Reynolds [Page 6]
RFC 1099 Summary of 1000-1099 December 1991
1070 Hagens Feb 89 Use of the Internet as a
for Experimentation with the
Network
This RFC proposes a scenario for experimentation with the
Organization for Standardization (ISO) Open Systems
(OSI) network layer protocols over the Internet and requests
and suggestions for improvements to this scenario. This RFC
proposes the creation of an experimental OSI internet. To
in the experimental OSI internet, a system must abide by the
set forth in this RFC
1069 Callon Feb 89 Guidelines for the use of Internet-
addresses in the ISO Connectionless
Mode Network
This RFC suggests an addressing scheme for use with the
Connectionless Network Protocol (CLNP) in the Internet. This is
solution to one of the problems inherent in the use of "ISO-grams"
the Internet. This memo is a revision of RFC 986. This RFC suggests
proposed protocol for the Internet community, and requests
and suggestions for improvements
1068 DeSchon Aug 88 Background File Transfer
(BFTP
This RFC describes an Internet background file transfer service that
built upon the third-party transfer model of FTP. No new protocols
involved. The purpose of this memo is to stimulate discussions on
Internet service modes
1067 Case Aug 88 A Simple Network Management
This RFC defines a simple protocol by which management information for
network element may be inspected or altered by logically remote users
In particular, together with its companion memos which describe
structure of management information along with the initial
information base, these documents provide a simple,
architecture and system for managing TCP/IP-based internets and
particular, the Internet
This memo specifies a draft standard for the Internet community. TCP/
implementations in the Internet which are network manageable
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
Management of TCP/IP-based
This RFC provides the initial version of the Management Information
(MIB) for use with network management protocols in TCP/IP-
internets in the short-term. In particular, together with its
memos which describe the structure of management information along
the initial network management protocol, these documents provide
simple, workable architecture and system for managing TCP/IP-
internets, and in particular, the Internet
This memo specifies a draft standard for the Internet community. TCP/
implementations in the Internet which are network manageable
expected to adopt and implement this specification
1065 Rose Aug 88 Structure and Identification
Management Information
TCP/IP-based
This RFC provides the common definitions for the structure
identification of management information for TCP/IP-based internets.
particular, together with its companion memos, which describe
initial management information base along with the initial
management protocol, these documents provide a simple,
architecture and system for managing TCP/IP-based internets and
particular, the Internet
This memo specifies a draft standard for the Internet community. TCP/
implementation in the Internet which are network manageable are
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
from a mailbox server ("respository"). This RFC specifies a
for the SUMEX-AIM community and a proposed experimental protocol for
Internet community. Discussion and suggestions for improvement
requested
1063 Mogul Jul 88 IP MTU Discovery
A pair of IP options that can be used to learn the minimum MTU of a
through an internet is described, along with its possible uses. This
a proposal for an Experimental protocol
Reynolds [Page 8]
RFC 1099 Summary of 1000-1099 December 1991
1062 Romano Aug 88 Internet
This memo is an official status report on the network numbers
gateway autonomous system numbers used in the Internet community
1061 Never issued
1060 Reynolds Mar 90 Assigned
This memo is a status report on the parameters (i.e., numbers
keywords) used in protocols in the Internet community. Distribution
this memo is unlimited
1059 Mills Jul 88 Network Time Protocol (Version 1)
Specification and
This memo describes the Network Time Protocol (NTP), specifies
formal structure and summarizes information useful for
implementation. NTP provides the mechanisms to synchronize time
coordinate time distribution in a large, diverse internet operating
rates from mundane to lightwave. It uses a returnable-time design
which a distributed subnet of time servers operating in a self
organizing, hierarchical master-slave configuration synchronizes
clocks within the subnet and to national time standards via wire
radio. The servers can also redistribute reference time via
routing algorithms and time daemons
The NTP architectures, algorithms and protocols which have evolved
several years of implementation and refinement are described in
document. The prototype system, which has been in regular operation
the Internet for the last two years, is described in an Appendix
with performance data which shows that timekeeping accuracy
most portions of the Internet can be ordinarily maintained to within
few tens of milliseconds, even the cases of failure or disruption
clocks, time servers or nets. This is a Draft Standard for an
protocol
1058 Hedrick Jun 88 Routing Information
This RFC describes an existing protocol for exchanging
information among gateways and other hosts. It is intended to be
as a basis for developing gateway software for use in the
community
Reynolds [Page 9]
RFC 1099 Summary of 1000-1099 December 1991
1057 Sun Jun 88 RPC: Remote Procedure Call
Specification Version 2
This RFC describes a standard that Sun Microsystems and others
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
for Personal
This memo is a discussion of the Pcmail workstation based
mail system. It is identical to the discussion in RFC-993, save that
new, much simpler mail transport protocol is described. The
transport protocol is the result of continued research into ease
protocol implementation and use issues
1055 Romkey Jun 88 A Nonstandard for Transmission
IP Datagrams over Serial Lines:
The TCP/IP protocol family runs over a variety of network media:
802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines,
links, and serial lines. There are standard encapsulations for
packets defined for many of these networks, but there is no standard
serial lines. SLIP, Serial Line IP, is a currently a de facto standard
commonly used for point-to-point serial connections running TCP/IP.
is not an Internet standard
1054 Deering May 88 Host Extensions for IP
This memo specifies the extensions required of a host implementation
the Internet Protocol (IP) to support multicasting. IP multicasting
the transmission of an IP datagram to a "host group", a set
identified by a single IP destination address. A multicast datagram
delivered to all members of its destination host group with the
"best-efforts" reliability as regular unicast IP datagrams. It
proposed as a standard for IP multicasting in the Internet.
specification is a major revision of RFC-988.
1053 Levy Apr 88 Telnet X.3 PAD
This RFC proposes a new option to Telnet for the Internet community,
requests discussion and suggestions for improvements
Reynolds [Page 10]
RFC 1099 Summary of 1000-1099 December 1991
1052 Cerf Apr 88 IAB Recommendations for
Development of Internet
Management
This RFC is intended to convey to the Internet community and
interested parties the recommendations of the Internet Activities
(IAB) for the development of network management protocols for use in
TCP/IP environment. This memo does NOT, in and of itself, define
propose an Official Internet Protocol. It does reflect, however,
policy of the IAB with respect to further network management
in the short and long term
1051 Prindeville Mar 88 A Standard for the Transmission of
Datagrams and ARP Packets over
This memo specifies a standard method of encapsulating Internet
(IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET.
RFC is a standard protocol for the Internet community
1050 Sun Apr 88 RPC: Remote Procedure
Protocol
This memo specifies a message protocol used in implementing Sun's
Procedure Call (RPC) package. This RFC describes a standard that
Microsystems and others are using and is one they wish to propose
the Internet's consideration. It is not an Internet standard at
time
1049 Sirbu Mar 88 A Content-Type Header Field
Internet
This memo suggests proposed additions to the Internet Mail Protocol
RFC-822, for the Internet community, and requests discussion
suggestions for improvements
1048 Prindeville Feb 88 BOOTP Vendor Information
This memo proposes an addition to the Bootstrap Protocol (BOOTP).
Comments and suggestions for improvements are sought
Reynolds [Page 11]
RFC 1099 Summary of 1000-1099 December 1991
1047 Partridge Feb 88 Duplicate Messages and
An examination of a synchronization problem in the Simple Mail
Protocol (SMTP) is presented. This synchronization problem can cause
message to be delivered multiple times. A method for avoiding
problem is suggested. Nodding familiarity with the SMTP specification
RFC-821, is required
1046 Prue Feb 88 A Queuing Algorithm to
Type-of-Service for IP
This memo is intended to explore how Type-of-Service might
implemented in the Internet. The proposal describes a method of
which can provide the different classes of service. The technique
prohibits one class of service from consuming excessive resources
excluding other classes of service. This is an "idea paper"
discussion is strongly encouraged
1045 Cheriton Feb 88 VMTP: Versatile Message
Protocol Protocol
This memo specifies the Versatile Message Transaction Protocol (VMTP
[Version 0.7 of 19-Feb-88], a transport protocol specifically
to support the transaction model of communication, as exemplified
remote procedure call (RPC). The full function of VMTP,
support for security, real-time, asynchronous message exchanges
streaming, multicast and idempotency, provides a rich selection to
VMTP user level. Subsettability allows the VMTP module for
clients and servers to be specialized and simplified to the
actually required. Examples of such simple clients and servers
PROM network bootload programs, network boot servers, data sensors
simple controllers, to mention but a few examples. This RFC describes
protocol proposed as a standard for the Internet community
1044 Hardwick Feb 88 Internet Protocol on Network
HYPERchannel Protocol
This memo intends to provide a complete discussion of the protocols
techniques used to embed DoD standard Internet Protocol datagrams (
its associated higher level protocols) on Network Systems Corporation'
HYPERchannel equipment. This document is directed toward
planners and implementors who are already familiar with the TCP/
protocol suite and the techniques used to carry TCP/IP traffic on
networks such as the DDN or the Ethernet. No great familiarity with
products is assumed; an appendix is devoted to a review of
Reynolds [Page 12]
RFC 1099 Summary of 1000-1099 December 1991
technologies and protocols
1043 Yasuda Feb 88 TELNET Data Entry Terminal
DODIIS
This RFC suggests a proposed protocol on the TELNET Data Entry
(DET) Option - DODIIS Implementation for the Internet community. It
intended that this specification be capatible with the specification
DET Option in RFC-732. Discussion and suggests for improvements
encouraged
1042 Postel Feb 88 A Standard for the Transmission
IP Datagrams over IEEE 802
This RFC specifies a standard method of encapsulating the
Protocol (IP) datagrams and Address Resolution Protocol (ARP)
and replies on IEEE 802 Networks to allow compatible and
implementations. This RFC specifies a protocol standard for
Internet community
1041 Rekhter Jan 88 Telnet 3270 Regime
This RFC specifies a proposed standard for the Internet community
Hosts on the Internet that want to support 3270 data stream within
Telnet protocol, are expected to adopt and implement this standard
1040 Linn Jan 88 Privacy Enhancement for
Electronic Mail: Part I
Encipherment and
This RFC is the Outgrowth of a series of IAB Privacy Task Force
and of internal working papers distributed for those meetings.
memo defines message encipherment and authentication procedures, as
initial phase of an effort to provide privacy enhancement services
electronic mail transfer in the Internet. Detailed key
mechanisms to support these procedures will be defined in a
RFC. As a goal of this initial phase, it is intended that
procedures defined here be compatible with a wide range of
management approaches, including both conventional (symmetric)
public-key (asymmetric) approaches for encryption of data
keys. Use of conventional cryptography for message text
and/or integrity check computation is anticipated
Reynolds [Page 13]
RFC 1099 Summary of 1000-1099 December 1991
1039 Latham Jan 88 A DoD Statement on Open
Interconnection
This RFC reproduces a memorandum issued on 2-JUL-87 from the
Secretary of Defense for Command, Control, Communications,
Intelligence (ASDC31) to the Director of the Defense
Agency (DCA). This memo is distributed for information only
1038 St. Johns Jan 88 Draft Revised IP Security
This memo is a pre-publication draft of the revised Internet
Security Option. This RFC reflects the version as approved by
Protocol Standards Steering group, and is provided for
purposes only. The final version of this document will be
from Navy publications and should not differ from this document in
major fashion. This document will be published as a change to the MIL
STD 1777, "Internet Protocol".
1037 Greenberg Dec 87 NFILE - A File Access
This document includes a specification of the NFILE file access
and its underlying levels of protocol, the Token List Transport
and Byte Stream with Mark. The goal of this specification is to
discussion of the ideas described here, and to encourage designers
future file protocols to take advantage of these ideas. A
goal is to make the specification available to sites that might
from implementing NFILE
1036 Horton Dec 87 Standard for Interchange
USENET
This RFC defines the standard format for the interchange of network
messages among USENET hosts. It updates and replaces RFC-850,
reflecting version B2.11 of the News program. This memo is
as an RFC to make this information easily accessible to the
community. It does not specify an Internet standard
1035 Mockapetris Nov 87 Domain Names -
This RFC is the revised specification of the protocol and format used
the implementation of the Domain Name System. It obsoletes RFC-883.
This memo documents the details of the domain name client -
communication
Reynolds [Page 14]
RFC 1099 Summary of 1000-1099 December 1991
1034 Mockapetris Nov 87 Domain Names - Concepts
This RFC is the revised basic definition of The Domain Name System.
obsoletes RFC-882. This memo describes the domain style names and
used for host address look up and electronic mail forwarding.
discusses the clients and servers in the domain name system and
protocol used between them
1033 Lottor Nov 87 Domain Administrators
This RFC provides guidelines for domain administrators in operating
domain server and maintaining their portion of the
database. Familiarity with the domain system is assumed (see RFCs 1031,
1032, 1034, and 1035).
1032 Stahl Nov 87 Domain Administrators
Domains are administrative entities that provide
management of host naming and addressing. The domain-naming system
distributed and hierarchical
This memo describes procedures for registering a domain with the
Information Center (NIC) of Defense Data Network (DDN), and
guidelines on the establishment and administration of a domain
accordance with the requirements specified in RFC-920. It is
that the guidelines described in this document be used by
administrators in the establishment and control of second-level domains
The role of the domain administrator (DA) is that of coordinator
manager, and technician. If his domain is established at the
level or lower in the tree, the domain administrator must register
interacting with the management of the domain directly above this
1031 Lazear Nov 87 Milnet Name Domain
This RFC consolidates information necessary for the implementation
domain style names throughout the DDN/MILNET Internet community.
introduction of domain style names will impact all hosts in
DDN/MILNET Internet. This RFC is designed as an aid to implementors
administrators by providing: 1) an overview of the transition
from host tables to domains, 2) a timetable for the transition, and 3)
references to documentation and software relating to the domain system
Reynolds [Page 15]
RFC 1099 Summary of 1000-1099 December 1991
1030 Lambert Nov 87 On Testing the NETBLT Protocol
Divers
This memo describes the results gathered from testing NETBLT over
networks of different bandwidths and round-trip delays. The results
not complete, but the information gathered so far has not
promising. The NETBLT protocol is specified in RFC-998; this
assumes an understanding of the specification as described in RFC-998.
1029 Parr May 88 A More Tolerant Approach to
Resolution for Multi-Lan system
This memo discusses an extension to a Bridge Protocol to detect
disclose changes in heighbouring host address parameters in a Multi-
system of Ethernets. The problem is one which is appearing more
more regularly as the interconnected systems grow larger on Campuses
in Commercial Institutions. This RFC suggests a protocol
for the Internet community, and requests discussion and suggestions
improvements
1028 Davin Nov 87 A Simple Gateway Monitoring
This memo defines a simple application-layer protocol by
management information for a gateway may be inspected or altered
remote users. This proposal is intended only as an interim response
immediate gateway monitoring needs
1027 Carl-Mitchell Oct 87 Using ARP to Implement
Subnet
This RFC describes the use of the Address Resolution Protocol (ARP)
subnet gateways to permit hosts on the connected subnets to
without being aware of the existence of subnets, using the technique
"Proxy ARP".
1026 Kille Sep 87 Addendum to RFC-987 (Mapping
X.400 and RFC-882)
This memo suggest a proposed protocol for the Internet community,
request discussion and suggestions for improvements
Reynolds [Page 16]
RFC 1099 Summary of 1000-1099 December 1991
1025 Postel Sep 87 TCP and IP Bake
This memo describes some of the procedures, scoring and tests used
the TCP and IP bake offs held in the early development of
protocols. These procedures and tests may still be of use in
newly implemented TCP and IP modules
1024 Partridge Oct 87 HEMS Variable
This memo assigns instruction codes, defines object formats and
semantics for use with the High-Level Monitoring and Control Language
defined in RFC-1023. A general system has been described in
memos (RFC-1021, RFC-1022). This system is called the High-Level
Management System (HEMS). This memo is provisional and the
are subject to change. Readers should confirm with the authors
they have the most recent version. This RFC assumes a working
of the ISO data encoding standard, ASN.1, and a general understanding
the IP protocol suite
1023 Partridge Oct 87 HEMS Monitoring and Control
This RFC specifies the High-Level Entity Management System (HEMS
Monitoring and Control Language. This language defines the requests
replies used in HEMS. This memo assumes knowledge of the HEMS
described in RFC-1021, and of the ISO data encoding standard, ASN.1.
1022 Partridge Oct 87 The High-Level Entity
Protocol (HEMP
This memo presents an application protocol for managing network
such as hosts, gateways, and front end machines. This protocol is
component of the High-level Entity Management System HEMS), described
RFC-1021. This memo also assumes a knowledge of the ISO data
standard, ASN.1.
1021 Partridge Oct 87 The High-Level Entity
System (HEMS
This memo provides a general overview of the High-level
management system (HEMS). This system is experimental, and is
being tested in portions of the Internet
Reynolds [Page 17]
RFC 1099 Summary of 1000-1099 December 1991
1020 Romano Nov 87 Internet
This RFC is a list of the Assigned IP Network Numbers and EGP
System Numbers. This RFC obsoletes RFC-997.
1019 Arnon Sep 87 Report of the Workshop
Environments for
This memo is a report on the discussion of the representation
equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim
California on 30 July 1987.
1018 McKenzie Aug 87 Some Comments on
This memo is a discussion of some of the ideas expressed in RFC-1016
Source Quench. This memo introduces the distinction of the cause
congestion in a gateway between the effects of "Funneling"
Mismatch". It is offered in the same spirit as RFC-1016; to
discussion. The opinions offered are personal, not corporate, opinions
1017 Leiner Aug 87 Network Requirements for
This RFC identifies the requirements on communication networks
supporting scientific research. It proposes some specific areas
near term work, as well as some long term goals. This is an "idea
paper and discussion is strongly encouraged
1016 Prue July 87 Something a Host Could Do with
Quench: The Source Quench
Delay (SQuID
The memo is intended to explore the issue of what a host could do with
source quench. The proposal is for each source host IP module
introduce some delay between datagrams sent to the same
host. This is a "crazy idea paper" and discussion is essential
1015 Leiner July 87 Implementation Plan for
Research
This RFC proposes an Interagency Research Internet as the
outgrowth of the current Internet. This is an "idea paper"
Reynolds [Page 18]
RFC 1099 Summary of 1000-1099 December 1991
discussion is strongly encouraged
1014 Sun Jun 87 XDR: External Data
XDR is a standard for the description and encoding of data. It
useful for transferring data between different computer architectures
XDR fits into ISO presentation layer, and is roughly analogous
purpose to X.409, ISO Abstract Syntax Notation. The major
between these two is that XDR uses implicit typing, while X.409
explicit typing. This RFC is distributed for information only, it
not establish a Internet standard
1013 Scheifler Jun 87 X Window System Protocol
Version 11-
This RFC is distributed to the Internet community for information only
It does not establish an Internet standard. The X window system
been widely reviewed and tested. The Internet community is
to experiment with it
1012 Reynolds Jun 87 Bibliography of Requests
Comments 1-999
This RFC is a reference guide for the Internet community which
a bibliographic summary of the Request for Comments numbers 1
999 issued between the years 1969-1987.
1011 Reynolds May 87 Official Internet
This memo is an official status report on the protocols used in
Internet community. It identifies the documents specifying the
protocols used in the Internet. Comments indicate any revisions
changes planned
1010 Reynolds May 87 Assigned
This memo is an official status report on the numbers used in
in the Internet community. It documents the currently assigned
from several series of numbers including link, socket, port,
protocol, used in network protocol implementations
Reynolds [Page 19]
RFC 1099 Summary of 1000-1099 December 1991
1009 Braden Jun 87 Requirements for Internet
This RFC summarizes the requirements for gateways to be used
networks supporting the Internet protocols. This document is a
statement of the requirements to be met by gateways used in the
system. As such, it is an official specification for the
community
1008 McCoy Jun 87 Implementation Guide for the
Transport
This RFC is being distributed to members of the Internet community
order to solicit comments on the Implementors Guide. While
document may not be directly relevant to the research problems of
Internet, it may be of some interest to a number of researchers
implementors
1007 McCoy Jun 87 Military Supplement to the
Transport
This document supplements the Transport Service and Protocol of
International Standards Organization (ISO), IS 8072 and IS 8073,
respectively, and their formal descriptions by providing conventions
option selections and parameter values. This RFC is being
to members of the Internet community in order to solicit comments on
Draft Military Supplement. While this document may not be
relevant to the research problems of the Internet, it may be of
interest to a number of researchers and implementors
1006 Rose May 87 ISO Transport Services on top
the TCP Version: 3
This memo specifies a standard for the Internet community. Hosts on
Internet that choose to implement ISO transport services on top of
TCP are expected to adopt and implement this standard. TCP port 102
reserved for hosts which implement this standard. This memo
version 3 of the protocol and supersedes RFC-983. Changes between
protocol is described in RFC-983 and this memo are minor,
unfortunately incompatible
1005 Khanna May 87 The ARPANET AHIP-E Host
Protocol (Enhanced AHIP
This RFC is a proposed specification for the encoding of Class A
Reynolds [Page 20]
RFC 1099 Summary of 1000-1099 December 1991
addresses for use on ARPANET-style networks such as the Milnet
Arpanet, and for enhancements to the ARPANET AHIP Host Access
(AHIP; formerly known as 1822). These enhancements increase the size
the PSN field, allow ARPANET hosts to use logical names to address
other, allow for the communication of type-of-service information
the host to the PSN and enable the PSN to provide congestion feedback
the host on a connection basis
1004 Mills Apr 87 A Distributed-
Authentication
The purpose of this RFC is to focus discussion on
problems in the Internet and possible methods of solution. The
solutions this document are not intended as standards for the
at this time. Rather, it is hoped that a general consensus will
as to the appropriate solution to authentication problems,
eventually to the adoption of standards. This document
mediated access-control and authentication procedures suitable for
cases when an association is to be set up between users belonging
different trust environments
1003 Katz Mar 87 Issues in Defining an
Representation
This memo is intended to identify and explore issues in defining
standard for the exchange of mathematical equations. No attempt is
at a complete definition and more questions are asked than are answered
Questions about the user interface are only addressed to the extent
they affect interchange issues
1002 NETBIOS Mar 87 Protocol Standard for A
Service on a TCP/UDP Transport
Detailed
This RFC defines a proposed standard protocol to support
services in a TCP/IP environment. Both local network and
operation are supported. Various node types are defined to
local and internet topologies and to allow operation with or without
use of IP broadcast. This RFC gives the detailed specifications of
netBIOS-over-TCP packets, protocols, and defined constants
variables. A more general overview is found in a companion RFC
"Protocol Standard For NetBIOS Service on TCP/UDP Transport:
and Methods".
Reynolds [Page 21]
RFC 1099 Summary of 1000-1099 December 1991
1001 NETBIOS Mar 87 Protocol Standard for A
Service on a TCP/UDP Transport
Concepts and
This RFC defines a proposed standard protocol to support
services in a TCP/IP environment. Both local network and
operation are supported. Various node types are defined to
local and internet topologies and to allow operation with or without
use of IP broadcast. This RFC describes the NetBIOS-over-TCP
in a general manner, emphasizing the underlying ideas and techniques
Detailed specifications are found in a companion RFC, "Protocol
For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications".
1000 Reynolds Aug 87 The Request for Comments
This RFC Reference Guide is intended to provide a historical account
categorizing and summarizing of the Request for Comments numbers 1
through 999 issued between the years 1969-1987. These documents
been crossed referenced to indicate which RFCs are current, obsolete,
revised
Security
Security issues are not discussed in this memo
Author's
Joyce K.
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: JKREY@ISI.
Reynolds [Page 22]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
