RFC 2667 (rfc2667) - Page 2 of 16
IP Tunnel MIB
Alternative Format: Original Text Document
RFC 2667 IP Tunnel MIB August 1999
2. Introduction
Over the past several years, there have been a number of "tunneling"
protocols specified by the IETF (see [28] for an early discussion of
the model and examples). This document describes a Management
Information Base (MIB) used for managing tunnels of any type over
IPv4 networks, including GRE [16,17], IP-in-IP [18], Minimal
Encapsulation [19], L2TP [20], PPTP [21], L2F [25], UDP (e.g., [26]),
ATMP [22], and IPv6-in-IPv4 [27] tunnels.
Extension MIBs may be designed for managing protocol-specific
objects. Likewise, extension MIBs may be designed for managing
security-specific objects (e.g., IPSEC [24]), and traffic conditioner
[29] objects. Finally, this MIB does not support tunnels over non-
IPv4 networks (including IPv6 networks). Management of such tunnels
may be supported by other MIBs.
3. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [8]. A second version of the SNMP
message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [9] and
RFC 1906 [10]. The third version of the message protocol is
called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and
RFC 2574 [12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[13].
Thaler Standards Track