RFC 6850: Definitions of Managed Objects for Routing Bridges (RBridges)
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it defines objects for managing a Routing Bridge (RBridge), also known as a TRILL Switch, based on the IETF TRILL (Transparent Interconnection of Lots of Links) protocol. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6850
- Published
- January 2013
- Authors
- A. Rijhsinghani; K. Zebrose
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 59
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6845OSPF Hybrid Broadcast and Point-to-Multipoint Interface TypeCurrent
January 2013
- RFC 6860Hiding Transit-Only Networks in OSPFCurrent
January 2013
- RFC 6862Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and RequirementsCurrent
March 2013
- RFC 6863Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
March 2013
- RFC 6836Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)Current
January 2013
- RFC 6835The Locator/ID Separation Protocol Internet Groper (LIG)Current
January 2013
- RFC 6834Locator/ID Separation Protocol (LISP) Map-VersioningObsoleted
January 2013
- RFC 6833Locator/ID Separation Protocol (LISP) Map-Server InterfaceObsoleted
January 2013
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?