RFC 5187, "OSPFv3 Graceful Restart", June 2008Source of RFC: ospf (rtg)
Errata ID: 1453
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-06-15
Held for Document Update by: Stewart Bryant
Date Held: 2012-10-26
Section 3.2 / 7.2 says:
a) The last paragraph of Section 3.2 (on top of page 5) says: | Many implementations currently use the interface's MIB-II IfIndex | [MIB-INTF] for Interface ID. The persistence of Interface ID across | reboots is described in section 3.1.5 of [MIB-PERS]. b) Section 7.2 (on page 6) says: | [MIB-INTF] McCloghrie, K. and M. Rose, "Management Information | Base for network management of TCP/IP-based internets: | MIB-II", STD 17, RFC 1213, March 1991. | [MIB-PERS] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
It should say:
a) | Many implementations currently use the interface's SNMP MIB IfIndex | [MIB-INTF] for Interface ID. The persistence of Interface ID across reboots is described in section 3.1.5 of [MIB-INTF]. b) | [MIB-INTF] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
Unfortunately, the IETF maintains the questionable 'luxury' of
two sets of Network Management Standards, where the second one
actually has obsoleted the former one.
Although all parts of RFC 1213 have either been obsoleted by
newer standards or deliberately been deprecated together with
the legacy protocols they were intended to support, STD 17
(RFC 1213) [as well as STD 16] have been resurrected in
rfcxx00.txt, including its latest RFC edition, RFC 5000.
In particular (omitting all intermediate RFCs now obsoleted as well),
- the basic part of RFC 1213 ("host group") has been replaced
by the SNMP MIB module in part 8 of STD 62, RFC 3418,
- the "interface group" has been obsoleted by RFC 2863,
- the "IP group" has been obsoleted by RFC 4293,
- the IP forwarding table has been obsoleted by RFC 4292,
- the "TCP group" has been obsoleted by RFC 4022,
- the "UDP group" has been obsoleted by RFC 4113.
References to "MIB-II" and RFC 1213 are the source of frequent
Therefore, new RFCs, in particular STANDARDS TRACK RFCs, should
not quote RFC 1213 any more.
It is observed current policy of the MIB Doctors to have all new
IETF documents defining MIB modules refer to the newer standards;
but RFC 5187, not defining a MIB module, apparently has not
undergone MIB Doctor review. Nevertheless, the confusing
reference to "MIB-II" and a document outdated since many years
should have been avoided here as well.