RFC 1665: Definitions of Managed Objects for SNA NAUs using SMIv2
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1666.
Current version: RFC 1666 — Definitions of Managed Objects for SNA NAUs using SMIv2
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1665
- Published
- July 1994
- Authors
- Z. Kielczewski; D. Kostick; K. Shih
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 67
- Also known as
- —
- Obsoleted by:
- RFC 1666
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 1657Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2Obsoleted
July 1994
- RFC 2024Definitions of Managed Objects for Data Link Switching using SMIv2Current
October 1996
- RFC 1660Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2Current
July 1994
- RFC 1659Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2Current
July 1994
- RFC 1658Definitions of Managed Objects for Character Stream Devices using SMIv2Current
July 1994
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?