Routing Bridges (RBridges): Operations, Administration, and Maintenance (OAM) Support
draft-ietf-trill-rbridge-oam-02
| Document | Type |
Expired Internet-Draft
(trill WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | David Mich Bond , Vishwas Manral | ||
| Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
| Replaces | draft-bond-trill-rbridge-oam | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Routing Bridges (RBridges) implement the TRansparent Interconnection of Lots of Links (TRILL) protocol which provide a transparent least- cost frame routing in multi-hop networks with arbitrary topologies, while also inherently providing loop mitigation. As RBridges are deployed in real-world situations, operators will need tools for debugging problems that arise. This document specifies a set of RBridge features for operations, administration, and maintenance (OAM) purposes in RBridge campuses. The features specified in this document include tools for traceroute, ping, and error reporting.
Authors
David Mich Bond
Vishwas Manral
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)