Browse Prior Art Database

IP Tunnel MIB (RFC2667)

IP.com Disclosure Number: IPCOM000003257D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 16 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Thaler: AUTHOR

Related Documents

10.17487/RFC2667: DOI

Abstract

This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group D. Thaler Request for Comments: 2667 Microsoft Category: Standards Track August 1999

IP Tunnel MIB

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 (1999). All Rights Reserved.

1. Abstract

This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. Extension MIBs may be designed for managing protocol-specific objects. Likewise, extension MIBs may be designed for managing security-specific objects. This MIB does not support tunnels over non-IPv4 networks (including IPv6 networks). Management of such tunnels may be supported by other MIBs.

Table of Contents

1 Abstract ...................................................... 1 2 Introduction .................................................. 2 3 The SNMP Network Management Framework ......................... 2 4 Overview ...................................................... 3 4.1 Relationship to the Interfaces MIB .......................... 3 4.1.1 Layering Model ............................................ 3 4.1.2 ifRcvAddressTable ......................................... 4 4.1.3 ifEntry ................................................... 4 5 Definitions ................................................... 4 6 Security Considerations ...................................... 12 7 Acknowledgements ............................................. 12 8 Author’s Address ............................................. 12 9 References ................................................... 13 10 Intellectual Property Notice ................................. 15 11 Full Copyright Statement ..................................... 16

Thaler Standards Track [Page 1]

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 support...

Processing...
Loading...