| |
| RFC 768 | User Datagram Protocol |
| |
| Authors: | J. Postel. |
| Date: | August 1980 |
| Formats: | txt pdf |
| Also: | STD 0006 |
| Status: | STANDARD |
|
|
|
| |
| RFC 791 | Internet Protocol |
| |
|
| |
| RFC 792 | Internet Control Message Protocol |
| |
|
| |
| RFC 793 | Transmission Control Protocol |
| |
|
| |
| RFC 821 | Simple Mail Transfer Protocol |
| |
|
|
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772. |
|
| |
| RFC 822 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES |
| |
|
|
This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952. |
|
| |
| RFC 826 | Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware |
| |
|
|
The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard. |
|
| |
| RFC 854 | Telnet Protocol Specification |
| |
|
|
This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. |
|
| |
| RFC 855 | Telnet Option Specifications |
| |
| Authors: | J. Postel, J.K. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 18640 |
| Also: | STD 0008 |
| Status: | STANDARD |
|
This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640. |
|
| |
| RFC 856 | Telnet Binary Transmission |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 15389 |
| Also: | STD 0027 |
| Status: | STANDARD |
|
This Telnet Option enables a binary data mode between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15389. |
|
| |
| RFC 857 | Telnet Echo Option |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 15390 |
| Also: | STD 0028 |
| Status: | STANDARD |
|
This Telnet Option enables remote echoing by the other Telnet module. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15390. |
|
| |
| RFC 858 | Telnet Suppress Go Ahead Option |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 15392 |
| Also: | STD 0029 |
| Status: | STANDARD |
|
This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15392. |
|
| |
| RFC 859 | Telnet Status Option |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0651 |
| Also: | STD 0030 |
| Status: | STANDARD |
|
This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154). |
|
| |
| RFC 860 | Telnet Timing Mark Option |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 16238 |
| Also: | STD 0031 |
| Status: | STANDARD |
|
This Telnet Option provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16238. |
|
| |
| RFC 861 | Telnet Extended Options: List Option |
| |
| Authors: | J. Postel, J. Reynolds. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Obsoletes: | NIC 16239 |
| Also: | STD 0032 |
| Status: | STANDARD |
|
This Telnet Option provides a mechanism for extending the set of possible options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16239. |
|
| |
| RFC 862 | Echo Protocol |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0020 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives. |
|
| |
| RFC 863 | Discard Protocol |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0021 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives. |
|
| |
| RFC 864 | Character Generator Protocol |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0022 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input. |
|
| |
| RFC 865 | Quote of the Day Protocol |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0023 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message without regard to the input. |
|
| |
| RFC 866 | Active users |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0024 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input. |
|
| |
| RFC 867 | Daytime Protocol |
| |
| Authors: | J. Postel. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0025 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input. |
|
| |
| RFC 868 | Time Protocol |
| |
| Authors: | J. Postel, K. Harrenstien. |
| Date: | May 1983 |
| Formats: | txt pdf |
| Also: | STD 0026 |
| Status: | STANDARD |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900. |
|
| |
| RFC 891 | DCN Local-Network Protocols |
| |
| Authors: | D.L. Mills. |
| Date: | December 1983 |
| Formats: | txt pdf |
| Also: | STD 0044 |
| Status: | STANDARD |
|
This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks. |
|
| |
| RFC 894 | A Standard for the Transmission of IP Datagrams over Ethernet Networks |
| |
| Authors: | C. Hornig. |
| Date: | April 1 1984 |
| Formats: | txt pdf |
| Also: | STD 0041 |
| Status: | STANDARD |
|
This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community. |
|
| |
| RFC 895 | Standard for the transmission of IP datagrams over experimental Ethernet networks |
| |
| Authors: | J. Postel. |
| Date: | April 1 1984 |
| Formats: | txt pdf |
| Also: | STD 0042 |
| Status: | STANDARD |
|
This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA Internet community. |
|
| |
| RFC 903 | A Reverse Address Resolution Protocol |
| |
| Authors: | R. Finlayson, T. Mann, J.C. Mogul, M. Theimer. |
| Date: | June 1984 |
| Formats: | txt pdf |
| Also: | STD 0038 |
| Status: | STANDARD |
|
This RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address), when they know only their hardware address (e.g., their attached physical network address). This RFC specifies a proposed protocol for the ARPA Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 907 | Host Access Protocol specification |
| |
| Authors: | Bolt Beranek and Newman Laboratories. |
| Date: | July 1984 |
| Formats: | txt pdf |
| Updated by: | RFC 1221 |
| Also: | STD 0040 |
| Status: | STANDARD |
|
This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel. |
|
| |
| RFC 919 | Broadcasting Internet Datagrams |
| |
| Authors: | J.C. Mogul. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Also: | STD 0005 |
| Status: | STANDARD |
|
This RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 922 | Broadcasting Internet datagrams in the presence of subnets |
| |
| Authors: | J.C. Mogul. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Also: | STD 0005 |
| Status: | STANDARD |
|
We propose simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 950 | Internet Standard Subnetting Procedure |
| |
| Authors: | J.C. Mogul, J. Postel. |
| Date: | August 1985 |
| Formats: | txt pdf |
| Updates: | RFC 0792 |
| Also: | STD 0005 |
| Status: | STANDARD |
|
This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This memo specifies procedures for the use of subnets. These procedures are for hosts (e.g., workstations). The procedures used in and between subnet gateways are not fully described. Important motivation and background information for a subnetting standard is provided in RFC-940. This RFC specifies a protocol for the ARPA-Internet community. If subnetting is implemented it is strongly recommended that these procedures be followed. |
|
| |
| RFC 959 | File Transfer Protocol |
| |
|
|
This memo is the official specification of the File Transfer Protocol (FTP) for the DARPA Internet community. The primary intent is to clarify and correct the documentation of the FTP specification, not to change the protocol. The following new optional commands are included in this edition of the specification: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST). Note that this specification is compatible with the previous edition. |
|
| |
| RFC 1001 | Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods |
| |
| Authors: | NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. |
| Date: | March 1987 |
| Formats: | txt pdf |
| Also: | STD 0019 |
| Status: | STANDARD |
|
This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications". |
|
| |
| RFC 1002 | Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications |
| |
| Authors: | NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. |
| Date: | March 1987 |
| Formats: | txt pdf |
| Also: | STD 0019 |
| Status: | STANDARD |
|
This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods". |
|
| |
| RFC 1006 | ISO Transport Service on top of the TCP Version: 3 |
| |
|
|
This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible. |
|
| |
| RFC 1034 | Domain names - concepts and facilities |
| |
| Authors: | P.V. Mockapetris. |
| Date: | November 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0973, RFC 0882, RFC 0883 |
| Updated by: | RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 4035, RFC 4592 |
| Also: | STD 0013 |
| Status: | STANDARD |
|
This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them. |
|
| |
| RFC 1035 | Domain names - implementation and specification |
| |
| Authors: | P.V. Mockapetris. |
| Date: | November 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0973, RFC 0882, RFC 0883 |
| Updated by: | RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996, RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2845, RFC 3425, RFC 3658, RFC 4033, RFC 4034, RFC 4035, RFC 4343 |
| Also: | STD 0013 |
| Status: | STANDARD |
|
This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. |
|
| |
| RFC 1042 | Standard for the transmission of IP datagrams over IEEE 802 networks |
| |
| Authors: | J. Postel, J.K. Reynolds. |
| Date: | February 1988 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0948 |
| Also: | STD 0043 |
| Status: | STANDARD |
|
This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community. |
|
| |
| RFC 1044 | Internet Protocol on Network System's HYPERchannel: Protocol Specification |
| |
| Authors: | K. Hardwick, J. Lekashman. |
| Date: | February 1988 |
| Formats: | txt pdf |
| Also: | STD 0045 |
| Status: | STANDARD |
|
This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols. |
|
| |
| RFC 1055 | Nonstandard for transmission of IP datagrams over serial lines: SLIP |
| |
| Authors: | J.L. Romkey. |
| Date: | June 1988 |
| Formats: | txt pdf |
| Also: | STD 0047 |
| Status: | STANDARD |
|
The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard. |
|
| |
| RFC 1065 | Structure and identification of management information for TCP/IP-based internets |
| |
| Authors: | K. McCloghrie, M.T. Rose. |
| Date: | August 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1155 |
| Status: | STANDARD |
|
This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1088 | Standard for the transmission of IP datagrams over NetBIOS networks |
| |
| Authors: | L.J. McLaughlin. |
| Date: | February 1989 |
| Formats: | txt pdf |
| Also: | STD 0048 |
| Status: | STANDARD |
|
This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks. |
|
| |
| RFC 1112 | Host extensions for IP multicasting |
| |
|
|
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] |
|
| |
| RFC 1119 | Network Time Protocol (version 2) specification and implementation |
| |
|
|
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK] |
|
| |
| RFC 1122 | Requirements for Internet Hosts - Communication Layers |
| |
|
|
This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] |
|
| |
| RFC 1123 | Requirements for Internet Hosts - Application and Support |
| |
|
|
This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] |
|
| |
| RFC 1132 | Standard for the transmission of 802.2 packets over IPX networks |
| |
| Authors: | L.J. McLaughlin. |
| Date: | November 1989 |
| Formats: | txt pdf |
| Also: | STD 0049 |
| Status: | STANDARD |
|
This document specifies a standard method of encapsulating 802.2 packets on networks supporting Novell's Internet Packet Exchange Protocol (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges. |
|
| |
| RFC 1155 | Structure and identification of management information for TCP/IP-based internets |
| |
| Authors: | M.T. Rose, K. McCloghrie. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1065 |
| Also: | STD 0016 |
| Status: | STANDARD |
|
This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK] |
|
| |
| RFC 1201 | Transmitting IP traffic over ARCNET networks |
| |
|
|
This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.This memo specifies a method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams for transmission across ARCNET using the "ARCNET Packet Header Definition Standard". [STANDARDS-TRACK] |
|
| |
| RFC 1209 | The Transmission of IP Datagrams over the SMDS Service |
| |
| Authors: | D. Piscitello, J. Lawrence. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Also: | STD 0052 |
| Status: | STANDARD |
|
This memo describes an initial use of IP and ARP in an SMDS service environment configured as a logical IP subnetwork, LIS (described below). The encapsulation method used is described, as well as various service-specific issues. This memo does not preclude subsequent treatment of the SMDS Service in configurations other thanLIS; specifically, public or inter-company, inter-enterprise configurations may be treated differently and will be described in future documents. This document considers only directly connected IP end-stations or routers; issues raised by MAC level bridging are beyond the scope of this paper. |
|
| |
| RFC 1212 | Concise MIB definitions |
| |
| Authors: | M.T. Rose, K. McCloghrie. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Also: | STD 0016 |
| Status: | STANDARD |
|
This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK] |
|
| |
| RFC 1213 | Management Information Base for Network Management of TCP/IP-based internets:MIB-II |
| |
|
|
This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] |
|
| |
| RFC 1350 | The TFTP Protocol (Revision 2) |
| |
|
|
TFTP is a very simple protocol used to transfer files. It is from this that its name comes, Trivial File Transfer Protocol or TFTP. Each nonterminal packet is acknowledged separately. This document describes the protocol and its types of packets. The document also explains the reasons behind some of the design decisions. [STANDARDS-TRACK] |
|
| |
| RFC 1390 | Transmission of IP and ARP over FDDI Networks |
| |
| Authors: | D. Katz. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Also: | STD 0036 |
| Status: | STANDARD |
|
This memo defines a method of encapsulating the Internet Protocol(IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks.
This RFC is the product of the IP over FDDI Working Group of theInternet Engineering Task Force (IETF). |
|
| |
| RFC 1661 | The Point-to-Point Protocol (PPP) |
| |
|
|
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP is comprised of three main components:
1. A method for encapsulating multi-protocol datagrams.
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 organization and methodology, and thePPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. The PPP Link Control Protocol (LCP) is described in terms of this mechanism. |
|
| |
| RFC 1662 | PPP in HDLC-like Framing |
| |
|
|
The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.
This document describes the use of HDLC-like framing for PPP encapsulated packets. |
|
| |
| RFC 1722 | RIP Version 2 Protocol Applicability Statement |
| |
| Authors: | G. Malkin. |
| Date: | November 1994 |
| Formats: | txt pdf |
| Also: | STD 0057 |
| Status: | STANDARD |
|
As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIP-2 protocol within the Internet.This report is a prerequisite to advancing RIP-2 on the standards track. |
|
| |
| RFC 1723 | RIP Version 2 - Carrying Additional Information |
| |
|
|
This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1,2], to expand the amount of useful information carried in RIP messages and to add a measure of security.This memo obsoletes RFC 1388, which specifies an update to the"Routing Information Protocol" STD 34, RFC 1058.
The RIP-2 protocol analysis is documented in RFC 1721 [4].
The RIP-2 applicability statement is document in RFC 1722 [5].
The RIP-2 MIB description is defined in RFC 1724 [3]. This memo obsoletes RFC 1389. |
|
| |
| RFC 1725 | Post Office Protocol - Version 3 |
| |
| Authors: | J. Myers, M. Rose. |
| Date: | November 1994 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1460 |
| Obsoleted by: | RFC 1939 |
| Status: | STANDARD |
|
This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK] |
|
| |
| RFC 1869 | SMTP Service Extensions |
| |
| Authors: | J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker. |
| Date: | November 1995 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1651 |
| Obsoleted by: | RFC 2821 |
| Also: | STD 0010 |
| Status: | 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 1870 | SMTP Service Extension for Message Size Declaration |
| |
| Authors: | J. Klensin, N. Freed, K. Moore. |
| Date: | November 1995 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1653 |
| Also: | STD 0010 |
| Status: | 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 1939 | Post Office Protocol - Version 3 |
| |
|
|
The Post Office Protocol - Version 3 (POP3) is intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. [STANDARDS-TRACK] |
|
| |
| RFC 2289 | A One-Time Password System |
| |
| Authors: | N. Haller, C. Metz, P. Nesser, M. Straw. |
| Date: | February 1998 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1938 |
| Also: | STD 0061 |
| Status: | STANDARD |
|
This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and other applications requiring authentication that is secure against passive attacks based on replaying captured reusable passwords. [STANDARDS- TRACK] |
|
| |
| RFC 2328 | OSPF Version 2 |
| |
|
|
This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest- path tree.
OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multipath. An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated.
The differences between this memo and RFC 2178 are explained inAppendix G. All differences are backward-compatible in nature.
Implementations of this memo and of RFCs 2178, 1583, and 1247 will interoperate.
Please send comments to ospf@gated.cornell.edu. |
|
| |
| RFC 2427 | Multiprotocol Interconnect over Frame Relay |
| |
|
|
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing.
Systems with the ability to transfer both the encapsulation method described in this document, and others must have a priori knowledge of which virtual circuits will carry which encapsulation method and this encapsulation must only be used over virtual circuits that have been explicitly configured for its use. |
|
| |
| RFC 2453 | RIP Version 2 |
| |
|
|
This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security.
A companion document will define the SNMP MIB objects for RIP-2 [2].An additional document will define cryptographic security improvements for RIP-2 [3]. |
|
| |
| RFC 2578 | Structure of Management Information Version 2 (SMIv2) |
| |
| Authors: | K. McCloghrie, D. Perkins, J. Schoenwaelder. |
| Date: | April 1999 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1902 |
| Also: | STD 0058 |
| Status: | STANDARD |
|
It is the purpose of this document, the Structure of Management Information Version 2 (SMIv2), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK] |
|
| |
| RFC 2579 | Textual Conventions for SMIv2 |
| |
| Authors: | K. McCloghrie, D. Perkins, J. Schoenwaelder. |
| Date: | April 1999 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1903 |
| Also: | STD 0058 |
| Status: | STANDARD |
|
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] |
|
| |
| RFC 2580 | Conformance Statements for SMIv2 |
| |
| Authors: | K. McCloghrie, D. Perkins, J. Schoenwaelder. |
| Date: | April 1999 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1904 |
| Also: | STD 0058 |
| Status: | STANDARD |
|
Collections of related objects are defined in MIB modules. 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 2819 | Remote Network Monitoring Management Information Base |
| |
|
|
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.
This memo obsoletes RFC 1757. This memo extends that specification by documenting the RMON MIB in SMIv2 format while remaining semantically identical to the existing SMIv1-based MIB. |
|
| |
| RFC 2920 | SMTP Service Extension for Command Pipelining |
| |
|
|
This memo defines an extension to the Simple Mail Transfer Protocol(SMTP) service whereby a server can indicate the extent of its ability to accept multiple commands in a single Transmission ControlProtocol (TCP) send operation. Using a single TCP send operation for multiple commands can improve SMTP performance significantly. |
|
| |
| RFC 3411 | An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks |
| |
|
|
This document describes an architecture for describing Simple NetworkManagement Protocol (SNMP) Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are anSNMP engine containing a Message Processing Subsystem, a SecuritySubsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. This document obsoletes RFC 2571. |
|
| |
| RFC 3412 | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) |
| |
| Authors: | J. Case, D. Harrington, R. Presuhn, B. Wijnen. |
| Date: | December 2002 |
| Formats: | txt pdf |
| Obsoletes: | RFC 2572 |
| Also: | STD 0062 |
| Status: | STANDARD |
|
This document describes the Message Processing and Dispatching forSimple Network Management Protocol (SNMP) messages within the SNMP architecture. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP MessageProcessing Models, and for dispatching PDUs to SNMP applications.This document also describes one Message Processing Model - theSNMPv3 Message Processing Model. This document obsoletes RFC 2572. |
|
| |
| RFC 3413 | Simple Network Management Protocol (SNMP) Applications |
| |
| Authors: | D. Levi, P. Meyer, B. Stewart. |
| Date: | December 2002 |
| Formats: | txt pdf |
| Obsoletes: | RFC 2573 |
| Also: | STD 0062 |
| Status: | STANDARD |
|
This document describes five types of Simple Network ManagementProtocol (SNMP) applications which make use of an SNMP engine as described in STD 62, RFC 3411. The types of application described are Command Generators, Command Responders, Notification Originators,Notification Receivers, and Proxy Forwarders.
This document also defines Management Information Base (MIB) modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. This document obsoletes RFC2573. |
|
| |
| RFC 3414 | User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) |
| |
| Authors: | U. Blumenthal, B. Wijnen. |
| Date: | December 2002 |
| Formats: | txt pdf |
| Obsoletes: | RFC 2574 |
| Also: | STD 0062 |
| Status: | STANDARD |
|
This document describes the User-based Security Model (USM) forSimple Network Management Protocol (SNMP) version 3 for use in theSNMP architecture. It defines the Elements of Procedure for providing SNMP message level security. This document also includes aManagement Information Base (MIB) for remotely monitoring/managing the configuration parameters for this Security Model. This document obsoletes RFC 2574. |
|
| |
| RFC 3415 | View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) |
| |
| Authors: | B. Wijnen, R. Presuhn, K. McCloghrie. |
| Date: | December 2002 |
| Formats: | txt pdf |
| Obsoletes: | RFC 2575 |
| Also: | STD 0062 |
| Status: | STANDARD |
|
This document describes the View-based Access Control Model (VACM) for use in the Simple Network Management Protocol (SNMP) architecture. It defines the Elements of Procedure for controlling access to management information. This document also includes aManagement Information Base (MIB) for remotely managing the configuration parameters for the View-based Access Control Model.This document obsoletes RFC 2575. |
|
| |
| RFC 3416 | Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) |
| |
|
|
This document defines version 2 of the protocol operations for theSimple Network Management Protocol (SNMP). It defines the syntax and elements of procedure for sending, receiving, and processing SNMPPDUs. This document obsoletes RFC 1905. |
|
| |
| RFC 3417 | Transport Mappings for the Simple Network Management Protocol (SNMP) |
| |
|
|
This document defines the transport of Simple Network ManagementProtocol (SNMP) messages over various protocols. This document obsoletes RFC 1906. |
|
| |
| RFC 3418 | Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) |
| |
|
|
This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity. This document obsoletes RFC 1907, Management Information Base for Version 2 of theSimple Network Management Protocol (SNMPv2). |
|
| |
| RFC 3550 | RTP: A Transport Protocol for Real-Time Applications |
| |
|
