Layer Two Tunneling Protocol "L2TP" Management Information Base
RFC 3371
|
| Document |
Type |
|
RFC - Proposed Standard
(September 2002; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 3371 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Thomas Narten
|
|
IESG note |
|
published as RFC 3371
|
|
Send notices to |
|
<mark@townsley.net>
|
Network Working Group E. Caves
Request for Comments: 3371 Occam Networks
Category: Standards Track P. Calhoun
Black Storm Networks
R. Wheeler
DoubleWide Software
August 2002
Layer Two Tunneling Protocol "L2TP"
Management Information Base
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.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
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 networks using Layer 2
Tunneling Protocol (L2TP).
Caves, et. al. Standards Track [Page 1]
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 [RFC2119].
2.0 The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
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 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
[RFC1215]. The second version, called SMIv2, is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580].
Caves, et. al. Standards Track [Page 2]
RFC 3371 L2TP Management Information Base August 2002
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 [RFC1157]. A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and
RFC 1906 [RFC1906]. The third version of the message protocol is
called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572
[RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[RFC1905].
o A set of fundamental applications described in RFC 2573 [RFC2573]
and the view-based access control mechanism described in RFC 2575
[RFC2575].
A more detailed introduction to the current SNMP Management Framework
Show full document text