rfc1742.txt

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

                  - RTMP
                  - RTMP Stub
                  - KIP
                  - ZIP Router
                  - ZIP End Node
                  - NBP
                  - ATEcho
                  - ATP
                  - PAP
                  - ASP
                  - ADSP
                  - ATPortPtoP
                  - Per Port Counters

   These groups are the basic unit of conformance. If the semantics of a
   group is applicable to an implementation, then it must implement all
   objects in that group.  For example, a managed agent must implement
   the KIP group if and only if it implements the KIP protocol.

   These groups are defined to provide a method for managed agents to
   know which objects they must implement.

4.2.  The LocalTalk Link Access Protocol Group

   The LocalTalk Link Access Protocol (LLAP) is a medium-speed data-link
   protocol designed for low cost and plug-and-play operation.  The LLAP
   group is designed to manage all interfaces on a managed device that
   use this protocol.

4.3.  The AppleTalk Address Resolution Protocol Group

   The AppleTalk Address Resolution Protocol (AARP) is used to map
   between AppleTalk node addresses, used by the Datagram Delivery
   Protocol, and the addresses of the underlying data link layer.  The
   AARP table allows for management of the Address Mapping Table on the
   managed device.






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


4.4.  The AppleTalk Port Group

   An AppleTalk Port is a logical connection to a network over which
   AppleTalk packets can be transmitted.  The "network" could be a
   tunnel, backbone network, point-to-point link, etc, as well as a
   native AppleTalk network.  This group allows the management of the
   configuration of these AppleTalk ports.

4.5.  The Datagram Delivery Protocol Group

   The Datagram Delivery Protocol (DDP) is the network-layer protocol
   that is responsible for the socket-to-socket delivery of datagrams
   over the AppleTalk Internet.  This group manages the DDP layer on the
   managed device.

   The DDP group contains statistical counters for the DDP protocol, and
   a table describing the DDP sockets that have protocol handlers
   registered.

4.6.  The Datagram Delivery Protocol Router Group

   Some variables relevant to the Datagram Delivery Protocol (DDP) are
   only applicable to AppleTalk routers.  These variables are included
   in this group.

4.7.  The Routing Table Maintenance Protocol Group

   The Routing Table Maintenance Protocol (RTMP) is used by AppleTalk
   routers to create and maintain the routing tables that dictate the
   process of forwarding datagrams on the AppleTalk internet.  The RTMP
   group manages the RTMP protocol as well as the routing tables
   generated by this protocol.

4.8.  The Routing Table Maintenance Protocol Stub Group

   The RTMP Stub process is implemented by end nodes in order to
   maintain information about the routers on their networks.  The
   variables in this group apply to both routers and end nodes.  This
   group manages the RTMP stub process.

4.9.  The Kinetics Internet Protocol Group

   The Kinetics Internet Protocol (KIP) is a protocol for encapsulating
   and routing AppleTalk datagrams over an IP internet.  This name is
   historical.  The KIP group manages the KIP routing protocol as well
   as the routing tables generated by this protocol.





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


4.10.  The Zone Information Protocol Router Group

   The Zone Information Protocol (ZIP) is used to maintain a mapping
   between networks and zone names to facilitate the name lookup process
   performed by the Name Binding Protocol.  Some variables relevant to
   the Zone Information Protocol (ZIP) are only applicable to AppleTalk
   routers.  These variables are included in this group.

4.11.  The Zone Information Protocol End Node Group

   The ZIP End Node group manages the variables relevant to the Zone
   Information Protocol (ZIP) that are applicable to both routers and
   end nodes.

4.12.  The Name Binding Protocol Group

   The Name Binding Protocol (NBP) is a transport-level protocol that is
   used to convert human readable service names into the numeric
   AppleTalk network addresses needed for communicating across the
   AppleTalk network.  The NBP group manages this protocol and the NBP
   services that exist on the managed device.

4.13.  The AppleTalk Echo Protocol Group

   The AppleTalk Echo Protocol is a transport-level protocol used to
   test and verify the status of the AppleTalk internet.  The AtEcho
   group manages this protocol.

4.14.  The AppleTalk Transaction Protocol Group

   The AppleTalk Transaction Protocol (ATP) is a transport-level
   protocol that is defined to support transaction based communications.
   The ATP group manages this protocol.

4.15.  The Printer Access Protocol Group

   The Printer Access Protocol (PAP) is a session-level protocol that
   enables communications between workstations and print servers.  The
   PAP group manages this protocol.

4.16.  The AppleTalk Session Protocol Group

   The AppleTalk Session Protocol (ASP) is a session-level protocol that
   enables sequences of communications to occur.  ASP uses the services
   of the AppleTalk Transaction Protocol (ATP), but extends these
   services into the session layer.  The ASP group manages this
   protocol.




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


4.17.  The AppleTalk Data Stream Protocol Group

   The AppleTalk Data Stream Protocol (ADSP) is a session-level protocol
   that provides symmetric, connection-oriented, full-duplex
   communication between two sockets on the AppleTalk internet.  In
   addition, ADSP handles flow-control and reliability.  The ADSP group
   manages this protocol.

4.18.  The AppleTalk Port Point to Point Group

   The AppleTalk Port Point to Point Group manages ports that have one
   or more associated point-to-point connections.

4.19.  The Per Port Counters Group

   The Per Port Counters Group contains a set of counters which are
   deemed useful on a per port basis.

4.20.  Textual Conventions

   New data types are introduced as textual conventions in this MIB
   document.  These textual conventions enhance the readability of the
   specification and can ease comparison with other specifications if
   appropriate.  It should be noted that the introduction of these
   textual conventions has no effect on either the syntax or the
   semantics of any managed objects.  The use of this is merely an
   artifact of the explanatory method used.  Objects defined in terms of
   this method are always encoded by means of the rules that define the
   primitive type.  Hence, no changes to the SMI or the SNMP are
   necessary to accommodate these textual conventions which are adopted
   merely for the convenience of readers and writers in pursuit of the
   elusive goal of clear, concise, and unambiguous MIB documents.

   The new data types are:

                  ATNetworkNumber ::=         -- 2 octets of network
                                              -- number in network
                                              -- byte order
                          OCTET STRING (SIZE (2))

                  DdpNodeAddress ::=          -- 2 octets of net number
                                              -- in network byte order,
                                              -- 1 octet of node number
                          OCTET STRING (SIZE (3))

                  DdpSocketAddress ::=        -- 2 octets of net number
                                              -- in network byte order,
                                              -- 1 octet of node number,



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


                                              -- 1 octet of socket
                                              -- number (0..255)
                          OCTET STRING (SIZE (4))

                  ATName ::=              -- 0 to 32 octets of
                                              -- AppleTalk ASCII [10]
                          OCTET STRING (SIZE (0..32))

5.  Definitions

          APPLETALK-MIB DEFINITIONS ::= BEGIN

          IMPORTS
              Counter, IpAddress, TimeTicks
                  FROM RFC1155-SMI
              DisplayString, mib-2
                  FROM RFC1213-MIB
              OBJECT-TYPE
                  FROM RFC-1212;

          --  This MIB module uses the extended OBJECT-TYPE macro as
          --  defined in RFC-1212.

          --  The following reference is used in this MIB:
          --  [Inside AppleTalk]
          --  This refers to Gursharan S. Sidhu, Richard F. Andrews, and
          --  Alan B. Oppenheimer, Inside AppleTalk, Second Edition,
          --  Addison Wesley, (1990).



          --  AppleTalk MIB

              appletalk    OBJECT IDENTIFIER ::= { mib-2 13 }


                  ATNetworkNumber ::=         -- 2 octets of net number
                                              -- in network byte order
                          OCTET STRING (SIZE (2))

                  DdpNodeAddress ::=          -- 2 octets of net number
                                              -- in network byte order,
                                              -- 1 octet of node number
                          OCTET STRING (SIZE (3))

                  DdpSocketAddress ::=        -- 2 octets of net number
                                              -- in network byte order,
                                              -- 1 octet of node number,



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


                                              -- 1 octet of socket number
                                              -- (0..255)
                          OCTET STRING (SIZE (4))

                  ATName ::=              -- 0 to 32 octets of AppleTalk
                                              -- ASCII [Inside AppleTalk]
                          OCTET STRING (SIZE (0..32))


              llap         OBJECT IDENTIFIER ::= { appletalk 1 }
              aarp         OBJECT IDENTIFIER ::= { appletalk 2 }
              atport       OBJECT IDENTIFIER ::= { appletalk 3 }
              ddp          OBJECT IDENTIFIER ::= { appletalk 4 }
              rtmp         OBJECT IDENTIFIER ::= { appletalk 5 }
              kip          OBJECT IDENTIFIER ::= { appletalk 6 }
              zipRouter    OBJECT IDENTIFIER ::= { appletalk 7 }
              nbp          OBJECT IDENTIFIER ::= { appletalk 8 }
              atecho       OBJECT IDENTIFIER ::= { appletalk 9 }
              atp          OBJECT IDENTIFIER ::= { appletalk 10 }
              pap          OBJECT IDENTIFIER ::= { appletalk 11 }
              asp          OBJECT IDENTIFIER ::= { appletalk 12 }
              adsp         OBJECT IDENTIFIER ::= { appletalk 13 }
              atportptop   OBJECT IDENTIFIER ::= { appletalk 14 }
              rtmpStub     OBJECT IDENTIFIER ::= { appletalk 16 }
              zipEndNode   OBJECT IDENTIFIER ::= { appletalk 17 }
              perPort  OBJECT IDENTIFIER ::= { appletalk 18 }


          -- The LLAP Group
          --
          -- Implementation of this group is mandatory for all
          -- entities that implement LLAP
          --
          -- Notes for the interfaces group
          --
          -- When implementing the Interfaces Group of MIB-II, it is
          -- suggested that the following values be used for any
          -- LocalTalk interfaces:
          --  ifMtu: 600
          --  ifSpeed: 230000
          --  ifPhysAddress: the one octet node number for the
          --      particular interface
          --
          -- Note also that LLAP control packets should not be
          -- included in the Interfaces Group packet or octet
          -- counters.





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


          llapTable OBJECT-TYPE
              SYNTAX SEQUENCE OF LlapEntry
              ACCESS not-accessible
              STATUS mandatory
              DESCRIPTION
                  "The list of LLAP entries."
              ::= { llap 1 }

          llapEntry OBJECT-TYPE
              SYNTAX LlapEntry
              ACCESS not-accessible
              STATUS mandatory
              DESCRIPTION
                  "An LLAP entry containing objects for the LocalTalk
                  Link Access Protocol for a particular LocalTalk
                  interface.

                  As an example, an instance of the llapOutPkts object
                  might be named llapOutPks.1"
              INDEX { llapIfIndex }
              ::= { llapTable 1 }

          LlapEntry ::= SEQUENCE {
              llapIfIndex             INTEGER,