Additional Managed Objects for Network Address Translators (NAT)
draft-ietf-behave-nat-mib-01

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-06-19
Replaces draft-perreault-opsawg-natmib-bis
Replaced by draft-perrault-behave-natv2-mib, draft-perrault-behave-deprecate-nat-mib-v1
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       S. Perreault
Internet-Draft                                                  Viagenie
Intended status: Standards Track                                 T. Tsou
Expires: December 20, 2012                     Huawei Technologies (USA)
                                                            S. Sivakumar
                                                           Cisco Systems
                                                           June 18, 2012

    Additional Managed Objects for Network Address Translators (NAT)
                      draft-ietf-behave-nat-mib-01

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.

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 December 20, 2012.

Copyright Notice

   Copyright (c) 2012 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Perreault, et al.       Expires December 20, 2012               [Page 1]
Internet-Draft                 NEW NAT MIB                     June 2012

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 26
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 26
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 27
   Appendix A.  Change Log (to be removed by RFC Editor prior to
                publication)  . . . . . . . . . . . . . . . . . . . . 27
     A.1.  Changed in -01 . . . . . . . . . . . . . . . . . . . . . . 27
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27

Perreault, et al.       Expires December 20, 2012               [Page 2]
Internet-Draft                 NEW NAT MIB                     June 2012

1.  Introduction

   [RFC4008] defines some objects for managing network address
   translators (NATs).  Current operational practice often requires
   additional objects, in particular for enterprise and Internet service
   provider (ISP) deployments.  This document defines those additional
   objects.

   This module is designed to be completely independent from [RFC4008].
   A NAT implementation could be managed using this module, the one from
   [RFC4008], or both.

2.  Overview

   New features in this module are as follows:

   Counters:  Many new counters are introduced.  Most of them are
      available in two variants: global and per-transport protocol.

   Limits:  A few limits on the quantity of state data stored by the NAT
      device.  Some of them can trigger notifications.

   Address+Port Pools:  Pools of external addresses and ports are often
      used in enterprise and ISP settings.  Pools are listed in a table,
      each with its range of addresses and ports.  It is possible to
      inspect each pool's usage, to set limits, and to receive
      notifications when thresholds are crossed.

   Address Mappings:  NATs that have an "IP address pooling" behavior of
      "Paired" [RFC4787] maintain a mapping from internal address to
Show full document text