Definitions of Managed Objects for Network Address Translators (NAT)
draft-ietf-behave-nat-mib-09

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-10-17
Replaces draft-perreault-opsawg-natmib-bis
Replaced by rfc7658, rfc7659, draft-perrault-behave-natv2-mib, draft-perrault-behave-deprecate-nat-mib-v1
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       S. Perreault
Internet-Draft                                                  Viagenie
Obsoletes: 4008 (if approved)                                    T. Tsou
Intended status: Standards Track               Huawei Technologies (USA)
Expires: April 20, 2014                                     S. Sivakumar
                                                           Cisco Systems
                                                        October 17, 2013

  Definitions of Managed Objects for Network Address Translators (NAT)
                      draft-ietf-behave-nat-mib-09

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for devices implementing Network Address Translator (NAT) function.
   This MIB module may be used for monitoring of a device capable of NAT
   function.

   This document obsoletes RFC 4008.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 20, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Perreault, et al.        Expires April 20, 2014                 [Page 1]
Internet-Draft                   NAT MIB                    October 2013

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Internet-Standard Management Framework  . . . . . . . . .   2
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Deprecated Features . . . . . . . . . . . . . . . . . . .   3
     3.2.  New Features  . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Realms  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  82
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  84
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  84
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  84
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  86
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  86

1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for devices implementing NAT function.  This MIB module may be used
   for monitoring of a device capable of NAT function.  Using it for
   configuration is deprecated.  NAT types and their characteristics are
   defined in [RFC2663].  Traditional NAT function, in particular is
   defined in [RFC3022].  This MIB does not address the firewall
   functions and must not be used for configuring or monitoring these.
   Section 2 provides references to the SNMP management framework, which
   was used as the basis for the MIB module definition.  Section 3
   provides an overview of the MIB features.  Lastly, Section 4 has the
   complete NAT MIB definition.

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

2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally

Perreault, et al.        Expires April 20, 2014                 [Page 2]
Internet-Draft                   NAT MIB                    October 2013

   accessed through the Simple Network Management Protocol (SNMP).
Show full document text