W.r.t. > > > >> RFC1269 Definitions of Managed Objects for the Border Gateway > >> Protocol: Version 3 > > > > > > Why would this be cruft? The BGP4 MIB was just recently approved... > > Good thing too. Take a good look at 1269. I don't think it would pass > a MIB compiler test today. If you approved the BGP4-MIB, > ought not that have obsoleted this guy? > > The new doc (in IESG evaluation status) is draft-ietf-idr-bgp4-mib-15.txt And its abstract says it all: Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower. The origin of this memo is from RFC 1269 "Definitions of Managed Objects for the Border Gateway Protocol (Version 3)", which was updated to support BGP-4 in RFC 1657. This memo fixes errors introduced when the MIB module was converted to use the SMIv2 language. This memo also updates references to the current SNMP framework documents. This memo is intended to document deployed implementations of this MIB module in a historical context, provide clarifications of some items and also note errors where the MIB module fails to fully represent the BGP protocol. Work is currently in progress to replace this MIB module with a new one representing the current state of the BGP protocol and its extensions. This document obsoletes RFC 1269 and RFC 1657. Distribution of this memo is unlimited. Please forward comments to idr@xxxxxxxxx So 1269 will soon be made OBSOLETED I will look at other MIB related documents next week. Bert _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf