TRILL Routing Requirements in Support of RBridges
draft-ietf-trill-routing-reqs-02

Document Type Expired Internet-Draft (trill WG)
Last updated 2015-10-14 (latest revision 2007-02-01)
Replaces draft-gray-trill-routing-reqs
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Mark Townsley
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-trill-routing-reqs-02.txt

Abstract

RBridges provide the ability to have an entire domain, with multiple physical links, look to IP like a single subnet. The design allows for zero configuration of switches within an RBridge domain, optimal pair-wise routing, safe forwarding even during periods of temporary loops, and potential additional advantages as well. The design also supports VLANs, allows forwarding tables to be based on destinations within the RBridge domain (rather than station destinations, allowing internal forwarding tables to be smaller than in conventional bridge systems). The intent is to re-uses one or more existing routing protocols to accomplish these goals. This document lays out the background and specific requirements of potential routing protocols to be considered for use in this design. In particular, this document defines what is needed to accomodate this design using IS-IS (or OSPF) as a basis for RBridge protocols.

Authors

Eric Gray (Eric.Gray@marconi.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)