[BEHAVE] new nat mib question

[Juergen Schoenwaelder <[e-mail]>]

Hi,

I have come across the new NAT MIB <draft-ietf-behave-nat-mib-01> and
I am not sure I understand the scope of this effort and how the result
will relate to the existing NAT-MIB in RFC 4008. The behave I-D says:

   [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

The first paragraph sounds like the goal is to define additional
objects relative to the RFC 4008 NAT-MIB while the second paragraph
says quite clearly that this is going to a competing MIB module. If
so, this is, as far as I know, the first time we have two
standards-track MIB modules for managing a single technology. Can
someone explain what the goal of this effort is or point me somewhere
into the archives so I can inform myself? Note, it might very well be
that the RFC 4008 NAT-MIB is seriously broken but then the proper
approach would be to write a new MIB replacing the old MIB, sending
RFC 4008 to historic.  Otherwise, it should be explained somewhere how
the new MIB plays together with the NAT-MIB. (My background on this is
essentially written down in draft-schoenw-behave-nat-mib-bis-00.)

I also think NEW-NAT-MIB is not a good name. What is new today is
going to be old tomorrow.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>