RFC 6527: Definitions of Managed Objects for Virtual Router Redundancy Protocol Version 3 (VRRPv3)
In plain English — editorial summary, not part of the RFC
This specification defines a portion of the Management Information Base (MIB) for use with network management based on the Simple Network Management Protocol (SNMP). In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol Version 3 (VRRPv3) for both IPv4 and IPv6 as defined in RFC 5798. This memo obsoletes RFC 2787. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6527
- Published
- March 2012
- Authors
- K. Tata
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
- Obsoletes:
- RFC 2787
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 6240Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) MIB Using SMIv2Current
May 2011
- RFC 7184Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2Current
April 2014
- RFC 5813Forwarding and Control Element Separation (ForCES) MIBCurrent
March 2010
- RFC 7330Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) ManagementCurrent
August 2014
- RFC 7331Bidirectional Forwarding Detection (BFD) Management Information BaseCurrent
August 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?