AppleTalk Management Information Base
RFC 1243

Document Type RFC - Proposed Standard (July 1991; No errata)
Obsoleted by RFC 1742
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 1243 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                             S. Waldbusser, Editor
Request for Comments: 1243                   Carnegie Mellon University
                                                              July 1991

                 AppleTalk Management Information Base

Status of this Memo

   This memo defines objects for managing AppleTalk objects for use with
   the SNMP protocol.  This memo is a product of the AppleTalk-IP
   Working Group of the Internet Engineering Task Force (IETF).  This
   RFC specifies an IAB standards track protocol for the Internet
   community, and requests discussion and suggestions for improvements.
   Please refer to the current edition of the "IAB Official Protocol
   Standards" for the standardization state and status of this protocol.
   Distribution of this memo is unlimited.

Table of Contents

   1. Abstract ..............................................    1
   2. The Network Management Framework.......................    2
   3. Objects ...............................................    2
   3.1 Format of Definitions ................................    3
   4. Overview ..............................................    3
   4.1 Structure of MIB .....................................    3
   4.2 The LocalTalk Link Access Protocol Group .............    3
   4.3 The AppleTalk Address Resolution Protocol Group ......    4
   4.4 The AppleTalk Port Group .............................    4
   4.5 The Datagram Delivery Protocol Group .................    4
   4.6 The Routing Table Maintenance Protocol Group .........    4
   4.7 The Kinetics Internet Protocol Group .................    4
   4.8 The Zone Information Protocol Group ..................    4
   4.9 The Name Binding Protocol Group ......................    4
   4.10 The AppleTalk Echo Protocol Group ...................    5
   4.11 Textual Conventions .................................    5
   5. Definitions ...........................................    5
   6. Acknowledgements ......................................   27
   7. References ............................................   28
   8. Security Considerations................................   29
   9. Author's Address.......................................   29

1.  Abstract

   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 AppleTalk networks.

AppleTalk-IP Working Group                                      [Page 1]
RFC 1243                     AppleTalk MIB                     July 1991

2.  The Network Management Framework

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

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

      RFC 1156 which defines MIB-I, the core set of managed objects for
      the Internet suite of protocols.  RFC 1213, defines MIB-II, an
      evolution of MIB-I based on implementation experience and new
      operational requirements.

      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.

3.  Objects

   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) [7]
   defined in the SMI.  In particular, each object has a name, a syntax,
   and an encoding.  The name is an object identifier, an
   administratively assigned name, which specifies an object type.  The
   object type together with an object instance serves to uniquely
   identify a specific instantiation of the object.  For human
   convenience, we often use a textual string, termed the OBJECT
   DESCRIPTOR, to also refer to the object type.

   The syntax of an object type defines the abstract data structure
   corresponding to that object type.  The ASN.1 language is used for
   this purpose.  However, the SMI [3] purposely restricts the ASN.1
   constructs which may be used.  These restrictions are explicitly made
   for simplicity.

   The encoding of an object type is simply how that object type is
   represented using the object type's syntax.  Implicitly tied to the
   notion of an object type's syntax and encoding is how the object type
   is represented when being transmitted on the network.

   The SMI specifies the use of the basic encoding rules of ASN.1 [8],
   subject to the additional requirements imposed by the SNMP.

AppleTalk-IP Working Group                                      [Page 2]
RFC 1243                     AppleTalk MIB                     July 1991

3.1.  Format of Definitions
Show full document text