{'fraction_non_alphanumeric': 0.023783783783783784, 'fraction_numerical': 0.0, 'mean_word_length': 5.299319727891157, '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}}
Fault handling mechanisms in the RETHER protocol

RETHER is a software-driven token-passing protocol designed to provide bandwidth guarantee for real-time multimedia applications over off-the-shelf Ethernet hardware. To our knowledge, it is the first all-software and fully-implemented real-time protocol on top of commodity Ethernet hardware. Because token passing is used to regulate network accesses, node crashes and/or packer corruption may lead to token loss, thus potentially shutting down the network completely. This paper describes the fault handling mechanisms built into RETHER to address this problem in both a single-segment and multi-segment Ethernet environment. The emphasis of the paper is on the uniqueness of the target application context and the rationale of chosen solutions. We present the performance tradeoffs of the fault detection/recovery schemes, the implementation experiences of the prototype.