{'fraction_non_alphanumeric': 0.019455252918287938, 'fraction_numerical': 0.0009727626459143969, 'mean_word_length': 5.198795180722891, '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}}
Towards RSVP Lite: light-weight RSVP for generic signaling

RSVP is a reservation setup protocol designed specifically to support QoS signaling in the Internet. However, RSVP end-to-end signaled QoS for the Internet has not become a reality. Moreover, there are many other applications demanding different signaling services. The paper analyses the features of RSVP version 1 we believe to be essential, and its complexity due to QoS-oriented design and multicast support as an indispensable component in a signaling protocol, deriving the design principles to be covered in a more generic signaling protocol. Based on this analysis, we present a light-weight version of RSVP, RSVP Lite, which clearly separates the signaled data from signaling messages and removes the multicast capability from the mandatory components of RSVP. RSVP Lite is intended to be applicable to a wide range of networking environments, while providing the flexibility to serve for generic signaling purposes and incremental deployment in the Internet.