DECnet Phase IV MIB Extensions
RFC 1559

Document Type RFC - Draft Standard (December 1993; No errata)
Obsoletes RFC 1289
Last updated 2013-03-02
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1559 (Draft Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Saperia
Request for Comments: 1559                 Digital Equipment Corporation
Obsoletes: 1289                                            December 1993
Category: Standards Track

                     DECnet Phase IV MIB Extensions

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Table of Contents

   1. Introduction ................................................  1
   2. The Network Management Framework ............................  2
   2.1 Object Definitions .........................................  2
   3. Selected Objects ............................................  3
   4. Textual Conventions .........................................  4
   5. Definitions .................................................  4
   6. Changes from RFC 1289 ....................................... 67
   7. Acknowledgements ...........................................  68
   8. References .................................................  68
   9. Security Considerations ....................................  69
   10. Author's Address ..........................................  69

1.  Introduction

   This memo defines a set of DECnet Phase IV extensions that have been
   created for the Internet MIB.  It reflects changes which are the
   result of operational experience based on RFC 1289.

   When used in conjunction with the structure of management information
   (STD 16, RFC 1155), the management information base for network
   management of TCP/IP-based internets (STD 17, RFC 1213) and the
   Simple Network Management Protocol (STD 15, RFC 1157), it will be
   possible to provide integrated network management of combined TCP/IP
   and DECnet Phase IV based internets.  This document was produced by
   the DECnet Phase IV MIB working group of the Internet Engineering
   Task Force (IETF).

   With the adoption of The Simple Network Management Protocol (STD 15,
   RFC 1157), the management information base for network management of
   TCP/IP-based internets (STD 17, RFC 1213), and the structure of

DECnet Phase IV MIB Working Group                               [Page 1]
RFC 1559                  DECnet Phase IV MIB              December 1993

   management information (STD 16, RFC 1155), by the Internet, and a
   large number of vendor implementations of these standards in
   commercially available products, it became possible to provide a
   higher level of effective network management in TCP/IP-based
   internets than previously available. With the growth in the use of
   these standards, network managers desired to use this environment as
   a base for providing integrated network management of multi-protocol
   networks.

   DECnet Phase IV is one widely used protocol which often coexists in
   IP-based internets. This memo provides the mechanisms by which IP-
   based management stations can effectively manage DECnet Phase IV
   based systems (especially router products) in an integrated fashion
   through the use of the standard Internet SMI, MIB and Simple Network
   Management Protocol.

   DECnet Phase IV objects have been defined to be used in conjunction
   with the Internet MIB to allow access and control of these new
   objects by the Internet community. Additional support for other
   DECnet-based protocols such as RBMS (Remote Bridge Management
   Software) or other Digital Equipment Corporation specific hardware
   platforms is not included in this document.

2.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

   o STD 16, RFC 1155 which defines the SMI, the mechanisms used for
     describing and naming objects for the purpose of management.
     STD 16, RFC 1212 defines a more concise description mechanism,
     which is wholly consistent with the SMI.

   o STD 17, RFC 1213 defines MIB-II, the core set of managed objects
     for the Internet suite of protocols.

   o STD 15, RFC 1157 which defines the SNMP, the protocol used for
     network access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.1  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an

DECnet Phase IV MIB Working Group                               [Page 2]
RFC 1559                  DECnet Phase IV MIB              December 1993

   OBJECT IDENTIFIER, an administratively assigned name.  The object
Show full document text