Future TRILL Work 2

1. Future TRILL Work 2 Donald Eastlake 3rd 155 Beaver Street Milford, MA 01757 USA d3e3e3@gmail.com Future TRILL Work

2. Future TRILL Work 2 • Future TRILL Work corresponding to specific points in the New Charter: • ARP/ND Optimization and ESADI • Multi-Level RBridge Routing • Data Center Bridging • Fine Grained Labeling Future TRILL Work

3. ARP/ND Optimization and ESADI • ARP/ND Optimization has been part of the idea for RBridges and TRILL since the initial paper by Radia Perlman in 2004. • ESADI (End Station Address Distribution Information) is an optional highly reliable VLAN scoped method for sharing data between RBridges, such as connected end station MAC addresses. • By using ESADI to distribute Layer 2 <-> Layer 3 address pairs, the resulting data can be used to respond locally to ARP/ND queries reducing multi-destination frame traffic. Future TRILL Work

4. ARP/ND Optimization and ESADI • If all the RBridges in a VLAN within an RBridge campus have ESADI enabled, gratuitous ARPs in that VLAN can be terminated at the ingress RBridge, the information they are providing can be distributed via ESADI and, where appropriate, regenerated at what would have been egress RBridges. • For VLANs with many end stations, gratuitous ARP should not update fast path MAC tables except for addresses actually in use. Future TRILL Work

5. Future TRILL Work 2 • Future TRILL Work corresponding to specific points in the New Charter: • ARP/ND Optimization and ESADI • Multi-Level RBridge Routing • Data Center Bridging • Fine Grained Labeling Future TRILL Work

6. Future TRILL Work 2 • Future TRILL Work corresponding to specific points in the New Charter: • ARP/ND Optimization and ESADI • Multi-Level RBridge Routing • Data Center Bridging • Fine Grained Labeling Future TRILL Work

7. Data Center Bridging • draft-eastlake-trill-rbridge-dcb-00.txt • Three standards being specified in 802.1 to allocate bandwidth and eliminate frame loss due to queue overflow. • 802.1Qbb – per priority PAUSE • 802.3bd – new PAUSE frame format • 802.1Qaz – allocation of link bandwidth to traffic classes • 802.1Qau – Congestion Notification. Facilities to limit flows at their originating end station Future TRILL Work

8. Data Center Bridging • The first two, 802.1Qbb and 802.1Qaz, can be implemented entirely within the ports of an RBridge. No TRILL processing changes but support should be announced in the LSP. • 802.1Qau requires a minor extension to TRILL, which has been discussed in the TRILL WG since at least 2007, and support should be announce in the LSP. Future TRILL Work

9. Data Center Bridging • TRILL extension required because of the case where a TRILL-ignorant bridge between RBridges generates a Congestion Notification Message. • The previous-hop RBRidge must adjust the CNM so it is returned to the true origin in the campus. RBridge Bridge(s) RBridge Origin CNM Adjusted CNM Future TRILL Work

10. Future TRILL Work 2 • Future TRILL Work corresponding to specific points in the New Charter: • ARP/ND Optimization and ESADI • Multi-Level RBridge Routing • Data Center Bridging • Fine Grained Labeling Future TRILL Work

11. Fine Grained Labeling • Requirements, in approximate order by importance with the most important first: • Many cloud computing applications and data centers require more than 4K labels of configurable isolation. • There should be provision for frame priority within the cloud / data center while preserving the original priority. • Due to the difficulty of all nodes optimally routing multi-destination frames by the many values of a fine grained label, some easier to route aggregate label should be available. Future TRILL Work

12. Fine Grained Labeling • (Requirements, continued…) • RBridges ignorant of file grained labeling should usefully and safely route and handle frames that have fine grained labeling. • It would be desirable to use existing standardized field types rather than to create a new flavor of label. Future TRILL Work

13. Solution • Use the 24-bit IEEE 802.1 Service Instance identifier as the fine grained label and • Use a VLAN ID as the aggregated routing label. • The can be done in at least two ways: • Insert an 802.1ah tag in the encapsulated frame; or • Insert the 802.1ah tag body camouflaged by a TRILL Header Option. Future TRILL Work

14. Solution A Outer MAC Addrs 12 TRILL Ethertype & Header 8 Inner MAC Addrs 12 Inner Cust. VLAN 4 Payload Payload Outer MAC Addrs 12 TRILL Ethertype & Header 8 Inner MAC Addrs 12 Data Center VLAN 4 802.1ah Ethertype . 2 Priority Service ID 4 Inner MAC Addrs 12 Cust. VLAN . 4 802.1ah body Future TRILL Work

15. Solution B Outer MAC Addrs 12 TRILL Ethertype & Header 8 Inner MAC Addrs 12 Inner Cust. VLAN 4 Payload Payload Outer MAC Addrs 12 TRILL Ethertype & Header 8 Bit Opt. Area 4 TLV & Cust. VLAN 2 + 2 Priority Service ID 4 Inner MAC Addrs 12 Data Center VLAN 4 802.1ah body Options Size = 3 Future TRILL Work

16. Solution B • From view of a fine grained labels ignorant RBridge • From the view of a fine grained aware RBridge Payload Payload options Outer MAC Addrs 12 TRILL Ethertype & Header 8 Bit Opt. Area 4 TLV & Cust. VLAN 2 + 2 Priority Service ID 4 Inner MAC Addrs 12 Data Center VLAN 4 802.1ah Body Outer MAC Addrs 12 TRILL Ethertype & Header 8 Bit Opt. Area 4 TLV & Cust. VLAN 2 + 2 Priority Service ID 4 Inner MAC Addrs 12 Data Center VLAN 4 Future TRILL Work

17. A versus B Comparison • Solution A • Adds 20 bytes • Fine grained label ignorant RBridges cannot parse the 802.1ah tag or anything past it. • Solution B • Adds 12 bytes • Fine grained label ignorant RBridges automatically skip the option and can properly parse the rest of the frame. Future TRILL Work

18. More Details on B • Solution B • Must be the last TLV option for parsing by fine grained labeling ignorant RBridge to work. • But, to be sure that the frame is not decapsulated and delivered outside its fine grained label, the option needs to be handled as critical. Future TRILL Work