RFC 1291: Mid-Level Networks Potential Technical Services
In plain English — editorial summary, not part of the RFC
This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. This RFC provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1291
- Published
- December 1991
- Authors
- V. Aggarwal
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1296Internet Growth (1981-1991)Current
January 1992
- RFC 1503Algorithms for Automating Administration in SNMPv2 ManagersCurrent
August 1993
- RFC 1593SNA APPN Node MIBCurrent
March 1994
- RFC 1604Definitions of Managed Objects for Frame Relay ServiceObsoleted
March 1994
- RFC 1643Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
July 1994
- RFC 1666Definitions of Managed Objects for SNA NAUs using SMIv2Current
August 1994
- RFC 1748IEEE 802.5 MIB using SMIv2Updated
December 1994
- RFC 1792TCP/IPX Connection Mib SpecificationCurrent
April 1995
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?