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

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-07-16
Replaces draft-perreault-opsawg-natmib-bis
Replaced by RFC 7658, RFC 7659, RFC 7659, RFC 7658
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
Intended status: Standards Track                                 T. Tsou
Expires: January 17, 2013                      Huawei Technologies (USA)
                                                            S. Sivakumar
                                                           Cisco Systems
                                                           July 16, 2012

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

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 January 17, 2013.

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 January 17, 2013                [Page 1]
Internet-Draft                 NEW NAT MIB                     July 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
     2.1.  Deprecated Features  . . . . . . . . . . . . . . . . . . .  3
     2.2.  New Features . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 69
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 69
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 69
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 70
   Appendix A.  Change Log (to be removed by RFC Editor prior to
                publication)  . . . . . . . . . . . . . . . . . . . . 70
     A.1.  Changed in -01 . . . . . . . . . . . . . . . . . . . . . . 70
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 70

Perreault, et al.       Expires January 17, 2013                [Page 2]
Internet-Draft                 NEW NAT MIB                     July 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

2.1.  Deprecated Features

   All objects defined in [RFC4008] have been marked with "STATUS
   deprecated" for the following reasons:

   Writability:  Experience with NAT has shown that implementations vary
      tremendously.  The NAT algorithms and data structures have little
      in common across devices, and this results in wildly incompatible
      configuration parameters.  Therefore, few implementations were
      ever able to claim full compliance.

      Lesson learned: the MIB should be read-only as much as possible.

   Exposing configuration parameters:  Even in read-only mode, many
      configuration parameters were exposed by [RFC4008] (e.g.
      timeouts).  Since implementations vary wildly in their sets of
      configuration parameters, few implementations could claim even
      basic compliance.

      Lesson learned: the NAT MIB's purpose is not to expose
Show full document text