Network Working Group M. Rose, Editor Request for Comments: 1158 Performance Systems International May 1990 Management Information Base for Network Management of TCP/IP-based internets: MIB-II 1. Status of this Memo This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network
Network Working Group Internet Activities Board Request for Comments: 1140 J. Postel, Editor Obsoletes: RFCs 1130, May 1990 1100, 1083 IAB OFFICIAL PROTOCOL STANDARDS Status of this Memo This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). ... It is not necessary for a gateway to implement TCP or the protocols that Internet Activities Board [Page 4] RFC 1140 IAB Standards May 1990 use TCP (though it may be useful). ...
Network Working Group M. Rose Request for Comments: 1155 Performance Systems International Obsoletes: RFC 1065 K. McCloghrie Hughes LAN Systems May 1990 Structure and Identification of Management Information for TCP/IP-based Internets Table of Contents 1. ... 7 3.2.1 Primitive Types .. ... Each type of object (termed an object type) has a name, a syntax, and an encoding. ... Guidelines for Object Names No object type in the Internet-Standard MIB shall use a sub- identifier of 0 in its name. ...
Network Working Group J. Case Request for Comments: 1157 SNMP Research Obsoletes: RFC 1098 M. Fedor Performance Systems International M. Schoffstall Performance Systems International J. Davin MIT Laboratory for Computer Science May 1990 A Simple Network Management Protocol (SNMP) Table of Contents 1. ... The SNMP Architecture .. ... This implies implementation of the Internet MIB (RFC-1156) and at least one of the two recommended management protocols SNMP (RFC-1157) or CMOT (RFC-1095). ...
... April 1990 Encoding Header Field for Internet Messages 1. Status of the Memo This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. ... Introduction RFC 822 [2] defines an electronic mail message to consist of two parts, the message header and the message body, separated by an apparently blank line. ... A "message" body part's message header may be a full internet message header or it may consist only of an Encoding field. ...
... This memo describes the de facto standard Digest Message Format. ... The header of a digest message should identify the digest in the Wancho [Page 1] RFC 1153 Digest Message Format April 1990 Subject line by listname, the key word, Digest, the volume number (usually a sequential number either starting at 1 or the last two digits of the year and incremented by one starting with the first issue of the next calendar year), and an issue number starting at one for the first issue of a new calendar year. ...
Network Working Group C. Partridge Request for Comments: 1152 BBN Systems and Technologies April 1990 Workshop Report Internet Research Steering Group Workshop on Very-High-Speed Networks Status of this Memo This memo is a report on a workshop sponsored by the Internet Research Steering Group. ... Two characteristics of network traffic that we can expect are the need to provide multiple data streams to the end user and the need to synchronize these streams. ... 2) Congestion control. ...
... April 1990 Version 2 of the Reliable Data Protocol (RDP) Status of this Memo This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. ... Changes To The Protocol Header There are three changes to the protocol header: the checksum algorithm has been changed, the port size increased, and the version number incremented. ... RDP now uses the 16-bit TCP checksum, which is specified on page 16 of RFC-793. ... Source Port |...
Network Working Group R. Stine, Editor Request for Comments: 1147 SPARTA, Inc. FYI: 2 April 1990 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices Status of this Memo The goal of this FYI memo is to provide practical informa- tion to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB pol- icy or recommendations. Comments,
Network Working Group R. Stine, Editor . F Request for Comments: 1147 SPARTA, Inc YI: 2 April 1990 T FYI on a Network Management Tool Catalog: ools for Monitoring and Debugging TCP/IP Internets T Status of this Memo and Interconnected Devices he goal of this FYI memo is to provide practical information to site administrators and network managers. m This memo provides information for the Internet community. It does not specify any standard. It is not a state ent of IAB policy or recommendations. Comments,
Network Working Group D. Waitzman Request for Comments: 1149 BBN STC 1 April 1990 A Standard for the Transmission of IP Datagrams on Avian Carriers Status of this Memo This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. ... The connection topology is limited to a single point-to-point path for each carrier, used with standard carriers, but many carriers can be used without significant interference with each other, outside of early spring. ...
Network Working Group J. Reynolds Request for Comments: 1060 J. Postel Obsoletes RFCs: 1010, 990, 960, 943, 923, 900, 870, ISI 820, 790, 776, 770, 762, 758,755, 750, 739, 604, March 1990 503, 433, 349 Obsoletes IENs: 127, 117, 93 ASSIGNED NUMBERS STATUS OF THIS MEMO 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. Table of Contents INTRODUCTION.................................................... 2
Network Working Group G. Malkin Request for Comments: 1150 Proteon FYI: 1 J. Reynolds ISI March 1990 F.Y.I. on F.Y.I. Introduction to the F.Y.I. Notes Status of this Memo This RFC is the first in a new sub-series of RFCs called FYIs (For Your Information). ... Distribution of this memo is unlimited. ... Introduction The FYI series of notes is designed to provide Internet users with a central repository of information about any topics which relate to the Internet. ... FYIs should share that respect. ...
... The DCN local-net protocols are intended to provide connectivity, routing and timekeeping functions for a set of randomly connected personal computers and service hosts. ... For class-A nets normally the third octet (ARPANET logical-host field) is used for routing where necessary. ... Net Name | ... The "Port ID" field contains the port ID of the net-output process on the shortest path to this virtual host and the "Delay" field contains the measured roundtrip delay to it. ... Host | Delay Host 0 | ...
Network Working Group S. Kille Request for Comments 1148 University College London Updates: RFCs 822, 987, 1026, 1138 March 1990 Mapping between X.400(1988) / ISO 10021 and RFC 822 Status of this Memo This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing. Distribution of this memo is unlimited. This
Network Working Group J. Zweig Request for Comments: 1146 UIUC Obsoletes: RFC 1145 C. Partridge BBN March 1990 TCP Alternate Checksum Options Status of This Memo This memo suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. ... During communication, the alternate checksum replaces the regular TCP checksum in the checksum field of the TCP header. ... Otherwise, the standard TCP checksum algorithm must be used for the entire connection. ... data | ...
Network Working Group V. Jacobson/1/ Request for Comments: 1144 LBL February 1990 Compressing TCP/IP Headers for Low-Speed Serial Links Status of this Memo This RFC is a proposed elective protocol for the Internet community and requests discussion and suggestions for improvement. ... If a matching connection is found, the incoming packet is compressed, the (uncompressed) packet header is copied into the array, and a packet of type COMPRESSED_TCP is sent to the framer. ... compress. |on data |on wire | ...
Network Working Group V. Jacobson y Request for Comments: 1144 LBL February 1990 Compressing TCP/IP Headers for LowSpeed Serial Links Status of this Memo This RFC is a proposed elective protocol for the Internet community and requests discus sion and suggestions for improvement. It describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motiva tion, implementation and performance of the method are described. C code for a sample