1 / 7

The RBridge Architecture Approach for TRILL Problem Solving

This iteration aims to clarify terms, streamline interactions, and define solution specifics regarding RBridges and TRILL. It includes terminologies, architectural details, and suggestions for future enhancements.

margaretjackson
Download Presentation

The RBridge Architecture Approach for TRILL Problem Solving

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. TRILL RBridge Architecture The RBridge Approach to Solving the TRILL Problem

  2. Goals in this Iteration • Nail down terms and definitions, • Eliminate complex interactions with other protocols and technologies and make a few choices, • Step forward in defining what must be specified in solution documents (Fill-in Architectural detail), • Seek input/guidance for future changes and • Accept as a working group document

  3. Terms & Definitions • Broken into 2 sections, the first provides specific definitions of existing terminology as they apply to RBridges • 802, Ethernet and LAN terminology • Basic Link-State Routing terminology • The second section defines RBridge specific terminology – especially those that have seemed controversial in dicussion on the list • Relating to RBridge forwarding • Ingress RBridge Tree – replaces the often confusing references to RBridge spanning trees • Forwarding Tunnels • “Campus” related terminology including various logical tables • RBridge roles – Edge (Ingress, Egress), DR, Cooperation

  4. Complicated Interactions • Reduce the amount of specification required for inter-working with other technologies by defining an abstract “co-located functionality” model • Co-located Bridge (potential STP/RSTP BPDU interactions) – allows us to use “block STP” mode only for an abstract RBridge (see section 4.8). • Define as optional/allowed functionality, those capabilities relating to optimization • IRT (Ingress RBridge Tree) Pruning • VLAN Pruning • Multicast Pruning • Flooding Optimization • ARP/ND Optimization

  5. Architectural Detail • Logical Tables • Details on logical content for unicast (CFT) and flooding/multicast/broadcast (CFT-IRT) logical tables for various RBridge roles • Details on: • topology discovery, • progression toward operating status – • Auto-configuration, peer & topology discovery, SPF and IRT computation, learning and forwarding • Forwarding • Population of the CFT and CTT • Uses of the CFT and CFT-IRT • Added content to “Conclusions” section.

  6. Future Changes? • Input on specific sections? • Further abstraction • Co-located VLAN (bridging and routing) • Add More details on VLAN interactions with CFT-IRT (section 4.6.2). • Add More details on Optimizations? • Complete section 5 (How this architecture addresses the problem statement. • Standard or Informational?

  7. Finally • Accept as a working group document?

More Related