Internet Documents RFCs RFCs All Documents STDs Internet Standards Documents BCPs Best Current Practice Documents FYIs Informational Documents

RFC 698	Telnet extended ASCII option
	Authors: T. Mock. Date: July 1975 Formats: txt pdf Obsoleted by: RFC 5198 Status: PROPOSED STANDARD Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.
RFC 726	Remote Controlled Transmission and Echoing Telnet option
	Authors: J. Postel, D. Crocker. Date: March 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 727	Telnet logout option
	Authors: M.R. Crispin. Date: April 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 735	Revised Telnet byte macro option
	Authors: D. Crocker, R.H. Gumpertz. Date: November 1977 Formats: txt pdf Obsoletes: RFC 0729 Status: PROPOSED STANDARD
RFC 736	Telnet SUPDUP option
	Authors: M.R. Crispin. Date: October 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 749	Telnet SUPDUP-Output option
	Authors: B. Greenberg. Date: September 1978 Formats: txt pdf Status: PROPOSED STANDARD
RFC 779	Telnet send-location option
	Authors: E. Killian. Date: April 1 1981 Formats: txt pdf Status: PROPOSED STANDARD
RFC 885	Telnet end of record option
	Authors: J. Postel. Date: December 1983 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a standard for the ARPA Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections.
RFC 927	TACACS user identification Telnet option
	Authors: B.A. Anderson. Date: December 1984 Formats: txt pdf Status: PROPOSED STANDARD The following is the description of a TELNET option designed to facilitate double login avoidance. It is intended primarily for TAC connections to target hosts on behalf of TAC users, but it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 933	Output marking Telnet option
	Authors: S. Silverman. Date: January 1985 Formats: txt pdf Status: PROPOSED STANDARD This proposed option would allow a Server-Telnet to send a banner to a User-Telnet so that this banner would be displayed on the workstation screen independently of the application software running in the Server-Telnet.
RFC 946	Telnet terminal location number option
	Authors: R. Nedved. Date: May 1985 Formats: txt pdf Status: PROPOSED STANDARD Many systems provide a mechanism for finding out where a user is logged in from usually including information about telephone extension and office occupants names. The information is useful for physically locating people and/or calling them on the phone. In 1982 CMU designed and implemented a terminal location database and modified existing network software to handle a 64-bit number called the Terminal Location Number (or TTYLOC). It now seems appropriate to incorporate this mechanism into the TCP-based network protocol family. The mechanism is not viewed as a replacement for the Terminal Location Telnet Option (SEND-LOCATION) but as a shorthand mechansim for communicating terminal location information between hosts in a localized community. This RFC proposes a new option for Telnet for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 977	Network News Transfer Protocol
	Authors: B. Kantor, P. Lapsley. Date: February 1986 Formats: txt pdf Obsoleted by: RFC 3977 Status: PROPOSED STANDARD NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream-based transmission of news among the ARPA-Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 1041	Telnet 3270 regime option
	Authors: Y. Rekhter. Date: January 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard.
RFC 1043	Telnet Data Entry Terminal option: DODIIS implementation
	Authors: A. Yasuda, T. Thompson. Date: February 1988 Formats: txt pdf Updates: RFC 0732 Status: PROPOSED STANDARD This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation for the Internet community. It is intended that this specification be capatible with the specification of DET Option in RFC-732. Discussion and suggests for improvements are encouraged.
RFC 1053	Telnet X.3 PAD option
	Authors: S. Levy, T. Jacobson. Date: April 1 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements.
RFC 1073	Telnet window size option
	Authors: D. Waitzman. Date: October 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server.
RFC 1079	Telnet terminal speed option
	Authors: C.L. Hedrick. Date: December 1988 Formats: txt pdf Status: PROPOSED STANDARD 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.
RFC 1091	Telnet terminal-type option
	Authors: J. VanBokkelen. Date: February 1989 Formats: txt pdf Obsoletes: RFC 0930 Status: PROPOSED STANDARD 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
RFC 1096	Telnet X display location option
	Authors: G.A. Marcy. Date: March 1989 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a standard for the Internet community. Hosts on the Internet that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard.
RFC 1116	Telnet Linemode option
	Authors: D.A. Borman. Date: August 1989 Formats: txt pdf Obsoleted by: RFC 1184 Status: PROPOSED STANDARD Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK]
RFC 1131	OSPF specification
	Authors: J. Moy. Date: October 1989 Formats: txt pdf ps Obsoleted by: RFC 1247 Status: PROPOSED STANDARD This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK]
RFC 1134	Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links
	Authors: D. Perkins. Date: November 1989 Formats: txt pdf Obsoleted by: RFC 1171 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts: 1. A method for encapsulating datagrams over serial links. 2. An extensible Link Control Protocol (LCP). 3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP). The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed.
RFC 1139	Echo function for ISO 8473
	Authors: R.A. Hagens. Date: January 1990 Formats: txt pdf Obsoleted by: RFC 1574, RFC 1575 Status: PROPOSED STANDARD This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item. When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard.
RFC 1144	Compressing TCP/IP Headers for Low-Speed Serial Links
	Authors: V. Jacobson. Date: February 1990 Formats: txt pdf ps Status: PROPOSED STANDARD This RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motivation, implementation and performance of the method are described. C code for a sample implementation is given for reference. [STANDARDS- TRACK]
RFC 1158	Management Information Base for network management of TCP/IP-based internets: MIB-II
	Authors: M.T. Rose. Date: May 1990 Formats: txt pdf Obsoleted by: RFC 1213 Status: PROPOSED STANDARD 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 management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK]
RFC 1172	Point-to-Point Protocol (PPP) initial configuration options
	Authors: D. Perkins, R. Hobby. Date: July 1990 Formats: txt pdf Obsoleted by: RFC 1331, RFC 1332 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of 1) a method for encapsulating datagrams over serial links,2) an extensible Link Control Protocol (LCP), and3) a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. The PPP encapsulating scheme, the basic LCP, and an NCP for controlling and establishing the Internet Protocol (IP) (called theIP Control Protocol, IPCP) are defined in The Point-to-Point Protocol(PPP) [1]. This document defines the intial options used by the LCP and IPCP. It also defines a method of Link Quality Monitoring and a simple authentication scheme.
RFC 1195	Use of OSI IS-IS for routing in TCP/IP and dual environments
	Authors: R.W. Callon. Date: December 1990 Formats: txt pdf ps Updated by: RFC 1349, RFC 5302, RFC 5304 Status: PROPOSED STANDARD This RFC specifies an integrated routing protocol, based on the OSIIntra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering TaskForce. The OSI IS-IS protocol has reached a mature state, and is ready for implementation and operational use. The most recent version of theOSI IS-IS protocol is contained in ISO DP 10589 [1]. The proposed standard for using IS-IS for support of TCP/IP will therefore make use of this version (with a minor bug correction, as discussed inAnnex B). We expect that future versions of this proposed standard will upgrade to the final International Standard version of IS-IS when available. Comments should be sent to "isis@merit.edu".
RFC 1220	Point-to-Point Protocol extensions for bridging
	Authors: F. Baker. Date: April 1 1991 Formats: txt pdf Obsoleted by: RFC 1638 Status: PROPOSED STANDARD This document defines an extension of the Internet Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use of Point-to- Point lines for Remote Bridging. [STANDARDS-TRACK]
RFC 1229	Extensions to the generic-interface MIB
	Authors: K. McCloghrie. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1573 Updated by: RFC 1239 Status: PROPOSED STANDARD This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS- TRACK]
RFC 1231	IEEE 802.5 Token Ring MIB
	Authors: K. McCloghrie, R. Fox, E. Decker. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1743, RFC 1748 Updated by: RFC 1239 Status: PROPOSED STANDARD This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]
RFC 1232	Definitions of managed objects for the DS1 Interface type
	Authors: F. Baker, C.P. Kolb. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1406 Updated by: RFC 1239 Status: PROPOSED STANDARD
RFC 1233	Definitions of managed objects for the DS3 Interface type
	Authors: T.A. Cox, K. Tesink. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1407 Updated by: RFC 1239 Status: PROPOSED STANDARD This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]
RFC 1237	Guidelines for OSI NSAP Allocation in the Internet
	Authors: R. Colella, E. Gardner, R. Callon. Date: July 1991 Formats: txt pdf ps Obsoleted by: RFC 1629 Status: PROPOSED STANDARD This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK]
RFC 1243	AppleTalk Management Information Base
	Authors: S. Waldbusser. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 1742 Status: PROPOSED STANDARD This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK]
RFC 1248	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 1252 Updated by: RFC 1349 Status: PROPOSED STANDARD This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
RFC 1252	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: August 1991 Formats: txt pdf Obsoletes: RFC 1248 Obsoleted by: RFC 1253 Also: RFC 1247, RFC 1245 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
RFC 1253	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: August 1991 Formats: txt pdf Obsoletes: RFC 1252 Obsoleted by: RFC 1850 Also: RFC 1247, RFC 1245, RFC 1246 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
RFC 1256	ICMP Router Discovery Messages
	Authors: S. Deering, Ed.. Date: September 1991 Formats: txt pdf Also: RFC 0792 Status: PROPOSED STANDARD This document specifies an extension of the Internet Control MessageProtocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers.
RFC 1269	Definitions of Managed Objects for the Border Gateway Protocol: Version 3
	Authors: S. Willis, J.W. Burruss. Date: October 1991 Formats: txt pdf Obsoleted by: RFC 4273 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK]
RFC 1271	Remote Network Monitoring Management Information Base
	Authors: S. Waldbusser. Date: November 1991 Formats: txt pdf Obsoleted by: RFC 1757 Updated by: RFC 1513 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
RFC 1274	The COSINE and Internet X.500 Schema
	Authors: P. Barker, S. Kille. Date: November 1991 Formats: txt pdf Obsoleted by: RFC 4524 Status: PROPOSED STANDARD This document suggests an X.500 Directory Schema, or NamingArchitecture, for use in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, a large number of generally useful object classes and attributes are also defined. An appendix to this document includes a machine processable version of the schema. This document also proposes a mechanism for allowing the schema to evolve in line with emerging requirements. Proformas to support this process are included. Corrections and additions to the schema should be sent to na- update@cs.ucl.ac.uk list, as described within.
RFC 1277	Encoding Network Addresses to Support Operation over Non-OSI Lower Layers
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt ps pdf Status: PROPOSED STANDARD The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSINetwork Layer standards [CCI88] [ISO87a]. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSINetwork Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a globalOSI Network Service. This document defines a new network address format, and rules for using some existing network address formats. The scope of this document is:
RFC 1284	Definitions of Managed Objects for the Ethernet-like Interface Types
	Authors: J. Cook, Ed.. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1398 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
RFC 1286	Definitions of Managed Objects for Bridges
	Authors: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1493, RFC 1525 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK]
RFC 1289	DECnet Phase IV MIB Extensions
	Authors: J. Saperia. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1559 Status: PROPOSED STANDARD This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. When used in conjunction with the structure of management information (RFC 1155), the management information base for network management of TCP/IP-based internets(RFC 1213) and the Simple Network Management Protocol (RFC 1157), it will be possible to provide integrated network management of combinedTCP/IP and DECnet Phase IV based internets. This document was produced by the DECnet Phase IV MIB working group of the InternetEngineering Task Force (IETF).
RFC 1293	Inverse Address Resolution Protocol
	Authors: T. Bradley, C. Brown. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 2390 Status: PROPOSED STANDARD This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
RFC 1294	Multiprotocol Interconnect over Frame Relay
	Authors: T. Bradley, C. Brown, A. Malis. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1490, RFC 2427 Status: PROPOSED STANDARD This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
RFC 1304	Definitions of Managed Objects for the SIP Interface Type
	Authors: T. Cox, K. Tesink, Eds.. Date: February 1992 Formats: txt pdf Obsoleted by: RFC 1694 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing SIP (SMDS InterfaceProtocol) objects.
RFC 1315	Management Information Base for Frame Relay DTEs
	Authors: C. Brown, F. Baker, C. Carvalho. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 2115 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing Frame Relay.
RFC 1316	Definitions of Managed Objects for Character Stream Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1658 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK]
RFC 1317	Definitions of Managed Objects for RS-232-like Hardware Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1659 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK]
RFC 1318	Definitions of Managed Objects for Parallel-printer-like Hardware Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1660 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK]
RFC 1323	TCP Extensions for High Performance
	Authors: V. Jacobson, R. Braden, D. Borman. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1072, RFC 1185 Status: PROPOSED STANDARD This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. The timestamps are used for two distinct mechanisms:RTTM (Round Trip Time Measurement) and PAWS (Protect Against WrappedSequences). Selective acknowledgments are not included in this memo. This memo combines and supersedes RFC-1072 and RFC-1185, adding additional clarification and more detailed specification. Appendix C summarizes the changes from the earlier RFCs.
RFC 1327	Mapping between X.400(1988) / ISO 10021 and RFC 822
	Authors: S. Hardcastle-Kille. Date: May 1992 Formats: txt pdf Obsoletes: RFC 0987, RFC 1026, RFC 1138, RFC 1148 Obsoleted by: RFC 2156 Updates: RFC 0822 Updated by: RFC 1495 Status: PROPOSED STANDARD This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 1988)Recommendations on Message Handling Systems / ISO IEC 10021 MessageOriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems using the RFC 822 mail protocol [Crocker82a] or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings.The mappings should not require any changes to end systems. This document is a revision based on RFCs 987, 1026, 1138, and 1148[Kille86a,Kille87a] which it obsoletes. This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on theDARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected.
RFC 1331	The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links
	Authors: W. Simpson. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1171, RFC 1172 Obsoleted by: RFC 1548 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is comprised of three main components: 1. A method for encapsulating datagrams over serial links. 2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. 3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the PPP encapsulation scheme, together with thePPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1332	The PPP Internet Protocol Control Protocol (IPCP)
	Authors: G. McGregor. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1172 Updated by: RFC 3241 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring theInternet Protocol [2] over PPP, and a method to negotiate and use VanJacobson TCP/IP header compression [3] with PPP. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF).
RFC 1333	PPP Link Quality Monitoring
	Authors: W. Simpson. Date: May 1992 Formats: txt pdf Obsoleted by: RFC 1989 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link. This document defines a protocol for generating Link-Quality-Reports. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1334	PPP Authentication Protocols
	Authors: B. Lloyd, W. Simpson. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1994 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. This document defines two protocols for Authentication: the PasswordAuthentication Protocol and the Challenge-Handshake AuthenticationProtocol. This memo is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1341	MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies
	Authors: N. Borenstein, N. Freed. Date: June 1992 Formats: txt pdf ps Obsoleted by: RFC 1521 Status: PROPOSED STANDARD This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK]
RFC 1342	Representation of Non-ASCII Text in Internet Message Headers
	Authors: K. Moore. Date: June 1992 Formats: txt pdf Obsoleted by: RFC 1522 Status: PROPOSED STANDARD This memo describes an extension to the message format defined in [1](known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC822 message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1341.
RFC 1349	Type of Service in the Internet Protocol Suite
	Authors: P. Almquist. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 2474 Updates: RFC 1248, RFC 1247, RFC 1195, RFC 1123, RFC 1122, RFC 1060, RFC 0791 Status: PROPOSED STANDARD This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK]
RFC 1354	IP Forwarding Table MIB
	Authors: F. Baker. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 2096 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing routes in the IPInternet. It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be deprecated and replaced with this table. This adds the ability to set or display multi-path routes, and varying routes by network management policy.
RFC 1364	BGP OSPF Interaction
	Authors: K. Varadhan. Date: September 1992 Formats: txt pdf Obsoleted by: RFC 1403 Also: RFC 1247, RFC 1267 Status: PROPOSED STANDARD This memo defines the various criteria to be used when designingAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP.
RFC 1368	Definition of Managed Objects for IEEE 802.3 Repeater Devices
	Authors: D. McMaster, K. McCloghrie. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1516 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs."
RFC 1372	Telnet Remote Flow Control Option
	Authors: C. Hedrick, D. Borman. Date: October 1992 Formats: txt pdf Obsoletes: RFC 1080 Status: PROPOSED STANDARD This document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK]
RFC 1374	IP and ARP on HIPPI
	Authors: J. Renwick, A. Nicholson. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 2834 Status: PROPOSED STANDARD The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP onHIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks.
RFC 1376	The PPP DECnet Phase IV Control Protocol (DNCP)
	Authors: S. Senum. Date: November 1992 Formats: txt pdf Obsoleted by: RFC 1762 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuringDigital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.).
RFC 1377	The PPP OSI Network Layer Control Protocol (OSINLCP)
	Authors: D. Katz. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring OSINetwork Layer Protocols. This memo is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1381	SNMP MIB Extension for X.25 LAPB
	Authors: D. Throop, F. Baker. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing the Link Layer ofX.25, LAPB. The objects defined here, along with the objects in the"SNMP MIB Extension for the Packet Layer of X.25" [9] and the"Definitions of Managed Objects for RS-232-like Hardware Devices"[8], combine to allow management of an X.25 protocol stack.
RFC 1382	SNMP MIB Extension for the X.25 Packet Layer
	Authors: D. Throop, Ed.. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing the Packet Layer ofX.25. The objects defined here, along with the objects in the "SNMPMIB Extension for LAPB" [9] and the "Definitions of Managed Objects for RS-232-like Hardware Devices" [8], combine to allow management of an X.25 protocol stack.
RFC 1388	RIP Version 2 Carrying Additional Information
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1723 Updates: RFC 1058 Status: PROPOSED STANDARD This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP packets and to add a measure of security.A companion document will define the SNMP MIB objects for RIP-2 [2].
RFC 1389	RIP Version 2 MIB Extensions
	Authors: G. Malkin, F. Baker. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1724 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing RIP Version 2.
RFC 1406	Definitions of Managed Objects for the DS1 and E1 Interface Types
	Authors: F. Baker, J. Watt, Eds.. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1232 Obsoleted by: RFC 2495 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. This document entirely replaces RFC 1232, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1232 should not be implemented.
RFC 1407	Definitions of Managed Objects for the DS3/E3 Interface Type
	Authors: T. Cox, K. Tesink. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1233 Obsoleted by: RFC 2496 Status: PROPOSED STANDARD This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3Interfaces. This document is a companion document with Definitions of Managed Objects for the DS1 Interface Type. This document entirely replaces RFC 1233, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1233 should not be implemented.
RFC 1413	Identification Protocol
	Authors: M. St. Johns. Date: February 1993 Formats: txt pdf Obsoletes: RFC 0931 Status: PROPOSED STANDARD The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK]
RFC 1420	SNMP over IPX
	Authors: S. Bostock. Date: March 1993 Formats: txt pdf Obsoletes: RFC 1298 Status: PROPOSED STANDARD This document defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].
RFC 1425	SMTP Service Extensions
	Authors: J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1651 Status: PROPOSED STANDARD This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
RFC 1426	SMTP Service Extension for 8bit-MIMEtransport
	Authors: J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1652 Status: PROPOSED STANDARD This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex
RFC 1427	SMTP Service Extension for Message Size Declaration
	Authors: J. Klensin, WG Chair, N. Freed, Ed., K. Moore. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1653 Status: PROPOSED STANDARD This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK]
RFC 1442	Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1902 Status: PROPOSED STANDARD Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK]
RFC 1443	Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1903 Status: PROPOSED STANDARD It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
RFC 1444	Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1904 Status: PROPOSED STANDARD It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]
RFC 1448	Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1905 Status: PROPOSED STANDARD It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]
RFC 1449	Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1906 Status: PROPOSED STANDARD It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
RFC 1450	Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1907 Status: PROPOSED STANDARD It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
RFC 1452	Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1908 Status: PROPOSED STANDARD The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]
RFC 1471	The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
	< Authors: F. Kastenholz. Date: June 1993 Formats: