Hello Bill, My guess would be that the only reason for not republishing these MIB modules as obsolete was the work involved, but since you have shouldered the burden, it seems to me like a good thing. That said, I am by no means sure that everyone would agree :-)
As for venue, it seems to me that opsawg is arguably more appriate than 6man, so I have cc:'d that WG. I would like to make two small suggestions on the document itself: - please change the occurrences of "Deprecating this MIB" to "Obsoleting this MIB module" in the REVISION clauses (and if it's not too much trouble, try to hunt down any other occurrences of "this MIB", "these MIBs" etc. and change them to "this MIB module", "these MIB modules", and so on. - it seems that it would be a good idea to have the metadata for the four obsolete RFCs indicate that they are obsoleted by the RFCs containing the replacement MIB modules AND this document as well, changing section 7 to something substantive that would remain. Mike Heard On Mon, 1 Jun 2015, Bill Fenner wrote: > Hi, > > I've just published > https://tools.ietf.org/html/draft-fenner-ipv6-mibs-obsolete-00 , whose goal > is twofold: > > 1) Explicitly change the status of RFC2452 (IPV6-TCP-MIB), RFC2454 > (IPV6-UDP-MIB), RFC2465 (IPV6-TC, IPV6-MIB), and RFC2466 (IPV6-ICMP-MIB) to > Historic. They are currently Proposed Standard, Obsoleted by the newer > (2005) version-independent IP-MIB, UDP-MIB, TCP-MIB and IP-FORWARD-MIB. > (Oddly, RFC2454 is already Historic, but the others remain PS.) > > 2) Publish the MIBs with the "STATUS" field changed from "current" to > "obsolete". Many MIB repositories are simply populated from the newest RFC > containing a given MIB, so since the original RFCs with their "STATUS > current" remain in place, there is no signal when simply looking at the > MIBs that the IETF has moved in a different direction. > > The end goal is to make it more clear that the IP version independent MIBs > are the ones to use. > > Since the ipv6 wg published the IP version independent MIBs originally, I > thought that 6man would be an appropriate home for this update. > > Your thoughts and comments would be appreciated. > > Bill > > (While composing this email, I realized that I accidentally omitted RFC2466 > from the list in the document; I'll fix this before the next revision.) > _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
