1 / 14

RBridge Architecture

This draft outlines significant changes made to the RBridge Architecture, including the removal of "Standards" language and the expansion of the introduction to clarify definitions. It addresses the forwarding strategy for RBridges, the required data, and necessary procedures while eliminating most discussions on "options considered." Key definitions have been clarified to enhance understanding, particularly around Designated RBridge roles, multicast optimization, and CRED (Cooperating RBridges and Encapsulation Tunnels). Further editing rounds and WG acceptance are anticipated.

zudora
Download Presentation

RBridge Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RBridge Architecture draft-gray-trill-rbridge-arch-01.txt

  2. Changes to the draft • Remove “Standards” (2119) language • Expanded the introduction • Clarified definitions • Removed most “options considered” discussion • Align text with protocol specification • Clarified use examples and roles • In particular, Designated RBridge roles • Removed redundant text, corrected minor wording issues • Included more text on the need for multicast optimization support

  3. Introduction • Includes text on: • RBridge forwarding strategy • Data required to support this strategy • Procedures required to derive this data

  4. Options Considered • Removed text on options considered • relative to RBridge forwarding at each hop • relative to STP “participation” roles

  5. Definitions • Removed ambiguous use of “campus” • Replaced with acronym “CRED” • “Cooperating RBridges and Encapsulation Tunnels (Domain)” • Fixed definitions for • Designated RBridge • SPF • Other minor clarifications/corrections

  6. Host Host Host Host Host Rtr Host Hub Host Host Host Host Host Host B Host B B B Host Host Host Host RB B Host RB B Rtr B B Hub Host B Host Hub B Host Host Host Host Host Host B B B Host Host Host Host Host Host B Host RB RB Host B B Host Host B Host Host B Host B B Host Host Host Host Host Host Host Host Network Host Host Host Rtr Host

  7. Host Host Host Host Host Rtr Host Hub Host Host Host Host Host Host B Host B B B Host Host Host Host RB B Host RB B Rtr B B Hub Host B Host Hub B Host Host Host Host Host Host B B B Host Host Host Host Host Host B Host RB RB Host B B Host Host B Host Host B Host B B Host Host Host Host Host Tunnel Overlay Host Host Host Host Host Host Rtr Host

  8. Rtr Hub B B B B RB B RB B Rtr B B Hub B Hub B B B B B RB RB B B B B B B Campus? Rtr

  9. Rtr Hub B B B B RB B RB B Rtr B B Hub B Hub B B B B B RB RB B B B B B B Campus? Rtr

  10. B B B RB RB B Hub B Hub B B B B B RB RB B B B Campus?

  11. B B B RB RB B Hub B Hub B B B B B RB RB B CRED B B

  12. Roles • Clarified the roles of Designated RBridge • In forwarding on and off of the CRED • In advertising MAC reachability • Clarified role/usage of forwarding table for the Ingress RBridge Tree (CFT-IRT

  13. Still to be discussed • Inclusion of “pseudo-node” use • Too detailed for architecture? • Too protocol specific for architecture? • Remove distinctions of Hubs, Switches and Bridges in section 4 discussion and figures? • More inclusive Security statement • More the “job” of normative document (such as protocol specification? • Contrary to goals of the WG?

  14. Next Steps • More comments? • At least a few more rounds of editing… • Accept as a WG document?

More Related