%% You should probably cite draft-ietf-dnsop-dnssec-bootstrapping instead of this I-D. @techreport{thomassen-dnsop-dnssec-bootstrapping-01, number = {draft-thomassen-dnsop-dnssec-bootstrapping-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-thomassen-dnsop-dnssec-bootstrapping/01/}, author = {Peter Thomassen and Nils Wisiol}, title = {{Automatic Commissioning of New Signers: Solving the DNSSEC Bootstrapping Problem using Authenticated Signals from the Zone's Operator}}, pagetotal = 17, year = , month = , day = , abstract = {This document describes an authenticated in-band method for automatic signaling of a Child DNS zone's delegation signer information from the zone's DNS operator(s). The zone's registrar or registry may subsequently use this signal for automatic DS record provisioning in the parent zone. The protocol is particularly useful in case of managed DNS providers hosting registrant's domains, where DS provisioning has so far been cumbersome. The signaling channel is not specific to the DS bootstrapping use case, but equally suitable for announcing other zone-specific information from the DNS Operator in an authenticated fashion. Further potential applications thus include, for example, key exchange between parties in an {[}RFC8901{]} multisigner setup. {[} Ed note: Text inside square brackets ({[}{]}) is additional background information, answers to frequently asked questions, general musings, etc. They will be removed before publication. This document is being collaborated on at https://github.com/desec-io/draft-thomassen- dnsop-dnssec-bootstrapping/ (https://github.com/desec-io/draft- thomassen-dnsop-dnssec-bootstrapping/). The most recent version of the document, open issues, etc. should all be available there. The authors gratefully accept pull requests. {]}}, }