RFC 4668, "RADIUS Authentication Client MIB for IPv6", August 2006Source of RFC: radext (sec)
Errata ID: 867
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-11-06
Held for Document Update by: Dan Romascanu
misleading RFC title, including abuse of defined terms (for RFCs 4668 - 4671) IMHO, the RFC titles, "RADIUS ... MIB for IPv6" are misleading. In fact, the new RFCs extend the RADIUS MIB modules to cover IPv6, but they are not IPv6 specific! Perhaps, better wording would have been "... for IPv4 and IPv6". Furthermore, a very 'popular' clash of terms shines up here. As specified in RFC 3410 and Part 1 of STD 62, RFC 3411, and re-stated in the boilerplate Section 3, "The Internet-Standard Management Framework", of all four RFCs, there's just one single Management Information Base (MIB) comprised of various "MIB modules". Thus, throughout the titles and the text bodies of the RFCs, the proper term, "RADIUS ... MIB module" should be used instead of the rather sluggish "RADIUS ... MIB".