Technical Summary
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-use 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 accommodate this
design using IS-IS (or OSPF) as a basis for RBridge protocols.
Working Group Summary
This document has working group consensus, and extensions to IS-IS are
underway within the IS-IS WG.
Note to RFC Editor
(Insert note to RFC Editor here)
IESG Note
(Insert IESG Note here)
IANA Note
(Insert IANA Note here)