{'fraction_non_alphanumeric': 0.030745580322828592, 'fraction_numerical': 0.0023059185242121443, 'mean_word_length': 3.913207547169811, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A distributed LAG mechanism for TRILL enabled fabrics

It is desirable to connect external switches or servers to a TRILL campus in a LAG for high availability and for better use of link bandwidth. This paper presents a way, called t-LAG, to allow this to occur via the use of extra RB (called the virtual-RB) for each t-LAG. It makes sense to put multiple t-LAGs together onto a pair of switches, called the t-LAG cluster. All the t-LAGs in a t-LAG cluster can share the same virtual-RB. The use of this virtual-RB for t-LAGs can resolve the load distribution issue for UC traffic. For MC/BC/DLF traffic, a primary link will need to be designated for each t-LAG in order to not receive more than one copy of packets destined to a t-LAG. 
 
It is recommended to separate the traffic forwarding in a t-LAG cluster into two domains: the TRILL routing domain and the regular L2 switching domain. The traffic handling in these two domains should not be mixed together; i.e., the data switching in the regular L2 domain in a cluster should be handled within the virtual-RB itself. The traffic should not go through the TRILL campus at all if not necessary. The t-LAG ISL for a t-LAG cluster should be used for packet redirection in the regular L2 switching domain when there is a link failure on any t-LAG.