RFC 3371 (rfc3371) - Page 2 of 70


Layer Two Tunneling Protocol "L2TP" Management Information Base



Alternative Format: Original Text Document



RFC 3371            L2TP Management Information Base         August 2002


Table of Contents

   1.0      Introduction   ..........................................  2
   2.0      The SNMP Management Framework ...........................  2
   3.0      Overview ................................................  4
   3.1      Relationship to the Interface MIB........................  5
   3.1.1    Layering Model ..........................................  5
   3.1.2    Interface MIB Object.....................................  7
   3.1.2.1  L2TP Tunnel Interfaces ..................................  7
   3.2      Relationship to other MIBs .............................. 10
   3.2.1    Relationship to the IP Tunnel MIB ....................... 10
   3.3      L2TP Tunnel Creation .................................... 10
   3.4      L2TP Session Mapping .................................... 10
   4.0      L2TP Object Definitions ................................. 11
   5.0      Security Considerations ................................. 66
   6.0      Acknowledgements ........................................ 67
   7.0      References .............................................. 67
   8.0      Authors' Addresses ...................................... 69
   9.0      Full Copyright Statement ................................ 70

1.0 Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet Community.
   In particular, it describes managed objects used for managing L2TP
   devices.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

2.0 The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o An overall architecture, described in RFC 2571 [RFC 2571].

   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 [RFC 1155], STD 16, RFC 1212 [RFC 1212] and RFC 1215
     [RFC 1215].  The second version, called SMIv2, is described in STD
     58, RFC 2578 [RFC 2578], STD 58, RFC 2579 [RFC 2579] and STD 58, RFC
     2580 [RFC 2580].






Caves, et. al.              Standards Track