Deprecation of MIB Module NAT-MIB (Managed Objects for Network Address Translators (NAT))
draft-perrault-behave-deprecate-nat-mib-v1-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-01-16 (latest revision 2014-10-19)
Replaced by draft-perrault-behave-natv2-mib
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to draft-perrault-behave-deprecate-nat-mib-v1.all@tools.ietf.org, simon.perreault@viagenie.ca, ssenthil@cisco.com, tom.taylor.stds@gmail.com, tina.tsou.zouting@huawei.com, behave@ietf.org
Network Working Group                                       S. Perreault
Internet-Draft                                                  Viagenie
Obsoletes: 4008 (if approved)                                    T. Tsou
Intended status: Standards Track               Huawei Technologies (USA)
Expires: April 22, 2015                                     S. Sivakumar
                                                           Cisco Systems
                                                               T. Taylor
                                                    PT Taylor Consulting
                                                        October 19, 2014

 Deprecation of MIB Module NAT-MIB (Managed Objects for Network Address
                           Translators (NAT))
             draft-perrault-behave-deprecate-nat-mib-v1-00

Abstract

   This memo deprecates MIB module NAT-MIB, a portion of the Management
   Information Base (MIB) previously defined in RFC 4008 for devices
   implementing Network Address Translator (NAT) function.  A companion
   document defines a new version, NAT-MIB-V2, which responds to
   deficiencies found in module NAT-MIB and adds new capabilities.

   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 22, 2015.

Copyright Notice

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

Perreault, et al.        Expires April 22, 2015                 [Page 1]
Internet-Draft          Deprecation of NAT MIB v1           October 2014

   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
   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  . . . . . . . . .   3
   3.  Motivation For Deprecating NAT-MIB  . . . . . . . . . . . . .   3
     3.1.  Deprecated Features . . . . . . . . . . . . . . . . . . .   3
     3.2.  Desirable New Features  . . . . . . . . . . . . . . . . .   4
   4.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  55
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  57
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  58
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  58
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  59
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  59

1.  Introduction

   This memo deprecates a portion of the Management Information Base
   (MIB), MIB module NAT-MIB, for devices implementing the Network
   Address Translator (NAT) function.  New implementations are
   encouraged to base themselves upon the second version of this MIB
   module, NAT-MIB-V2, defined in [I-D.ietf-behave-nat-mib-v2].  NAT
   types and their characteristics are defined in [RFC2663].
   Traditional NAT function, in particular is defined in [RFC3022].
   Neither NAT-MIB nor NAT-MIB-V2 addresses the firewall functions and
   neither can be used for configuring or monitoring them.

   Section 2 provides references to the SNMP management framework, which
   was used as the basis for the original MIB module definition and its
   deprecation.  Section 3 provides motivation for the deprecation of
   module NAT-MIB and its replacement by module NAT-MIB-V2.  Section 4
   has the complete NAT-MIB module definition, with the STATUS of all
   objects changed to deprecated.  Section 5 describes security
   considerations relating to NAT-MIB, basically elaborating on the
   security considerations in [RFC4008].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text