As per Relevance of the word describe, we have this rfc below:
Network Working Group J.
Request for Comments: 1199
December 1991
Request for Comments
RFC Numbers 1100-1199
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 1100
through RFCs 1199. 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
Many RFCs, but not all, are Proposed Standards, Draft Standards,
Standards. Since the status of these RFCs may change during
standards processing, we note here only that they are on
standards track. Please see the latest edition of "IAB
Protocol Standards" for the current state and status of these RFCs
In the following, RFCs on the standards track are marked [STANDARDS
TRACK].
RFC Author Date
--- ------ ---- -----
1199 Reynolds Dec 91 Requests For Comments
This memo
1198 Scheifler Jan 91 FYI on the X Window
This FYI RFC provides pointers to the published standards of the MIT
Consortium. This memo provides information for the Internet community
It does not specify any Internet standard
1197 Sherman Dec 90 Using ODA for Translating
The purpose of this RFC is to inform implementors of multimedia
about our experiences using ISO 8613: Office Document
(ODA). Because ODA is being proposed as an encoding format for use
multimedia mail and file exchange, implementors wishing to use ODA in
Reynolds [Page 1]
RFC 1199 Summary of 1100-1199 December 1991
open systems environment may profit from our experiences. This
provides information for the Internet community. It does not
any standard
1196 Zimmerman Dec 90 The Finger User Information
This memo describes the Finger User Information Protocol. This is
simple protocol which provides an interface to a remote user
program. Based on RFC 742, a description of the original
protocol, this memo attempts to clarify the expected
between the two ends of a Finger connection. It also tries not
invalidate the many existing implementations or add
restrictions to the original protocol definition. This edition
and clarifies in a minor way, RFC 1194. [STANDARDS-TRACK
1195 Callon Dec 90 Use of OSI IS-IS for Routing in TCP/
and Dual
This memo specifies an integrated routing protocol, based on the
Intra-Domain IS-IS Routing Protocol, which may be used as an
gateway protocol (IGP) to support TCP/IP as well as OSI. This allows
single routing protocol to be used to support pure IP environments,
OSI environments, and dual environments. This specification
developed by the IS-IS working group of the Internet Engineering
Force. [STANDARDS-TRACK
1194 Zimmerman Nov 90 The Finger User Information
This memo describes the Finger User Information Protocol. This is
simple protocol which provides an interface to a remote user
program. Based on RFC 742, a description of the original
protocol, this memo attempts to clarify the expected
between the two ends of a Finger connection. It also tries not
invalidate the many existing implementations or add
restrictions to the original protocol definition. [STANDARDS-TRACK
1193 Ferrari Nov 90 Client Requirements for Real-
Communication
This memo describes client requirements for real-time
services. This memo provides information for the Internet community
and requests discussion and suggestions for improvements. It does
specify any standard
Reynolds [Page 2]
RFC 1199 Summary of 1100-1199 December 1991
1192 Kahin Nov 90 Commercialization of the
Summary
This memo is based on a workshop held by the Science, Technology
Public Policy Program of the John F. Kennedy School of Government
Harvard University, March 1-3, 1990. This memo provides information
the Internet community. It does not specify any standard
1191 Mogul Nov 90 Path MTU
This memo describes a technique for dynamically discovering the
transmission unit (MTU) of an arbitrary internet path. It specifies
small change to the way routers generate one type of ICMP message.
a path that passes through a router that has not been so changed,
technique might not discover the correct Path MTU, but it will
choose a Path MTU as accurate as, and in many cases more accurate than
the Path MTU that would be chosen by current practice. [STANDARDS
TRACK
1190 Topolcic Oct 90 Experimental Internet Stream Protocol
Version 2 (ST-II
This memo defines a revised version of the Internet Stream Protocol
originally defined in IEN-119 [8], based on results from
with the original version, and subsequent requests, discussion,
suggestions for improvements. This is a Limited-Use
Protocol. Please refer to the current edition of the "IAB
Protocol Standards" for the standardization state and status of
protocol
1189 Warrier Oct 90 The Common Management
Services and Protocols for the
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 the Internet. [STANDARDS-TRACK
1188 Katz Oct 90 A Proposed Standard for
Transmission of IP Datagrams
FDDI
This memo defines a method of encapsulating the Internet Protocol (IP
datagrams and Address Resolution Protocol (ARP) requests and replies
Reynolds [Page 3]
RFC 1199 Summary of 1100-1199 December 1991
Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK
1187 Rose Oct 90 Bulk Table Retrieval with the
This memo reports an interesting family of algorithms for bulk
retrieval using the Simple Network Management Protocol (SNMP).
memo describes an Experimental Protocol for the Internet community,
requests discussion and suggestions for improvements. This memo
not specify a standard for the Internet community. Please refer to
current edition of the "IAB Official Protocol Standards" for
standardization state and status of this protocol
1186 Rivest Oct 90 The MD4 Message Digest
This RFC is the specification of the MD4 Digest Algorithm. If you
going to implement MD4, it is suggested you do it this way. This
is for informational use and does not constitute a standard
1185 Jacobson Oct 90 TCP Extension for High-Speed
This memo describes an Experimental Protocol extension to TCP for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "IAB
Protocol Standards" for the standardization state and status of
protocol
1184 Borman Oct 90 Telnet Linemode
This RFC specifies a procedure for line at a time terminal
based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK
1183 Everhart Oct 90 New DNS RR
This memo defines five new DNS types for experimental purposes.
RFC describes an Experimental Protocol for the Internet community,
requests discussion and suggestions for improvements
1182 Never issued
Reynolds [Page 4]
RFC 1199 Summary of 1100-1199 December 1991
1181 Blokzijl Sep 90 RIPE Terms of
This RFC describes the Terms of Reference of RIPE (Reseaux
Europeens), the cooperation of European IP networks. This memo
information for the Internet community. It does not specify
standard
1180 Socolofsky Jan 91 A TCP/IP
This RFC is a tutorial on the TCP-IP protocol suite,
particularly on the steps in forwarding an IP datagram from source
to destination host through a router. It does not specify an
standard
1179 McLaughlin Aug 90 Line Printer Daemon
This RFC describes an existing print server protocol widely used on
Internet for communicating between line printer daemons (both
and servers). This memo is for informational purposes only, and
not specify an Internet standard. Please refer to the current
of the "IAB Official Protocol Standards" for the standardization
and status of this protocol
1178 Libes Aug 90 Choosing a Name for Your
This FYI RFC is a republication of a Communications of the ACM
on guidelines on what to do and what not to do when naming
computer. This memo provides information for the Internet community
It does not specify any standard. [Also FYI 5.]
1177 Malkin Aug 90 FYI on Questions and
Answers to Commonly asked "
Internet User"
This FYI RFC is one of three FYI's called, "Questions and Answers
(Q/A), produced by the User Services Working Group (USWG) of
Internet Engineering Task Force (IETF). The goal is to document
most commonly asked questions and answers in the Internet. This
provides information for the Internet community. It does not
any standard. [Also FYI 4.]
Reynolds [Page 5]
RFC 1199 Summary of 1100-1199 December 1991
1176 Crispin Aug 90 Interactive Mail Access Protocol -
Version 2
This RFC suggests a method for personal computers and workstations
dynamically access mail from a mailbox server ("repository").
obosoletes RFC 1064. This RFC specifies an Experimental Protocol
the Internet community. Discussion and suggestions for improvement
requested. Please refer to the current edition of the "IAB
Protocol Standards" for the standardization state and status of
protocol
1175 Bowers Aug 90 FYI on Where to Start - A
of Internetworking
This FYI RFC is a bibliography of information about TCP/
internetworking, prepared by the User Services Working Group (USWG)
the Internet Engineering Task Force (IETF). This memo
information for the Internet community. It does not specify
standard. [Also FYI 3.]
1174 Cerf Aug 90 IAB Recommended Policy on
Internet Identifier Assignment
IAB Recommended
Change to Internet "Connected"
This informational RFC represents the official view of the
Activities Board (IAB), and describes the recommended policies
procedures on distributing Internet identifier assignments and
the connected status requirement. This RFC does not specify a standard
1173 Van Bokkelen Aug 90 Responsibilities of Host and
Managers: A Summary of the "
Tradition" of the
This informational RFC describes the conventions to be followed by
in charge of networks and hosts in the Internet. It is a summary of
"oral tradition" of the Internet on this subject. [RFC Editor's note
This memo is a contribution by the author of his view of
conventions. It is expected that this RFC will provide a basis for
development of official policies in the future.] These conventions
be supplemented or amended by the policies of specific local
regional components of the Internet. This RFC does not specify
standard, or a policy of the IAB
Reynolds [Page 6]
RFC 1199 Summary of 1100-1199 December 1991
1172 Perkins Jul 90 The Point-to-Point Protocol (PPP
Initial Configuration
This memo specifies the Point-to-Point Protocol (PPP)
Configuration Options as a Proposed Standard Protocol for the
community. When it becomes a full Standard, this protocol will
recommended for all TCP/IP implementations that communicate over
links
1171 Perkins Jul 90 The Point-to-Point Protocol for
Transmission of Multi-Protocol
Over Point-to-Point
This memo specifies the Point-to-Point Protocol (PPP) as a
Standard Protocol for the Internet community. When it becomes a
Standard, this protocol will be recommended for all TCP/
implementations that communicate over serial links
1170 Fougner Jan 91 Public Key Standards and
This RFC is a public statement by Public Key Partners regarding
Key Standards and Licenses. This memo is for informational use only
and does not constitute an Internet standard
1169 Cerf Aug 90 Explaining the Role of
This informational RFC represents the official view of the
Activities Board (IAB), after coordination with the Federal
Council (FNC). This RFC does not specify a standard
1168 Westine Jul 90 Intermail and Commercial
Relay
This RFC discusses the history and evolution of the Intermail
Commercial mail systems. The problems encountered in operating
store-and-forward mail relay between commercial systems such
Telemail, MCI Mail and Dialcom are also discussed. This RFC
information for the Internet community, and does not specify
standard
Reynolds [Page 7]
RFC 1199 Summary of 1100-1199 December 1991
1167 Cerf Jul 90 Thoughts on the National Research
Education
The memo provides a brief outline of a National Research and
Network (NREN). This memo provides information for the
community. It does not specify any standard. It is not a statement
IAB policy or recommendations
1166 Kirkpatrick Jul 90 Internet
This memo is a status report on the network numbers and
system numbers used in the Internet community
1165 Crowcrowft Jun 90 Network Time Protocol (NTP
over the OSI Remote Operations
This memo suggests an Experimental Protocol for the OSI and
communities. Hosts in either community, and in particular those on
are encouraged to experiment with this mechanism
1164 Honig Jun 90 Application of the Border
Protocol in the
This RFC, together with its companion RFC-1163, "A Border
Protocol (BGP)", specify an inter-autonomous system routing protocol
the Internet. [STANDARDS-TRACK
1163 Lougheed Jun 90 A Border Gateway Protocol (BGP
This RFC, together with its companion RFC-1164, "Application of
Border Gateway Protocol in the Internet", specify an inter-
system routing protocol for the Internet. [STANDARDS-TRACK
1162 Satz Jun 90 Connectionless Network
(ISO 8473) and End System
Intermediate System (ISO 9542)
Management Information
This memo defines an experimental portion of the Management
Base (MIB) for use with network management protocols in TCP/IP-
internets. This memo does not specify a standard for the
community
Reynolds [Page 8]
RFC 1199 Summary of 1100-1199 December 1991
1161 Rose Jun 90 SNMP over
This memo defines an experimental means for running the Simple
Management Protocol (SNMP) over OSI transports. This memo does
specify a standard for the Internet community
1160 Cerf May 90 The Internet Activities
This RFC provides a history and description of the Internet
Board (IAB) and its subsidiary organizations. This memo is
informational use and does not constitute a standard. This is
revision of RFC 1120.
1159 Nelson Jun 90 Message Send
This RFC suggests an Experimental Protocol for the Internet community
Hosts on the Internet that choose to implement a Message Send
may experiment with this protocol
1158 Rose May 90 Management Information Base
Network Management of TCP/IP-
internets: MIB-
This memo defines the second version of the Management Information
(MIB-II) for use with network management protocols in TCP/IP-
internets. In particular, together with its companion memos
describe the structure of management information (RFC 1155) along
the network management protocol (RFC 1157) for TCP/IP- based internets
these documents provide a simple, workable architecture and system
managing TCP/IP-based internets and in particular the
community
This document on MIB-II incorporates all of the technical content of
1156 on MIB-I and extends it, without loss of compatibilty
[STANDARDS-TRACK
1157 Case May 90 A Simple Network
Protocol (SNMP
This RFC is a re-release of RFC 1098, with a changed "Status of
Memo" section plus a few minor typographical corrections. This
defines a simple protocol by which management information for a
element may be inspected or altered by logically remote users
[STANDARDS-TRACK
Reynolds [Page 9]
RFC 1199 Summary of 1100-1199 December 1991
1156 McCloghrie May 90 Management Information Base
Network Management
TCP/IP-based
This RFC is a re-release of RFC 1066, with a changed "Status of
Memo", "IAB Policy Statement", and "Introduction" sections plus a
minor typographical corrections. The technical content of the
is unchanged from RFC 1066. [STANDARDS-TRACK
1155 Rose May 90 Structure and Identification
Management Information
TCP/IP-based
This RFC is a re-release of RFC 1065, with a changed "Status of
Memo", plus a few minor typographical corrections. The
content of the document is unchanged from RFC 1065. [STANDARDS-TRACK
1154 Robinson Apr 90 Encoding Header Field
Internet
This RFC proposes an elective experimental Encoding header field
permit the mailing of multi-part, multi-structured messages
The use of Encoding updates RFC 1049 (Content-Type), and is a
update to RFCs 1113, 1114, and 1115 (Privacy Enhancement).
1153 Wancho Apr 90 Digest Message
This memo describes the de facto standard Digest Message Format.
is an elective experimental protocol
1152 Partridge Apr 90 Workshop Report: Internet
Steering GroupWorkshop
Very-High-Speed
This memo is a report on a workshop sponsored by the Internet
Steering Group. This memo is for information only. This RFC does
specify an Internet standard
1151 Partridge Apr 90 Version 2 of the Reliable
Protocol (RDP
This RFC suggests several updates to the specification of the
Reynolds [Page 10]
RFC 1199 Summary of 1100-1199 December 1991
Data Protocol (RDP) in RFC-908 based on experience with the protocol
This revised version of the protocol is experimental
1150 Malkin Mar 90 F.Y.I on F.Y.I
Introduction to the F.Y.I.
This memo is the first in a new sub-series of RFCs called FYIs (For
Information). This memo provides information for the
community. It does not specify any standard. [Also FYI 1.]
1149 Waitzman Apr 90 A Standard for the Transmission
IP Datagrams on Avian
This memo describes an experimental method for the encapsulation of
datagrams in avian carriers. This specification is primarily useful
Metropolitan Area Networks. This is an experimental, not
standard
1148 Kille Mar 90 Mapping between X.400(1988) /
ISO 10021 and RFC 822
This RFC suggests an electronic mail protocol mapping for the
community and UK Academic Community, and requests discussion
suggestions for improvements. This memo does not specify an
standard. This edition includes material lost in editing
1147 Stine Apr 90 FYI on a Network Management
Catalog: Tools for Monitoring
Debugging TCP/IP
and Interconnected
The goal of this FYI memo is to provide practical information to
administrators and network managers. This memo provides information
the Internet community. It does not specify any standard. It is not
statement of IAB policy or recommendations. [Also FYI 2.] This
contains descriptions of several tools available to assist
managers in debugging and maintaining TCP/IP internets
interconnected communications resources. Entries in the catalog
what a tool does, how it works, and how it can be obtained
Reynolds [Page 11]
RFC 1199 Summary of 1100-1199 December 1991
1146 Zweig Mar 90 TCP Alternate Checksum
This memo is suggests a pair of TCP options to allow use of
data checksum algorithms in the TCP header. The use of these options
experimental, and not recommended for production use. Note: This
corrects errors introduced in the editing process in RFC 1145.
1145 Zweig Feb 90 TCP Alternate Checksum
This memo is suggests a pair of TCP options to allow use of
data checksum algorithms in the TCP header. The use of these options
experimental, and not recommended for production use
1144 Jacobson Feb 90 Compressing TCP/IP Headers
Low-Speed Serial
This RFC describes a method for compressing the headers of TCP/
datagrams to improve performance over low speed serial links.
motivation, implementation and performance of the method are described
C code for a sample implementation is given for reference. [STANDARDS
TRACK
1143 Bernstein Feb 90 The Q Method of Implementing
Option
This is RFC discusses an implementation approach to option
in the Telnet protocol (RFC 854). It does not propose any changes
the TELNET protocol. Rather, it discusses the implementation of
protocol of one feature, only. This is not a protocol specification
This is an experimental method of implementing a protocol
1142 Oran Feb 90 OSI IS-IS Intra-domain Routing
This RFC is a republication of ISO DP 10589 as a service to
Internet community. This is not an Internet standard
1141 Mallory Jan 90 Incremental Updating of
Internet
This memo correctly describes the incremental update procedure for
with the standard Internet checksum. It is intended to replace
description of Incremental Update in RFC 1071. This is not a
but rather, an implementation technique
Reynolds [Page 12]
RFC 1199 Summary of 1100-1199 December 1991
1140 Postel May 90 IAB Official Protocol
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Activities Board (IAB).
This memo is issued quarterly, please be sure the copy you are
is dated within the last three months. Current copies may be
from the Network Information Center or from the Internet
Numbers Authority. Do not use this edition after 31-Aug-90.
1139 Hagens Jan 90 An Echo Function for ISO 8473
This memo defines an echo function for the connection-less network
protocol. Two mechanisms are introduced that may be used to
the echo function. The first mechanism is recommended as an
solution for the Internet community. The second mechanism will
progressed to the ANSI X3S3.3 working group for consideration as a
item
When an ISO standard is adopted that provides functionality similar
that described by this memo, then this memo will become obsolete
superceded by the ISO standard. This memo is not intended to
with an ISO standard. [STANDARDS-TRACK
1138 Kille Dec 89 Mapping between X.400(1988) / ISO 10021
and RFC 822
Ths RFC suggests an electronic mail protocol mapping for the
community and UK Academic Community, and requests discussion
suggestions for improvements. This memo does not specify an
standard. This memo updates RFCs 822, 987, and 1026.
1137 Kille Dec 89 Mapping Between Full RFC 822
RFC 822 with Restricted
This RFC suggests an electronic mail protocol mapping for the
community and UK Academic Community, and requests discussion
suggestions for improvements. This memo does not specify an
standard
1136 Hares Dec 89 Administrative Domains and Routing
A Model for Routing in the
This RFC proposes a model for describing routing within the Internet
Reynolds [Page 13]
RFC 1199 Summary of 1100-1199 December 1991
The model is an adaptation of the "OSI Routeing Framework". This
does not specify an Internet standard
1135 Reynolds Dec 89 The Helminthiasis of the
This memo takes a look back at the helminthiasis (infestation with,
disease caused by parasitic worms) of the Internet that was
the evening of 2 November 1988. This RFC provides information about
event that occurred in the life of the Internet. This memo does
specify any standard
This document provides a glimpse at the infection, its festering,
cure. The impact of the worm on the Internet community,
statements, the role of the news media, crime in the computer world,
future prevention is discussed. A documentation review presents
publications that describe in detail this particular parasitic
program. Reference and bibliography sections are also included
1134 Perkins Nov 89 The Point-to-Point Protocol: A
for Multi-Protocol Transmission
Datagrams Over Point-to-Point
This proposal is the product of the Point-to-Point Protocol
Group of the Internet Engineering Task Force (IETF). Comments on
memo should be submitted to the IETF Point-to-Point Protocol
Group chair by January 15, 1990. Comments will be reviewed at
February 1990 IETF meeting, with the goal of advancing PPP to
standard status. [STANDARDS-TRACK
1133 Yu Nov 89 Routing between the NSFNET and the
This document is a case study of the implementation of routing
the NSFNET and the DDN components (the MILNET and the ARPANET). We
that it can be used to expand towards interconnection of
Administrative Domains. We would welcome discussion and
about the methods employed for the interconnections. No standards
specified in this memo
1132 McLaughlin Nov 89 A Standard for the Transmission
802.2 Packets over IPX
This document specifies a standard method of encapsulating 802.2
on networks supporting Novell's Internet Packet Exchange Protocol (IPX).
It obsoletes earlier documents detailing the transmission of
Reynolds [Page 14]
RFC 1199 Summary of 1100-1199 December 1991
packets over IPX networks. It differs from these earlier documents
that it allows for the transmission of multiple network protocols
IPX and for the transmission of packets through IPX bridges
1131 Moy Oct 89 The OSPF
This RFC is the specification of the Open Shortest Path First (OSPF
Internet routing protocol. OSPF is in the class of Internal
Protocols (IGPs) for distributing routing information between
of a single Autonomous System. This routing protocol is based on
link-state approach (in contrast to the distance-vector approach).
specification was developed by the OSPF Working Group of the
Engineering Task Force. [STANDARDS-TRACK
1130 Postel Oct 89 IAB Official Protocol
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Activities Board (IAB).
1129 Mills Oct 89 Internet Time Synchronization
the Network Time
This memo describes the Network Time Protocol (NTP) designed
distribute time information in a large, diverse internet
operating at speeds from mundane to lightwave. It uses a returnable
time architecture in which a distributed subnet of time
operating in a self-organizing, hierarchical, master-slave
synchronizes local clocks within the subnet and to national
standards via wire or radio. The servers can also redistribute
information within a network via local routing algorithms and
daemons
The architectures, algorithms and protocols which have evolved to
over several years of implementation and refinement are described
this paper. The synchronization subnet which has been in
operation in the Internet for the last several years is described
with performance data which shows that timekeeping accuracy
most portions of the Internet can be ordinarily maintained to within
few tens of milliseconds, even in cases of failure or disruption
clocks, time servers or networks
This memo describes the Network Time Protocol in RFC-1119.
Reynolds [Page 15]
RFC 1199 Summary of 1100-1199 December 1991
1128 Mills Oct 89 Measured Performance of the Network
Protocol in the Internet
This paper describes a series of experiments involving over 100,000
hosts of the Internet system and located in the U.S., Europe and
Pacific. The experiments are designed to evaluate the availability
accuracy and reliability of international standard time
using the DARPA/NSF Internet and the Network Time Protocol (NTP),
is specified in RFC-1119. NTP is designed specifically for use in
large, diverse internet system operating at speeds from mundane
lightwave. In NTP a distributed subnet of time servers operating in
self-organizing, hierarchical, master-slave configuration
precision timestamps in order to synchronize subnet clocks to each
and national time standards via wire or radio
The experiments are designed to locate Internet hosts and gateways
provide time by one of three time distribution protocols and
the accuracy of their indications. For those hosts that support NTP
the experiments determine the distribution of errors and
statistics over paths spanning major portions of the globe. Finally
the experiments evaluate the accuracy and reliability of
timekeeping using NTP and typical Internet paths involving DARPA,
and other agency networks. The experiments demonstrate that
accuracy throughout most portions of the Internet can be
maintained to within a few tens of milliseconds, even in cases
failure or disruption of clocks, time servers or networks
This memo does not specify a standard
1127 Braden Oct 89 Perspective on Host
This RFC is for information only; it does not constitute a standard
draft standard, or proposed standard, and it does not define a protocol
1126 Little Oct 89 Goals and Functional Requirements
Inter-Autonomous System
This document describes the functional requirements for a
protocol to be used between autonomous systems. This document
intended as a necessary precursor to the design of a new inter
autonomous system routing protocol and specifies requirements for
Internet applicable for use with the current DoD IP, the ISO IP,
future Internet Protocols. It is intended that these requirements
form the basis for the future development of a new inter-
systems routing architecture and protocol. This memo does not specify
standard
Reynolds [Page 16]
RFC 1199 Summary of 1100-1199 December 1991
1125 Estrin Nov 89 Policy Requirements for
Administrative Domain
The purpose of this memo is to focus discussion on particular
in the Internet and possible methods of solution. No proposed
in this document are intended as standards for the Internet. Rather,
is hoped that a general consensus will emerge as to the
solution to such problems, leading eventually to the development
adoption of standards
1124 Leiner Sep 89 Policy Issues in Interconnecting
To support the activities of the Federal Research Internet
Committee (FRICC) in creating an interconnected set of networks to
the research community, two workshops were held to address the
support of policy issues that arise when interconnecting such networks
Held under the suspices of the Internet Activities Board at the
of the FRICC, and sponsored by NASA through RIACS, the
addressed the required and feasible technologies and architectures
could be used to satisfy the desired policies for interconnection.
purpose of this RFC is to report the results of these workshops
1123 Braden Oct 89 Requirements for Internet Hosts --
Application and
This RFC is an official specification for the Internet community.
incorporates by reference, amends, corrects, and supplements the
protocol standards documents relating to hosts. [STANDARDS-TRACK
1122 Braden Oct 89 Requirements for Internet Hosts --
Communication
This RFC is an official specification for the Internet community.
incorporates by reference, amends, corrects, and supplements the
protocol standards documents relating to hosts. [STANDARDS-TRACK
1121 Postel Sep 89 Act One - The
This RFC presents a collection of poems that were presented at "
One", a symposium held partially in celebration of the 20th
of the ARPANET
Reynolds [Page 17]
RFC 1199 Summary of 1100-1199 December 1991
1120 Cerf Sep 89 The Internet Activities
This RFC provides a history and description of the Internet
Board (IAB) and its subsidiary organizations. This memo is
informational use and does not constitute a standard
1119 Mills Sep 89 Network Time Protocol (Version 2)
Specification and
This document 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. [STANDARDS-TRACK
1118 Krol Sep 89 The Hitchhikers Guide to the
This RFC is being distributed to members of the Internet community
order to make available some "hints" which will allow new
participants to understand how the direction of the Internet is set,
to acquire online information and how to be a good Internet neighbor
While the information discussed may not be relevant to the
problems of the Internet, it may be interesting to a number
researchers and implementors. No standards are defined or specified
this memo
1117 Romano Aug 89 Internet
This memo is an official status report on the network numbers and
autonomous system numbers used in the Internet community
1116 Borman Aug 89 Telnet Linemode
Hosts on the Internet that support Linemode within the Telnet
are expected to adopt and implement this protocol. Obsoleted by
1184. [STANDARDS-TRACK
Reynolds [Page 18]
RFC 1199 Summary of 1100-1199 December 1991
1115 Linn Aug 89 Privacy Enhancement for
Electronic Mail: Part III --
Algorithms, Modes, and
This RFC provides definitions, references, and citations
algorithms, usage modes, and associated identifiers used in RFC-1113
and RFC-1114 in support of privacy-enhanced electronic mail
[STANDARDS-TRACK
1114 Kent Aug 89 Privacy Enhancement for
Electronic Mail: Part II --
Certificate-Based Key
This RFC specifies the key management aspects of Privacy Enhanced Mail
[STANDARDS-TRACK
1113 Linn Aug 89 Privacy Enhancement for
Electronic Mail: Part I --
Encipherment and
This RFC specifies features for private electronic mail based
encryption technology. [STANDARDS-TRACK
1112 Deering Aug 89 Host Extensions for IP
This memo specifies the extensions required of a host implementation
the Internet Protocol (IP) to support multicasting.
procedure for IP multicasting in the Internet. This RFC obsoletes
998 and 1054. [STANDARDS-TRACK
1111 Postel Aug 89 Request for Comments on Request
Comments - Instructions
RFC
This RFC specifies a standard for the Internet community. Authors
RFCs are expected to adopt and implement this standard
1110 McKenzie Aug 89 A Problem with the TCP Big
This memo comments on the TCP Big Window option described in RFC 1106.
Reynolds [Page 19]
RFC 1199 Summary of 1100-1199 December 1991
1109 Cerf Aug 89 Report of the Second Ad
Network Management Review
This RFC reports an official Internet Activities Board (IAB)
position on the treatment of Network Management in the Internet.
RFC presents the results and recommendations of the second Ad
Network Management Review on June 12, 1989. The results of the
such meeting were reported in RFC 1052.
1108 Kent Nov 91 U.S. Department of Defense
Options for the Internet
This RFC specifies the U.S. Department of Defense Basic
Option and the top-level description of the Extended Security
for use with the Internet Protocol. This RFC obsoletes RFC 1038,
"Revised IP Security Option", dated January 1988. [STANDARDS-TRACK
1107 Sollins Jul 89 A Plan for Internet Directory
This memo proposes a program to develop a directory service for
Internet. It reports the results of a meeting held in February 1989,
which was convened to review requirements and options for such
service. This proposal is offered for comment, and does not represent
committed research activity of the Internet community
1106 Fox Jun 89 TCP Big Window and Nak
This memo discusses two extensions to the TCP protocol to provide a
efficient operation over a network with a high bandwidth*delay product
The extensions described in this document have been implemented
shown to work using resources at NASA. This memo describes
Experimental Protocol, these extensions are not proposed as an
standard, but as a starting point for further research
1105 Lougheed Jun 89 A Border Gateway Protocol (BGP
This RFC outlines a specific approach for the exchange of
reachability information between Autonomous Systems. Updated by
1163 and 1164. [STANDARDS-TRACK
Reynolds [Page 20]
RFC 1199 Summary of 1100-1199 December 1991
1104 Braun Jun 89 Models of Policy Based
The purpose of this RFC is to outline a variety of models for
based routing. The relative benefits of the different approaches
reviewed. Discussions and comments are explicitly encouraged to
toward the best policy based routing model that scales well within
large internetworking environment
1103 Katz Jun 89 A Proposed Standard for the
of IP Datagrams over FDDI
This RFC specifies a method of encapsulating the Internet Protocol (IP
datagrams and Address Resolution Protocol (ARP) requests and replies
Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK
1102 Clark May 89 Policy Routing in Internet
The purpose of this RFC is to focus discussion on particular problems
the Internet and possible methods of solution. No proposed solutions
this document are intended as standards for the Internet
1101 Mockapetris Apr 89 DNS Encoding of Network Names
Other
This RFC proposes two extensions to the Domain Name System
- A specific method for entering and retrieving RRs which
between network names and numbers
- Ideas for a general method for describing mappings
arbitrary identifiers and numbers
The method for mapping between network names and addresses is a
standard, the ideas for a general method are experimental
1100 IAB Apr 89 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
Reynolds [Page 21]
RFC 1199 Summary of 1100-1199 December 1991
This memo is issued quarterly, please be sure the copy you are
is dated within the last three months. Current copies may be
from the Network Information Center or from the Internet
Numbers Authority (see the contact information at the end of this memo).
Do not use this memo after 31-July-89.
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
