Definitions of Managed Objects for BGP-4
RFC 4273, “Definitions of Managed Objects for BGP-4”, is a Proposed Standard document published in January 2006 by J. Haas, S. Hares. It obsoletes RFC 1269, RFC 1657. The canonical text is published by the RFC Editor.
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, to provide clarifications of some items, and to 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. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4273 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4272 BGP Security Vulnerabilities Analysis
- RFC 4274 BGP-4 Protocol Analysis
- RFC 4271 A Border Gateway Protocol 4
- RFC 4275 BGP-4 MIB Implementation Survey
- RFC 4276 BGP-4 Implementation Report
- RFC 4277 Experience with the BGP-4 Protocol
- RFC 4278 Standards Maturity Variance Regarding the TCP MD5 Signature Option and the BGP-4 Specification
- RFC 4263 Media Subtype Registration for Media Type text/troff