1 / 10

Future TRILL Work

Future TRILL Work. Donald Eastlake 3 rd +1-508-333-2270 d3e3e3@gmail.com. Future TRILL Work. Potential Future TRILL Work/Documents: Management (MIB) 802.1 Features Enhanced Transmission Selection (802.1Qaz) Priority-Based Flow Control (802.1Qbb)

MikeCarlo
Télécharger la présentation

Future TRILL Work

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. Future TRILL Work Donald Eastlake 3rd +1-508-333-2270 d3e3e3@gmail.com Future TRILL Work

  2. Future TRILL Work • Potential Future TRILL Work/Documents: • Management (MIB) • 802.1 Features • Enhanced Transmission Selection (802.1Qaz) • Priority-Based Flow Control (802.1Qbb) • Customer versus Provider RBridges (802.1ad) • Connectivity Fault Management (802.1ag) • Congestion Notification (802.1Qau) • ARP/ND/IP/… Optimization Future TRILL Work

  3. Important & Urgent Important & Distant Unimportant & Urgent Unimportant & Distant Questions on These Work Items • Is the item important/high-value? • Is the item urgent/time-sensitive? • Who would like to work on it? Future TRILL Work

  4. Management (MIB) • Possible components: • Bridge MIB stuff (from RFC 4188?) • IS-IS MIB stuff (from RFC 4444?) • IP Multicast stuff (from RFC 5132?) • RBridge stuff • Nickname configuration • Distribution tree priority, etc. • VLAN, Multicast router, etc., connectivity • … Future TRILL Work

  5. Enhanced Transmission Selection (802.1Qaz) • An amendment to 802.1Q that permits separately specifying limits for different traffic class queues, distinguished by priority, to enforce bandwidth quotas and the like. • Currently at Draft 0.0 in IEEE 802.1. • I think this is now automatically supported by RBridges with the default inclusion of 802.1Q below the EISS layer. Future TRILL Work

  6. Priority-Based Flow Control (802.1Qbb) • An amendment to 802.1Q that is more or less to provide the 802.3 PAUSE facility separately for different traffic classes. • Currently at Draft 0.2 in IEEE 802.1. • I think this is now automatically supported by RBridges with the default inclusion of 802.1Q below the EISS layer. Future TRILL Work

  7. Customer/Provider RBridges • IEEE 802.1ad-2005, “Provider Bridges”, is a completed amendment to 802.1Q-2005. • (not to be confused with the completed 802.1ah-2008 “Provider Backbone Bridges” amendment) • Provider Bridges use outer S-Tags and are transparent to some bridging multicast addresses. • “Provider Edge Bridges” talk C-Tags (formerly called Q-Tags) on customer ports and S-Tags on provider ports. • It would be possible to specify how to configure RBridges as Provider or Provider Edge Bridges and/or incrementally replaced such bridges with RBridges. Future TRILL Work

  8. Connectivity Fault Management (802.1ag) • 802.1ag-2007 is a completed amendment to 802.1Q-2005 proving: • “This amendment specifies protocols, procedures, and managed objects to support connectivity fault management. These allow discovery and verification of the path, through bridges and LANs, taken for frames addressed to and from specified network users. Connectivity faults can be detected and isolated to an individual bridge or LAN.” • Do RBridges support 802.1ag? Do we want to provide similar facilities in a different way. Future TRILL Work

  9. Congestion Notification (802.1Qau) • Layer 2 method to rate limit flows causing congestion. • Has been progressing slowly in 802.1 but is now at Draft D1.3. • Some changes to RBridges beyond those required in 802.1 Bridges would be required to support 802.1Qau. • For example, a congestion control message in response to a TRILL data frame should get back to the true origin station, not just the ingress RBridge. Future TRILL Work

  10. IP Related Optimizations • ARP/ND optimization was included in the paper cited in our Charter and in early protocol drafts but was removed from base specification by WG consensus, to be placed in a separate document. • Included learning IP addresses and sometimes responding to ARP/ND. Future TRILL Work

More Related