Hi,
As a MIB Doctor, and one who just worked with the Behave WG’s document to deprecate/obsolete the old NAT-MIB, I think it would be fairly simple to get Bill’s proposed changes through the process. As long as the only thing changing in the MIB is the status of the objects, that should be a slam dunk. Publishing a new RFC has a few new wrinkles, mostly the legal stuff like copyright and permission from the original authors. But that should be fairly simple. Just changing the status of the RFC really is not the right way to obsolete a MIB module, because MIB modules often are published separate from the RFC, and when a MIB module is imported into an NMS, the whole RFC is not imported, just the MIB module. It could be helpful to operators to see the current status of the relevant objects, which doesn’t happen in an NMS by re-categorizing the status of the RFC. David Harrington <mailto:[email protected]> [email protected] +1-603-828-1401 From: OPSAWG [mailto:[email protected]] On Behalf Of Bill Fenner Sent: Thursday, June 04, 2015 5:58 PM To: t.petch Cc: C. M. Heard; OPSAWG Subject: Re: [OPSAWG] Cleaning up the state of IPv6 MIBs On Thu, Jun 4, 2015 at 7:14 AM, t.petch <[email protected]> wrote: Far simpler just to declare a status change of the RFC; no RFC needed. But it doesn't address my primary problem: if you look at a MIB repository, you see a nice IPV6-MIB with lots of "STATUS current" objects, and you say "Ah, cool, here are all the objects I need to implement for IPv6!". I knew going into this effort that "just reclassify things as historic" would be one possible outcome, but I want to aim higher than that. Despite outward appearances, the IESG is not an inflexible automaton; I hope to be able to work with them to be able to come to agreement that this is a worthwhile endeavor and need not be subject to the significant scrutiny that a MIB module with implementable objects should be. The first step down that path is to publish my draft and say "this is what I'm thinking it'll look like". Bill
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
