rfc1742.txt

来自「<VC++网络游戏建摸与实现>源代码」· 文本 代码 · 共 1,754 行 · 第 1/5 页

Network Working Group                                      S. Waldbusser
Request for Comments: 1742                    Carnegie Mellon University
Obsoletes: 1243                                                 K. Frisa
Category: Standards Track                             FORE Systems, Inc.
                                                            January 1995


                AppleTalk Management Information Base II

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.

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.

   RFC 1243 defines a set of MIB objects for managing the lower layers
   of the AppleTalk protocol stack, up to the Network layer.  This memo
   defines additional objects that exist in the AppleTalk portion of the
   MIB.  These objects provide for the management of the transport and
   session layers of the AppleTalk protocol stack, as well as extensions
   to the lower layers.  This is achieved in an upwardly-compatable
   fashion.

Table of Contents

   1. The Network Management Framework ......................    2
   2. Additions and Changes .................................    3
   2.1 New Groups ...........................................    3
   2.2 Additional Variables .................................    3
   2.2.1 AARP Additions .....................................    3
   2.2.2 ATPort Additions ...................................    3
   2.2.3 DDP Addition .......................................    3
   2.2.4 RTMP Additions .....................................    4
   2.2.5 KIP Addition .......................................    4
   2.2.6 ZIP Additions ......................................    4
   2.2.7 NBP Additions ......................................    4
   2.2.8 ATEcho Additions ...................................    4
   2.3 Deprecations .........................................    4
   2.4 Changes ..............................................    5
   3. Objects ...............................................    6



Waldbusser & Frisa                                              [Page 1]

RFC 1742                    AppleTalk MIB II                January 1995


   3.1 Format of Definitions ................................    6
   4. Overview ..............................................    6
   4.1 Structure of MIB .....................................    7
   4.2 The LocalTalk Link Access Protocol Group .............    7
   4.3 The AppleTalk Address Resolution Protocol Group ......    7
   4.4 The AppleTalk Port Group .............................    8
   4.5 The Datagram Delivery Protocol Group .................    8
   4.6 The Datagram Delivery Protocol Router Group ..........    8
   4.7 The Routing Table Maintenance Protocol Group .........    8
   4.8 The Routing Table Maintenance Protocol Stub Group ....    8
   4.9 The Kinetics Internet Protocol Group .................    8
   4.10 The Zone Information Protocol Router Group ..........    9
   4.11 The Zone Information Protocol End Node Group ........    9
   4.12 The Name Binding Protocol Group .....................    9
   4.13 The AppleTalk Echo Protocol Group ...................    9
   4.14 The AppleTalk Transaction Protocol Group ............    9
   4.15 The Printer Access Protocol Group ...................    9
   4.16 The AppleTalk Session Protocol Group ................    9
   4.17 The AppleTalk Data Stream Protocol Group ............   10
   4.18 The AppleTalk Port Point to Point Group .............   10
   4.19 The Per Port Counters Group .........................   10
   4.20 Textual Conventions .................................   10
   5. Definitions ...........................................   11
   6. Acknowledgmnts ........................................   82
   7. References ............................................   83
   8. Security Considerations ...............................   84
   9. Authors' Addresses ....................................   84

1. The Network Management Framework

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

      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.

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

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





Waldbusser & Frisa                                              [Page 2]

RFC 1742                    AppleTalk MIB II                January 1995


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

2.  Additions and Changes

   This MIB includes additions and changes to RFC 1243.  These changes
   are outlined in the following sections.

2.1.  New Groups

   The following groups are introduced in this MIB:

                  - DDP Router
                  - RTMP Stub
                  - ZIP Router
                  - ATP
                  - PAP
                  - ASP
                  - ADSP
                  - ATPortPtoP
                  - Per Port Counters

2.2.  Additional Variables

   Many variables, mostly counters, were added to groups that existed in
   RFC 1243.  These variables are listed in the following sections.

2.2.1.  AARP Additions

                     aarpStatus
                     aarpLookups
                     aarpHits

2.2.2.  ATPort Additions

                     atportNetFrom
                     atportZoneFrom
                     atportInPkts
                     atportOutPkts
                     atportHome
                     atportCurrentZone
                     atportConflictPhysAddr
                     atportZoneTable

2.2.3.  DDP Addition

                     ddpListenerTable




Waldbusser & Frisa                                              [Page 3]

RFC 1742                    AppleTalk MIB II                January 1995


2.2.4.  RTMP Additions

                     rtmpInDataPkts
                     rtmpOutDataPkts
                     rtmpInRequestPkts
                     rtmpNextIREqualChanges
                     rtmpNextIRLessChanges
                     rtmpRouteDeletes
                     rtmpRoutingTableOverflows

2.2.5.  KIP Addition

                     kipFrom

2.2.6.  ZIP Additions

                     zipNetInfoTable
                     zipInErrors

2.2.7.  NBP Additions

                     nbpAddress
                     nbpSocket
                     nbpEnumerator
                     nbpInLookUpRequests
                     nbpInLookUpReplies
                     nbpInBroadcastRequests
                     nbpInForwardRequests
                     nbpOutLookUpReplies
                     nbpRegistrationFailures
                     nbpInErrors

2.2.8.  ATEcho Additions

                     atechoOutRequests
                     atechoInReplies

2.3.  Deprecations

   The following variables have been deprecated in this version of the
   MIB:

                  llapInPkts
                  llapOutPkts
                  llapInNoHandlers
                  llapInErrors





Waldbusser & Frisa                                              [Page 4]

RFC 1742                    AppleTalk MIB II                January 1995


   These llap variables were duplicated in the interfaces table of MIB-
   II.

2.4.  Changes

   The IMPORTS list has been updated to reflect the current SNMP
   documents.

   New textual conventions have been defined.

   Hyphens have been removed from enumeration strings.

   Variables used as INDEXes to new tables have ACCESS not-accessible.
   This is because the values of the INDEX variables are contained in
   the object identifier for any of the other variables in the table;
   therefore, it does not need to be explicitly available as data.

   The atportNetConfig and atportZoneConfig variables have been changed
   from read-only to read-write.

   The atportZone variable has be renamed to atportZoneDefault, and its
   DESCRIPTION clause has been clarified.

   The atportType, atportStatus, and kipType variables have had more
   values added to their enumeration lists.

   The DDP group has been split into two groups; one includes variables
   that any AppleTalk node would implement and the other includes
   variables only a router would implement.

   The rtmpState variable now includes another enumeration, invalid(5),
   which is used when deleting rows.

   The variables rtmpRangeStart, rtmpRangeEnd, rtmpNextHop, rtmpType,
   rtmpPort, and rtmpHops have been changed from read-write to read-
   only.

   The ZIP Group has been renamed the ZIP End Node Group.

   The DESCRIPTION clause for zipZoneIndex has been clarified.

   The variables zipZoneName, zipZoneNetStart, and zipZoneNetEnd have
   been changed from read-write to read-only.

   The nbpIndex variable has been changed from read-only to read-write.

   The nbpObject, nbpType, and nbpZone variables now suggest that the
   agent reregister its service when any of these variables is changed.



Waldbusser & Frisa                                              [Page 5]

RFC 1742                    AppleTalk MIB II                January 1995


   The nbpState variable includes new enumerations.

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.

3.1.  Format of Definitions

   Section 5 contains the specification of all object types contained in
   this MIB module.  The object types are defined using the conventions
   defined in the SMI, as amended by the extensions specified in [9].

4.  Overview

   AppleTalk is a protocol suite which features an open peer-to-peer
   architecture that runs over a variety of transmission media.
   AppleTalk is defined in [10].  This protocol suite interoperates with
   the IP protocol suite through various encapsulation methods.  As
   large AppleTalk networks are built that coexist with large IP
   networks, a method to manage the AppleTalk networks with SNMP becomes
   necessary.  This MIB defines managed objects to be used for managing
   AppleTalk networks.






Waldbusser & Frisa                                              [Page 6]

RFC 1742                    AppleTalk MIB II                January 1995


4.1.  Structure of MIB

   The objects are arranged into the following groups:

                  - LLAP
                  - AARP
                  - ATPort
                  - DDP
                  - DDP Router