{'fraction_non_alphanumeric': 0.0142602495543672, 'fraction_numerical': 0.0, 'mean_word_length': 4.941798941798941, '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}}
Motivations and Terminology for DNSSEC Operations Handover

On the contemporary Internet, the DNS services for many domain names are operated by parties other than the registrant of the domain name. If a registrant wishes to move the domain name’s DNS operations from one party to another, several different actors need to coordinate their actions. While this has always been true, the addition of DNSSEC signatures and validation to the DNS means that these operations become more delicate; while DNS without DNSSEC is mostly tolerant of data inconsistencies, DNSSEC is designed to detect such inconsistencies and to stop resolution after detection. In order to create a complete description of a smooth operational transfer without the domain having to go through an insecure phase, it is necessary to develop a taxonomy of all the actors in such a transfer, to understand when and how their roles might be combined and what that might mean, and to understand the effects of any actor’s failing to act. We provide this description, and go on to suggest the next steps for a complete procedure for DNS operation transfer.