MIB II or RFC1213 and its successors

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

The RFC-Editor wants to know which documents they should
tag as related and/or obsoleting or updating which.

I think it was all triggered by a question from Dave Harrington.
Dave has already commented and cobtributed to the below.

Anyway, this is what I have documented sofar.
Any comments or suggestions for change?

I think it would be good if these relationships are
expressed in the RFC indexes. 

> 
> First, RFC1213 is a STD level.
> 
> RFC2011,2012 and 2013 are at PS level. 
> RFC2863 is at DS level
> RC3418 is at STD level
> 
> RFC2011 updates the ip group in RFC1213,
>         so it updates the objects under { mib-2 4 }
>         it also updates the icmp group in RFC1213
>         so it updates the objects under { mib-2 5 }
> RFC2012 updates the TCP group in RFC1213
>         so it updates the objects under { mib-2 6 }
> RFC2013 updates the UDP gropup in RFC1213
>         so it updates the objects under { mib-2 7 }
> RFC2863 updates the interfaces group in RFC1213. 
>         so it updates the objects under { mib-2 2 }
> RFC3418 updates the system group in RFC1213
>         so it updates the objects under { mib-2 1 }
>         it also updates the SNMP group in RFC1213
>         so it updates the objects under { mib-2 11 }
> 
> Further, RFC1213 has these groups
> 
> - at group which is { mib-2 3 }
>   not sure if it is still used anywhere, but in any event
>   it is already "deprecated".
> - egp group which is { mib-2 8 }
>   I also doubt that this is still used anywhere
> - cmot group, which is { mib-2 9 }
>   it was already historical at RFC1213 publication time
> - transmission group, which is { mib-2 10 }
>   This is just an anchor in RFC1213
> 
> Of course, mib-2 itself was defined in RFC1213 as the anchor/root
> for all standards track MIB modules. The various groups under
> mib-2 (as you can see above) were/are defined in RFC1213.
> 
> But RFC2578 has taken over some of the role of defining the mib-2 
> root and some of the groups (still in use).
> 
> RFC2578 sort of also updates RFC1213 in that
>         it defines the root mib-2
>         it defines the transmission group as { mib-2 10 }
> 
> In summary:
> 
> - quite a few docs contains updates or pieces of replacements for
>   RFC1213. I am not even 100% sure I have listed all of it above,
>   I think I am close, and if you want I can check some more.
> - Although RFC1213 is at full STD, most of the things that are
>   currently in use and implemented, are those as defined in the
>   newwer MIB modules, even though those are at PS or DS level.
> - At some point we may want to write an RFC that deprecates or
>   obsoletes those pieces from RFC1213 that we believe are no longer
>   used.
> - At some time we may want to make RFC1213 HISTORIC.
>   Not sure if we should do that before the all the replacements 
>   reach at least DS or maybe even STD level.
> 
> If you want, I can bring this up in the MIB Doctor mailing list to
> see if we have any consensus on what would be wise.
> 
> Hope this helps.
> Bert